❯ We run a property firm with forty desks. Every viewing request still lands on me, because which ones are worth a slot is a judgement nobody else here makes the same way.
- firstThe call itself, replayed against requests you already ruled on, so every disagreement is visible before a tenant sees one.
- hardGetting it past the bar you write before it ever decides in front of a tenant.
- refusedWiring it into your CRM. It decides; the plumbing is a separate casting at a separate sum.
The decision only you can make, running without you.
You know how the work is done. Writing it down is the part that defeats you — and that is exactly why the thing you want does not exist yet.
This is for a founder who holds the what and not the how: you have the vision, the money and the domain knowledge, and no engineering function to hand it to. A company of three to twenty people, funded by one of its own founders. Not a procurement department: at that size the person signing is the person whose money it is.
You are building this because you know something about your field that almost nobody else does. If that were not true you would be buying something that already exists instead of building it. It does not exist. So there is nothing to point at and say: like that, but for us.
Which is why it is so hard to write down. Every attempt to specify it turns into a description of how you do it by hand today — and how you do it by hand is not the thing you want. It is the thing you want to stop doing.
Half-baked is the industry standard, and that is what the name is about. Most of what a founder pays an outside firm for arrives as a picture of the thing rather than a thing that runs. This is the opposite trade: it comes out finished.
No spec for you to write. No ramp plan. Nobody for you to manage.
A working system, built and run end to end up to the day it clears your bar. Architecture, build, infrastructure and the running of it while it is being built — and nobody for you to manage while it happens.
- 01Architecture, build, infrastructure and the running of it — end to end, to the bar-clear
- 02Written progress in your inbox before every call
- 03One call a week while it is built, and a recorded demo where there is something to show
- 04A board you can open at any hour, without asking
- 05Nothing is owed until it has cleared your bar, under Term 2 — Cancellation.
You cannot specify it. You can always correct it.
Every week the build runs, you see the current version make the call on your own cases, and you say where it is wrong and why. Written progress before the call. One call. A recorded demo where there is something to show. The proposed scope for the coming week, which you accept, cut or change. And a board you can open at any hour. It is how the build is carried, and it runs until the system clears your bar.
Specimen — a constructed example, not a record of real work. No client work is published on this site.
That correction is the specification you were never able to write. Nobody asks you for a requirements document, because the document was never the problem. You look at a decision the system made and say: not that one, and here is why. Do that enough times and the rule you could never state is running in production.
The build is carried by a fleet of AI agents this company builds and operates. It is said here rather than discovered later, and Term 6 — What You Send Us says exactly what that means for your code and your data. It is also the reason what is sold below is one fixed sum for one finished thing. The third lane is what is never delegated to one: what gets built, what gets refused, and who answers for it.
The person who makes the promise is the person who keeps it. I scope your build on the first call, I am accountable for the roadmap, and I am on your weekly call. That is Term 1 — Provenance, and it holds whoever is paying.
Four systems that run. No logos, no invented numbers.
These firms each run different software and each describe their process as unique. Underneath, one call keeps repeating: what happens next on this lead, and who touches it. That call now runs inside whichever system the firm already had.
KIMA — German real estateAn AI meeting scheduler that turns an executive assistant’s tacit judgement into a transparent constraint engine.
Ush — schedulingA US personal-injury legal-tech platform got a complete AI document platform across eleven document categories. An enterprise HR-analytics platform had its data processing lag eliminated.
Two more, anonymisedUsh is the one worth reading twice. Those stakeholders arrived holding UI prototypes they had already paid someone else to draw, and the shipped product replaced them — because the money had gone on a picture of the thing rather than on a thing that runs. That is the money this replaces: not a salary, and not a cheaper developer. The spend that bought a picture instead of a system.
One decision, cast and running. Not a project, and not a month of anyone’s time.
You name the call that still has to go through you. It comes back as a system that makes it, in production, deciding your own cases. The invoice reads: One decision cast: the named call — in production, deciding your own cases. One fixed sum, agreed before the build starts, and Term 5 — Rate is where it is written down.
It decides, it does not integrate. Send the inputs in whatever form you already have them — a file, an export, a paste. Wiring it into your stack is a second casting at a second sum, and it is refused rather than discounted. That boundary is Term 5 — Rate.
You write the bar before the build begins. One condition, in writing, that the system either clears or does not: on your own data, in your environment, doing the actual job. Not a demo. Not a criteria document reviewed in a meeting.
It is built, you watch it clear your bar, and it is invoiced after that. Nothing is owed before.
That is the whole of what one sum buys: the sitting where you name the call, the build and the weekly rhythm that carries it, the system running on your own cases, and the assignment on payment. It is not an open-ended engagement and it is not an operations contract — after the bar is cleared, anything further is its own casting at its own sum.
If you can write down the rule, you do not need this — hire a developer and hand them the spec. This is for the call you have never been able to specify, the one people bring to you because the judgement is yours. That you cannot write it down is the entry ticket, not a problem to fix first.
- ✓You name the call. You never specify it.
- ✓Built against the cases you pick.
- ✓It clears the bar you wrote, or there is no invoice.
- ✓You own it outright on payment.
- ✓One fixed sum, under Term 5 — Rate.
Free · commits you to nothing.
Describe the thing you want to exist.
Not a proposal, not a deck. In whatever shape it is in — including the shape where you cannot explain it. You get a call where I explain it back: how it is buildable, what is hard, what would be built first and what would be refused. It is free and it commits you to nothing.
That arrived. You get a reply from a person.
Business supply only. Not offered to consumers. The terms are on the terms page — provenance, cancellation, your time, continuity, rate, and what you send us.