02 · Builds
The hosted portal is one thing we build. The underlying capability is broader: a written scope goes in, working software comes out, and it costs a fraction of assembling a development team to do it.
Scoped by a person · built by agents · reviewed before it ships
What we build
They are not the same engagement. The first we host and run for you. The other two we build and hand over, in your name.
The red-route platform itself — a dashboard, a branded portal, automations and an assistant, hosted by us. If what you need is an operations layer for your organisation and the partners you approve, this is the product.
See the portal →A mobile or web product aimed at your own customers rather than your partners. Built as a standalone product in your name, on accounts you own, and handed over to you. It is deliberately not part of the hosted platform.
The thing that currently lives in a spreadsheet with a macro nobody understands. A calculator, an intake system, a reporting layer, a migration off something you have outgrown.
Why it costs what it costs
Custom software has historically been priced by how many developer-months it consumed. When agents do the building, that number changes — and so does what is 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 their operation to fit.
Now
A written scope, agents doing the build, a person reviewing. The cost of getting something shaped around how you actually work falls far enough to be worth doing.
The catch
Agents build fast from a clear scope and confidently from a bad one. The discovery conversation is where the value is, so we do not skip it or automate it.
How it goes
No procurement marathon, no discovery deck, nobody technical needed on your side.
We sit with you and work out what the software actually has to do — the data, the people, the decisions, the things that keep slipping. AI does not do the discovery. This part is a conversation.
The build itself is done by AI agents working to that written scope, with a person reviewing. That is the reason the economics work: bespoke software without a bespoke development team behind it.
You get something to click through long before it is finished, because the fastest way to find out that a spec was wrong is to use the thing.
For anything outside the hosted platform, the accounts, the repository and the product are in your name from day one — not migrated to you at the end, which is where hand-overs usually go wrong.
The honest part
Worth being clear about the boundary before you ask, because it is a deliberate design decision rather than a limitation we are apologising for.
The red-route platform is client-facing: it serves an organisation and the partners it approves. A product aimed at the general public has a different risk profile, so it is built as its own thing, on its own infrastructure, in your name — never as a tenant on our platform.
Our hosted platform holds safeguarding-grade records for other organisations. Keeping a public-facing product off that infrastructure is what keeps its security boundary meaningful — and means your product is not constrained by someone else’s compliance scope.
For work outside the hosted platform we are the builder, not the host. You hold the accounts and the infrastructure. If you want us to stay involved afterwards, that is a support arrangement we agree separately — not an assumption.
If your idea does not need custom software, or is better served by something that already exists, we will say so. A build that should not have happened is worse for us than a project we turned down.
Bring the problem rather than the specification. If it should not be custom software, we will tell you that too.