An MVP and an internal tool look the same size. Both fit in weeks. Both get cut. They are not the same job — not the same price band or test of “done”.
An MVP is used by someone outside. The tool is used by the team. Put both sentences in one scope and you build both badly: the stranger never finishes, the month never closes, and the quote uses the wrong figure.
This page separates. It does not define: what is a studio MVP. It does not decide whether an MVP is worth building: when an MVP is worth building. The commission, depending on the side, lives at startup MVP or internal tools, both under custom software. Wallion does not open a root /mvp ranking URL.
The short answer
| MVP | Internal tool | |
|---|---|---|
| User | Stranger (customer, venue, workshop, buyer) | Internal role (admin, ops, month-end) |
| Cut | Hurts outward | Hurts inward |
| Signal | Returned / paid / asked for the next slice | On the 28th the number is there; the manual step is gone |
| Commission | Written fixed price (a different figure) | Public band €6,900–14,900 = one flow |
| Landing | /en/software/mvp | /en/software/internal-tools |
If both rows fit in the same scope paragraph, they are two projects. Write them apart. Quote them apart.
It is an MVP
There is a stranger. A customer, a venue, a workshop that does not invoice you. They will do one thing the week it ships. You watch whether they return, pay, or ask for the next slice without being sold it.
The cut hurts outward. Screens the stranger does not need for that one thing stay out. The dreamed-of admin panel stays out. Full definition: what is a studio MVP. Decision guide: when an MVP is worth building.
The success test is theirs, not the meeting’s. Did they pay? Return? Ask for the next slice without being pushed? If you measure “does the month close?”, you are not measuring an MVP.
It is an internal tool
The user works here, or invoices here, or closes the month here. There is no stranger. There is a flow that today lives in a spreadsheet, an email, or three tools that do not talk — and that, when it fails, stops the close.
The cut hurts inward. “The whole month” stays out. One flow stays in: the one that stops when it fails. Replacing the sheet that blocks the 28th is the pattern — not “digitising the company”.
The success test is operational. On the 28th the number is there. The person who typed it by hand no longer types it. Nobody “comes back to buy”. The month closes or it does not.
How not to mix them
Do not ask for “an MVP for the team”. That is a half-built tool with a product name. The team is not a market. If only in-house people use it, it is a tool — even if it sounds like a startup.
Do not ask for “a tool we will also sell”. On day one the owner is internal. The stranger arrives later, if they arrive. That later is another commission, another scope sentence, another price. Do not hide it in the same quote.
Do not measure a tool with “did the partners like it?”. Do not measure an MVP with “does the month close?”. Each has its question. If you cannot write it first, do not start.
Do not compare the €6,900–14,900 band with an MVP. That band is one internal tool / one flow after Diagnosis. Apps, MVPs and staffing go to a written fixed price — same model, different figure. Mixing the two in one negotiation is the costliest failure here.
Do not invent a root /mvp. The module hangs off the hub: /en/software/mvp and /en/software/internal-tools.
One line each
MVP: “A [stranger] does [one action] and I see [one signal].”
Tool: “The [role] stops doing [this step] and the [data] lives in [this place].”
Table examples (no invented clients): “A workshop sends the quote and I see whether it is accepted in seven days.” vs “Admin stops copying the close into the sheet and the number lives in the system on the 28th.”
If both lines fit in the same paragraph, they are two projects. Write them apart. Quote them apart. If you cannot tell which line you are writing, do not sign “MVP” or “tool”: you are signing confusion.
Separation table (fast decisions)
| Question | If you answer… | Then it is… |
|---|---|---|
| Who uses it the week it ships? | An outside buyer / venue / workshop | MVP |
| Who uses it the week it ships? | Only people in-house | Tool |
| What do you measure? | Returned / paid / asked for the next slice | MVP |
| What do you measure? | Month closes / manual step disappears | Tool |
| What hurts when you cut? | Screens the stranger does not need | MVP |
| What hurts when you cut? | “The whole month” vs one flow | Tool |
| Which figure do you compare? | Written fixed after Diagnosis | MVP (or app / staffing) |
| Which figure do you compare? | €6,900–14,900 | One tool / one flow |
Failure modes
MVP with an internal user. You call the month’s spreadsheet a product. The “market” is Monday’s meeting. You learn nothing about buyers — and you misprice if you treat the tool band as an external-product fixed (or the reverse).
Tool with a product pitch. “We build it for us and sell it later.” On day one there is no stranger. Scope balloons with sales screens nobody will try. Two commissions in one — both limp.
One sentence, two jobs. “MVP + admin panel + month-end close” in a single scope. Nobody knows what “done” is. The fixed price opens or swells.
Wrong band. You ask for an MVP and anchor on €6,900–14,900. Or you ask for an internal flow and expect a product fixed price. Option D: that band is one tool / one flow; MVP = written fixed.
Staffing labelled as product or tool. Living backlog, you need hands. Say it. It is neither an MVP nor a single-slice fixed-price flow.
Comparing with Mobility, Glowapp or Nummo. They are not Wallion products of this service. They are not a reference.
Public prices (Option D — no invented figures)
Only the numbers on the site.
- Diagnosis — €1,900. Written scope, prototype, fixed build quote. If you proceed, it is credited against the build. Useful to decide which of the two you are before you sign the wrong name.
- 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 (or app / staffing): 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).
Do not mix the tool band with the MVP figure. Offers: MVP, internal tools. Hub: custom software.
What Wallion does (and when not to buy it)
Wallion is a custom-software studio in Barcelona. It builds both — MVPs and internal tools — at different tables: Diagnosis €1,900 (credited if you proceed); one tool / one flow in the €6,900–14,900 band; MVP at a written fixed; licence from €390/month if kept running.
Do not buy “an MVP” when the user is only the team. Do not buy “a tool” when the user is a stranger and the signal is market — or buy it under the right name and the right price. If on the call you say “this is a tool, not an MVP” (or the reverse), say it first. Geo: /en/software/barcelona.
Separation checklist (before you commission)
Tick each point. If any stays blank, do not sign the name yet.
- Is there a stranger — or only the team?
- Is the line “does [action] and I see [signal]” or “stops [step] and the data lives in [place]”?
- Are you measuring external use or month-end close?
- Does the cut hurt outward or inward?
- Can you write what stays out without stuffing the other side into the same paragraph?
- Are you comparing €6,900–14,900 (one flow) or a written MVP fixed price?
- Are you asking for a Diagnosis to choose the name — or an ownerless pilot?
- Have you opened the definition (studio MVP) and the decision (when it is worth building) before signing?
- Do you need a product / tool or hands on a backlog (staffing)?
- Is “done” that a stranger finishes — or that the month closes without manual glue?
Without those answers, the name is marketing — not a commission.
Questions buyers actually ask
Do they look the same size?
Yes: weeks, a cut, one slice. No: user, signal, band, landing.
Can we start with a tool and “productise” later?
You can. That later is another commission. Do not fold it into day-one’s fixed price.
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.
Does the €1,900 Diagnosis help us choose which one?
Yes — written scope, prototype, fixed quote. If you proceed, it is credited. If you don’t, it is 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 each?
MVP or internal tools, under /en/software. This page separates; it does not invent a root /mvp URL.
What this page is not
Not the definition (what is a studio MVP). Not the decision guide (when an MVP is worth building). Not the offer (/en/software/mvp, /en/software/internal-tools; hub /en/software). Option D only — no invented tariffs. Not Mobility, Glowapp or Nummo.
Thirty minutes
If the blocker is “is this an MVP or a tool?”, say so in the first conversation. Book a 30-minute call.