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 us 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 technical ownership from a company. Not a headcount, not a calendar, and not a quantity of anyone’s time.
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.
Where it starts
A free live call. You describe what you want to build; I explain back — in the conversation, not in a document afterwards — how it is buildable, what is hard, what would be built first and what would be refused.
There is no deliverable attached to it and it commits you to nothing. It is not a discovery process and it is not a qualification call. It is the thing being sold, performed once, for free, so that you can tell whether it is real.
If it is a fit, the build starts and the weekly rhythm below starts with it. The rhythm is how the build is carried and it runs for as long as the build does: it stops when the system clears the bar you wrote and the invoice is settled. It is not an ongoing service sold on the side of one.
The week
The week is the unit of the rhythm while the build runs: the scope, the progress and the reporting.
- 01Written progress, sent in advance. Not a summary at the meeting. Something you read before it, so the meeting can be about decisions.
- 02The weekly call. One. Nothing else is assumed of you — see Term 3 — Your Time.
- 03A recorded demo, where there is something to show. A screen recording you can watch at double speed, or not at all.
- 04The 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 this company owns.
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 we need from you
- Digest cadence: daily or weekly? We 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 us. 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 we work from.
Specimen — a constructed example, not a record of real work. No client work is published on this site.
Done
api. health check returns 200.In progress
mcp. endpoint returns 200.Waiting
What you get, and when
- 01Written answers to questions, in writing, so they are still there in a month.
- 02Feature requests and issue reports, taken on the board like everything else.
- 03The handover pack, on payment and not as a parting favour: your repository, your cloud accounts, your password manager, your wiki. Until the bar is cleared the build runs on our infrastructure; once the invoice is settled the whole of it moves into your own estate, with no lock-in left in it. See Term 4 — Continuity.
How it is built this fast
The build is carried by a fleet of AI agents this company builds and operates, and I answer for every line of it. That is Term 1 — Provenance, and Term 6 — What You Send Us says what it means for your material. 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, before there is an invoice at all.
Accountability does not move. The person who makes the promise is the person who keeps it, regardless of what typed the line — Term 1 — Provenance.
Here is the division of labour behind that. It is a split of the work, not a split of the week.
Done by the fleet
- Domain immersion
- Draft shapes
- The build
- Integration and operations
Never delegated
- What gets built
- What gets refused
- The weekly call
- Who answers for it
Scope, weekly
Next week’s scope is proposed in the weekly progress and agreed by you. You are buying a decision that runs, not a quantity of anyone’s time. If it takes half as long as 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. If it does not clear the bar you wrote, there is no invoice — see Term 2 — Cancellation.
What is bought is the decision, cast and running, and the build that gets it there. Not an open-ended engagement, not on-call, and not a standing operations service: after the bar is cleared and the invoice is settled, anything further is its own casting at its own sum.
The terms are on the terms page — the unit, the sequence, what the invoice reads, and what it includes. The sum is not published: it is one fixed sum, named when the decision is named. What this has produced before is on KIMA and Ush. If you want to start, tell us what you want to build.