Adham Altony — the monthly, in full
Keep it running.
$2,500 a month.
This is the whole arrangement on one page: how fast I answer, when I am working, what you own, what I will not do, and how you end it. If anything here is not what you need, that is useful to both of us before a call rather than after one.
- The monthly
- $2,500
- Working week
- Sun–Thu · 09:00–18:00 GMT+3
- P1 response
- 4 business hours
- Notice to end it
- 30 days, any month
For comparison: a contractor with no history on your system costs $2,400–15,200 a month before they’ve read a line of your code. This is the person who already has, for close to the floor of that range.
How fast I answer
Severity is about what it is costing you, not about how loudly it was reported. I set it, you can argue with it, and the clock runs in business hours.
| Level | I respond within | What it means |
|---|---|---|
| P1 | 4 business hours | It is down, or money cannot move.Checkout failing, site unreachable, orders not arriving. |
| P2 | Next business day | It works, but something important does not.A report is wrong, one payment method fails, a page errors. |
| P3 | Two business days | It is annoying, not costly.Copy changes, a slow query, a small layout fault. |
Respond means a human who knows your system has read it and started work, not an auto-reply and not a ticket number. If I miss a response time, that month is credited. Credits are capped at one month’s fee, because a cap is the honest way to say what a guarantee is actually worth.
When I am working
Sunday to Thursday, 09:00–18:00 GMT+3. The Gulf working week, because I live in it rather than covering it. Your 10am is my 10am.
Deploys and anything else that could interrupt trading happen in a window we agree up front, published in advance, outside your busiest hours. Nothing goes out on a Thursday afternoon.
What you own
All of it, from the first day. The GitHub organization, the AWS account, the Stripe account and the domain are opened in your name, on your card. I am an invited admin on your accounts, not the other way round.
Monitoring runs in your workspace, billed to you, so you see what I see. There is no account of mine that your business depends on, and nothing to hand over later because nothing was ever mine to hold.
How you end it
Any month, with thirty days’ notice, without giving a reason. On the last day your credentials are rotated and my access is removed. You do not have to ask, and you do not have to wait for me to be finished with something.
Being able to prove you can end this in thirty days is the only honest reason to start it. A build-and-run arrangement makes one person important to your business, and the answer to that is not a promise about my character. It is that you hold every key and can turn one.
What the month does not cover
Running something is open-ended by nature, and an open-ended promise at a flat fee is how these arrangements go bad, usually for the client, who stops asking because everything feels like an imposition.
- New features.Those are quoted as builds, at the same rate as any other build.
- A redesign, or a second product.Same — that is a build, not a month.
- Round-the-clock cover.The honest version of that needs a second engineer, and I will not sell it until there is one.
- An uptime percentage.I will not promise a number I do not control. Ask me again after three months of running yours, when there is a real record to point at.
- Your hosting, domain, or third-party bills.Those are on your card, in your accounts, so nothing is hostage to me.
If that is the arrangement you want, start here.
Tell me what the system does and what happens the day it is down. If I am not the right person to run it, I will say so.