The end of guesswork.
XO is your AI second-in-command. It runs a process you rely on, the same way every time. It comes to you only when a case needs a person — and it brings the evidence with it.
The work
nobody owns.
Every operation has one: a detailed process the whole place leans on, where the information arrives in four different systems that don’t talk to each other, and the knowledge that joins them up lives in two or three people’s heads.
Nobody’s job description covers it. It gets done in the gaps — evenings, weekends, the hour before the meeting. It is accurate because those people are good, not because the process makes it so.
Then one of them leaves.
That’s the role this fills. It has never actually been properly filled before.
You’re not buying software.
You’re filling a role.
Write the job description the way you’d write it for a person: what they handle, what they need to know, what they can decide on their own, and when they should come and find you. Then hire XO into it.
It picks up every case, every day. The same attention at four in the afternoon as at nine in the morning, and the same in a busy week as a quiet one. The small things still get done when the big ones land.
It stays. Everything it learns stays with it, and all of it stays in your business — yours, not ours. No notice period, no handover, nothing walking out of the door.
It learns your rules and how your operation has actually handled things before, and works to the standard your best people set. Clever enough to know the difference between a case it has seen a hundred times and one it hasn’t.
Trust it because you can check it. Every decision is tied to the evidence behind it, kept and replayable. Ask why it did something and you get the working, not a promise.
It works alongside your team, not instead of them. It settles what is straightforward. It brings you what needs a person — thinking done, evidence attached. The only thing left is your judgement. Not a system to roll out. A role you fill, and someone to do it.
XO is short for executive officer — on a ship, the second-in-command who runs things day to day so the captain can command.
What changes
on Monday.
Your people get their week back. The reading, the checking, the chasing, the rekeying — done. That time goes into the work that actually moves you forward: the cases that need judgement, the people who need a person, the projects that never start because nobody has a clear day. It does not take anyone’s job. It gives them back the part of theirs that got squeezed out.
Information stops being retyped. What lands in one system moves into the next. The rekeying errors stop, because the rekeying stops.
It comes to you where you already are. The cases that need you arrive in the channel your team already uses. Approve with a reply. There is no new system for anyone to learn.
What a process looks like
when XO runs it.
Same shape every time. Sector and role only; no client named.
A missing instrument caught six days out, so the list is re-rostered before anyone notices. The 14:00 day-before gate: every case on tomorrow’s list checked against tray sterile status and location.
Statement review, receipt capture and exception intake — the finance team’s month-end stops being eaten. “I’ve reconciled ninety of these. Three need a human.”
Referrals, resident management, finance and compliance on one spine.
Visa, finance, supervisor and peer-group approvals coordinated so an offer takes two weeks instead of six.
Signed without anyone chasing.
Read against the credit policy, resolved inside the authority set, the rest handed back unsigned.
Finance, ordering, rota and tills each do their own job. None of them decides anything. Seven venues going to nineteen is exactly when this bites.
We run XO ourselves, on live operations, and have for over a year. Not something we sell; something we use.
Most of these are still proving themselves — some are live, some are in build, some are trials agreed last month. We’ll tell you exactly which is which on a call, before you ask.
Start with one. Every one of those began as a single problem that was hurting, and widened from there.
The sector knowledge — we call it a Domain Cartridge — already exists for supported housing, and for sterile services and surgical trays. For most sectors it does not exist yet — and the first organisation in shapes what everyone after them inherits.
Two sectors are written up in full, for the people who run them: social housing and supported & exempt housing.
XO runs in the UK, on AWS in London. Your system of record stays the source of truth. Nothing is migrated, nothing is torn out. Close the workflow and your data is gone. We keep the reasoning record, which is yours. Nothing trains on your data. The precedent knowledge base sits on our own EU infrastructure. If you need it all in your own country, or on your own premises, that is a setting — not a rebuild.
We didn’t set out
to build a product.
We went looking for something to fix our own operation and found Streamline — forms, documents, signatures, the connections into the systems we already had. We put the workflows in, and then the obvious thought: the information is arriving now — why are we still reading it afterwards? We tried it on a live business and kept hitting the same wall. We weren’t a vendor who found a partner. We were the customer who built the missing half.
And we still run it ourselves, and have done for over a year. We are not selling you something we don’t use.
So XO runs the work end to end — the reading and the deciding, and the forms, the documents, the signatures and the connections into your existing systems. It sits across what you already have. Nothing is torn out and nothing is migrated.
Grounded. Checkable.
Honest at the edge.
Not a bigger model — a better memory, and the discipline to use it. Three moves sit under every decision.
Three layers. The first is general business sense.
The second is your sector: the vocabulary, the practices, the rules, and what has gone wrong before. That is the Domain Cartridge. It is loaded before XO starts, so it turns up already speaking your language.
The third is you. Your rules, your procedures, and the things your best people know that nobody ever wrote down — what time the van turns up on a Wednesday, and who’s driving it.
That third layer is yours. Your intellectual property, not ours. When somebody leaves, it stays. And it grows every time XO handles a case, so it is worth more each year than the last.
XO acts below the line you set.
Above it, a named person decides.
You don’t let a new starter sign off unsupervised in week one. You choose how far it can go, per workflow. It can watch and flag. It can recommend and wait for you. Or it can act, within limits you set. XO manages the decision, not the procedure, and stays out of your critical operational and safety systems. It does not make clinical or regulated decisions: it scores and recommends, and a named person reviews before anything moves. Where you want XO to take the action itself, that is defined and separately agreed. We never cross it quietly.
The Consequence Engine holds what actually happened.
XO decides what to do about it.
A record of what actually happened when operators built, scaled and rescued real businesses — structured, anonymised, and there from day one so XO has something to reason from. Your own living knowledge base builds on top of it.
One XO. One role.
£3,000 a month.
£3,000 covers XO and the first role you hire it into. About half what a good manager costs you, once you have added NI and pension.
More roles as the operation grows, each scoped and priced before you commit. No platform fee, no seat licence. Any build is scoped and fixed before it starts. Non-profit discount available.
In our experience — running it ourselves, and in other operations:
The standard holds. The process runs the way you set it, not the way a busy week allows.
The front line stops waiting. The rules, the history and the precedent are there when your people need them. The decision happens at the desk, not in a queue.
Cases move at the pace of the work — not the pace of whoever has time this week. The resident, the patient, the applicant feels that first.
You can see it. What was decided, where it stands, what needs you. Without anyone building a report.
We’ll show you it doing this on your own material before you commit.
The roles you already have don’t go up in year two.
Built by operators,
for operators.
Alan has lived and worked all over the world — the UK, the United States, Asia — building and running businesses in technology, hospitality, live events and operations, and staying through the hard parts, not just the launches. The last operation he ran spanned several sites and put out two and a half million meals; for five years he opened a spreadsheet at six in the morning to find out what had happened the day before. XO is what he wishes he’d had. He leads commercial strategy, the UK market and client relationships, and holds the line on what XO is allowed to claim.
A career in commercial real estate — acquisitions, tenant negotiations and disposals: exactly the high-stakes, precedent-heavy calls XO is built to support. Ken owns XO’s product and the system architecture beneath it, including the AWS build, and is the one who says what isn’t built yet — the discipline that keeps its confidence earned rather than asserted.
Richie leads the engineering behind the Consequence Engine — the retrieval architecture, ingestion pipeline and system design that make the knowledge layer production-grade, and keep every decision traceable to the source it drew on.
There’s a role at your operation
that’s never actually been filled.
Tell us one process you run by hand that matters, and hurts. Send us the shape of it — it doesn’t have to be beautiful — and we’ll build it and show you it working on your own operation. Proposal inside two weeks; running on your own material inside a month. If it doesn’t stand up, we’ll tell you. A no is a perfectly good answer.