{"id":283,"date":"2026-10-22T18:13:39","date_gmt":"2026-10-22T18:13:39","guid":{"rendered":"https:\/\/wallion.com\/?p=283"},"modified":"2026-10-29T23:41:46","modified_gmt":"2026-10-29T23:41:46","slug":"cuando-tiene-sentido-un-mvp","status":"publish","type":"post","link":"https:\/\/wallion.com\/en\/blog\/cuando-tiene-sentido-un-mvp\/","title":{"rendered":"When an MVP is worth building"},"content":{"rendered":"
\n

2026-09-08 \u00b7 Wallion<\/p>\n\n\n

\"When<\/figure>\n\n\n

An MVP makes sense when there's a stranger, an action, and a sign that you can write down before<\/em> to build. If any of the three are missing, you're not asking for an MVP: you're asking for something else \u2014 or you don't know what yet.<\/p>\n\n\n

This page decides. It does not define: the definition of Studio MVP<\/a> It lives apart. It doesn't separate: the boundary with the internal tool is in MVP or internal tool<\/a>. The commission, if the decision is yes, lives in MVP for startups<\/a>, within custom software<\/a>. Wallion does not open a root URL \/mvp<\/code>.<\/p>\n\n\n

The short answer<\/h2>\n\n\n

Yeah<\/strong> when: (1) the user is external \u2014 customer, store, workshop, buyer who doesn't get paid by you; (2) the action fits in a sentence without "and also"; (3) someone external will use it the week it comes out; (4) you can list what No<\/em> enter without fighting; (5) the signal (returned \/ paid \/ asked for the next piece) is written before the first commit.<\/p>\n\n\n

No<\/strong> When: the user is only the team; you want to replace the entire month; nobody is going to touch it; you can't say what's left out; the "MVP" is a backlog disguised as a minimum; or you need staffing and you call it a product.<\/p>\n\n\n

If the line is \u201cMaria from administration closes the month,\u201d read the tool guide, not this one. If the line is \u201ca local makes a reservation and I\u2019ll see if they return,\u201d continue here.<\/p>\n\n\n

When to do it (specific signs)<\/h2>\n\n\n

There's a bet that can be lost soon.<\/strong> One buyer, one use case, one yes or no in weeks\u2014not a quarter of slides. The learning or the sale has to fit into the current quarter's timeline, not "when the product is ready.".<\/p>\n\n\n

The scope can be summed up in one sentence.<\/strong> \u201cA restaurant reserves a table.\u201d \u201cA workshop sends a quote.\u201d \u201cA buyer places and pays for the first order.\u201d If the sentence includes \u201cand also,\u201d it\u2019s still not the minimum: it\u2019s a product that hasn\u2019t been prioritized.<\/p>\n\n\n

Someone from outside will use it the week it comes out.<\/strong> Family and partners don't count. A client who's already said they'll try it, does. Without that someone, you're just putting on a show: there's a demo, but no signal.<\/p>\n\n\n

You can write what is not included.<\/strong> No arguing in the meeting. The dream panel, the five integrations, the app on three platforms: gone. If the cuts don't hurt, you didn't cut anything.<\/p>\n\n\n

The sign is written before.<\/strong> He came back. He paid. He asked for the next piece even though you wouldn't sell it to him. One of those three (or yours, with the same rigor). Without prior criteria, the MVP is only useful for having built something.<\/p>\n\n\n

When not (and what do you ask for instead)<\/h2>\n\n\n
Situation<\/th>Why he's not MVP<\/th>What to order instead<\/th><\/tr><\/thead>
Only used by the team \/ closes at the end of the month<\/td>There is no external market<\/td>Internal tool<\/a> \/ un flujo<\/td><\/tr>
\u201cWe need to digitize\u201d without a phrase of scope<\/td>There's no betting that can't be won.<\/td>Diagnosis or wait<\/td><\/tr>
Prototype for the deck \/ investors<\/td>Nobody touches it the week it "comes out"\u201c<\/td>Don't call him MVP<\/td><\/tr>
Replace the entire month of the company<\/td>It's for multiple projects or a large tool<\/td>A flow first<\/td><\/tr>
Live backlog, you need hands<\/td>It's staffing, not a minimum product.<\/td>To put it simply: reinforcement, not \u201cMVP\u201d<\/td><\/tr>
Landing page with form<\/td>The stranger did not ends<\/em> an action<\/td>Marketing, not product<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n

If you fit into the left column and still ask for "MVP", you're misnaming \u2014 and misjudging if you're comparing the wrong band.<\/p>\n\n\n

What's in and what's out (the cut)<\/h2>\n\n\n

Enter:<\/strong> an action, an external user, a usable happy path from end to end, data you can read later (who, when, if they returned or paid), an owner of the "fact" in the studio.<\/p>\n\n\n

It doesn't fit:<\/strong> The dream admin panel; the five integrations; the brand redesign; the app on three platforms; \u201ceverything the team will also need.\u201d That\u2019s it. after<\/em>, if the first one is used.<\/p>\n\n\n

The cut hurts the outside. If no one at the table loses a screen they wanted, you haven't cut: you've postponed the fight to sprint three.<\/p>\n\n\n

How to know if it worked<\/h2>\n\n\n

It's not "we liked it in the demo." It's: Did anyone come back? Did they pay? Did they order the next piece on their own? One of those three\u2014or the signal you wrote. before<\/em>.<\/p>\n\n\n

If the criteria are invented later ("Did they like it?"), the MVP only proves that you built it. If the stranger can't finish it without the founder acting as glue via WhatsApp, you didn't deliver an MVP: you delivered a draft with hosting.<\/p>\n\n\n

After the yes.<\/strong> If the stranger returned, the next piece is written the same way: a sentence, a snippet, a deadline. If they didn't return, you stop. You don't "expand the MVP." Expanding without a signal is the full product disguised as a minimum.<\/p>\n\n\n

Failure modes<\/h2>\n\n\n

\u201cMVP\u201d = cheap product.<\/strong> You asked for five screens, three platforms, and the panel, "but the bare minimum." The cutbacks aren't a big deal. It wasn't an MVP; it was a product that wasn't a priority.<\/p>\n\n\n

Eternal PoC.<\/strong> There's a prototype. It's taught. It's stored away. Nobody touches it. You learn zero. Don't call it an MVP to feel productive.<\/p>\n\n\n

Tool with product name.<\/strong> Only the team uses it. You measure it monthly. You call it an MVP because it sounds like a startup. Poorly named\u2014and poorly budgeted if you look at the toolbar as if it were the minimum product (or vice versa).<\/p>\n\n\n

Signal invented after the fact.<\/strong> You build first. Then, "Did they like it?" Without written criteria beforehand, there's no decision: there's just spending.<\/p>\n\n\n

Staff in disguise.<\/strong> Live backlog, you need hands, you're asking for "an MVP." Say it. Don't mix tables or prices.<\/p>\n\n\n

Compare with Mobility, Glowapp or Nummo.<\/strong> These are not Wallion products from this service. They are not a reference for scope or price.<\/p>\n\n\n

Confusing definition and decision.<\/strong> This page does not replace What is a studio MVP?<\/a>. That one defines; this one decides.<\/p>\n\n\n

Public prices (Option D \u2014 without inventing other figures)<\/h2>\n\n\n

Only the figures from the site. The \u20ac6,900\u2013\u20ac14,900 price range is not the price of an MVP.<\/strong><\/p>\n\n\n