The Minimum Viable Product Myth: Why Most Founders Test the Wrong Thing

On November 1, 1998, Motorola lit up the most ambitious telecommunications network ever built. Sixty-six satellites, orbiting 485 miles above Earth, covering every square inch of the planet's surface. The project was called Iridium. It had taken more than a decade and roughly $5 billion to build. The phones cost $3,000 and charged up to $30 per minute. But they worked. You could dial a number from the middle of the Sahara Desert and hear a voice as clearly as if you were calling from Manhattan.

Nine months later, Iridium filed for bankruptcy. It remains the most expensive minimum viable product lesson in history, though the team never thought of it in those terms. They had built the product. It was viable. It worked perfectly. What they hadn't tested was whether anyone would pay for it.

During Iridium's decade of development, cellular networks had expanded to cover the vast majority of places anyone actually made calls. By launch day, the people willing to spend $3,000 on a satellite phone and $30 per minute to use it were oil rig workers, polar researchers, and military contractors, a sliver of the mass market Iridium had targeted. Ten years and $5 billion had answered the engineering question flawlessly. The market question had never been asked. The MVP, as a concept, wouldn't exist for another thirteen years. But even if it had, it wouldn't have saved them, because the minimum viable product answers the wrong question first.

The Question Nobody Asked

In January 2015, a cartoonist named Matthew Inman and a game designer named Elan Lee had an idea for a card game. Lee had spent years at Microsoft, most recently as Chief Design Officer at Xbox Entertainment Studios. Inman had built The Oatmeal into one of the most-read webcomics on the internet. Between them, they had plenty of credentials. What they didn't have was a product.

The concept: players would draw cards from a deck, trying to avoid the one card that would eliminate them. An exploding kitten. The mechanics were simple, the illustrations deliberately absurd.

They had no manufacturing partner, no distribution deal, no retail relationships, and no inventory. What they had was a Kickstarter page, a short video, and a few hand-drawn prototype cards.

They set a funding goal of $10,000. They hit it in eight minutes. Within the first twenty-four hours, they'd crossed $1 million. When the campaign closed thirty days later, 219,382 people had backed the project for a combined $8.78 million, making it the most-backed project in Kickstarter history at the time, by number of supporters.

Lee and Inman didn't test whether they could manufacture a card game. They tested whether anyone would pay for one. The manufacturing and distribution problems that Iridium had solved first and Exploding Kittens had solved last were both real. The difference was the order. One team spent a decade and $5 billion answering "Can we build this?" The other spent a few weeks answering "Will anyone buy this?" and raised nearly $9 million.

What Should Come Before Your Minimum Viable Product?

Eric Ries defined the minimum viable product in The Lean Startup as "that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort." The concept changed how a generation of founders thought about building. Instead of spending years in stealth mode, you ship something small, learn from real usage, and iterate.

The problem isn't the MVP. The problem is what founders skip before they get there.

An MVP tests whether your solution works. But there's a prior question most founders never isolate: does anyone want the transformation your solution provides badly enough to pay for it? Building a minimum viable product still requires weeks or months of development. Still requires engineering decisions, design choices, architecture trade-offs. And all of that investment rests on an assumption that hasn't been tested — that the market wants what you're about to build.

The Minimum Sellable Product is the step that should come first. An MSP is the simplest, fastest way to test whether real people will exchange something of genuine value for the transformation you're proposing, before you build anything. Not a prototype. Not a beta. A test of willingness to commit.

The distinction matters because of how the brain processes hypothetical value versus real value. When you ask potential customers "Would you use this?" or "Does this sound interesting?" you're engaging their deliberative system, the analytical mind that evaluates ideas in the abstract. That system is generous. It says yes to things that sound good. It imagines futures it won't inhabit.

But purchasing decisions aren't made by the deliberative system. They're made by the evaluative system, the fast, emotional, loss-aware machinery that computes whether parting with real money is worth it right now. Research on hypothetical bias shows that people routinely overstate their willingness to pay, with some studies finding exaggeration by a factor of two or more across product categories. The only way to engage the system that actually makes buying decisions is to ask for a real commitment: money, time, effort, or reputation.

An MSP forces that real commitment. A landing page with a "Buy Now" button. A Kickstarter campaign. A pre-sale. A consulting offer delivered manually. Anything that requires the potential customer to put something on the line.

Why Do Smart Founders Build the Wrong Thing?

If testing sellability first is the obvious move, why do experienced, well-funded founders keep skipping it?

Because building feels like progress. Sketching wireframes, writing code, designing features, hiring engineers: these activities create visible evidence that you're moving forward. They generate the dopamine of accomplishment. You can show investors a demo, point your team to a roadmap, watch the product take shape on a screen.

Selling before you build feels like the opposite. There's nothing to show. The conversations are uncomfortable. You're asking people to pay for something that doesn't exist yet. And the rejection is personal. It's not the product that failed. It's you who couldn't convince someone.

So founders build. They build because building is comfortable and selling is scary. They build because lean startup methodology told them to ship an MVP, and they interpreted "minimum viable product" as permission to start coding. They build because they confuse enthusiasm for evidence and motion for validation.

Iridium's team wasn't lacking intelligence. They were Motorola's best engineers solving one of the hardest technical challenges in telecommunications history. But solving hard problems is seductive. Each engineering milestone reinforced the narrative that the project was working. Every milestone answered a question about feasibility. None answered the question about sellability. A $750,000 personal investment can produce the same blinding effect as a $5 billion corporate one. The scale changes. The psychology doesn't.

The Validation Ladder

Not all customer signals carry the same weight. A like on social media is not the same as a credit card number. The useful way to think about validation is as a ladder, where each rung represents a deeper level of genuine commitment.

At the bottom: social engagement. Likes, follows, comments. These feel validating but cost the customer nothing. They're vanity metrics produced by the deliberative mind, not the purchasing mind.

One rung up: time investment. Someone attending a live demo, joining a webinar, or completing a detailed survey is investing something scarce. People protect their time more carefully than their compliments, which makes time a more honest signal than applause.

Higher still: information exchange. When someone provides their email, phone number, or detailed preferences, they're giving up personal data they can't take back. Stronger than a like, though weaker than money.

Near the top: social capital. When someone recommends you to their network or publicly endorses your product, they're investing something they can't easily replace. Reputation is expensive to build and painful to waste. A referral means more than a review.

At the top: money. Someone paying, pre-ordering, or putting a deposit down has engaged their evaluative system. The loss-averse, economically real purchasing brain has fired and produced a "yes." This is the signal that matters most, and the signal most founders avoid collecting because it's the hardest to get.

The MSP is designed to reach as high on this ladder as possible, as quickly as possible, with as little investment as possible. DoorDash started with a landing page and a phone number. Buffer started with a two-page website where the "Plans and Pricing" button led to an email signup form. When people clicked, founder Joel Gascoigne added an actual pricing page between the landing page and the signup. He was testing willingness to pay with zero product and an afternoon's work. Seven weeks after the initial idea, he had his first paying customer.

How the MSP Changes What You Build

The MSP doesn't just tell you whether to build. It tells you what to build.

A sellability test wouldn't just have revealed that Iridium's mass market didn't exist. It would have revealed who the actual customers were. That information, available before a single satellite launched, would have changed everything: the pricing, the handset design, the marketing strategy, the constellation size, the entire business model.

After the bankruptcy, a group of investors acquired the satellite constellation for $25 million, half a cent on the dollar, and relaunched the service targeting the niche that was always there: the workers and contractors in places cell towers would never reach. The new Iridium Communications has been profitable for over a decade. Same satellites. Same technology. Different understanding of who would pay, and why.

The most expensive market research in telecommunications history was also the most avoidable.