Systems that remove the work, not just software that records it.

02 · How the work runs

Four steps that turn a bottleneck into a system your team runs.

Each step exists to de-risk the next: the call names the bottleneck, the audit measures and prices it, the build removes it, and maintenance keeps it removed while the business changes. In an ordinary business the result looks like this: information captured once, jobs that stop queueing for one person, and reporting nobody has to rebuild by hand.

1. Step one

   Discovery call

   Free30 minutes

   Tell us where the business is getting stuck.

   We ask about the work rather than the budget, because the budget is not what decides whether this is worth doing. You describe the process that keeps going wrong and we ask questions about it.

   You leave withA straight answer on whether there is anything here worth pursuing, and what we would look at first.

2. Step two

   Constraint audit

   £2,00014 days

   We go and measure it, inside the actual work.

   Fourteen days and three sixty minute calls with Sam or Adam directly, not an account manager. The calls are the smallest part. Between them we are inside the work: tracing every hand-off, counting where information gets retyped, timing how long a job actually waits against how long anyone touches it, reading the exceptions your team has been absorbing without telling anyone, and pulling the real numbers out of the tools you already run on.

   You leave withA written constraint map of the process, the measurements underneath it, a recommendation, and a fixed price for the build.

3. Step three

   Proposal and build

   £5,000 to £20,000One off, scoped by the audit

   The price is agreed before anyone writes code.

   One system at the bottom of the band, and at the top the five processes costing you the most time or money, built and connected together. We design, write, integrate, test and deploy against your real data, your real rules and the exceptions your team already works around. The audit set the scope, so there is no discovery happening on your invoice.

   You leave withThe first systems in ordinary daily use, and a team that can operate them without us in the room.

4. Step four

   Maintenance

   £2,000 to £5,000Per month, reviewed yearly

   The systems keep earning after we stop building them.

   Owned, monitored and improved while the business changes around it. That includes changes, not just uptime: rules move, people join, volumes shift, and we move the systems with them. The contract is reviewed every year against what the systems are actually carrying, so it goes up, down or ends on evidence rather than by default.

   You leave withSystems that still fit the business in a year, the people who built them still answering the phone, and a yearly review that has to justify itself.