Production Sprint
8-12 weeksSteer the launch
A Production Sprint steers one defined commercial process to the point where it is ready to go into service. One sponsor. One manager rhythm. One before/after measure.
TokenShift frames the expected result, designs the target process, organises delivery with your teams and your technical partners, and checks that the process can be used and measured. Your teams or your suppliers build and integrate. See the split of work.
Who does what
Who actually delivers
A Production Sprint aims at a process ready to go into service. So that nobody reads it as "you will build the solution for us", here is how the work is split, as written into every engagement.
TokenShift
- Frames the expected result and the before/after measure.
- Designs the target process: steps, human review points, guardrails, named owners.
- Organises and facilitates delivery with your teams and your suppliers, at the pace of an 8 to 12 week sprint.
- Checks that the process can be used, controlled and measured before launch.
Your teams
- A named executive sponsor, available for the duration.
- The people who run the process today, and access to its data.
- The build, configuration and integration, if you do them in-house.
- The decision to launch.
Your technical partners
- Software development and systems integration, if you do not do them in-house. TokenShift is not that supplier.
- Licences, model consumption and infrastructure: these costs are not included in the fees.
- Running the platform after launch.
What ends the engagement
- A process ready to go into service: owners named, guardrails in place, human review defined, before/after measure established.
- A process ready to launch and a process actually in use are not the same deliverable. The sprint delivers the first. Following real usage is what the Governance Retainer is for.
Budget and calendar, without surprises
- If Decision Clarity and then a Production Sprint follow each other at the published entry prices, cumulative fees start at EUR 75K (25K + 50K), before technical spend, licences and infrastructure. Both steps are not always needed: a team that already knows which process to target, and has named its owner, can enter a Production Sprint directly.
- 4 to 6 weeks, then 8 to 12 weeks: 12 to 18 weeks if the two phases run back to back, not counting the gap between them. The "90-day path" is the plan delivered at the end of Decision Clarity. It starts after the decision and is not a guaranteed total duration.
The problem this solves
Many teams know which use case they want. What they do not yet have is a delivery path that operations, risk, and leadership can all support.
Production Sprint closes that gap. If ownership is still unclear, begin with Decision Clarity.
What is included
- One revenue workflow redesigned
- Manager operating rhythm
- CRM workflow integration
- Seller adoption model
- AI guardrails and human review points
- Before/after revenue metric
- Named owner assignments across revenue, RevOps, marketing, technology, and risk/legal where needed
- Production launch plan
Illustrative pattern
A typical revenue workflow pattern
In complex B2B environments, a validated sales-process pilot often still lacks a production workflow. Production Sprint restructures one target process, aligns sponsor ownership, and brings it to the production decision, with human review and a before/after measure.
Limits
What a Production Sprint is not
A sprint is deliberately bounded. Stating the boundary is part of the engagement, because most of the risk sits in what a buyer assumed was included.
Scope
- One workflow and one sponsor. A second workflow is a second sprint, not an extension of this one.
- The sprint delivers a workflow that can go into production with named owners, guardrails and a before/after measure. The decision to launch stays with the sponsor.
Solo or pod
- Solo: one senior operator carries the design, the governance and the facilitation. Your teams — or the suppliers you already work with — do the build, the configuration and the integration.
- Pod: a senior operator plus named associates, for a wider workflow or a tighter window. A pod still designs and governs. It does not replace an engineering team or an integrator.
- Which shape applies is agreed before the sprint starts and is written into the engagement.
Not included
- Software development, systems integration and platform operation.
- Running the workflow after handover, or standing on-call for it.
- Licences, model consumption and infrastructure spend.
- Legal advice, regulatory certification or an audit opinion.
Not promised
- No guaranteed return, no guaranteed compliance verdict, no guaranteed cost reduction. The sprint makes the decision, the controls and the measurement explicit; the result then depends on execution inside your organisation.
Conditions
- A named executive sponsor, available for the duration.
- Access to the workflow, to its data and to the people who run it.
- An existing baseline, or the ability to establish one in the first weeks. Without it, before/after cannot be measured — start with Decision Clarity instead.
Next phase: Governance Retainer
Once the first workflow is live, Governance Retainer keeps value, risk, and change under control.