Automation Builds
Four build lanes with published bands. The scope drivers below decide the lane, the signed SOW controls the exact number, and the $999 Current State Assessment sets both before any build begins.
The four lanes
A price supports its advertised scope only when delivery fits it. These are the boundaries we sell by, so a build never quietly outgrows its number.
One known, contained workflow using a supported delivery pattern.
One primary workflow requiring tailored logic or a broader integration set.
Linked workflows, multiple teams, or deeper production integration.
Required for business-critical implementations or work that needs private infrastructure.
What moves a build up a lane
| Driver | Defined | Custom | Operations | Business-Critical |
|---|---|---|---|---|
| Workflow breadth | One contained workflow | One tailored primary workflow | Linked workflows or multiple teams | Business-critical or high-consequence process |
| Systems and data | Up to two supported integrations | Broader SOW-defined integration and data prep | Multi-system production data flow | Private infrastructure or dedicated custom architecture |
| Actions and autonomy | Bounded actions with a clear owner | Tailored workflow actions and exceptions | Cross-system actions with human review | Consequential or high-risk autonomous actions |
| Assurance | Defined acceptance test | Custom evaluation and standard security | Regression, permissions, traceability | Business-critical recovery, availability, or SLA |
| Launch and adoption | Standard deployment and handoff | Tailored training and documentation | Multi-team rollout and change control | Private infrastructure or dedicated engineering program |
| Post-launch responsibility | Defined stabilization window only | Stabilization defined; Managed Care optional | Operating handoff; Managed Operations separate | Critical schedule and SLA separately priced |
What no lane includes automatically
No build lane automatically includes cloud or model usage, licenses, legal or compliance attestation, 24/7 coverage, a tailored SLA, or uncapped new feature work. The signed SOW controls exact systems, data, acceptance criteria, support, usage, third-party costs, and exclusions. Every production workflow names the decisions a human approves and where exceptions escalate. Every build has a defined acceptance test. Operations-scale builds ship an evaluation and regression suite. Build and operations are separate contracts and separate prices. Handover support is scoped into every contract. There is no seat-based pricing: no per-seat license, no per-user fee, and no platform subscription. A build is a one-time price. Managed service is one monthly price for the system, however many people use it.
Frequently asked
A free 30-minute AI Strategy Call qualifies the workflow. If it is known, the $999 Current State Assessment sets the exact lane, scope, and price.