- Price
- $2,500 USD per agreed automation, fixed
- Payment
- 50% before build, 50% after acceptance
- Duration
- 2-4 weeks, assuming agreed access, stable third-party systems and timely client review
- Scope
- One defined workflow with one primary business outcome. Integrations, decision rules, failure paths and acceptance criteria are fixed in writing before build.
- Stabilization
- 14 days after launch for defects inside the agreed scope
ServicesStep 02$2,500 USD per agreed automation
System Build
One agreed automation for one defined workflow with one primary business outcome. Delivered in 2-4 weeks after scope and access are agreed, with architecture, QA record, monitoring, documentation, runbook and handover.
What you receive
- Architecture. The design of the automation and its integrations.
- Working automation. The agreed workflow running in production.
- QA record. The tests run against the written acceptance criteria.
- Monitoring. Visibility into runs and failures.
- Documentation and runbook. What the system does, how to operate it and what to do when it fails.
- Handover. The delivered system in your hands, under your accounts.
Who it is for
Teams that have completed a Diagnostic Sprint, the required starting point for paid work, and have chosen one workflow to automate against one primary business outcome.
Where AI sits, and where people stay in control
AI handles variable analysis only where appropriate. Deterministic work uses rules. Ambiguous or high-consequence work routes to a person. The decision rules and failure paths that set those boundaries are written down and agreed before build.
What is excluded
- New workflows and material scope changes. A new workflow is a separate System Build.
- Third-party outages.
- Vendor pricing and usage costs. Third-party API, hosting and software costs are separate and require your approval.
After launch
Stabilization covers defects inside the agreed scope for 14 days after launch. After that, the Optimization Retainer is optional. The system must remain operable without a retainer.
What you own
- The delivered workflow, code, configuration, prompts, documentation and your data.
- Production accounts and credentials remain under your control. AfterMachines uses least-privilege access and managed credential storage.
- Your data is not used to train AI models.
- US-first. Available worldwide.
Start with the free workflow review
Paid work begins with the Diagnostic Sprint, and before that comes a free 30-minute workflow review: one candidate workflow, a fit decision and a recommended next step.
Book the free reviewQuestions about the System Build
What does a System Build cost, and how is it paid?
$2,500 USD per agreed automation, fixed. 50% is due before build and 50% after acceptance.
How long does a System Build take?
2-4 weeks after scope and access are agreed. This assumes agreed access, stable third-party systems and timely client review.
What is in scope?
One defined workflow with one primary business outcome. Integrations, decision rules, failure paths and acceptance criteria are fixed in writing before build.
What is excluded?
New workflows, material scope changes, third-party outages, vendor pricing and usage costs. Third-party API, hosting and software costs are separate and require your approval.
What happens after launch?
Stabilization covers defects inside the agreed scope for 14 days after launch. After that, the Optimization Retainer is optional. The system must remain operable without a retainer.
Where does AI sit in the build, and where do people stay in control?
AI handles variable analysis only where appropriate. Deterministic work uses rules. Ambiguous or high-consequence work routes to a person. The decision rules and failure paths that set those boundaries are fixed in writing before build.