I spent eleven months building a product before I sold a single unit. Not because I lacked the ability to sell earlier, but because I told myself, repeatedly, that it wasn’t ready yet. When I finally did start selling, in month twelve, three of my first five conversations revealed a feature I’d spent six weeks building that literally nobody wanted, and a completely different feature I hadn’t built at all that every single person asked about.
Eleven months of building, and the actual market feedback I needed took about a week to gather once I finally started asking for it. That gap, and the cost of it, is the single most expensive mistake I’ve watched founders make, myself included, and it’s rarely framed honestly as the mistake it actually is.
Why Building Feels Safer Than Selling
Building is comfortable in a specific way that selling isn’t. You control the pace, the quality bar is entirely your own to set, and nobody tells you no to your face while you’re doing it. Selling means putting something in front of a stranger and asking them, directly, to give you money or tell you why not. That’s uncomfortable in a way that writing another line of code or refining another feature simply isn’t.
Founders, especially first-time founders with a background in building things, gravitate toward the comfortable work and call it necessary preparation. Sometimes it genuinely is. Far more often, it’s avoidance dressed up as diligence, and the dressing is convincing enough that even the founder doing it usually believes it at the time.
What Selling Before Building Actually Looks Like
This doesn’t mean selling something that doesn’t exist through outright deception. It means selling the outcome and the promise before the full execution exists, then building specifically what those early conversations reveal is actually needed, not what you assumed would be needed before anyone confirmed it.
I’ve since run this differently on a second business. Before building anything beyond a rough prototype, I had fifteen direct conversations with potential customers, describing exactly what the product would do and asking directly whether they’d pay a specific price for it today. Eight said yes clearly enough that I took a deposit, a real financial commitment, before the product was fully built. Building against eight paying commitments produced a dramatically more focused product than building against my own eleven months of assumptions had the first time.
The Real Cost of Building First, Beyond Just Time
The time cost is the obvious one, but it’s not actually the biggest cost. The bigger cost is that a product built for eleven months without market contact develops its own internal logic, features that make sense to the founder because of decisions made three months earlier, priorities that reflect what was technically interesting to build rather than what customers actually needed. Unwinding that internal logic once real feedback finally arrives is far harder than building correctly from early, real signal in the first place.
There’s also a psychological cost that’s easy to underestimate. Eleven months of building creates real emotional investment in the product as it exists, which makes it genuinely harder to hear that a feature needs to be cut or a core assumption was wrong. Selling first keeps that emotional investment lower and the willingness to pivot higher, simply because less has been sunk into the wrong direction before the correction arrives.
Why This Mistake Is Especially Common With Digital Products
Physical products carry an obvious excuse for needing to build first, you can’t easily sell a physical prototype that doesn’t yet exist in a testable form. Digital products and services rarely have that excuse, and yet founders building software or digital services fall into the build-first trap just as often, usually because “I need to build the MVP first” feels like a real technical constraint even when a landing page, a mockup, or a direct conversation describing the offering would have generated the same validation without the eleven months.
What Actually Counts as “Selling Before Building”
A landing page describing the specific outcome, with a real payment or deposit mechanism attached, not just an email signup. A direct conversation with a specific price mentioned out loud, not a vague “would you be interested” question that avoids the real commitment test. A pre-order or deposit taken before the full product exists, which creates real stakes on both sides and generates far more honest feedback than a free beta ever will.
Each of these puts a real, if small, financial commitment on the table before the bulk of the building happens, and that commitment is what makes the resulting feedback trustworthy instead of just polite.
What to Do Now
If you’re currently building something nobody’s paid for yet, stop and run one real sales conversation this week, with a specific price mentioned out loud, before writing another line of code or refining another feature. If nobody says yes at a real price, that’s the most valuable and cheapest information you’ll get all year, cheaper by months than finding out after building the whole thing.
Sell the outcome first. Build exactly what those conversations reveal you actually need. In that order, every time.
