Build engagement
One pre-scoped automation. Shipped to production. Measured on a real business metric.
The Implementation Sprint is what happens after a Nano-Pilot, or when you arrive with a workflow already scoped and you just need someone who can build it without ceremony. Weekly milestones, production deployment, an honest measurement plan. We're out of your way when it's running.
Prices shown are in USD and exclude applicable taxes. The written scope controls the final fee, deliverables, and timing.
Who it's for
Is this the right engagement for you?
You've already identified the automation, either through a Nano-Pilot with us, or because you've thought about it long enough that the scope is obvious.
You want this shipped, not studied. No steering committees, no second-guessing workshops. Weekly written updates, a working prototype by week three or four, production by the end date.
You value measurement. We insist on picking a single business metric upfront, time saved, error rate, cycle time, conversion, and reporting against it honestly after go-live.
Good fit / not a fit
Fit is about readiness, not persuasion.
A bounded workflow with access to the people who run it.
You can name the operational problem, provide a responsible decision-maker, and evaluate a written recommendation against a real business measure.
An undefined mandate to “add AI everywhere.”
We are not the right choice for speculative transformation programs, unsupported compliance shortcuts, or work without an owner who can validate the workflow.
What you get
Deliverables.
- A detailed build plan at kickoff, with weekly milestones and deliverables mapped out.
- A working prototype by week three or four for you to test against real data.
- Integration with your existing systems, ERP, CRM, accounting, document store, whatever the workflow actually touches.
- The production deployment itself, either on your infrastructure or a managed environment we set up.
- A runbook documenting how the automation works, how to monitor it, and how to roll back if something breaks.
- A 30-day post-launch measurement window with a written report on whether the chosen business metric moved, and by how much.
- Handoff documentation thorough enough that another engineer could maintain it without us.
Implementation Sprint deliverable excerpt
A detailed build plan at kickoff, with weekly milestones and deliverables mapped out.
Format: Written, scope-specific, and usable without a presentation.How it runs
Timeline.
Week 1
Kickoff and detailed scope
We turn the Nano-Pilot scope (or your pre-scoped brief) into a detailed build plan with weekly milestones. Access is provisioned. The measurement metric is agreed in writing.
Weeks 2 – 4
Build and early prototype
First working version running against real data. You test it. We adjust. Weekly written update every Friday, no status meetings required.
Weeks 5 – 8
Integration and hardening
Production integration, error handling, edge cases, the unglamorous work that separates a demo from something you can trust on a Monday morning.
Weeks 9 – 10
Staged rollout
Production deployment, limited rollout to a subset of users or workflows, monitoring in place. You sign off before full rollout.
Weeks 11 – 12
Full rollout and measurement
Full production use. 30-day measurement window begins. Handoff runbook delivered. We're still reachable; we're just no longer on a retainer you're paying for.
Questions
Common concerns.
Why the price range?
Complexity. A document-ingestion pipeline for a dental office costs very different money than a real-time pricing engine for a trucking dispatcher. We scope exactly what it will be before you sign anything, and the number in your engagement letter is the number you pay.
What if we need to change scope mid-sprint?
We pause, write a change order, you approve it in writing, then we continue. No scope creep by ambush. If the change is small we absorb it. If it's material, the timeline and price adjust, visibly.
Do you work on top of existing systems, or do you replace them?
We work on top of existing systems by default. Ripping out your ERP is a separate multi-year problem that we will not sell you. The whole thesis is that intelligence conforms to your business, which starts with your business's current software stack, not a greenfield replacement.
What happens after the 12 weeks?
One of three things. (1) Nothing, the automation runs, you don't need us. (2) A small maintenance arrangement billed hourly as-needed. (3) You roll into Embedded AI Ops to keep improving it and tackle the next automation. Your choice, not ours.
Who owns the code?
You do. Full commercial rights to everything we build, in writing, at engagement close. No vendor lock-in, no 'you need us to run it.'
Have a scope already? Send it over. Don't have one yet? Start with a Nano-Pilot.
We reply to every intake with a written fit-assessment within two business days, pointing you at either an Implementation Sprint, a Nano-Pilot, or somewhere else entirely.
Send us your situationAlso