30 days to validate or kill your idea.
Validate what the market wants in 4 weeks. A clickable prototype, 5 user tests, and a defensible go/no-go decision.
Walk out with a decision, not another report that dies in a drive.
PDF studies decide nothing. Rushed MVPs burn runway on hunches. Between them: a real prototype, tested by users, backed by research.
What you walk away with
- [01]
A defensible go/no-go decision argued by the data, not by a designer’s opinion.
- [02]
A clickable prototype of the critical journey, tested by 5 real users.
- [03]
A competitor and market benchmark you can defend in front of a board or a VC.
- [04]
A board-ready deck packaging research, user feedback, and the recommendation in one place.
What the sprint covers.
Four pillars in four weeks: research, personas, prototype, user tests. Defensible assets, not decks.
[01]
Market benchmark
Know where you stand vs the competition.
Map of the active players, products, and pricing in your segment
Audience analysis: who they are, what they already pay for
A sharp formulation of the key need and the primary problem to solve
[02]
Personas & critical journey
Lock the journey your MVP has to nail.
Personas grounded in real desk research, not stock archetypes
The one critical journey the MVP has to nail end to end
First MVP screens you can already react to in week two
[03]
Clickable prototype
A testable artefact your users can react to.
A real Figma prototype of the critical journey, click-through ready
AI-assisted production so 4 weeks is enough for something testable
Iteration reviews so you steer the design before users touch it
[04]
Real user tests & readout
5 users decide if you ship or pivot.
Recruitment of 5 real users in your target segment (handled for you)
Moderated test sessions and a clean synthesis of what surfaced
A live readout: argued go / no-go / pivot, plus 1 included iteration
Sprint agenda.
Four weeks, fixed cadence. Each week feeds the next, and the readout is built into the schedule.
[Week 0]
Framing
One working session to lock the market hypothesis, the target segment, and the validation criterion the sprint will be argued on. You leave with a brief everyone agrees to.
[Week 1]
Market research
Benchmark of competitors and active players, audience analysis, sharp formulation of the key need and the primary problem to solve. The narrative the prototype is going to test.
[Week 2]
Design & personas
Personas grounded in the research, the one critical journey the MVP has to nail, and the first MVP screens you can already react to. Direction is locked here.
[Week 3]
Prototyping
Clickable prototype of the critical journey in Figma, accelerated with AI tooling so 4 weeks is enough for something real. Iteration reviews so you steer it before users touch it.
[Week 4]
Tests & readout
Moderated tests with 5 real users in your target segment, synthesis of what surfaced, and a live readout: argued go / no-go / pivot recommendation. 1 iteration included.
[Follow-up]
After the readout
One included iteration after the live readout, so the recommendation can absorb a follow-up question or a board ask without becoming a new engagement.
Meet the Design Strategist.
Lucas Rappart
Senior Product Designer
8+ years · 15+ products shipped
I’ve designed products from zero across investment, energy, cybersecurity, and editorial — Foodhack (now KAPITAL), Le Temps Chronos, Hafnova DoHzel. The throughline is the same: turn a fuzzy product intuition into something real enough that the right users can react to it.
The sprint is the packaged version of that work. User research that actually talks to your segment, paired with senior product design — the two skills a founder alone can’t hold both of inside four weeks.
No idea-stage workshops, no PDF that dies in a drive. Maximum two sprints a month so each one gets the attention it’s priced for, and a Decision Guarantee that puts the risk on me, not on you.
Book a discovery callWho this sprint is for.
You have a strong product intuition and no real proof the market wants it.
You’re hesitating between two or three segments or problems to attack.
Your board or your investors want a tested proof before they finance the build.
You’re entering a new market and refuse to commit a quarter of dev blind.
Who this sprint is not for.
You already have product–market fit and want to scale execution.
You expect a 100-page market study, not a working prototype you can test.
You can’t commit time or access to your target users for 4 weeks straight.
You want an outsourced product manager, not a decision tool with a deadline.
Inside the sprint.
Competitor & market benchmark
Active players, audience analysis, key need, primary problem to solve — packaged so you can hand it to a board without rewriting.
Personas + critical journey
Personas built from the research and the one critical journey the MVP has to nail. The spine of everything tested.
Clickable Figma prototype
A real prototype of the critical journey, click-through ready. AI tooling used where it earns its keep on speed.
5 user tests + synthesis
Moderated tests with 5 real users in your target segment, plus a clean synthesis of what surfaced — the spine of the recommendation.
Live readout + 1 iteration
Argued go / no-go / pivot recommendation in a live session, plus one included iteration so a follow-up question doesn’t become a new engagement.
Bonuses included
S0 framing offered
One working session before the sprint starts to define the market hypothesis and the validation criterion. So the sprint is argued on the right question.
Recruitment of 5 testers included
Sourcing real users in your segment is usually the bottleneck. I handle it, from outreach to scheduling.
Board-ready validation deck
Research, user feedback, and the recommendation packaged into a deck you can hand to a board or a VC without rewriting.
1 iteration after the readout
One included follow-up iteration so a board question or a refinement of the recommendation doesn’t open a new engagement.
Decision Guarantee
If at the readout you don’t walk away with a clickable prototype tested by 5 real users and a defensible go / no-go recommendation, I keep working until you do — or the final installment isn’t due.
Hard cap on capacity
Maximum 2 sprints per month. One facilitator, 4 intensive weeks each. So the sprint you book actually gets the attention it’s priced for.
Frequently asked questions.
Four weeks feels too short to validate a market.
The sprint doesn’t validate the whole market. It validates a precise hypothesis on a precise segment, with a testable proof. That’s what unblocks the decision. Validating the whole market is what the next year of execution is for.
We could run this in-house. We have a PM.
You could, if you have the time, the access to 5 real users in the right segment, and the senior recall on how to read the feedback. The sprint buys you founder time, not a missing skill. If you have all three, run it internally.
How is the price set?
The forfait is benchmarked against the cost of the decision, not against a day rate. The starting tier covers a focused single-segment hypothesis; broader scopes (multi-segment, B2B + B2C, deeper benchmark) move up from there. We confirm the scope and the price on the discovery call.
What if the recommendation is “no-go”?
That is exactly the point. Catching a no-go in week 4 instead of month 6 is what the sprint is built for. A precise no-go is a sprint success, not a failure — it’s a quarter of runway saved.
Will you really find 5 real users in our segment?
Recruitment is included (bonus). Sourcing combines your network where it makes sense, and external sourcing in the right segment when it doesn’t. If 5 real users aren’t reachable in 4 weeks for your segment, we’d catch that in S0 before kick-off.
How does the discovery call work?
A 30-minute call to qualify whether your hypothesis is actually “validatable” in 4 weeks. No pitch, no pressure. If the hypothesis isn’t a good fit for a sprint, I’ll tell you on the call.