We don't sell strategy documents. We build software that runs.
From the first call to a working system in your business, here's what actually happens. Plain steps, written by the people who do them, with no jargon and no surprises.
Book a call What we buildWe start by listening, not pitching.
The first thing we do is ask where the time is going. Not what you’d like to do with AI, not which tools you’ve heard about — where the time is actually going. Which jobs is the team doing every week that they shouldn’t be doing? Which mistakes keep happening? Which information is sitting in someone’s head that nobody else can get to?
This conversation lasts about half an hour and is free. By the end of it we either know there’s something worth doing, or we tell you there isn’t and we don’t take the project. We turn down work all the time.
A short, paid piece of work that ends in a fixed price.
If the first call shows there’s something worth building, the next step is a paid assessment. It usually takes one to two weeks. We work with the people who actually do the work — going through the spreadsheets, the inbox, the screens, the workflow nobody has documented because everyone already knows it. We ask awkward questions.
The assessment ends in a short written brief. It says: this is the problem we found, this is what we’d build, this is what it would change, this is what it would cost, and this is what it wouldn’t do. Fixed price. No surprises later. If you decide not to go ahead, the brief is yours to keep — and if you take it to another developer, they’ll have a much easier time of it than they would have done without it.
Working software in weeks, not months.
Most systems we ship are some combination of rule-based plumbing and agentic AI judgement. The plumbing — pulling data, formatting reports, sending notifications — gets built first because it’s the fastest to verify. Then we layer in the AI parts where the work actually needs judgement, and we wrap them in deterministic guardrails so nothing reaches a real user without passing through a known Configuration.
You see working software within the first couple of weeks. Not slides, not mock-ups — actual running code, on your real data, that the team can try out. We iterate in short cycles with whoever in your team is closest to the problem. They tell us what’s wrong; we fix it; they tell us what’s still wrong; we fix that.
By the time the system goes live, the people who’ll be using it have already been using it for a fortnight. That isn’t a coincidence — it’s the only way to make sure it actually fits.
A working system, plus everything you need to keep it that way.
Working software in production
Running on UK servers we operate. Connected to your data. Processing real work, not test fixtures. Handed over only when it does the job it was built for.
Documentation written for humans
What it does, how it does it, what to check if something looks wrong, who to call. Short and readable. Not a 60-page technical spec nobody can decipher.
A training session for your team
We run a session with the people who'll use it. We walk through it. We answer their questions. We stay until they're confident. Recorded so they can refer back.
Optional ongoing support
Most clients keep a small monthly support arrangement so we're available when something needs adjusting. Some don't, and that's fine — the systems are built to run without us.
An audit trail you can read
Every decision the system makes is logged in a form a human can follow. If you ever want to check what happened on a specific day, you can. No black boxes.
A clear answer on what we won't do
If we hit something we don't think we should build, we say so and we explain why. We'd rather lose a project than ship something that won't survive contact with reality.
We use this same process on our own business.
Our own email triage, document handling, server monitoring, task management and daily briefing systems were all built by us, for us, in exactly this way. They run every day. When we say weeks-not-months, plain-English documentation, and audit trails you can read, we mean it because we use them ourselves.
What people ask us about the process
“What if we don't know what we want?”
Most clients don't, exactly. That's what the first conversation is for. You tell us where the time is going and we tell you what we think is worth doing about it. If nothing is, we'll say.
“How much does it cost?”
The first call is free. The assessment is paid and is the only part of the engagement with a variable cost — it depends on the scope. The build itself is fixed-price, agreed before we start, with no surprises later.
“Do we have to be technical to work with you?”
No. Most of the people we work with aren't technical. We write and talk in plain English on purpose. If anything we say is unclear, that's our failure, not yours.
“Will we be locked in?”
No. Your data always belongs to you and you can use it as you see fit. We've never made a client feel trapped, and we never would. We'd rather earn the next project than hold the last one hostage.
“What sectors do you work in?”
Home improvements, construction, professional services, lead-gen, contracts, and our own internal operations. The sector matters less than the shape of the problem — if there's a repetitive job that needs both data plumbing and judgement, we can probably help.
“Where are you based?”
Swindon, Wiltshire. We work with clients across the South West, Thames Valley, the Midlands and London — most of our delivery is remote, with on-site visits when they make a difference.
Start with a 30-minute conversation.
No sales pitch, no commitment, no slides. We listen, we ask awkward questions, and we tell you honestly whether there's something worth building.
Book a call What we build