How to validate a startup idea before you build anything
By Terry Chapman, Founder & CEO, Start Up Partners
Founder and CEO of Start Up Partners, a venture studio in Birmingham, Alabama. Decades building technology ventures across medical imaging, data analytics, marketplaces, and medical devices.
Every founder we meet has an idea they are sure about. The hard truth is that being sure is not the same as being right. Learning how to validate a startup idea before you pour months and money into building it is the single most valuable skill an early founder can have. It is also the part most people skip.
We run customer discovery with every founder who walks through our door, and the pattern is always the same. The ideas that survive contact with real customers get stronger. The ones that do not fail cheaply, on paper, before anyone writes a line of code or builds a prototype. That is exactly the point.
Why most ideas never really get tested
Validation feels risky because it invites a no. So founders build instead. Building feels like progress, and it postpones the moment someone tells you the truth. But a polished product nobody wants is far more expensive than an honest conversation that saves you a year. The goal here is not to prove you are right. It is to find out, as fast and as cheaply as possible, whether you are.
Start with the problem, not the product
The most common mistake we see is founders who fall in love with a solution and then go looking for a problem to attach it to. Flip it. A problem worth solving has three traits, and the strongest ideas hit all three.
- It is painful enough that people already spend time, money, or awkward workarounds trying to solve it
- It happens often, not once a decade
- The people who have it can actually be reached, and they are willing to pay
How to validate a startup idea in five moves
When a founder asks us how to validate a startup idea without quitting their job or raising money first, we walk them through the same five moves. None of them require a finished product.
- 1
Write down your riskiest assumption
Every idea rests on one belief that, if wrong, sinks everything. Maybe it is that people will pay, or that they will switch from what they use today. Name that single assumption first, because that is what you are actually testing.
- 2
Find ten people who have the problem
Not friends, not family. Ten people in your real target market. If you cannot find ten, that is a finding too, and a cheap one to learn now rather than after you build.
- 3
Interview, do not pitch
Ask them how they handle the problem today, what they have tried, and what it costs them in time or money. Listen for the workarounds. Do not describe your solution yet, because the moment you pitch, people get polite and stop telling you the truth.
- 4
Ask for a small commitment
Talk is cheap, so test for action. A preorder, a deposit, a signed letter of intent, a spot on a paid waitlist. What people do with their wallet or their calendar tells you far more than what they say.
- 5
Decide, adjust, or walk away
Look at the evidence honestly. Strong signal means build. Mixed signal means narrow the problem or the audience and test again. No signal means save yourself a year and move on. All three outcomes are wins.
What a validated idea actually looks like
Validation is rarely a clean yes. It is a stack of small, real signals all pointing the same direction. After dozens of customer discovery conversations, here is what we look for before we tell a founder it is time to build.
- 1People described the problem in their own words before you did
- 2They are already paying for a worse solution, or losing real money living without one
- 3At least a few of them committed something real: money, time, or a written promise to buy
- 4You can clearly name who the first customer is and where to find more of them
You do not have to validate alone
Customer discovery is uncomfortable, and it is easy to hear what you want to hear. That is why we sit in it with the founders we work with. Validation is the first stage of our Concept to Company framework, and we run it shoulder to shoulder with you, from writing the interview script to reading the signal in the answers. You can see a few of the founders we have worked with and what came of it. Once an idea is validated and you are ready to make it real, our pre-incorporation checklist covers the week before you file.
Frequently asked
How do I validate a startup idea without any money?
You do not need money, you need conversations. Find ten people who have the problem, ask how they solve it today, and ask for a small commitment like a preorder or a paid waitlist spot. The most useful validation costs nothing but time and honesty.
How many customer interviews are enough?
There is no magic number, but ten focused conversations with people in your real target market will usually reveal a clear pattern. If ten people cannot describe the problem the way you do, that is a signal worth listening to.
What if customers say they like my idea?
Liking is not buying. People are polite, especially with founders they want to encourage. Trust what people do with their wallet or calendar over what they say. One small real commitment beats a hundred compliments.
Should I build an MVP to validate my idea?
Usually not first. An MVP tests a solution, but you validate the problem before you build anything. Start with interviews and small commitments, then build the MVP once you know the problem is real and you know who will pay for it.
When should I stop validating and start building?
When the signals stack up: people describe the problem unprompted, they are already paying to solve it, and a few have committed something real. At that point more research is just procrastination, and it is time to build.