The Build rung · scoped and priced in writing

Your company’s operating system, on your server

Most businesses do not lack software. They lack state: a written record of what is true, checks that notice when systems disagree, and one place where the joins between platforms are written down. This is a build I install on a server your organisation controls. You own it. It is documented for handover from the first week, and nothing load-bearing lives on my laptop.

What gets installed

• The record. One plain-text file per project, workflow and supplier, each decision written with its date and its evidence. Readable without special tools, exportable in one step, diffable so change is visible. If it matters, it is written down where the next person will find it.
• The checks. The two-numbers check, installed as a script your server runs on a rhythm you set: weekly, monthly, quarterly. It reads counts and writes a line in a log you own. It never changes anything, and the first time two systems drift, you read about it in days rather than fifteen months.
• The join inventory. A register of every place two of your systems touch: shop and email platform, store and ledger, warehouse and site. Who owns each join, when it was last verified, and what breaks when it breaks. Every silent failure I have found lived in a join nobody had written down.
• The agents, where you approve them. Agent capacity for the work that should not need a person every time: reconciling order counts between two systems, drafting the monthly record summary, assembling the review pack a quarterly check reads. The sessions are ones I start, watch and end, on infrastructure you can point at. What leaves your environment is documented provider by provider, with the exit path for each. Read-only by default; nothing changes state or sends without your named approver.
• The runbook and the handover. Exported logs, a runbook any competent engineer can pick up, and credentials that are yours and revocable. From month one, not at the end.

What it is not

• It is not software you rent, and it is not a subscription. There is no platform of mine to be locked into; there is nothing of mine to be locked into at all.
• It is not a dashboard. Dashboards show what each system says; this records whether the systems agree with each other.
• It is not unattended automation. No agent monitors your business on its own or acts while nobody is looking. The always-on agent I am working towards is a specification, not running software, and it is not part of anything I sell.
• No revenue, conversion or deliverability outcome is promised, at any price.

Where it lives

A small server in your organisation’s name, in the region you choose: your account, your credentials, issued and revocable by you. I build on it, hand it over, and from then on it is yours in the plain sense. If the engagement stops, the system, the records and the runbook stay with you. What leaves that server is written down, provider by provider, with the exit path for each, and where an EU region matters to you, it is used.

Where it sits

Nothing about the ladder changes. Work still starts with the £150 analysis, which needs no credentials, and the read-only £750 inspection is usually how a build gets justified. The two-numbers workflow has a named build at a fixed £1,500, described on its own page. The operating system is the Build rung proper: scoped and priced in writing before it starts, from £2,500, and only where the evidence justifies building something. It is also what the Operate rung keeps alive: the quarterly reviews, the checks read, the record kept true, from £750 a month.

From standing start to handover, the usual path is analysis, inspection, build, operate. You can stop after any step, and I would rather you stopped at a step that was worth it than continued into one that was not. And nothing already paid for is done twice: the analysis fee is credited against the fixed build, and a build’s scope begins from what the earlier steps established.

Start with the £150 analysis How the work runs