Fixed scope, fixed fee. Three ways to start, and what each one includes.
Fixed scope, fixed fee. Anything outside the scope gets quoted before it starts, never after.
For teams who need to know whether there is a case at all, and want a number they can take to a board.
One workflow taken from ground truth to production, with targets written into the statement of work.
For organisations running several workflows at once who want a dedicated group instead of a queue of requests.
Each one is scoped as a standalone piece of work. Most clients start with one and add the next once the numbers hold.
We sit with your team for two weeks, watch the work, and come back with a ranked list of what is worth automating and what is not.
Open weights, hosted APIs or a small task-specific model. We test candidates against your data before anyone signs a licence.
The unglamorous part: queues, retries, human review steps and the handoffs that decide whether anyone actually uses the thing.
Audit trails, access rules, red-team runs and a written record of what the system may and may not decide on its own.
A test suite built from your real edge cases, running on every change, with alerts when quality drifts instead of after a complaint.
Your engineers run it after we leave. Documentation, pairing sessions and a 90-day window where we stay reachable.
If yours is not here, write to us and we will answer it in plain language.
No. Waiting for clean data is the most common reason projects never begin. We work with what exists, document what is missing, and fix the records that actually affect the outcome.
Inside your cloud account, your data centre, or an isolated environment with no outbound network. We have delivered all three. The choice is yours and it does not change our fee.
The final invoice reduces on a scale written into the statement of work. We would rather agree that up front than argue about it at the end.
Only on your written instruction, only on your infrastructure, and only for a model you own. Vendor terms are reviewed and summarised for you before anything is signed.
We prefer it. Projects with two or three of your engineers embedded hand over faster and hold their results longer. It also reduces the fee.
Assessments usually begin within three weeks. Build engagements depend on team availability — as of this quarter, the next opening is in about six weeks.
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.
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.
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.
The eval suite is the thing that changed the argument internally. We stopped debating whether it worked and started reading a number every morning.
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.
Everything sits in our own cloud account with our own keys. Our security review took two weeks instead of the usual six months.
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.
