Most founders don’t fail because their idea is “bad.” They fail because they spend weeks building a story instead of running experiments. If you’re in the 0–12 month phase, the fastest way to stop wasting time is to run a tight 2-week customer interview sprint designed to produce decisions, not opinions.
This is the sprint I wish every aspiring founder had before they touch their MVP.
Why a 2-week sprint beats “casual interviews”: At your stage, the goal isn’t to “learn everything.” It’s to answer three questions quickly:
Do people with the problem exist in reachable numbers?
Do they experience the problem intensely enough to change behavior?
Are you progressing towards providing a solution they would be willing to pay for or adopt?
Casual interviews usually fail because they’re unstructured. Founders ask broad questions like “How do you handle X?” or “Would you use this?” Those answers are polite, vague, and non-committal. A 2-week sprint forces you to run a specific sequence of conversations with a clear output: evidence you can act on.
The output you want by day 14 By the end of the sprint, you should have: A problem validation verdict (validated / unclear / rejected) A customer segment shortlist (who exactly you should talk to next) A list of top willingness-to-change signals (what people did, paid for, or complained about) A revised MVP scope (what you will build first, and what you will intentionally not build) A next experiment plan (what to test in week 3)
Simple framework: the 2-week interview sprint loop (4 steps) Step 1: Define the “decision” before you schedule calls Write down the exact decision you’re trying to make. Example: “Within 2 weeks, I will determine whether [target customer] experiences [problem] frequently and urgently enough that they would consider [solution category].” If you can’t state that clearly, your interviews will drift.
Step 2: Recruit for signal, not convenience Your recruiting criteria should be tied to the problem, not your network. Choose one primary segment and one backup segment. Then screen for: They currently have the problem (or had it recently) They’re the person who feels it (or influences the purchase) They’ve tried something already (tools, workarounds, vendors, DIY) They’re accessible enough to interview again (so you can iterate)
You’re not looking for “interested people.” You’re looking for people who can tell you what they actually do.
Step 3: Run interviews with a structured “story” flow Use the same interview path each time so you can compare answers. A high-signal flow:
Trigger and context: “Tell me about the last time this happened. What was going on?”
Current coping: “What did you do next? What have you tried?”
Cost of the problem: “What did it cost you (time, money, stress, missed outcomes)?”
Decision moments: “What makes you decide to change? Who else is involved?”
Solution reaction without selling: “If you could wave a wand and fix one part of this, what would you change first?”
Commitment test: “If a tool existed that did X in Y way, how would you evaluate it? What would you need to see to try it?”
This keeps you from pitching too early while still surfacing real buying criteria.
Step 4: Synthesize into a verdict and next experiment After each day, do a 20-minute debrief: What patterns repeated? What objections were consistent? What did people do instead of your idea? What evidence contradicts your assumptions?
Then at day 14, write a verdict: Validated: repeated urgency + clear alternatives + willingness-to-change signals Unclear: mixed signals or unclear segment Rejected: problem isn’t frequent/urgent, or people don’t change behavior
Mini-example: how the sprint changes the idea Let’s say you’re building “a budgeting app for freelancers.” In a casual approach, you might ask: “Would you use it?” You’ll get: “Maybe, but I already have an app.”
In the sprint, your interview script starts with the last time the problem happened: “What’s the last month you really struggled with money?” You hear: “I didn’t get paid on time, so I missed taxes and had to pull from savings. I spent hours reconciling invoices and chasing clients.”
Then you ask coping: “What did you do?” They say: “I use spreadsheets, but I still miss deadlines. I also pay an accountant, and I wish I had earlier warnings.”
Commitment test: “If you had a system that alerted you 10 days before you’d miss a tax deadline and tracked invoice cashflow, how would you evaluate it?” Now the signals are different. People mention specific pain, timing, and the cost of being late. You discover your real problem isn’t “budgeting.” It’s “cashflow timing risk and deadline avoidance.”
Verdict by day 14: You likely reject the “budgeting app” framing and pivot to “deadline + cashflow alerts for freelancers.” That’s not a small tweak. It’s a direction change that saves months.
What to say when you’re afraid of sounding naive You don’t need to be impressive. You need to be accurate. A simple opener: “I’m working on something related to [problem area]. I’m not trying to sell you. I’m trying to understand how you handle this today and what would actually make you change.”
If they ask “Is it like…?” you can respond: “I’m not sure yet what the best form is. I’d rather learn what you’d want fixed first, and what you’d need to see to try something new.”
This reduces defensiveness and increases honesty.
How many interviews you need (and how to avoid drowning) For a 2-week sprint, aim for 12–20 interviews total. That’s enough to see patterns without turning it into a second job.
Recruit in batches: Week 1: 8–10 interviews Week 2: 4–10 interviews, focused on the segment that showed the strongest signals
If you find a clear winner early, don’t keep interviewing the wrong segment. Use the sprint to compress uncertainty.
Where founders get stuck: the “landing page trap” Some founders try to validate with a landing page before they validate with conversations. Landing pages can work, but they’re a weaker signal than interviews at your stage because clicks don’t equal urgency or willingness-to-change.
A better approach during the sprint: Don’t build a full MVP. Instead, create a lightweight “problem framing” page or one-sentence value hypothesis you can test in interviews: “If we could help you [outcome] by [mechanism], would that matter to you?” You’re using it to clarify language and buying criteria, not to measure demand in isolation.
If you want co-founders or advisors, use the sprint as a magnet Your interview sprint will naturally surface people who are:
knowledgeable about the domain
connected to the problem space
responsive to collaboration
After interviews, ask one meta-question: “Do you know anyone else dealing with this who’s more intense about it?” That creates warm intros. And when you debrief your findings publicly or with peers, advisors recognize you’re doing real work.
Your next steps: a 14-day action checklist Day 1: Write your decision statement Pick one segment and one problem. Define what “validated” looks like.
Day 1–2: Build your interview recruiting screen Create 3–5 screening questions. Decide where you’ll recruit (LinkedIn, communities, forums, cold email to job titles, university groups, coworking circles).
Day 2–3: Draft your interview script Use the story flow: trigger, coping, cost, decision moments, wand fix, commitment test.
Day 3: Schedule interviews in batches Target 8–10 for week 1. Offer 20–30 minutes. Confirm with a short note: “I’ll ask about your last time dealing with X.”
Days 4–9: Run interviews and debrief daily After each interview: capture quotes, patterns, and “what they did instead.” At day’s end: update your verdict notes.
Days 10–13: Focus on the strongest segment or strongest missing evidence If people don’t show urgency, recruit for higher-intensity cases. If you’re unclear on willingness-to-change, recruit for decision-makers or budget owners.
Day 14: Publish your sprint verdict (even if it’s just for yourself) Write:
What we learned about the problem
Who the customer really is
The top willingness-to-change signals
What we will build first (MVP scope)
The next experiment to run in week 3
If you want, tell me your startup idea in one sentence and who you think the customer is. I’ll help you turn it into a decision statement and a recruiting screen you can use immediately for your first 8 interviews.