That claim runs against a lot of founder instinct. Most people building something new assume the work is to make the thing better — sharper design, more features, a cleaner build. But if brilliance were the bottleneck, good products would rarely fail, and mediocre ones would rarely succeed. Anyone who has watched a well-engineered product sit unsold while a rougher competitor takes the market knows that isn’t how it works. The bottleneck sits somewhere else entirely: in the person selling it, in the buyer’s math, and in the story that makes the whole thing believable.
This matters most right at the point where founders are deciding whether to pour money into manufacturing, marketing, or a bigger team. That decision is expensive to reverse. The three signals below are cheap to test before you make it — through conversation and observation, not through building more product.
Why "It’s a Good Product" Isn’t a Strategy
Anyone who has studied how inventions actually reach a market recognizes a recurring failure pattern: teams gather evidence about whether customers want the thing far too late, often after most of the capital is already spent. The technical term for the gap where good technologies stall between research and real commercial investment is the "valley of death," and it exists partly because validation happens after the money, not before it. The three-signal approach described here is really a way of forcing that validation earlier, cheaply, using nothing more than attention and a few honest conversations.
The signals themselves are not exotic. They are: whether the person behind the product has put real skin in the game, whether the product moves a number the customer already cares about, and whether there’s a real story connecting the product to the problem it solves. None of the three describes the product. All three describe the person, the buyer, and the reason the thing exists at all.
Signal One: Is the Founder Actually All In?
The single strongest predictor is whether the inventor believes in the product enough to fund it, staff it, and stay with it before it’s proven — not after demand shows up, when it’s too late to catch up. This isn’t a romantic idea about hustle. It’s a practical filter: a founder who won’t invest their own time or money is quietly telling you the risk-adjusted upside doesn’t look worth it to the one person with the most information.
There’s a mirror-image version of this signal on the investor side. People who fund very early-stage companies look for tangible progress beyond a slide deck — a prototype, evidence from real customer conversations, a clear plan for how new capital gets spent. They aren’t asking founders to prove the market yet. They’re asking founders to prove they’re the kind of person who will keep showing up when the market doesn’t cooperate.
Commitment isn’t a dollar figure, and it isn’t measured by whether someone has quit a day job. It shows up in smaller, more observable behaviors:
- Signals of commitment: funding the first production run before a single order is confirmed; personally taking customer calls instead of outsourcing them; pre-selling before the product exists; being able to describe, in detail, three conversations with real prospective buyers from the past month.
- Signals of avoidance: waiting for the product to be "perfect" before talking to anyone who might buy it; hiring an agency to generate demand before confirming anyone wants the thing; treating a wave of unexpected orders as a happy accident rather than something to plan for; being unable to name a single specific customer objection.
The test isn’t whether a founder is spending a particular amount of money or working a particular number of hours — it’s whether their behavior shows they expect to be believed, and are backing that expectation with something they’d lose if they’re wrong.
Signal Two: Does It Move a Number the Customer Already Cares About?
This is the signal most founders skip, because it requires admitting the product itself isn’t the selling point — the customer’s arithmetic is. Buyers, whatever they’re purchasing, are quietly running the same calculation: what do I get back, minus the risk of switching to you. Farmers make this calculation with unusual honesty because every purchase competes directly against a season’s yield — will this cut my cost or grow my crop, full stop. Every other buyer runs the same math; they’re just less transparent about showing it.
The mistake founders make in customer conversations is leading with the product instead of listening for the buyer’s own metric. The fix is almost entirely about question design. Closed questions ("Would this save you time?") invite polite agreement and tell you almost nothing, because people are wired to be agreeable with strangers. Open questions — "Tell me about the last time this problem cost you something" or "Describe how you currently deal with this" — let the customer supply their own number, in their own words, without being nudged toward the one you hoped to hear. Interviewers who talk roughly 20% of the time and let the customer talk the other 80% consistently surface the real metric faster than interviewers who lead the conversation. In one documented case, this discipline didn’t just surface a number — it revealed the interviewer was targeting the wrong customer entirely, because open questions uncovered that the people most bothered by a problem weren’t the people using the product, but the people around them. That’s the value of resisting the urge to explain your idea: sometimes the conversation tells you who should actually be answering the question.
A concrete illustration of "moving the number" comes from a mechanic-turned-inventor who built agricultural machinery after seeing firsthand how much labor and fuel farmers were burning on tasks that could be automated. His high-capacity water pump, introduced when he calculated it could do the work of roughly twenty laborers across a hectare of crops, wasn’t sold on cleverness — it was sold on hours and wages saved, numbers a farmer could check against their own ledger. That specificity — a number a buyer can verify themselves — is what separates a pitch from a purchase.
If you can’t say exactly what number your product moves and by roughly how much, you don’t yet have a product the market will buy. You have a clever idea waiting for its business case.
Signal Three: Is There a Real Story to Tell?
The third signal is easy to dismiss as marketing polish, but it does load-bearing work. A story is what makes the number believable and gives anyone selling the product — including the founder — something concrete to say. Spectacle draws a crowd; a crowd isn’t a sale. The buyers who actually convert are usually the ones who heard that the product came from someone who hit the exact problem themselves, got frustrated, and built the fix.
You don’t need a polished narrative to find out if this signal exists — you need a short, honest interview with yourself or your co-founder:
- What problem did you personally run into that made you build this, rather than just complain about it?
- Who else, besides you, runs into this same problem regularly? Can you name three of them?
- What did you try before building your own fix, and why didn’t it work?
- What would you tell someone who asked, "Why should I trust that this actually solves my version of the problem?"
If the honest answer to the first question is "I saw a market opportunity," that’s not disqualifying — plenty of good products start as opportunities rather than personal frustrations. But it does mean the origin-story signal will carry less commercial weight for you than for a founder who lived the problem, and you’ll need to lean more heavily on the quantified-return signal to compensate. A real story matters more to some buyers than others: a farmer buying a pump built by someone who farms is buying trust as much as machinery; a procurement officer evaluating enterprise software is running a spreadsheet, and the number will usually outweigh the biography.
Running the Audit
Because these three signals are observable, they can be checked before you commit to manufacturing tooling, a marketing budget, or a fundraising round — with a conversation, not a factory order. The table below turns each signal into something testable this week.
| Signal | What "yes" looks like | What "no" looks like | How to test it |
|---|---|---|---|
| Founder commitment | Founder has funded a first batch, pre-sold, or personally run customer calls before demand appeared | Founder is waiting for the product to "prove itself" before investing time or money | Observation: track your own last 30 days of decisions and spend |
| Quantified return | You can state the exact number moved (cost cut, hours saved, revenue gained) and roughly by how much | You can only describe features or benefits, not a number the buyer would recognize | Open-ended customer interviews, 80% listening, no leading questions |
| Origin story | A specific person and problem can be named, with others who share it | The product exists because of a market gap you noticed, with no personal stake in the problem | Self-interview: name the problem, the person, and three others who face it |
When the Signals Disagree
Rarely do all three line up cleanly on the first pass, and that disagreement is itself useful information about where to spend the next round of effort.
If you have genuine founder commitment and a strong origin story, but customers can’t name a return, the problem probably isn’t your story — it’s your value proposition, or how you’re framing it. Two different fixes apply depending on which. If customers understand the problem but describe the benefit in vague terms ("it would help"), the issue is likely positioning: you haven’t translated the product into the buyer’s own metric yet, and a sharper set of discovery questions may surface a number that was there all along. If customers can’t connect the problem to any measurable cost or gain at all, the issue is more structural — the product may not currently move anything the buyer tracks, and no amount of storytelling will manufacture a return that isn’t there. A compelling personal narrative earns trust, but trust alone doesn’t move a customer’s spreadsheet if there’s no number behind it.
If the return is clear and quantified but the founder shows the avoidance behaviors described above — no personal capital, no direct customer contact, waiting for the "right" moment — the fix isn’t a better pitch. It’s a harder look at whether the person behind the idea is willing to be the one who builds the market, because a proven number in someone else’s hands rarely sells itself.
One Caveat: Signals Aren’t Guarantees, and They Don’t Travel Evenly
None of this promises a product will succeed or generate meaningful revenue — it only tells you whether the three most common, testable failure modes are present before you spend serious money finding out the hard way. The three signals were sharpened in physical-product and agricultural markets, where buyers do visible arithmetic and founders often self-fund early runs; in software or services, capital commitment can look different — a founder backed by an institutional pre-seed round is not necessarily less committed, just committed differently. And even where these signals hold, they interact with things outside a founder’s control — market timing, competition, execution quality — that no interview can fully surface.
It’s also worth remembering that customer signals aren’t the whole story once a product does start selling, particularly in business-to-business markets. Internal teams — sales reps, support staff — need to be primed and confident in a new product’s value before it reaches the field, or even a well-validated product will stall because the people supposed to sell it don’t yet believe in it either. The three-signal audit gets you to the starting line with real evidence instead of hope. What happens after that first sale is its own discipline, built on the same principle: keep listening, keep testing, and let the evidence — not the enthusiasm — decide what happens next.
