The death of the MVP mindset

The Demo Tape Doesn't Matter Anymore

In 1994, if you were a band in a garage in Bombay or Baltimore, the hard part wasn't writing a good song. The hard part was recording it. Studio time was expensive. Equipment was scarce. Mixing and mastering required people who owned machines that cost more than your apartment.

So the demo tape meant something. If you had one, it proved you could actually make music. It was your ticket to being taken seriously. Labels listened to demo tapes because the tape itself was evidence of commitment, resourcefulness, and at least a basic level of competence.

Today, a seventeen-year-old with a laptop and a cracked copy of Ableton can produce a track that sounds better than most studio recordings from the 1990s. The demo tape is worthless. Not because music got worse. Because making music got easy.

The question is no longer "can you make a song?"

The question is "can you get anyone to hear it?"

This is exactly what happened to the MVP. And most product teams haven't caught up.

The MVP was built for a world where building was expensive.

The Minimum Viable Product made sense when shipping software was genuinely hard. When building the first version of something required months of engineering, real infrastructure costs, and significant upfront investment, the MVP was a smart way to de-risk. Ship the smallest thing that works. See if anyone uses it. Learn. Iterate.

The MVP wasn't really about the product. It was about the question: can we build this at all?

I remember working on a product years ago where the MVP took five months. Five months of engineering, design, QA, and more standups than I want to think about. When we finally shipped it, the fact that it existed and functioned felt like a victory. And it was. Because building the thing was the hard part.

But that was a different era. And I don't think it's coming back.

Building is now the easy part. That changes everything.

AI has collapsed the cost of building a first version of almost anything. A solo founder can go from idea to working prototype in a weekend. A PM can build a functional demo without writing a line of code. A designer can ship a front-end that would have taken an engineering team three sprints two years ago.

This is genuinely exciting. But it also means the MVP, as we've traditionally understood it, is answering a question nobody is asking anymore.

"Can we build this?" is no longer the risky bet. Of course you can build it. Everyone can build it. Your competitor can build it. A college student in Kochi can build it over a long weekend while simultaneously failing to do their laundry.

The risky bet has moved. It's no longer "can we ship this?" It's "can we get anyone to care?"

Can you distribute it? Can you find the people who need it? Can you get them to try it? Can you make them come back? Can you do all of that for less money than those people will ever pay you?

That's the new validation question. And most MVPs don't even attempt to answer it.

The graveyard is full of functional products.

Here's what I've noticed over the last few years, across multiple teams and companies I've been close to. The products that fail aren't failing because they don't work. They're failing because nobody knows they exist.

I talked to a founder recently who had built something genuinely clever. Clean interface. Real problem being solved. Fast, reliable, well-designed. He'd spent four months building it and was proud of the craft. I asked him how he was planning to get users. He paused, then said, "I figured I'd post it on Product Hunt and see what happens."

That's not a distribution strategy. That's a prayer.

And he's not unusual. He's the norm. Most builders, especially technical ones, treat distribution as the thing that happens after the real work is done. Build the product, then "do some marketing." As if marketing is a condiment you add at the end rather than the main ingredient you plan around from day one.

The MVP mindset trained a generation of product people to believe that if you build something good enough, people will find it. That was always a little optimistic. In 2026, it's delusional.

Validation now means proving distribution, not function.

If I were starting a product today, the first thing I'd build isn't the product. It's the audience.

I'd want to know, before writing a single line of code or pushing a single pixel, whether the people I'm building for actually exist in a place I can reach them. Can I find them? Can I talk to them? Will they listen? Do they already gather somewhere, a subreddit, a Slack community, a newsletter, a Discord server, where I can show up and earn attention before I have anything to sell?

That's the new MVP. Not a minimum viable product. A minimum viable path to the customer.

Because the product is the easy part now. The demo tape is free. Anyone can record one. The question that separates the bands that make it from the bands that play to an empty room is the same question that separates the startups that scale from the ones that quietly shut down:

Can you get anyone to listen?

The best product I ever worked on wasn't the most technically impressive one. It wasn't the most beautifully designed one. It was the one where we knew exactly who it was for and exactly where to find them before we built a single screen.

That felt like cheating at the time.

Now I think it's the only way to play.