Handbook
/
Idea & Validation
How to Run a Validation Sprint in One Week
A structured process for testing your startup idea in five days, before you write any code.
Most founders spend months building before they validate. This is backwards. The goal of early-stage work is learning, not building. A validation sprint compresses that learning into one intense week.
By Friday, you’ll know whether your idea has legs—or whether you need to pivot. Here’s how to run one.
Before You Start
You need three things going in:
1.
A clear hypothesis. “I believe [customer segment] has [problem] and would pay [amount] for [solution].” Write it down. Be specific.
2.
Access to potential customers. You need to be able to reach 15-20 people in your target segment this week. If you can’t, spend the week before the sprint building that access.
3.
One week of focused time. This isn’t a side project. Clear your calendar. Tell people you’re unavailable.
Day 1: Problem Mapping
Morning: Research
Spend the morning gathering everything you can about the problem:
•
Search Google for how people describe this problem
•
Find communities (Reddit, forums, Slack groups) where these people hang out
•
Read reviews of existing solutions—what do people complain about?
•
Look at job postings to understand how companies think about this problem
•
Find any industry reports or data about the market
Document everything. You’re building a map of the problem landscape.
Afternoon: Customer Identification
Create a list of 25-30 potential customers to contact. You’ll need this buffer because not everyone will respond. Sources:
•
LinkedIn (search by job title, company, industry)
•
Professional communities you’ve identified
•
Personal network (but not friends—ask for introductions to strangers)
•
Twitter/X (search for people discussing this problem)
•
Company websites (find relevant employees)
For each person, find their email or a way to contact them. Write a short, specific outreach message explaining you’re researching this problem and asking for 20 minutes of their time.
End of Day: Send all outreach messages. Aim to have 10-12 conversations scheduled for Days 2-4.
Day 2: Customer Conversations (Batch 1)
Goal: 4-5 conversations
Use Mom Test principles. Your questions:
1.
“Tell me about your role and responsibilities.”
2.
“What’s the hardest part about [problem area]?”
3.
“Can you walk me through the last time this happened?”
4.
“What have you tried to solve this? How did that go?”
5.
“If you had a magic wand, what would you want?”
6.
“How much time/money does this cost you?”
Take detailed notes during each call. Immediately after, write a summary:
•
What did you learn?
•
What surprised you?
•
Does this validate or invalidate your hypothesis?
End of Day: Update your hypothesis based on what you learned. What patterns are emerging?
Day 3: Customer Conversations (Batch 2)
Goal: 4-5 more conversations
Same process as Day 2, but refine your questions based on what you learned. Go deeper on the themes that emerged.
Start asking about willingness to pay:
•
“What would a solution to this be worth to you?”
•
“What are you spending on this today?”
•
“If I could solve this for $X/month, would that be interesting?”
End of Day: You should have 8-10 conversations completed. You should be seeing clear patterns. If you’re not, either your customer segment is too broad or the problem isn’t consistent.
Day 4: Solution Sketching
Morning: Synthesize Learnings
Create a document summarizing what you’ve learned:
•
The core problem (in customers’ words, not yours)
•
Who has this problem most acutely
•
What they’ve tried and why it failed
•
What they would pay for a solution
•
Key insights and surprises
Afternoon: Sketch Solutions
Based on customer conversations, sketch 2-3 possible solutions. Not detailed specs—rough concepts. For each:
•
What would the core value proposition be?
•
What’s the minimum version that would solve the problem?
•
How would customers find this?
•
What would you charge?
Create simple mockups or descriptions you can show people. This could be:
•
Hand-drawn wireframes
•
A one-page concept document
•
A simple landing page (use Carrd, Webflow, or similar)
•
A slide deck
End of Day: Have something concrete you can show potential customers tomorrow.
Day 5: Validation
Morning: Solution Conversations (3-4 calls)
Go back to the most promising prospects from earlier conversations. Show them your solution concept. Questions:
•
“Based on our earlier conversation, I’ve been thinking about a solution. Can I get your reaction?”
•
Show the concept. Watch their face. Do they light up or look polite?
•
“Does this address the problem you described?”
•
“What’s missing? What would make this a must-have?”
•
“If this existed today at $X, would you buy it?”
•
“Would you be willing to be a beta tester / pay in advance / sign a letter of intent?”
The last question is crucial. Enthusiasm is cheap. Commitment is signal.
Afternoon: Decision Time
Gather your evidence and make a decision:
Green Light signals:
•
Multiple people expressed strong interest
•
At least one person made a concrete commitment (pre-order, deposit, LOI)
•
Clear, consistent problem across conversations
•
Willingness to pay at a viable price point
•
You can articulate a clear path to reaching more customers like these
Red Light signals:
•
Polite interest but no commitments
•
Problem was real but not painful enough to pay for
•
Couldn’t find enough people with this problem
•
Wildly inconsistent feedback
•
Customers liked the idea but wanted it free
Yellow Light signals:
•
Strong interest from a different segment than expected
•
Problem validated but solution didn’t resonate
•
Need to adjust price point significantly
What Comes Next
If you got a green light: Start building an MVP. Your next milestone is getting those committed early users actually using the product.
If you got a red light: Pivot. Either change the customer segment, change the problem, or abandon this idea entirely.
If you got a yellow light: Run another mini-sprint. Adjust your hypothesis based on learnings and test again with the new angle.
Common Mistakes
Not enough conversations. Five conversations isn’t enough to see patterns. Push for 10+.
Pitching instead of learning. If you spent your conversations selling, you learned nothing.
Confirmation bias. You’ll remember the positive conversations and forget the negative ones. Write everything down.
Broad customer segment. “Small business owners” is too broad. Narrow it down.
Skipping the commitment ask. Enthusiasm isn’t validation. Ask for something concrete.
Key Takeaways
•
Clear your calendar for a full week of focused validation
•
Have 10+ customer conversations using Mom Test principles
•
Look for patterns in problems, not just positive feedback
•
Always ask for concrete commitment—enthusiasm isn’t enough
•
Make a clear go/no-go decision by end of week
AIMake has access to all of this
Our AI has access to the entire Startup Handbook. Ask it anything about building your startup.
Get started →
← Previous
How to Know If Your Startup Idea Is Worth Pursuing
Next →
Signs You've Found Product-Market Fit