A studio MVP is not “the cheap version of the product”. It is the smallest slice a stranger can actually finish — built by a custom-software studio with written scope, a closed price, a date, and someone on the other end when Monday fails.
That is the definition. It is not the whole product shrunk. It is not a deck prototype you show and shelve. It is not the team’s month-end tool wearing a product name. And it is not a marketing landing with a form.
This page defines. The decision guide — when yes, when no — lives at when an MVP is worth building. The border with an internal tool lives at MVP or internal tool. The commission lives at startup MVP, inside the same custom software hub. Wallion does not open a root /mvp ranking URL: the module hangs off the hub.
The short answer
An outside user. Customer, venue, workshop, buyer. Not the team. If only in-house people use it, it is not an MVP — almost always an internal tool.
One action. It fits in one sentence. “Books.” “Requests a quote.” “Uploads the job sheet.” If the sentence has “and also”, it is not the minimum yet.
One signal written before you build. They came back, paid, or asked for the next slice without being sold it. Without a test, you only delivered code.
A studio that closes. Scope, price, weeks, an owner of “done”. Not a “we’ll see”. Not a PoC nobody touches the week it ships.
If you cannot write the line — “A [stranger] does [one action] and I see [one signal]” — do not ask for an MVP. Ask for help writing the scope, or wait. If the line is about the team and the 28th, read the internal-tool page — not this one.
What it is / what it is not
What it is. A minimum product with real users, built as a custom-software commission: a painful outward cut, one flow a stranger can complete, and a learning or sales test written before the first line of code.
“Studio” matters. Not ownerless no-code. Not a freelancer who vanishes when payment fails. A studio (Wallion, Barcelona) that writes the scope, fixes a number, ships in weeks, and stays on the other end if Monday does not start — under the licence-and-responsibility model on the offer.
What it is not.
- Not a prototype. A Figma or a deck shown and shelved learns nothing. If nobody touches it the week it “ships”, it is product theatre.
- Not an internal tool. The company’s month is not a market. Replacing the spreadsheet that stops the close is another commission, another band, another test. Guide: MVP or internal tool.
- Not the full product. Dream admin, five integrations, app on three platforms: that is later, if the first slice gets used. If the cut does not hurt, you did not cut.
- Not a marketing landing. A page with a CTA is not a minimum product. An MVP lets the stranger finish an action.
- Not Mobility, Glowapp or Nummo. They are not Wallion products of this service.
How it shows up at an SME table (Barcelona / Spain)
No logo case study needed. The pattern is the table: a founder still closing sales by hand, someone in ops with a WhatsApp thread that “almost is the product”, and sometimes a partner (advisory firm, ERP, a3-style stack) quoting the next module when the spreadsheet or chat stops holding.
In Barcelona, the metro area and the rest of Spain, that table often asks for the same thing in different words: “an MVP”. Sometimes the pain is real — outside buyer, clear action, someone who will try it the week it ships. Sometimes it is “we must digitise” with no scope sentence, or “a product for the team” that is not a market. Wallion talks to that profile often: one bounded external bet, Diagnosis before build, written fixed price. No invented clients or volumes. The pattern is the table.
If the “user” is María in admin and the test is “the month closes”, it is not an MVP. If the user is a venue, workshop or buyer who does not invoice you, and the signal is return or pay, it is.
When it makes sense vs when it does not
It makes sense when there is a bet you can fail early; the scope fits in one sentence; someone outside will use it the week it ships; and you can write what stays out without a fight.
It does not make sense when you want to replace the whole month (a tool, or several projects); when you cannot say what stays out; when nobody will touch it; when the “MVP” is a backlog wearing a minimum label; or when you need staffing and call it a product — say it.
The long guide lives at when an MVP is worth building. This page defines; that one decides.
What “done” looks like
“Done” is not “we liked the demo”. It is: a stranger completes the action end to end the week it ships — without the founder acting as WhatsApp glue.
At minimum: a usable happy path; data you can read afterwards; a signal written before you build; a studio owner of close; someone on the other end when it fails — not a zip and “good luck”.
If the stranger cannot finish without calling you, you shipped a draft with hosting — not an MVP.
Public prices (Option D — no invented figures)
Only the numbers on the site. The €6,900–14,900 band is not the price of an MVP.
- Diagnosis — €1,900. Written scope, prototype, fixed build quote. If you proceed, it is credited against the build.
- Build — €6,900–14,900. One internal tool / one flow after Diagnosis. Not the price of a large app, an MVP or staffing.
- MVP build: a written fixed price after Diagnosis — same model (scope + number + date), a different figure, not that band.
- Licence — from €390/month if Wallion keeps what it built running (hosting, security, regulatory and API changes, a ceiling of small changes, business-hours support — as published on the offer).
Apps, MVPs and staffing: Diagnosis → written fixed price → optional licence. Do not mix the tool band with the MVP figure. Offer: startup MVP. Hub: custom software.
Failure modes
“MVP” = cheap product. You ask for five screens, three platforms and the dream admin “but minimum”. The cut does not hurt. It was not an MVP: it was an unprioritised product.
Eternal PoC. There is a prototype. It gets shown. It gets shelved. Nobody touches it. You learn nothing.
Tool with a product name. Only the team uses it. You measure month-end. You call it an MVP because it sounds like a startup. Misnamed — and mispriced if you compare the wrong band.
Signal invented afterwards. You build first. Then “did they like it?”. Without a written test beforehand, the MVP only served to have built something.
Staffing in disguise. Living backlog, you need hands, you ask for “an MVP”. Say it. Do not mix tables.
Comparing with Mobility, Glowapp or Nummo. They are not this service.
What Wallion does (and when not to buy it)
Wallion builds MVPs inside custom software, at a written fixed price after Diagnosis (€1,900, credited if you proceed). MVP construction does not use the public internal-tool band. Licence, if kept running: from €390/month.
Model in one line: stranger, action, written signal; painful scope; closed number; date of “done”; someone on the other end when it fails.
Do not buy an MVP with Wallion when the user is only the team; when you cannot write what stays out; when nobody will touch it the week it ships; when you want to replace the whole month; or when you need staffing and call it a product.
If on the call you say “this is a tool, not an MVP”, say it first. Geo: /en/software/barcelona.
Decision checklist (before you commission)
Tick each point. If any stays blank, do not sign “MVP”.
- Is there a stranger — or only the team?
- Does the action fit in one sentence without “and also”?
- Is the signal (returned / paid / asked for the next slice) written before you build?
- Will someone outside use it the week it ships — not only partners?
- Can you list what stays out without a fight?
- Are you measuring external use, or month-end close? (If the month → tool.)
- Are you comparing the €6,900–14,900 band (tool) or a written MVP fixed price?
- Are you asking for a Diagnosis with a scope sentence, or an ownerless pilot?
- Do you need a minimum product or hands on a backlog (staffing)?
- Is “done” that a stranger finishes the flow — or that you like the demo?
Without those answers, “MVP” is an adjective — not a commission.
Questions buyers actually ask
Is this the same as a startup “agile” MVP?
Same idea of a minimum with real users. Different commission: written scope, closed price, a date, a responsible studio — not an endless sprint with no owner of done.
When is it not an MVP?
When only the team uses it, nobody touches it, or you cannot say what stays out. Guides: when it is worth building, MVP or internal tool.
Does the €6,900–14,900 band cover the MVP?
No. That band is one internal tool / one flow. The MVP is a written fixed price.
Is the €1,900 Diagnosis lost if we don’t proceed?
If you proceed, it is credited. If you don’t, you paid for a diagnosis with a prototype and a written fixed quote — not an empty deck.
What does the licence from €390/month include?
What the offer publishes: hosting, security, regulatory and API changes, a ceiling of small changes, business-hours support. Bigger changes: a fixed quote in days.
Barcelona only?
Studio based in Barcelona. Startups and SMEs in the city, the metro area and the rest of Spain. Geo: /en/software/barcelona.
Mobility, Glowapp or Nummo?
No. They are not Wallion products of this service.
Where do we commission?
Startup MVP, under /en/software. This page defines; it does not sell a root /mvp ranking URL.
What this page is not
Not the offer (/en/software/mvp; hub /en/software). Option D only — no invented tariffs. Not Mobility, Glowapp or Nummo. Does not replace when an MVP is worth building or MVP or internal tool: those decide; this defines.
Thirty minutes
If the blocker is “is this an MVP or a tool / a PoC?”, say so in the first conversation. Book a 30-minute call.