Cirreo
120+
Systems in production across cloud, on-premise and air-gapped environments.
About us
A consulting partner built for the messy middle — where a promising model meets a real process, a real ledger and a real team
Targets met on contract 100%
They rewrote how our claims desk works. Quiet, fast, and nothing broke on the way in.
Contracts, claims, invoices and field reports — read, routed and checked against your own rules.
4.2×
median return on the first workflow shipped
How we work
We stay until the numbers move, then we leave
Most AI work stalls somewhere between a convincing prototype and a Tuesday morning shift. Our whole practice is built around that gap.
-
One team, start to finish
The people who write the strategy write the code. No handover to a delivery pod you have never met.
-
Targets written into the contract
Cost per item, cycle time, accuracy floor. If we miss them, the last invoice adjusts.
-
Your data stays yours
Deployment inside your account or on your hardware. Nothing trains on your records without a signed instruction.
-
No lock-in by design
Standard tooling, documented interfaces, and a swap path for every model we recommend.
Delivery path
Four stages, in this order, every time
Order matters here — each stage produces the input the next one needs. We do not skip ahead, and we stop at any gate that fails.
Ground truth
We measure the current process by hand: volume, cost per item, error rate, where time goes. Nothing gets built against a guess.
Weeks 1–2Narrow prototype
One workflow, one team, real data. The goal is a decision, not a demo: is this worth the integration cost or not.
Weeks 3–6Production build
Hardening, permissions, monitoring and the review steps your risk team asked for. Rolled out to one site before all of them.
Weeks 7–14Handover
Your team takes the keys. We shadow for a month, answer questions for two more, then step back for good.
Weeks 15–18
Measured, not estimated
What the last three years produced
Figures come from client-side reporting at the six-month mark, not from our own dashboards.
90
Engagements delivered since 2019, across 20 countries.
69
%
Median share of a queue handled without a person touching it.
11
wks
Average time from kickoff to the first workflow running live.
4.2 ×
Median first-year return on the initial build cost.
Client words
What people say once we have gone
All of these were collected at the six-month review, not at go-live.
They spent the first fortnight watching our adjusters work and asking questions. Everything after that was built for the desk we actually have, not the one on the org chart.
Priya Raghunathan
Head of Claims, Northmoor Trust
We had been burned by a pilot that never shipped. Cirreo scoped the smallest useful thing, put it live in nine weeks, and let the results argue for the rest.
Tomas Berglund
COO, Halyard Freight
The handover was the part I did not expect. My engineers can change the system without calling anyone, which is the only reason it is still improving.
Adaeze Okonkwo
CTO, Ironvale Works
The eval suite is the thing that changed the argument internally. We stopped debating whether it worked and started reading a number every morning.
Marcus Feld
Director of Ops, Calder Health
They told us one of the three workflows we asked for was not worth building. That is the moment I decided to keep working with them.
Yuki Tanaka
Head of Data, Basten Retail
Everything sits in our own cloud account with our own keys. Our security review took two weeks instead of the usual six months.
Ana Ferreira
CISO, Meridian Group
Next step
Bring us the process nobody wants to touch
Send a short note about the workflow and the number you need to move. You will get a written reply from an engineer, not a form response, within two working days.