I've had some version of this conversation over 300 times. A founder walks in — smart, driven, clearly onto something — and within the first ten minutes, I can see the problem. They are three steps ahead of where the evidence actually puts them.
They've built a product. They have some users. Maybe they even have some early revenue. And they're already talking about scaling, about Series A timing, about the enterprise market, about international expansion. The pitch is polished. The TAM slide is impressive. The vision is genuinely compelling.
And when I ask the question — why do your customers pay for this, and what happens if they stop? — the answer gets soft.
That's the business model question. Most founders haven't answered it yet. Not really.
The distinction that matters
A product solves a problem. A business model answers a different set of questions: Who pays? How much? How often? Why do they keep paying? What happens to the economics as you scale?
These questions sound basic. They're not. I've seen companies with millions of users who couldn't answer them. I've seen companies with significant revenue who had never honestly examined whether the unit economics worked. I've seen founders who knew their product inside and out but had never sat across from a customer and asked directly: If this went away tomorrow, would you pay to get it back? How much?
The willingness to ask that question — and to accept the answer honestly — is what separates founders who are building businesses from founders who are building products. Both are legitimate things to build. Only one of them supports a venture-scale outcome.
"Most founders fall in love with their solution before they've fully proven the problem. Customer discovery isn't a box to check. It's the most important work a founder does before they build anything."
The three steps founders skip
When I say founders are three steps ahead of the actual problem, I mean something specific. Here are the steps that typically get skipped:
Step one: Is the problem real? Not real in the sense that people say they have it — real in the sense that it's painful enough to motivate action. There are thousands of problems people acknowledge exist. Very few of them are painful enough that people will pay money, change their behavior, or go through organizational friction to solve them. Before you build anything, you need evidence — not surveys, not interest, but actual behavioral evidence — that this problem is one people will act on.
Step two: Is your solution the answer? People who have a real problem already have a solution, even if it's a bad one. They've built a workaround. They're tolerating the pain. They're using something inferior. Your job is not to prove that the problem exists — they've already proven that by living with it. Your job is to prove that your solution is better enough that they'll go through the friction of switching. That's a different question, and most founders skip to it without adequately answering step one.
Step three: Will they pay what the economics require? This is where most business models quietly break. A customer can love your product, prefer it to everything else on the market, and still not be willing to pay the price your unit economics require. The willingness to pay has to be validated at the price point that makes the business work — not at a discounted pilot price, not at a freemium tier, but at the actual price the business needs to sustain itself.
Most founders arrive at my door having validated steps two and three at a surface level and having mostly skipped step one. The customers they've talked to are already interested — they sought them out, which means they're not representative. The pricing they've validated is often below what the model requires. And the conversion from "this is interesting" to "I will pay for this ongoing" is assumed rather than proven.
What I've seen happen when this isn't fixed early
The pattern is consistent. A company raises a seed round on the strength of the vision and early traction. They use the capital to hire, build, and scale the sales motion. They start to close customers — but the sales cycle is longer than expected, and the contract values are lower than the model assumed. Churn is higher than expected because customers who were convinced by a compelling pitch are discovering that the product doesn't fit their workflow as cleanly as it seemed.
By the time they're raising Series A, the numbers tell a story that doesn't support the valuation they need. Not because the product is bad — often the product is genuinely good. But because the business model was never properly validated. They scaled before they understood why customers actually bought and what it would take to keep them.
At that point, fixing the business model requires going backwards — slowing down, talking to customers again, potentially repositioning the product — while the burn rate is high and investor patience is limited. It's a solvable problem, but it's much more expensive to solve at Series A than it would have been at the seed stage, and infinitely more expensive than it would have been before the first line of code was written.
The customer discovery work that most founders underdo
The antidote is genuine customer discovery — and I want to be precise about what that means, because most founders believe they've done it when they haven't.
Customer discovery is not a pitch meeting where you watch for positive reactions. It's not a survey that asks people if they'd use your product. It's not a conversation with your professional network about whether the idea sounds good.
Customer discovery is listening to understand, not listening to validate. It means going into conversations with the explicit goal of finding out whether your assumptions are wrong. It means talking to people who are not already inclined to be supportive. It means asking about behavior — what they currently do, what they pay for it, what they hate about it, what they've tried before — rather than asking about intentions.
And critically: it means being willing to hear something that changes the direction. The founders who do this work well are the ones who come back from fifty customer conversations and say, "We were wrong about X, and here's what we learned." That willingness to be wrong — and to be changed by the evidence — is what converts a product into a business.
The question worth sitting with
If you're a founder reading this, here's the question I'd leave you with: Can you describe your business model — who pays, how much, how often, and why they keep paying — in a way that is grounded in evidence rather than assumption?
Not the model as you hope it will work. Not the model that makes the financial projections look right. The model as it actually works today, validated by real customers paying real money for real reasons that you understand well enough to reproduce.
If the answer is yes, build faster. If the answer is no — or not yet — the most important thing you can do right now is go talk to customers. Not to pitch them. To understand them. The business model is in those conversations. You just have to be willing to find it.