Judgment, applied.
Precision Sprint
Four to eight weeks alongside your team on one specific, bounded challenge. Fixed scope, fixed price, concrete deliverable. From €20,000.
A four- to eight-week sprint where a senior engineer from Craftosphere works alongside your team on one specific, bounded challenge. A sprint with a fixed goal, fixed duration, and a clear deliverable. Three kinds of sprints cover the problems we see most. A fourth, the Custom Precision Sprint, covers anything that doesn't fit the predefined ones.
How it runs
- 1
Week 0: scoping
One conversation to define the challenge and pick the right sprint type. A written scope with the deliverable, the duration and the price. You approve before anything starts.
- 2
The sprint weeks
A senior engineer from Craftosphere works inside your codebase and your review process alongside the team: pairing, reviewing, building. Working results every week.
- 3
The last week: handover
The deliverable, documented and yours: the review practice, the playbook, and the decision records.
What you get
From €20,000
Remote by default. On-site days are agreed and priced in the scope. Prices exclude VAT.
| Sprint | Price | Choose it when |
|---|---|---|
| AI Review Sprint 4 weeks | from €20,000 | your AI review practice doesn't work |
| Architecture Decision Sprint 4-8 weeks | from €25,000 | architectural decisions keep getting relitigated |
| Quality Culture Sprint 4-8 weeks | from €30,000 | quality drift after a period of fast shipping |
| Custom Precision Sprint custom duration | price after scoping | a bounded problem that fits none of the above |
- One bounded problem solved, with the deliverable named in the scope.
- The practice, playbook or decision records that keep it solved.
- The team that did the work with us, able to do it without us.
- A before-and-after reading across the four dimensions of CODA (Comprehension and Ownership Depth Assessment) where the kind of sprint has one.
Who it's for
Engineering leaders with a specific, bounded challenge they want to unblock in weeks, not quarters. Common triggers:
- "Our AI review practice is not landing"
- "Quality drift after a period of fast shipping"
- "Architectural decisions keep getting relitigated"
- Not for open-ended advisory or a standing retainer. When the challenge isn't bounded yet, the Scorecard finds the bound first.
What to expect
Fixed goal, fixed duration, fixed price, agreed in writing before day one. We're in the codebase with the team, on site or remote. A change in scope is agreed and priced before it happens. Where AI is in the loop we say so, and we show the judgment that made the result trustworthy.
Questions engineering leaders ask
No. The first conversation is enough to pick a Dojo track or scope a Sprint. A Scorecard before and after gives you the measured change if you want it.
The Custom Precision Sprint is for that, priced after scoping and agreed in writing like the others. If the problem isn't bounded yet, a Scorecard finds the bound first.
The engineers closest to the challenge work with us for part of their week. The rest of the team keeps delivering. The exact hours are in the scope.
Only by a new written scope. The price and the duration agreed at the start don't change.
What a program at scale taught us: the case study.