"Build something you'd use yourself."
"Scratch your own itch."
"You are your first customer."
This advice is everywhere. It's in every startup book, every podcast, every Twitter thread from successful founders.
And it's dangerously incomplete.
Don't get me wrong—some of the best companies started this way. Basecamp. Notion. Linear. But survivorship bias is hiding the thousands of "scratch your own itch" startups that failed.
Let me explain why this advice fails more often than it works—and what to do instead.
The Appeal of Building for Yourself
I understand why this advice is popular. It feels right.
The benefits seem obvious:
- You understand the problem deeply
- You can be your own beta tester
- You're motivated by personal pain
- You don't need customer interviews (you ARE the customer)
But here's what this advice ignores:
- Your problem might not be anyone else's problem
- Your solution might not be how others want to solve it
- Your willingness to pay might not match the market's
- Your use case might be an edge case
Let me break each of these down.
Failure Mode #1: Your Problem Is Too Niche
I once met a founder who built a tool for managing fantasy sports leagues for competitive Settlers of Catan players.
Yes, really.
He was scratching his own itch. He was in a competitive Catan league. They needed better tournament management. He built it.
The market? Maybe 500 people worldwide.
This is an extreme example, but variations of it happen constantly. Developers build tools for developers at their specific company size, using their specific tech stack, with their specific workflow quirks.
The problem: You're not a representative sample. Your pain points might be artifacts of your unusual situation.
The test: Can you find 100+ strangers on the internet complaining about this exact problem? If not, your itch might be uniquely yours.
Failure Mode #2: You'll Build For Power Users
When you build for yourself, you build for someone with:
- High technical literacy
- Patience for complexity
- Tolerance for rough edges
- Motivation to figure things out
In other words, you build for power users.
The problem: Power users are a tiny fraction of any market. The mass market wants simplicity, not features.
I've watched technical founders build products that are incredibly powerful and completely unusable by normal people. They can't see the complexity because they're swimming in it.
Example: A developer builds a note-taking app with:
- Markdown support
- Vim keybindings
- Git-backed sync
- Plugin architecture
They've scratched their itch beautifully. And they've built a product that 95% of potential users will bounce from in 30 seconds.
The test: Can your mom use it? Can someone with zero technical background accomplish the core task in under 2 minutes?
Failure Mode #3: Your Willingness to Pay ≠ Market's
Solo developers often have weird spending patterns.
They'll pay $200/year for a JetBrains IDE but refuse to pay $5/month for a productivity app. They'll happily use a free tier forever. They'll build their own version before paying for someone else's.
The problem: If you're building for people like yourself, and people like yourself don't pay for software, you don't have a business.
I know a founder who built a beautiful developer tool. He would have paid $50/month for it easily. His target market of developers? They expected it to be free, complained about a $9/month price, and churned at 15% monthly.
The test: Not "would I pay for this?" but "do people ALREADY pay for this?" Check if competitors have paying customers. Check if adjacent products charge successfully.
Failure Mode #4: You'll Skip Validation
This is the sneakiest failure mode.
When you're scratching your own itch, you convince yourself you don't need validation. After all, you know the problem exists—you live it every day.
The problem: Validation isn't about confirming the problem exists. It's about confirming:
- Enough people have this problem
- They're actively seeking solutions
- They're willing to pay for solutions
- Your solution approach resonates
"I have this problem" proves exactly one data point. You need hundreds.
I've seen founders skip customer interviews, skip market research, skip competitive analysis—all because "I'm the target customer, I know what they need."
The test: Have you talked to 20+ potential customers who aren't you? Have you heard them describe the problem in their words?
What Actually Works: Informed Scratching
I'm not saying ignore personal experience. That's a valuable input. But it's ONE input.
Here's a better framework:
Step 1: Validate the Problem Is Widespread
Before building anything:
- Find 100+ people discussing this problem online
- Identify existing solutions they're using (even bad ones)
- Confirm the problem exists outside your bubble
If you can't find evidence of widespread pain, your itch might be personal.
Step 2: Validate Your Solution Approach
Your intuition about the solution is informed by your specific context. Test it:
- Show mockups to 10 potential users
- Ask: "How would you expect this to work?"
- Listen for confusion, alternative approaches, missing features
You might discover others want to solve the problem completely differently.
Step 3: Validate Willingness to Pay
Before you build:
- Check if competitors charge (and if customers pay)
- Ask potential customers what they currently spend on this problem
- Test price sensitivity with landing page experiments
If nobody's paying for solutions in this space, you need to understand why.
Step 4: Build With, Not Just For, Customers
Even if you're the target customer, involve others:
- Beta test with people who aren't you
- Prioritize features based on customer feedback, not your preferences
- Watch real users struggle (you'll be humbled)
Your experience is valuable but incomplete.
When "Scratch Your Own Itch" Actually Works
This advice succeeds when:
1. You represent a large market segment
If you're a typical example of your target customer—similar needs, similar technical level, similar budget—your intuition is more reliable.
2. The problem is clearly underserved
If existing solutions are obviously terrible and you have expertise to build better, personal experience is a valid starting point.
3. You combine it with external validation
The founders who succeed with this approach don't stop at their own experience. They validate obsessively. They talk to customers constantly. They question their assumptions.
4. You have relevant domain expertise
Building for yourself works better when you have deep expertise in the problem space—not just personal pain, but professional knowledge.
The Better Advice
Instead of "scratch your own itch," here's what I'd tell new founders:
"Start with problems you understand, but validate like you don't."
Personal experience gives you:
- Faster problem identification
- Intuition about solutions
- Motivation to persist
- Credibility with customers
But it doesn't give you:
- Market size confirmation
- Solution validation
- Price validation
- Product-market fit
Use your experience as a hypothesis, not a conclusion. Then test it rigorously.
The Validation Checklist
Before committing to any idea—even one scratching your own itch:
- [ ] Found 100+ people discussing this problem online
- [ ] Identified 5+ existing solutions (competitors validate demand)
- [ ] Talked to 20+ potential customers who aren't me
- [ ] Confirmed willingness to pay (not just willingness to use)
- [ ] Scored the idea across multiple dimensions, not just personal fit
- [ ] Had someone outside my bubble use a prototype
If you can't check these boxes, you're not validating. You're hoping.
The Meta-Point
"Scratch your own itch" persists because it's easy. It lets you skip the hard work of validation.
Real validation is uncomfortable:
- What if nobody else has this problem?
- What if my solution is wrong?
- What if the market is smaller than I thought?
But discomfort now is better than failure later.
The best founders I know are paranoid validators. They assume their intuition is wrong until proven otherwise. They seek disconfirming evidence as aggressively as confirming evidence.
That's not natural. But it's necessary.
Ready to validate beyond your own experience? Launchcrew helps you systematically research markets, analyze competitors, and score ideas—so you can build with confidence, not just intuition.