How we work
Audit. Build. Run. In that order, every time.
This page is for the careful reader — the co-director, the accountant, the person doing the checking before the business commits. It says what happens, in what order, under what rules.
The audit — £1,000
It starts with a full day inside your business. The morning with the owner, on where the hours and the money actually go. A pass through what you run on today — the systems, the spreadsheets, the procedures and SOPs, written and unwritten — and what you pay for each piece of software, because a savings case should be built from your own invoices, not projections. Then most of the day with the people doing the actual work, because they know where the real bottlenecks are and how the week actually runs, including the workarounds nobody wrote down. Mapping the business’s processes with the people who operate them is the most important thing we do.
Two rules govern everything that follows. First: we never automate a broken process. If the process needs fixing first, the audit says so. Second: we never build what a shelf product already does well. If one genuinely fits your business, the audit names it and points you at it — we build for the processes no shelf product fits.
After the day, rapidly, you get a working prototype your team can click through, a one-page scope with the price of the build, and a short ranked note of the next things worth fixing — the roadmap the monthly service works through — with the exact timing agreed when we book. The prototype is the point: anyone can write a report, and a report can’t prove anything. Working software can. The £1,000 is credited in full against the build.
The build — £4,000–£6,000
The prototype becomes the real system: live on your real data, connected to what it needs to be connected to, your people trained on it. The price is fixed and agreed before we start.
Here is how that price is possible, stated plainly: AI agents write the software, and an experienced consultant supervises them — every plan approved by a person, every change clicked through by a person before it ships. The agents replace the team of developers this work used to need at £500–£750 a day each; they don’t replace the judgement. You pay for the consultation and the running of it, not for months of typing.
Your system runs on the platform we run for every client, co-designed with your people and shaped around your process. One platform, well-run, is why the monthly cost stays low and why fixes arrive fast — improvements made for one client become improvements for all of them.
There’s a quieter benefit, worth naming for anyone thinking further ahead: once the processes live in a system rather than in someone’s head, the business itself becomes easier to hand over — to a new manager, the next generation, or a buyer — because how it runs no longer leaves when a person does.
The running of it — £1,000 a month, and the part that matters
Software that isn’t looked after decays. The licence — £1,000 a month — is the looking after: support when something’s wrong, fixes when something breaks, and a steady stream of small improvements as your business changes — starting with the roadmap your audit found. Twelve-month term with a notice period.
The rhythm is steady: improvements ship in a monthly release. And because we run the system, we can see how it’s actually being used — so when something changes in how your business works, the check-in call comes from us, before you’ve had to ask. If a workflow stops being used, we notice, call, and fix the reason. Adoption is watched, not hoped.
Support is tiered by what’s actually at stake, not by how loudly the clock ticks:
| Tier | What it covers | Response |
|---|---|---|
| 1 | System down, or a data or security incident | The founder, personally, within hours |
| 2 | Something broken but workable around | Next business day |
| 3 | Feature requests and improvements | Queued into a monthly release |
The guardrails
Agents make software faster to build. They don’t change what makes it safe: people, tests, and a record of everything. Every system we ship is governed by five rules:
- A person approves every plan and every result. Nothing is designed or shipped without human sign-off, and someone clicks through every change before it goes live.
- Tests are the law. Nothing ships unless every automated test passes. No green suite, no ship — no exceptions.
- The sensitive parts are handled by a person. Always. Logins, permissions, payments and security are never automated work.
- Personal data stays out of error logs. Your people’s and your customers’ details don’t leak into diagnostics, by design.
- Everything is on the record. Every change has a ticket, a test run, and a deployment log. If you ask what changed and when, there is an answer.
Security and data, plainly
Your data stays yours. Access is limited to the people who need it to do their jobs. Personal data is kept out of error tracking. Changes to anything security-adjacent are made by a person, reviewed by a person, and recorded. A one-page security and data note covering hosting, backups and access in detail is being written; it will live on this page.
Continuity — the “what if” answer
What happens to your system if something happens to us? You’re covered: continuity is part of every agreement — an orderly handover of your system and your data if we can no longer look after you. It’s the question every sensible buyer asks, so the answer belongs in writing, not in goodwill.
The commercial terms, summarised
- The £1,000 audit is credited in full against the build fee.
- The build is a fixed price, agreed before work starts: £4,000–£6,000.
- The licence is £1,000 a month on a twelve-month term with a notice period — never rolling monthly, never evergreen small print.
- If you leave, leaving is orderly: handover and continuity are part of the agreement.
If the checking is done and it holds up, the next step is a conversation. Book an audit conversation.