What a Sprint is
A four-to-six week engagement to ship one thing — well — that the floor will actually use. Document generation, intake flow, reporting, guest communications, internal reporting — whatever your one biggest weekly time sink looks like.
A Sprint is closest in shape to the prequal build: scope it tight, build it well, hand it off with a runbook.
How it runs
- Week 1: Discovery. I sit with the team, watch the workflow, document the constraints, and lock scope.
- Weeks 2–4: Build. Daily check-ins; weekly demos.
- Weeks 5–6: Deploy, train, watch, fix.
- +2 weeks: Post-launch support — because the real bugs show up after the team uses it under load.
What you get
A working tool, the runbook to operate it, and the team trained to use it. No dependency on me afterwards — that's the whole point.