Proximity early, ownership by the end.
A six-phase engagement: we sit with your team, prove the method on real work, then deliberately fade out. The handover is the proof.
The engagement, end to end
- 00
Immerse
Shadow the team, learn the product, meet the skeptics. Week one is for understanding and trust, not deliverables.
Week 1On-site, full-time - 01
Scope & Baseline
Pick a real, bounded problem with the PO, capture the status-quo baseline, and pre-register the gate before any code moves.
Weeks 2–3On-site - 02
Co-author Run
Your developers build the solution with 99x coaching, running the method on real work; data captured against the baseline.
Weeks 4–12On-site, easing - 03
Evaluate
Read the scorecard against the baseline; hold the promote/extend decision openly, with the team as jury.
Weeks 12–13Hybrid - 04
Iterate & Widen
Apply the learnings and begin phasing adoption into normal work; the team is now driving.
Weeks 13–16Hybrid - 05
Fade-out & Handover
Taper involvement and watch whether the practice and the numbers hold without us. The real adoption gate.
Weeks 16+Light-touch
Why on-site, and why early
The value of the first phases is closeness to the people and the product. We work from your office while we shadow, scope, and start building, because that’s where trust is earned and the right problem reveals itself. As your team takes ownership, our presence lightens. By the end, the practice and the numbers should hold without us in the room.
See it on your own team
Start with a fixed-fee diagnostic: a measured read before you commit.