Ch5 03: MVP Isn’t a Stripped-Down Product. It’s a Single Drop of Espresso.#

What if everything you know about MVPs is wrong?

Most founders hear “minimum viable product” and think: take the full product, slash features until it’s small enough to ship. So they slash. And slash. What’s left is a skeleton—functional but soulless. Users try it, shrug, and leave. “I don’t get it.”

That’s not minimum viable. That’s minimum effort. And it teaches you nothing.

A real MVP isn’t about subtraction. It’s about concentration. Isolate your core value and deliver it in the purest, most undiluted form possible. One drop of espresso, not a watered-down cup of coffee. One drop—and you know exactly what you’re tasting.

I call this Minimum Value Delivery—MVD. The distinction isn’t semantic. It changes everything about how you build and what you learn.

MVP vs. MVD: Why the Difference Kills or Saves You#

Here’s the standard MVP playbook: list twenty planned features, rank by importance, cut the bottom fifteen, build the top five, ship.

Result: a product that does five things poorly. Users experience a partial version of the future and think, “This isn’t ready.” They’re right—but the problem isn’t missing features. The problem is those five features, taken together, don’t deliver a clear, compelling value.

MVD flips the script. You don’t start with a feature list. You start with one question: What is the single thing that, if my product delivered nothing else, would still make someone say “this is worth it”?

That’s your core value. Everything else is decoration.

Core value is why someone shows up. Features are why they stay comfortable. At the earliest stage, you only need the first. Comfort comes later.

An online education startup wanted to build a learning platform. Full vision: recorded lectures, interactive exercises, peer forums, certificates, progress tracking, AI recommendations. Now strip it all away. What’s left?

One thing: someone teaches you a skill you didn’t have before.

Their MVD: a Zoom link, a Google Sheet for scheduling, ten students who paid $50 each. The instructor taught live. Students asked questions in real time. No recording. No exercises. No certificates. Just raw core value, delivered directly.

Three weeks in, they discovered things no platform could have revealed. Students didn’t want recordings—they craved live interaction. The most-requested feature wasn’t exercises; it was office hours. And $50 was too low: students said they’d pay $120 for more personal attention.

That’s MVD in action. Signal isolated from noise.

The One-Sentence Test (30 Seconds to Clarity)#

Complete this sentence: “My product helps people ______ by ______.”

The first blank is the outcome. The second is the mechanism. Now cross out the mechanism. The outcome is your core value.

“My product helps people eat healthier by delivering pre-portioned ingredients with recipes.” → Core value: eat healthier. Delivery, portioning, recipes—those are mechanisms. They might change. The core value won’t.

“My product helps people find freelance work by matching them with clients using AI.” → Core value: find freelance work. The MVD version? You manually match freelancers with clients via email. Same value. Zero technology.

“My product helps people sleep better by tracking sleep patterns and providing personalized recommendations.” → Core value: sleep better. MVD: a two-week program where you personally text each user every morning, ask how they slept, and give one specific suggestion. Manual, unscalable—and brutally effective at revealing what actually helps people sleep.

If you can’t complete this sentence in under a minute, you don’t know your core value yet. That’s okay. But don’t build anything until you do.

Three Steps to Design Your MVD#

Step 1: Kill all technology assumptions. Pretend software doesn’t exist. How would you deliver this core value using only phone calls, physical meetings, paper, and existing tools? This isn’t your final product—it’s a thought experiment that forces you to separate value from implementation.

Step 2: Find the cheapest delivery vehicle. What existing platform can carry your core value to the user? A WhatsApp group. A Google Form. An email newsletter. A Zoom call. A physical meetup. Don’t build what you can borrow.

Step 3: Set a hard constraint—ten users. Not a hundred. Not fifty. Ten. This does two things: keeps your cost near zero and forces direct relationships with every user. You’ll hear feedback without surveys. You’ll see behavior without analytics dashboards. Ten users, deeply served, teach you more than a thousand anonymous sign-ups.

A fitness coaching startup used this exact method. Core value: help busy professionals get stronger. Technology assumption killed: no app. Cheapest vehicle: a shared Google Sheet—coach posts daily workouts, clients log results. Constraint: ten clients, $30/month each. The coach reviewed every log entry personally and sent voice messages with form corrections.

After one month, the breakthrough insight: clients didn’t need workout variety—they needed accountability. The daily log wasn’t about exercises; it was about having someone notice whether you showed up. That single insight shaped the entire product. The app they eventually built was 80% accountability features, 20% workout content. Without the MVD phase, they would have built it exactly backwards.

The Trap: “Concentrated” vs. “Careless”#

MVD is not an excuse for laziness. There’s a razor-thin line between concentrated and careless.

A concentrated MVD delivers one thing brilliantly. A careless MVP delivers many things badly. If your MVD feels sloppy to the user—if they can’t understand what they’re getting or why it matters—you haven’t distilled your value. You’ve shipped something unfinished.

The litmus test: After using your MVD, can a user tell someone else what it does in one sentence? If yes, your core value is clear. If they stumble—“well, it sort of does this, and also that, and eventually it’ll…"—you’ve got feature soup, not an MVD.

Second trap: testing the wrong variable. Your MVD should test whether the core value resonates, not whether the delivery mechanism works. If users love the value but hate the manual process—that’s a win. The process will improve. The value validation is what matters.

But if users shrug at the core promise itself—if the value doesn’t land—no technology upgrade fixes that. Better to know now, after a weekend and fifty bucks, than six months and six figures later.

Real MVDs vs. Fake MVPs#

Real MVD: A language learning service pairing users with native speakers for 15-minute WhatsApp voice conversations. No app. No curriculum. No gamification. Just core value: practice speaking with a real person. Twenty users tested for free. Twelve said they’d pay. Value validated.

Fake MVP: A language learning app with flashcards, grammar quizzes, and a chatbot—each half-baked. Users try it, compare it unfavorably to Duolingo, and leave. Insight gained: you can’t out-feature Duolingo. You already knew that.

Real MVD: A project management tool for creative teams. Before writing code, the founder spent two weeks manually managing three teams’ projects with a shared Notion page and a daily check-in message. Discovery: the biggest pain wasn’t task tracking—it was handoff communication between team members. That insight would have been invisible inside a feature-laden MVP.

Fake MVP: A project management tool with task boards, time tracking, and file sharing—all at 60% quality. Users compare to Trello and Asana. Unfavorably. No insight. Six months gone.

The pattern: Real MVDs test value. Fake MVPs test features. Features are easy to iterate. Value, once found, is your foundation.

Reflect and Self-Diagnose#

Try this right now:

Describe your product—every feature, every function, every nice-to-have. Write it all down.

Now cross out everything except one thing. The one thing that, alone, would make someone say: “That’s worth paying for.”

Can you deliver that one thing without custom technology? Using tools that already exist? To ten people, starting this week?

If yes—you’ve found your MVD. Build it this weekend. Talk to those ten people next week. Learn what no amount of planning can teach you.

If no—if that one thing inherently requires complex technology—ask the harder question: is your core value really about the technology, or have you confused the mechanism with the outcome?

Most of the time, the value is simpler than you think. And the fastest way to prove it is the crudest way to deliver it.

Stop building the factory. Deliver the product by hand. See if anyone wants it. Then—and only then—build the machine.