Do not index
Do not index
Over the past few weeks, I’ve been experimenting with one-week discovery sprints at Lunch Pail Labs. Traditionally, I’d start projects with a detailed scoping process, but this often felt overly theoretical, making it hard to predict every detail before diving into real code.
With discovery sprints, we focus on quick wins and tangible results. Clients pay a lower upfront fee and get to see real progress early on. (David Heinemeier Hanson has some cool thoughts on the futility of detailed project estimates here).
How It Works
Here’s how I’ve structured the process:
Clients start by filling out a routing form, which lets them book an intro call.
After the intro call, I send them a link to book a 1-week discovery sprint, where they pay the fee upfront.
The discovery sprint is already showing potential in a few key areas:
- Tangible deliverables build trust: Clients see progress right away, whether it’s a prototype or a roadmap. This creates momentum and turns early conversations into action. A scope document doesn’t always have the same level of excitement.
- Early risk reduction: By starting to build, I can identify potential integration challenges early, reducing risks and helping clients feel more confident.
- Smaller commitment, faster results: Clients invest in a one-week sprint that delivers something tangible, like a prototype or roadmap. If they choose to move forward, the discovery fee is credited towards the larger project. It’s a smaller, lower-risk step compared to committing to a large build from the start.
I’d love to hear your thoughts! Have you tried a paid discovery process like this before? Send me a note
.png?table=block&id=9ba33ac6-8e12-48f6-b980-4333b612ec56&cache=v2)