A spreadsheet starts well. One process, one person, one month that closes. The problem is not the file. The problem is when the month no longer fits in a cell.
This page is not the offer. It is the question before: is it still a file, or is it already the month? The internal tools offer lives under custom software. If the blocker is the number, the public table is how much custom software costs in 2026.
The short answer
One flow. The one that stops the month when it fails. Quoting, scheduling, tracking, or reporting. One. Not “digitise the company”.
A named owner. Who enters the data. Who sees it. Who answers on the 28th if it does not add up. If that lives in “everyone”, you do not have a process — you have a chat with cells.
One official number. Access per person. No two Friday versions. No rebuilding the figure outside just to show it.
Written scope before the quote. Who, what, what must not fail. Without that page, any tool is another spreadsheet with better type.
If two of the signs below are true, you do not need an essay. You need to decide whether the process is still a file or becomes a tool.
Four signs (with the month on top)
1. Only one person understands it.
If they are out, the month stops. It is not a file. It is a job without a contract. “I keep it in my head” does not scale: it is risk with formatting.
2. Two versions, and nobody knows which one is true.
The desktop copy, the email copy, Friday’s copy. The error is not a formula. It is who holds the last number. When the official figure lives in three places, you do not have a system — you have a weekly fight.
3. Every close needs a workaround.
Copy, paste, “I do this by hand.” The workaround becomes the ritual. Then nobody remembers why. The ritual is the debt: each month more fragile, each month more expensive in hours.
4. The number you show is not the number in the sheet.
You rebuild it in another document because the sheet cannot be shown. If the official figure lives outside, the sheet is no longer the system. It is a draft someone dresses up.
Two signs are enough. Four mean the month depends on human glue — and glue takes holidays.
What not to do (before you commission)
Do not ask for a system that does everything. Copying the sheet into an app with the same holes does not fix the month — it disguises it.
Do not open a quote with no scope. A PDF with a range and no “this is in / this is out” is not a fixed price. It is a hope with a number.
Do not mix an internal tool and a customer-facing product in the same engagement. The spreadsheet’s user is usually the team. If the user is a stranger, that is a different table — MVP or internal tool.
Do not commission “AI on top of Excel” to avoid writing the flow. Guide: AI automation for SMEs.
Start with one flow. Write it on a page: who enters the data, who sees it, what must not fail on the 28th. That is the scope. Without it, there is no tool — only another file.
How this shows up at an SME table (Barcelona / Spain)
You do not need a logo case study. The pattern is the table: a founder still signing quotes, someone in admin keeping the spreadsheet that “almost works”, and a partner (tax firm, ERP house, the a3-style stack next door) quoting the next module when Excel stops.
In Barcelona, the metro area and the rest of Spain, that table usually asks for the same thing: “stop depending on María.” Sometimes the pain is real — a close only one person reconciles, a quote in three folders, a report rebuilt every Monday. Sometimes it is “digitise” without a line. Wallion talks to that profile often: one concrete flow; fixed price; Diagnosis before build. The pattern is the table, not a case study.
If the sheet is the bridge between two systems that already do the work, integrate before you build. If the gap is the work — no system, only cells and ritual — build the flow. Guide: integrate or build.
Failure modes (ones you have seen, or will)
Copying the sheet into an app.
Same holes, better type. The month still depends on the same workaround. Digitising is not migrating cells: it is bounding one flow with an owner and a visible failure.
Quote with no scope.
“A tool to manage sales” is not scope. It is a wish. Whoever signed the number either loses it or reopens it with endless change requests.
Three flows in one fixed price.
Quoting + scheduling + reporting + “and the CRM while we’re at it.” Month two, nobody knows what “done” meant. One flow. Then the next.
Eternal pilot with no owner.
There is an Airtable, a Notion, a script. Nobody watches the queue. Failure shows up at month-end. Visibility first. Then the tool.
Comparing one-flow pricing with an ERP, an MVP or unrelated brands.
A partner module, a minimum product and an internal tool are not the same product. Mobility, Glowapp or Nummo are not this service. Price criterion: how much custom software costs in 2026. Model: fixed price or hourly.
These failures separate a month that closes from a file that accumulates.
What Wallion does (and when not to buy it)
Wallion builds internal tools inside the same custom software service, at a fixed price. It starts with a Diagnosis. One tool / one flow after Diagnosis sits in the published build band. The licence, if Wallion keeps what it built running, is monthly.
The model in one line: a flow the team actually uses; access per person; one official number; small changes without reopening the project; someone who answers when it stops adding up. It fits when you can write the flow on a page and want Diagnosis → fixed price → licence, not a meter “while we digitise”.
Do not buy this model when the process is not written and you want “the tool to discover it”; when the engagement is replacing the whole ERP in one jump; when the user is a stranger and the signal is market (that is an MVP, another table); or when you already own a live backlog and need hands — that is staff augmentation: say it.
If on the call you say “this is one flow, not the whole house”, say it in the first conversation. Geo: /en/software/barcelona.
Public prices (Option D — no invented figures)
Only the numbers that live on the site:
- Diagnosis — €1,900. One workflow audit, prototype, fixed build quote. If you proceed, the Diagnosis 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 — those are a written fixed price, not that band.
- Licence — from €390/month. Hosting, security updates, regulatory and API changes, a ceiling of small-change hours, business-hours support — as published on the offer.
Apps, MVPs and staffing: same model of scope + closed number, different figure, in writing. This page does not invent tariffs. Table and nuance: how much custom software costs in 2026. Offer: internal tools.
Decision checklist (before you commission)
Tick each point. If any stays blank, do not sign “replace the spreadsheet”.
- Can you name one flow that stops the month when it fails — or are you talking about “all of Excel”?
- Who enters the data and who sees it? Is there a named owner?
- Is there one official version, or two (or three) from Friday?
- Is the number you show the one in the sheet, or do you rebuild it outside?
- Does every close need a manual workaround that is already ritual?
- Does scope fit on one page — this is in / this is out — before the quote?
- Do we integrate (A and B already do the work) or build (the gap is the work)?
- Are you comparing the €6,900–14,900 band (one flow) or another written fixed (app/MVP/staffing/ERP)?
- Are you asking for Diagnosis with a scope sentence, or a pilot with no owner?
- Is “done” that the month closes without glue — or “having an app”?
Without those answers, “digitise the spreadsheet” is an adjective, not an engagement.
Questions buyers actually ask
Do we have to throw Excel away entirely?
No. Pull out the flow that stops the month. The rest can stay in a sheet until the next slice. One flow. Then the next.
Is this an “AI” project or an internal tool?
An internal tool. AI enters only if the data already exists and helps — classify, draft, route — not to “think the month”. See AI automation for SMEs.
How much does replacing the spreadsheet cost?
If it is one bounded flow after Diagnosis, the public build band is €6,900–14,900, plus Diagnosis €1,900 (credited if you proceed) and licence from €390/month if Wallion keeps what it built running. Detail: how much custom software costs in 2026.
Does the €6,900–14,900 band cover an app or an MVP?
No. That band is one internal tool / one flow. Apps, MVPs and staffing: written fixed price, not that table.
Is the €1,900 Diagnosis lost if we don’t proceed?
If you proceed, it is credited against the build. 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.
Where do we commission?
Internal tools, under /en/software. If the blocker is code ownership or escrow, read who owns the code. Code ownership and any escrow are set in the project contract, not on this website.
What this page is not
Not the offer (/en/software/internal-tools; hub /en/software). It does not invent tariffs — Option D only; table at how much custom software costs in 2026. It does not treat Mobility, Glowapp or Nummo as Wallion products. It does not promise magic savings: if the flow is one and the scope is written, it can be built; if not, write the flow first.
Thirty minutes
If the blocker is “is it still a file, or already the month?”, say it in the first conversation. Book a 30-minute call.