*Most startups don't fail because the founder couldn't execute. They fail because nobody actually wanted the thing being executed. Here's how to find that out before you spend six months building it.*
Table of Contents
1. Why Validation Matters More Than Execution
2. Fake Validation vs Real Validation
3. The Validation Ladder: A Four-Stage Framework
4. How to Talk to Customers Without Lying to Yourself
5. The Signals That Actually Predict Success
6. Cheap, Fast Ways to Test Before You Build Anything
7. When to Stop Validating and Start Building
8. Validation Mistakes That Waste Months
9. A Step-by-Step Validation Checklist
10. FAQ
---
1. Why Validation Matters More Than Execution
A founder who builds the wrong thing extremely well has still built the wrong thing. Execution quality gets most of the attention in startup advice, because it's visible and measurable: the product shipped, the code is clean, the launch went smoothly. Whether anyone actually needed it in the first place is a much quieter question, and it's the one that determines everything else.
Most startup failures trace back to this exact gap, not a lack of effort or skill, but months spent building something nobody was waiting for. Validation isn't a box to check before the real work starts. It is the real work, at least for the first stretch of a company's life, and treating it as a formality is how founders end up executing flawlessly on an idea nobody wanted.
2. Fake Validation vs Real Validation
Most founders believe they've validated an idea when what they've actually collected is encouragement, which is a completely different thing and considerably less useful.
**Fake validation** looks like: friends and family saying it's a great idea, a survey where people say they'd probably use something like this, a LinkedIn post getting enthusiastic comments, a handful of people saying "yes, I'd pay for that" in a hypothetical conversation. All of this feels like proof. None of it costs the person saying it anything, and people are reliably generous with opinions that cost them nothing.
**Real validation** looks like: someone actually opening their wallet before the product exists, a waitlist with real information attached rather than just an email address, a genuine change in someone's current behavior because of what you're offering, a signed letter of intent from a business customer. The common thread is cost. Real validation always requires the person validating to give up something, money, time, current habits, and that cost is exactly what makes it trustworthy in a way encouragement never is.
3. The Validation Ladder: A Four-Stage Framework
Validation isn't a single yes-or-no question. It's a sequence of increasingly expensive commitments, and skipping a rung is how founders end up building something that passed an earlier, easier test but fails the one that actually mattered.
**Rung one: Problem validation.** Does this problem actually exist, and does it hurt enough that people are already doing something imperfect to solve it? If nobody's cobbling together a spreadsheet, a workaround, or a competitor's product to deal with this, the problem likely isn't painful enough to build a business around yet, no matter how real it sounds in theory.
**Rung two: Solution validation.** Does your specific approach to the problem resonate once people actually see or hear it described concretely? This still isn't about money. It's about whether the mechanism itself makes sense to the person experiencing the pain, described specifically enough that they could explain it back to you.
**Rung three: Willingness to pay.** Will someone commit money, or something equally costly, before the product fully exists? This is the rung most founders skip because it's the first genuinely uncomfortable one, and it's also the single most predictive signal on the entire ladder.
**Rung four: Willingness to scale.** Will this work repeat itself with the next ten customers, not just the first enthusiastic one? A single person paying for something proves less than founders think. The same result repeating across a handful of unconnected people is what starts to look like an actual market instead of one generous early believer.
Most founders stop at rung two and proceed as if they've reached rung four. That gap is where a huge share of failed startups actually originate, not in the building, but in mistaking encouragement for commitment months before the first line of code.
> **Validating alone means guessing at your own blind spots.**
> BNC's free chat groups on X, WhatsApp, and Telegram are full of founders who've been through this exact process and will tell you honestly where your idea sits on the ladder.
> [Join the free chat groups at businessnetworking.club/chatgroups](https://businessnetworking.club/chatgroups)
4. How to Talk to Customers Without Lying to Yourself
Customer conversations are the most common validation tool and the most commonly done badly. The failure mode is almost always the same: leading questions that make it easy for a polite stranger to agree with you.
Asking "would you use something that does X?" invites a polite yes from almost anyone, because agreeing costs the other person nothing and disagreeing feels confrontational. Better questions dig into current behavior instead of hypothetical future behavior: "walk me through the last time you dealt with this problem," "what have you already tried," "what did that cost you, in time or money." Past behavior is far harder to fake politely than a hypothetical opinion about the future.
The single most useful moment in any validation conversation is the one most founders rush past: silence after asking about the problem. Let the person describe their actual frustration in their own words before offering your solution. A founder who pitches too early contaminates the rest of the conversation, because everything the person says afterward is now a reaction to your pitch instead of an honest description of their own experience.
5. The Signals That Actually Predict Success
Not all positive signals carry equal weight, and treating them as interchangeable is a common validation mistake.
**Weak signals:** verbal enthusiasm, a "yes I'd use that," social media engagement on a post describing the idea, friends and family encouragement. All worth noting. None worth building a business around alone.
**Strong signals:** a waitlist that required real information, not just an email, a pre-order or deposit before the product exists, a letter of intent from a business customer with a specific number attached, someone actively trying to pay you before you've built a way for them to. The strength of a signal correlates almost directly with what it cost the person to give it.
**The strongest signal of all** is often invisible until you look for it directly: people already spending time or money on an imperfect workaround for the exact problem you're solving. A market that's already paying for a bad solution is one of the clearest indicators that a better one has a real chance.
6. Cheap, Fast Ways to Test Before You Build Anything
You don't need a working product to gather rung-three signal. A well-written landing page describing the offer clearly, with a real payment or deposit button attached, tests willingness to pay directly, often within days, for a fraction of what building the actual product would cost.
A concierge-style test, manually delivering the outcome yourself before building any software to automate it, validates whether the outcome itself is valuable, separate from the question of whether your specific technical approach works. Plenty of founders discover the outcome genuinely matters to people well before they've built anything resembling the eventual product, simply by doing the work by hand first.
Pre-selling a defined batch, a limited number of spots, a specific service delivered manually, a clear scope with a real price, forces the validation question to resolve quickly, because people either commit within the window or they don't, and a slow trickle of maybes over months is itself useful information about how real the demand is.
7. When to Stop Validating and Start Building
Validation isn't meant to continue indefinitely, and knowing when to stop matters as much as knowing how to start. Endless validation without ever building is its own failure mode, often driven by fear of a real test rather than genuine uncertainty.
A reasonable threshold: once you've collected several instances of rung-three signal, real payment or equivalent commitment, from people who don't know you personally and aren't validating out of politeness, you likely have enough to justify building a first version. Waiting for certainty beyond that point usually isn't gathering more useful information. It's avoiding the discomfort of finding out for real.
8. Validation Mistakes That Waste Months
**Asking leading questions.** Framing questions in a way that makes agreement the polite, easy answer produces validation that says more about social dynamics than actual demand.
**Only talking to people who already like you.** Friends, existing network, warm introductions are useful for early conversations but structurally biased toward encouragement. Real validation requires reaching strangers who have no reason to be kind about it.
**Treating one enthusiastic response as proof.** A single generous early believer is a data point, not a market. The willingness-to-scale rung exists specifically to catch this mistake before too much gets built around one person's enthusiasm.
**Validating the idea instead of the specific mechanism.** "People want to save time on X" is almost always true and almost never useful. The specific version of your solution, priced and described concretely, is what actually needs testing, not the broad, sympathetic category it belongs to.
9. A Step-by-Step Validation Checklist
Confirm the problem already has an imperfect workaround people are actively using. Talk to at least ten people outside your existing network about their current behavior, not a hypothetical future product. Build a simple landing page describing the specific offer, with a real way to commit money or a deposit attached. Attempt to pre-sell or pre-book a defined batch before building the full product. Deliver the outcome manually to the first few committed customers before automating anything. Confirm the result repeats across several unconnected people, not just the first enthusiastic one. Only then, start building the version meant to scale.
FAQ
**How many customer conversations are enough?**
There's no fixed number, but a useful marker is when new conversations stop surfacing new information, roughly ten to twenty conversations outside your existing network for most early-stage ideas.
**What if nobody will pay before the product exists?**
That's a real and useful signal, not a reason to lower the bar and accept a weaker one instead. It usually means either the problem isn't painful enough yet or the specific solution described isn't the right one, both worth knowing before building.
**Can I validate a genuinely new idea nobody's seen before?**
Yes, though the focus shifts toward the underlying problem and current workaround rather than the specific solution, since a truly novel solution is harder for people to react to accurately in the abstract. The imperfect-workaround signal becomes especially important in this case.
---
> **Test your idea against founders who've actually been through this.**
> BNC's free chat groups on X, WhatsApp, and Telegram are where founders stress-test ideas honestly, before months get spent building the wrong thing.
> [Join the free chat groups at businessnetworking.club/chatgroups](https://businessnetworking.club/chatgroups)
---
**Jason Barrett** is the founder of BNC, the global network for people building businesses, and GrowthStack, an organic social revenue consultancy. He is a former Head of Digital at McCann London with credits including Microsoft, Nike and Apple. He has generated over $5.5 million in revenue through organic social systems for 400+ businesses. Jason built and sold TwitJobs in 2009 and is a Lovie Awards judge. Join the BNC community at [businessnetworking.club](https://businessnetworking.club).
Related Reading
- [Stuck at $10K MRR? Here's the Framework to Break Through](https://businessnetworking.club/blog/stuck-at-10k-mrr-framework)
- [How to Get Honest Pitch Deck Feedback](https://businessnetworking.club/blog/how-to-get-honest-pitch-deck-feedback)
- [The Ultimate Guide to Startup Networking](https://businessnetworking.club/guides/ultimate-guide-startup-networking)