01Physical & operations · 16
We run the AI that runs your process.
Once a model, an agent, a robot cell or a pipeline is live, someone has to watch it, retrain it, answer the page and report the cost. We do that, around the clock, under your keys and your accounts, with the exit planned from the first day.
For operators who have automation in production, or about to be, and no team to run it at three in the morning, and for teams who would rather own the outcome than the rota.
01Overview
RunningRunning automation is not the same as building it. It means a desk that sees every run, a retraining cadence that keeps the models current, service levels defined on what the system does rather than whether it is up, and a runbook for the failures we have already met.
01/ 02
Running
Watched, retrained and held to account, every day.
Running automation is not the same as building it. It means a desk that sees every run, a retraining cadence that keeps the models current, service levels defined on what the system does rather than whether it is up, and a runbook for the failures we have already met.
- 01
Monitored around the clock
Every automated run, model call, robot cycle and pipeline job reports to one desk, staffed around the clock. An anomaly is seen and acted on before your team's morning, not found in it.
- 02
Retraining on a cadence you agree
Models are retrained on a schedule we agree with you, or sooner when drift is detected, through the same evaluation gate as the original release. You approve what changes and when, and nothing ships silently.
- 03
SLAs on behaviour, not uptime
Service levels are written on what the automation does: documents posted within the window, calls answered within the budget, rejects reviewed within the shift, evaluation scores held above the line. Uptime is a prerequisite, not the promise.
- 04
Runbooks for every failure we have seen
Every incident across every process we run ends in a runbook, so the next occurrence is handled by procedure rather than by heroics. Your team can read every runbook that applies to your processes.
02/ 02
Ownership
Your keys, your accounts, your exit.
An operations contract should make you more independent, not less. Everything runs in your accounts under your keys, the cost of every process is on one monthly report, physical and digital automation are watched from one desk, and the handover is written before the work starts.
- 05
Cost reported per process, every month
Compute, model calls, telephony, storage and our time are reported per process every month, against the budget agreed for it. A process whose cost rises is a conversation, not a surprise.
- 06
Your keys, your accounts, our operators
Every system runs in your cloud accounts, under your keys and your data agreements. Our operators hold scoped access you can see and revoke; we hold nothing you would need to run it without us.
- 07
Physical and digital under one desk
Robot cells, vision lines and conveyor controls are watched by the same desk as the agents, models and pipelines, because a fault in one is usually a fault in the other. One incident, one owner, one record.
- 08
Exit and handover, planned from day one
The handover pack, the runbooks, the access lists and the training for your team are deliverables from the first month, kept current throughout. Leaving us is a scheduled task, not a project.
At a glance
Every capability, at a glance
8 figures, one per capability. Open any to read it in full.
How it runs
From first call to running unattended
Every engagement runs the same five steps, whatever the service.
- 01
Map the process
We sit with the people who do the work today and write down every step, exception and hand-off before anything is built.
- 02
Build against a golden set
A held-out set of real cases, agreed with you, is the bar each build has to clear before it goes anywhere near production.
- 03
Run beside the team
The system runs in parallel with the team for as long as it takes, and every disagreement between them is reviewed together.
- 04
Hand over the keys
The code, the prompts, the evaluation set and the runbooks are handed over in your accounts, under your keys.
- 05
Keep it running
We watch the runs, retrain and repair as the inputs drift, or train your own team to do the same.
Outcomes
What this looks like when it lands.
01 Automation that is run, not just built
A desk watching every process around the clock, with a runbook for each failure and a person accountable for each incident.
02 A monthly cost per process
One report showing what each automated process costs to run, against the budget agreed for it.
03 Independence that grows with the contract
Everything under your keys, the handover pack kept current, and your team trained to take over when you choose.
Details
On the spec sheet.
- Service
- Autonomous Operations
- Group
- Physical & operations
- Capabilities
- 8
- Engagement
- Map, build, run beside the team, hand over, keep running
- Ownership
- Your accounts, your keys, your region
Questions we are asked about autonomous operations
Asked before signing.
Do you run systems you did not build?
Yes, after an onboarding period in which we put monitoring, runbooks and an evaluation gate around them. Some fixes usually come first; we tell you which before we take the pager.
What does the SLA actually cover?
The behaviour of each process, written with you: throughput windows, response budgets, review times and evaluation thresholds, with reporting against each. Uptime is measured too, but it is not the promise.
Who has access to our systems?
Named operators with scoped roles in your accounts, visible in your audit logs and revocable by you at any time. Nothing runs in accounts you cannot see.
How is the cost reported?
Per process, every month, covering compute, model calls, telephony, storage and our time, against the budget agreed for that process.
What happens if we want to stop?
The handover pack has been kept current since the first month. We train your team or your next provider, transfer the rota, and revoke our own access on the date you set.
Start