Shipped in six weeks
Not a pilot. Not a proof of concept. A working agent, in production, doing real work — six weeks from the day you sign.
The short version: a working agent in production six weeks from signing — audit in week one, scope locked in week two, demos in weeks three and four, shadow mode in week five, live in week six. If the overrun is ours, you don’t pay for it.
Last updated:
The commitment
| Week | What ships |
|---|---|
| 1 | Audit delivered. Workflow map, integration feasibility tested against your live systems, fixed build estimate. |
| 2 | Scope locked and quoted fixed. You choose the workflow. We price it. Audit fee credited. |
| 3 | First working demo. Not a mockup. Something that runs against your data. |
| 4 | Second demo. Integration complete, escalation paths built. |
| 5 | Shadow mode live. The agent runs alongside your team, logging what it would have done. |
| 6 | In production. Staged rollout, rollback path tested. |
What we need from you
The schedule holds only if these do:
- Two hours of a senior operator’s time in week 1, and one hour weekly after
- System access by day 3 of week 2. This is the single most common cause of slip, and it’s almost always procurement or IT, not you.
- A decision-maker who can approve scope without a committee
- One nominated reviewer for the Friday demos
If any of those aren’t available, tell us during the audit and we’ll quote a realistic timeline instead of a heroic one.
What happens if we miss
If the delay is ours, you don’t pay for the overrun weeks. The fixed price stays fixed and we absorb the time.
If the delay is access, approvals or scope change on your side, we’ll have flagged it in writing at the point it happened, and we re-baseline together.
We’d rather tell you in week 2 that six weeks isn’t realistic than discover it in week 5.
When six weeks isn’t the right answer
- Multi-agent systems. These are a second engagement. Don’t attempt one first.
- Legacy systems without APIs. If we have to build an integration layer before the agent, the clock is longer, and the audit tells you that in week 1.
- Regulated approval workflows requiring sign-off from a body outside your organisation.
- Enterprise procurement cycles measured in quarters. The build takes six weeks; getting permission to start might not.
Why six and not twelve
Because agent projects that run long usually aren’t building — they’re discovering. Discovery is what the audit is for. Once integration feasibility is proven and scope is fixed, a single-workflow agent is a six-week build.
Long timelines in this category are typically a symptom of unscoped work, not complex work.
Frequently asked questions
Is six weeks from signing or from first contact?
From scope sign-off at the end of week 2. The audit is week 1. So roughly six weeks total, or four from the build starting.
What if we want more than one workflow?
Then it’s longer, and we’ll say so. One workflow, six weeks. The second is faster because the integration already exists.
Does moving fast mean cutting evaluation?
No. The eval suite is built during the build, not after, and shadow mode in week 5 is non-negotiable. Speed comes from scope discipline, not from skipping the parts that make it trustworthy.
Can you go faster than six weeks?
Voice deployments on well-supported platforms sometimes land in 2–4 weeks. We won’t promise it up front.
What’s the catch?
Scope. Six weeks is achievable because we fix scope hard at week 2. If you want to change direction in week 4, we’ll do it and re-quote — but the six-week clock resets, and we’ll tell you that before you decide.