A Forge Sprint runs 10 to 14 weeks from kickoff to a live production system. Not a prototype, not a pilot, not a report. This article walks through what fills those weeks.
The Sprint starts where the Forge Diagnostic ended: one workflow, mapped and sized, with a priced build decision. That means week one of a Sprint is build work, not discovery.
What the weeks buy
- The system is built inside the workflow the team already runs.
- An eval harness checks outputs against a test set from the first build week.
- Reliability gates are set and must pass before production release.
- Cutover lands the system in production, live for the team.
The deliverable is the working system, not a report.
After the cutover
Production day is the start of the Adoption Mile: a named operator, a weekly working cadence, and a live adoption scoreboard, built to the 70 percent weekly-active bar by day 90. After that, Forge Run keeps the system operating on a monthly retainer, scoped to the system.