operators.sh takes one recurring business workflow that is too judgment-heavy to automate blindly and too specialized for a generalist to run alone, and turns it into a defined, auditable operation. We scope it, build it against OperatorSpec, run it with trained operators and expert agent workers, and hand it over whenever you are ready.
Each package is a phase of the same lifecycle. Most engagements start with a discovery sprint and stop wherever the workflow is ready to stand on its own.
A short, fixed-scope engagement to map one recurring business workflow. We research the need, the tools, the access, the data, the risks, and the points where expert judgment and escalation actually happen. You leave with an OperatorSpec definition, not a slide deck.
Turn the discovery definition into a running workflow: the OperatorSpec contracts, operator runbooks, agent worker setup, templates, state and evidence files, and a validation path that proves it works before anyone depends on it.
We run the workflow for you with trained human operators driving expert agent workers. Checkpoints, evidence, and escalation boundaries are enforced every cycle. You get the outcome and the audit trail without building the practice in-house.
Train one of your own people to take the workflow over. They inherit the same state, evidence model, and decision boundaries we operate against, so the handover is a continuation rather than a restart.
Transfer the whole workflow: repository, OperatorSpec definition, runbooks, durable state, audit trail, and the open-risk register. The workflow is portable by design, so leaving is a documented step, not a renegotiation.
This is a hypothesis, not a final price list. operators.sh is early, and these models are how we expect to charge while we learn what the work actually costs. We will publish real numbers once enough workflows have run to back them.
Hypothesis — directional pricing models, subject to change as we run more workflows.
| Package | Pricing model | How it works |
|---|---|---|
| Workflow Discovery Sprint | Fixed price | One workflow, fixed scope, fixed fee. The cheapest way to find out whether a workflow is real. |
| Workflow Buildout | Fixed price or scoped project | Fixed price when the discovery sprint scoped it cleanly; a scoped project when the surface is larger. |
| Managed Operation | Monthly retainer | Priced to the operating cadence and volume, billed monthly while we run it. |
| Operator Training | Scoped with the buildout or operation | Usually folded into a buildout or a managed operation rather than sold alone. |
| Handoff Package | Fixed price | A defined transfer deliverable, priced once, so exit is never a surprise line item. |
A sample statement of work. The sprint is deliberately small: enough to define one workflow precisely, not so large that it becomes the project itself.
What the workflow is for, who depends on its output, and what "good" looks like in concrete terms.
The systems involved, the credentials and permissions required, and the runtimes the agent workers will use.
What the workflow reads and produces, where it lives, and what must never leave the boundary.
Where the work can go wrong, what evidence proves each step, and what gets recorded for audit.
The decisions the operator makes alone, and the ones that must be escalated to a human owner.
An OperatorSpec workflow definition, an operator runbook, and a validation path that proves the workflow before it carries real work.
Deliverable: an OperatorSpec workflow definition, an operator runbook, and a validation path — the inputs the Workflow Buildout package builds against.
The discovery sprint is the front door. If the workflow turns out not to be a fit, you leave with a clear definition and no further commitment. If it is, you have everything the buildout needs.