Introduction
Before writing a single line of code or spending money on marketing, you need to validate your business idea. This template helps you think through the critical questions that determine whether your startup has a real chance — and identify the assumptions that could kill it early.
Based on lean startup methodology and the Business Model Canvas, this framework forces you to articulate your hypotheses clearly so you can test them quickly.
Part 1: Business Hypothesis
1. What problem are you solving?
Describe the specific pain point your customers experience. Be concrete — avoid vague statements like “people need better productivity tools.”
Good: “Freelance designers spend 3-4 hours per week chasing late invoice payments, causing cash flow problems.”
Bad: “People need better invoicing software.”
2. What is your solution?
How does your product or service solve the problem? Describe the core mechanism, not the features.
Example: “Automated payment reminders with one-click payment links that reduce average payment time from 45 days to 7 days.”
3. Who are your initial customers?
Be specific. “Everyone” is not a customer segment. Define:
- Industry or profession
- Company size or demographic
- Geographic location
- Specific behavior or characteristic that makes them a good fit
Example: “Freelance designers and developers in the US with 2-10 clients, billing $5,000-$50,000/month.”
4. What is the primary value your customers get?
What is the single most important outcome your customer achieves? Focus on the result, not the feature.
Example: “Get paid faster — reduce average invoice payment time by 80%.”
5. What additional benefits do customers get?
Secondary value beyond the primary benefit:
- Time saved
- Stress reduced
- Professional image improved
- Data/insights gained
6. How will you acquire your first customers?
Be specific about channels and tactics:
- Direct outreach (LinkedIn, email, cold calls)
- Content marketing (blog, YouTube, SEO)
- Communities (Reddit, Slack groups, forums)
- Partnerships
- Paid advertising
- Product Hunt / AppSumo launch
7. How will you make money?
Define your revenue model:
- Subscription (monthly/annual)
- Per-transaction fee
- Freemium with paid upgrades
- One-time purchase
- Usage-based pricing
- Services/consulting
Include pricing tiers if applicable.
8. Who are your main competitors?
List direct and indirect competitors. For each, note:
- Their primary strength
- Their primary weakness
- Why customers choose them
9. Why will you beat the competition?
Your sustainable competitive advantage — what makes you different in a way that matters to customers and is hard to copy:
- 10x better on a specific dimension
- Unique distribution channel
- Network effects
- Proprietary data or technology
- Specific expertise or relationships
10. What are the biggest risks?
List the top 3-5 assumptions that, if wrong, would kill the business:
Example risks:
- Customers won’t pay for this (willingness to pay)
- The problem isn’t painful enough to change behavior
- The market is too small
- Acquisition cost is too high relative to lifetime value
- A large competitor could copy this in 3 months
11. How will you know if you’ve succeeded?
Define the specific customer behavior change that signals product-market fit:
Example: “When 40% of users who try the product are still using it after 30 days, and at least 3 customers say they’d be ‘very disappointed’ if the product disappeared.”
12. What other assumptions could invalidate the business?
Beyond the main risks, what else could go wrong?
- Regulatory changes
- Technology dependencies
- Key person dependencies
- Seasonal demand
- Economic sensitivity
Part 2: User Hypothesis
1. Who is your user?
Describe a specific person (not a demographic):
- What is their job/role?
- What does their typical day look like?
- What tools do they currently use?
- What are their goals and frustrations?
Create a user persona with a name, photo (stock), and story.
2. Where does your product fit in their life?
- When do they encounter the problem you solve?
- What triggers them to look for a solution?
- What are they doing right before and after using your product?
3. What problem does your product solve for them?
From the user’s perspective — not your perspective. Use their language.
4. When and how will they use your product?
- Frequency of use (daily, weekly, monthly)
- Context (at work, at home, on mobile)
- Alone or with others
- Triggered by an event or habitual
5. Which features are most important?
Rank the top 3-5 features by importance to the user. Be ruthless — most features are nice-to-have, not must-have.
Must-have: Without this, the product doesn’t solve the problem. Nice-to-have: Improves the experience but not essential for initial launch.
6. What should the product look and feel like?
- Simple or powerful?
- Consumer-grade or enterprise?
- Fast and minimal or feature-rich?
- What existing products do users love and why?
Part 3: Validation Plan
Before building, validate your key assumptions:
Customer Discovery (Week 1-2)
Talk to 10-20 potential customers. Ask:
- “Tell me about the last time you experienced [problem].”
- “How do you currently handle it?”
- “What have you tried? What didn’t work?”
- “How much time/money does this cost you?”
Do not: Pitch your solution. Listen.
Problem Validation (Week 2-3)
Confirm the problem is real and painful enough:
- At least 7/10 interviews confirm the problem exists
- Customers describe it as a significant pain point
- They’ve tried to solve it (shows motivation)
Solution Validation (Week 3-4)
Show mockups or a simple prototype:
- Customers understand the solution immediately
- At least 3 customers say “I would pay for this”
- At least 1 customer offers to pay now (pre-order)
MVP Definition
Based on validation, define the minimum feature set:
- What is the smallest thing you can build that delivers the core value?
- What can you cut without losing the core value proposition?
- What is the fastest way to get this in front of paying customers?
Resources
- The Lean Startup — Eric Ries
- The Mom Test — Rob Fitzpatrick — how to talk to customers
- Business Model Generation — Osterwalder
- Y Combinator Application — great questions to answer for any startup
- Indie Hackers — community of bootstrapped founders
Comments