Internal systems
Internal systems, built in weeks and run for years
In most organisations the operational work lives in email, spreadsheets and three portals that nobody agrees on, so nobody can see what needs a decision, who owns it, or what happens next. We build the console that puts all of it in one place, with an owner, a date and a next action on every item. We build it fast enough that you click through a working version within weeks, and we have run systems of this kind for one client for years.
What we build
What we build
A dashboard reports what already happened. A console is for getting the work done. Every case, service order, contract and payment in one place, each with somebody responsible for it and an obvious next move.
The cycle it holds together
- 01 A request or incident comes in
- 02 It becomes a case with an owner
- 03 A service order goes out
- 04 The contract and contractor are tracked
- 05 Work is confirmed and signed off
- 06 The invoice and payment are reconciled
- 07 It is archived, with the next action set
Leadership sees what needs a decision, where, why, by when, and who is expected to respond: without chasing it across inboxes.
How we build it this fast
How we build it this fast
We start from a shell of our own, so you see something working in weeks. Then we harden it once the shape has stopped changing, later than most people expect and earlier than a big-bang build.
-
A working system on day one
The first thing you see is a branded, clickable console running your own process on synthetic data. So your team judges the working system before anyone commits to a full build, and the slide deck never gets written.
-
Parameterised during discovery
Your areas, contracts, roles and procedures are configuration, so a change to them is a change to a file and never a rewrite. We shape the console to how you work in the discovery conversation, months before anyone would normally ask.
-
The method is built into the screen
Every item carries an owner, a date and a next action. An item with none of those gets lost, and the console exists to stop that.
Demonstrations
Two we have built
Two of them are municipal operations consoles for a mayor's office: every case, service order, contract, contractor, work report and payment in one place, in the local language and on the local process. Both are proofs of concept running on synthetic data. The areas and contracts are set to yours during discovery.
A city's cases, each with an owner, a date and a next action
Decisions, actions, service orders, grants, contracts, tasks, meetings and documents in one console, with governed email intake and document review. Built for a small town hall, in Spanish, responsive from desktop to phone.
A city's services, incidents and contracts in one place
From an incident or location, to a case, to a service order, to contractual control, to sign-off, to invoice and payment: the operational cycle a mayor's office runs, in one place. Not a citizen portal or an accounting system: a control core for leadership.
Both run on synthetic demo data and are clearly marked as demonstration environments. Names, areas and procedures are parameterised for your organisation during discovery.
It does not stop at a demo
Where we already run systems like this
Two different claims on this page rest on two different pieces of evidence, and it is worth keeping them apart. That you can see a working console on your own process within weeks rests on the two consoles above, which run on synthetic data. That such a system can then be trusted for years rests on Livesport, where we built and still run nine internal systems behind a sports platform used by more than 100 million people. The same team does both, and that is the reason the first is worth starting.
100M+
people served by internal systems we built and still run, nine of them, in production, for Livesport.
How it is bought
What it costs, and what you need to bring
Three steps, and the first one is free. Each paid step is quoted and agreed in writing before it starts, so you know the number going in.
One · free
A conversation about where the work lives
An hour with the people who run the process today. We come out of it knowing which cases, contracts and actions are scattered where, and you come out of it with the shape of a console and a fixed price for building one.
Two · fixed price
A working console on your own process
Branded, clickable, running your areas, roles and procedures on synthetic data, in weeks. The person who would use it every day clicks through it before anyone commits to a build. We publish no rate card for this because the scope follows the process being modelled, and a number invented before we have seen yours would be worth nothing to either of us.
Three · quoted separately
Production hardening, if you want it
Your data and integrations, access control and security, deployment behind your own TLS and secrets, and the operational care a system people depend on needs. It is a separate piece of work with its own price, and the console is yours whether or not you buy it.
When we are a fit
- The work is scattered across email, spreadsheets and portals that do not talk.
- Somebody senior can describe the process and decide to change it.
- The items have owners and dates, or should have.
When we are not
- An off-the-shelf tool already fits the process, in which case buy it.
- Nobody will own the system once it is live. That is how a console quietly stops being opened.
- What you want is a citizen portal, a CRM or an accounting system. This is none of those.
Who runs it
A partner runs the discovery conversation and stays on the work through the console and the hardening, and is who you call when something is wrong. Everything we see is confidential, and no organisation appears in a deck or on this site without written permission. Our standard for what counts as evidence before anything is trusted is set out in how we validate, and the stages above are the same Find, Prove, Build ladder the rest of the company runs on.
Where it stands
What the proof of concept is, and what it is not
The consoles above are working demonstrations on synthetic data. Turning one into a system your organisation depends on is work of its own after the POC: your data and integrations, access control and security, deployment behind your own TLS and secrets, and the operational care any production system needs. We say which of those is done and which is next, and we do not present a demo stack as a hardened deployment.
FAQ
Questions about internal systems
How quickly can we see something working?
A working, branded console running your own process on synthetic data, usually within weeks. You click through it before committing to a full build, and so does the person who will use it every day.
Is the proof of concept ready for production?
No. It is a demonstration on synthetic data. Turning it into a system your organisation depends on is a second piece of work after the POC: your data and integrations, access control and security, deployment behind your own TLS and secrets, and ongoing operation.
Do you only build demonstrations, or do you run systems in production?
We run internal systems in production at scale. For Livesport we built and still operate nine internal systems behind a sports platform used by more than 100 million people. So a proof of concept starts the work, and the deliverable is the system that runs.
What kind of work is an operations console for?
Operational work that currently lives across email, spreadsheets and several portals: cases, service orders, contracts, tasks and payments that no single system holds together. The console puts each item in one place with an owner, a date and a next action.
Can it use AI?
Where it earns its place. The municipal consoles include governed email intake and document review, and can use a language model for extraction, with deterministic fallbacks so the system still works without one. We do not add AI where a simpler mechanism is better.
How do we start?
With a conversation about where your cases, contracts and actions live today. Usually that is email, spreadsheets and three portals. It costs nothing and it ends with the shape of a console and a fixed price for building one.
What does it cost?
The first conversation is free. The console is a fixed price agreed in writing before the work starts, and production hardening is quoted separately after you have clicked through the console and decided you want it. We do not publish a rate card, because the scope follows the process being modelled and a number invented before we have seen yours would be worth nothing to either of us. You get the number before the work starts.
Bring us a hard problem
Tell us where the work lives today
Tell us where the cases, contracts and actions live today. The first conversation costs nothing, and it ends with the shape of a console and a fixed price for building one.