How your project goes from idea to production
This page is the process, in the order that matters to you. It starts with what you do not get, because that is the part most likely to make this a bad fit, and you should find that out here rather than partway into an engagement.
What you do not get
No daily calls. There is no morning ritual where progress gets performed to an audience.
No on-call. Nothing pages me at 3am unless that is separately contracted.
No guaranteed response speed. There is a chat channel and it is used. It carries no service level, and nothing on this site pretends otherwise.
Not an employee. You are buying an agreed scope of work from a company, not a seat, a headcount or a person’s calendar.
If you need someone available on demand, you need to hire someone, and you should. Everything below is what you get instead, and why it is a fair trade.
The week
The week is the unit of everything: the scope, the price and the reporting.
- Written progress, sent in advance. Not a summary at the meeting. Something you read before it, so the meeting can be about decisions.
- A 30-minute meeting. One. Your time budget is capped by default and the engagement is designed to fit inside it — see Term 3 — Your Time.
- A recorded demo, where there is something to show. A screen recording you can watch at double speed, or not at all.
- The proposed scope for the coming week, which you accept, cut or change.
Here is what the written progress looks like. This one is constructed, against a system I own.
Specimen — a constructed example, not a record of real work. No client work is published on this site.
Reqbeat — week 3
Shipped
api.subdomain returns 200 on health check; the 502 was an upstream timeout, not a crash.- Demand digest job moved off the request path — it now runs on a queue and retries.
Not shipped, and why
mcp.endpoint still 502s. The fix depends on the queue change above landing first, which it now has, so it moves to next week rather than being worked around.
Decisions I need from you
- Digest cadence: daily or weekly? I have built it daily and made the interval a setting, so this is reversible either way.
Proposed scope, coming week
mcp.endpoint returning 200.- Digest cadence set to whatever you answer above.
- One end-to-end test that fails if any of the three subdomains stops answering.
The board
Every piece of work sits on a board you can open whenever you like, without asking me. Nothing is staged for it and nothing waits for the weekly meeting to appear on it. That is what “you can watch it happen” means concretely: the board is the same board I work from.
Specimen — a constructed example, not a record of real work. No client work is published on this site.
| Item | State |
|---|---|
api. health check returns 200 | Done |
| Demand digest moved to a queue | Done |
mcp. endpoint returns 200 | In progress |
| Digest cadence setting | Blocked, waiting on your answer |
| Subdomain end-to-end test | Next |
What you get, and when
- Written answers to questions, in writing, so they are still there in a month.
- Feature requests and issue reports, taken on the board like everything else.
- The handover pack, from day one and not at the end: your repository, your cloud accounts, your password manager, your wiki. See Term 4 — Continuity.
How it is built this fast
One named engineer accountable, with a fleet of AI agents doing the work under them. That is Term 1 — Provenance, and it is the mechanism behind the speed. Every other shop running this way hides it.
Saying it out loud raises the obvious fear: that this is machine-written code nobody understands, delivered fast and unmaintainable. The answer is not a reassurance, it is the three things above. The board shows what is being built while it is being built. The demo shows it running. The written progress says what did not work and why. If the quality were not there, those three artifacts are where you would see it first, weeks before an invoice.
Accountability does not move. One person answers for every line, regardless of what typed it.
Scope, weekly
Next week’s scope is proposed in the weekly progress and agreed by you. Agreed scope, not agreed hours — you are buying a result, and if it takes half the time it was going to, that is not a discount you are owed, it is why the price is worth paying.
When something changes mid-week, it gets said in writing, immediately, and it changes the proposed scope for the following week rather than quietly consuming it. Work you have already paid for that does not get finished is finished or credited — see Term 2 — Cancellation.
The price and the terms are on the terms page. What this has produced before is on KIMA and Ush.