How long does a sprint take?
Sprint timelines depend on the tier you choose.
Sprint timelines
| Tier | Timeline |
|---|---|
| Proof of Concept | 2 weeks |
| Process Transformation | 30 days |
| Multi-Process Rollout | 45 days |
What affects delivery time
Most sprints run to schedule. The things that can slow a sprint down are:
- Integration access delays — if it takes time to get API credentials or system access from your IT team, this can add days. We flag what we need at the start of Week 1.
- Document sample availability — we need real document samples to train and test the assistant. Having these ready at the start of Week 2 keeps things on track.
- Stakeholder availability — the Week 1 discovery workshops require 3–4 hours of your team's time. If key people are unavailable, we may need to delay the build phase.
What we do if something slips
If an integration takes longer than expected or a discovery finding changes the scope, we will tell you immediately with a revised plan. We do not silently extend the timeline.
After the sprint
The 30-day post-launch support period begins from go-live, not from the end of the sprint timeline. If deployment runs to the end of Day 30, your support period still runs for 30 days from that date.