02 · Builds
You don’t need a specification. Bring the problem — working out what the software has to do is the part we do with you. AI agents then do the building, which is why bespoke now costs a fraction of hiring a development team. A person scopes it, reviews it and stays accountable for it.
Scoped by a person · built by agents · reviewed before it ships
What we build
They’re not the same deal, and it’s worth knowing which one you’re asking about. The first we host and run for you on a monthly fee. The other two we build in your name and hand over.
The red-route platform itself — a dashboard, a branded portal, automations and an assistant, hosted, maintained, backed up and supported by us for a monthly fee. If what you need is one place for your organisation and the partners you approve to work, this is it.
See the portal →A mobile or web product aimed at your own customers rather than your partners. The accounts, the code and the product are in your name from day one, and it’s handed over to you. Deliberately not part of the hosted platform.
Quote calculators, job trackers, booking forms, reporting tools, something to fill in on a phone on site, a move off whatever you’ve outgrown. Usually the thing that lives in a spreadsheet with a macro nobody understands. Yours, the same way.
Why it costs what it costs
Custom software has always been priced by how many developer-months it ate. When agents do the building, that number changes — and so does what’s worth building at all.
Before
Bespoke meant a team, a year, and a number that ruled it out for most organisations. So they bought generic software and bent themselves to fit it.
Now
A written scope, agents doing the build, a person reviewing. The cost of getting something shaped around how you actually work drops far enough to be worth doing.
The catch
Agents build fast from a clear scope and confidently from a bad one. The first conversation is where the value is, so we don’t skip it or automate it.
How it goes
No procurement marathon, no discovery deck, and nobody technical needed on your side.
Bring the problem. We sit with you and work out what the software actually has to do — what you hold, who touches it, what gets decided, what keeps slipping. AI doesn’t do this part. It’s a conversation.
The build itself is done by AI agents working to that written scope, with a person reviewing. That’s why the economics work: bespoke software without a bespoke development team behind it.
You get something to click through long before it’s finished, because the fastest way to find out a spec was wrong is to use the thing.
For anything outside the hosted platform, the accounts, the code and the product are in your name from day one — not moved across at the end, which is where hand-overs usually go wrong. You can take it elsewhere or keep us on. That’s a decision you make later, not one baked in now.
The honest part
Both are deliberate decisions rather than limitations we’re apologising for.
The red-route platform serves an organisation and the partners it approves. A product aimed at the general public carries a different kind of risk, so it’s built as its own thing, on its own infrastructure, in your name — never as a tenant on our platform. That keeps your product out of someone else’s compliance scope as much as it keeps them out of yours.
For work outside the hosted platform we’re the builder, not the host. You hold the accounts and the infrastructure. If you want us to stay involved afterwards, that’s a support arrangement we agree separately — not an assumption baked into a hand-over you can’t undo.
Bring the problem rather than the specification. If it shouldn’t be custom software, we’ll tell you that too.