Validate the idea
before you validate your assumptions about it.
Product validation tests, honestly and directly, whether real customers want what you are planning to build, before significant time and money are committed to building it.
Validating a product idea means testing, with real evidence rather than internal conviction, whether customers genuinely want what you are planning to build and would actually pay for it. This is distinct from simply believing the idea is good, however strongly that belief is held.
Product validation uses a range of lightweight methods, direct customer conversations, landing pages measuring genuine interest, small paid pilots, to gather real signal before committing to a full build, which is precisely when a wrong assumption is cheapest to catch.
The goal is not certainty, which is rarely available before real customers actually use a product, but a genuinely honest reduction in risk, replacing pure conviction with evidence wherever evidence can reasonably be gathered.
Founders and product teams are naturally inclined to believe in their own idea, which makes external, honest validation considerably more valuable than internal conviction alone, however sincerely held.
The cost of validating an idea properly is a small fraction of the cost of building a full product that turns out nobody wants, making validation one of the highest-return investments in the entire product development process.
Validation methods that only reach friendly, enthusiastic contacts tend to produce falsely encouraging signal, which is why genuine validation deliberately seeks out honest, sometimes uncomfortable, feedback from real target customers.
How it actually works: Product validation applies lightweight, honest methods, customer conversations, interest-testing landing pages, small paid pilots, to gather real evidence about demand before a full product is built, treating negative signal as genuinely useful, not as a failure to be avoided.
A structured process, not a black box.
Validation method selection
We choose the validation methods genuinely suited to your product and audience, rather than a generic, one-size-fits-all checklist.
Honest audience targeting
We seek out genuine target customers for validation, not just friendly, enthusiastic contacts likely to respond generously.
Signal gathering
We gather real evidence, conversations, interest metrics, pilot uptake, rather than relying on assumption or internal enthusiasm.
Honest interpretation
We interpret the evidence honestly, including where it points away from the original idea, rather than reading only what confirms existing belief.
Decision framing
We frame what was learned into a clear decision: proceed with confidence, adjust the approach, or reconsider the idea entirely.
Handoff into MVP or strategy
We carry validated learning directly into MVP scoping or product strategy, so the evidence gathered actually shapes what happens next.
What's technically involved
- Validation methods matched to your specific product and audience
- Genuine target customer engagement, not just friendly contacts
- Real evidence gathering: conversations, interest metrics, pilot data
- Honest interpretation, including negative or disconfirming signal
- A clear decision framework based on what was actually learned
- Direct handoff of validated learning into MVP or strategy work
Related, but distinct.
Product validation and product discovery are closely related, discovery focuses on understanding the problem and customer deeply, while validation focuses specifically on testing whether a proposed solution genuinely has demand before building it fully.
Common questions
What is the fastest way to validate a SaaS idea?
A combination of direct conversations with genuine target customers and a simple landing page measuring real interest, sign-ups or a small deposit, tends to give useful signal quickly and cheaply.
How do we know if validation results are genuinely encouraging or just friendly noise?
By deliberately seeking feedback from people with no personal stake in being encouraging, and by looking for evidence of genuine commitment, time, money, real usage, not just polite enthusiasm.
What if validation results are discouraging?
This is valuable information, not a failure. It means the idea, or its current framing, can be revisited before a costly build, which is precisely the point of validating early.
Can validation happen alongside early development?
It can, particularly through lightweight, testable increments, but the core value of validation comes from testing before significant investment is locked in, not after.
How much should we spend on validation before building?
A small fraction of what a full build would cost, since the entire purpose is reducing risk cheaply before that larger investment is made.
Product Validation works best alongside a strong technical foundation: Custom Software, Technology Partner. Explore the wider Technology Partner Knowledge Centre for more.
Let's map out where this fits in your business.
A short, honest conversation is the fastest way to know where to start.