Own vertical software vs vertical SaaS: when fit to process outweighs price
Consultoría Fiscal Levante has been serving SMEs in the Valencia region of Spain for 14 years. 22 employees. A book of 380 recurring clients. In 2024 the head of operations decides to drop the horizontal ERP they had been using and sign up for a vertical SaaS built for tax advisory firms, one of the three big names in the Spanish market. The reason given to the management committee: "it's designed for us, we're not going to reinvent the wheel".
Eight months later the contract is a problem.
Not because the software is bad. It is solid, well maintained, and support actually answers. The problem is something else. Half the team opens the SaaS in the morning, does what it can in there, and by mid-afternoon exports the data to Excel to do the work the SaaS won't allow. The intercompany reconciliation for the group of clients they manage as one. The pipeline for strategic advisory, which is not tax advisory but a separate line. The split of fees by partner and by referring partner. None of that fits in the SaaS. All of it lives in parallel folders.
This is where it gets messy.
What vertical SaaS is, what horizontal SaaS is and what own vertical software is
A horizontal SaaS covers a function that exists in every company in the world: invoicing, CRM, accounting, HR. The sector doesn't matter. Salesforce, Notion, Holded, Factorial. Configurable, extensible, with integrations. It is the off-the-peg suit in a standard size.
A vertical SaaS covers the full process of one specific sector: tax advisory firms, dental clinics, customs agencies, opticians, driving schools, beauty salons. The sector's logic comes built in. Less configuration, more templates. A3 Software, Iberflora, DentalGest, Q10 Academias. It is the sector's suit, cut in a medium size.
Own vertical software (SVP) is a system built for one specific company, on the exact logic that company operates with. It is not bespoke in the craft sense, and it is not a build from scratch that never ends. It is a stable core with that company's operational particularities built into it. It is the suit tailored to the body.
Rule: vertical SaaS assumes you operate like the sector average. SVP assumes you operate the way you operate.
Translation: if your edge over competitors lies in how you do things, vertical SaaS forces you to give that edge up. If your edge lies only in the name and the logo, vertical SaaS will do.
Objective signs that a SaaS is changing your process
These are not opinions. They are observable facts. If three or more of them show up in your monthly operations, the SaaS is already changing your process.
- Parallel Excel. Each team has a spreadsheet that copies data out of the SaaS to run calculations, cross-references or groupings the tool doesn't allow. Nobody maintains it officially. Everybody uses it.
- Double entry. Every piece of data goes in twice: once in the SaaS, once in the system that actually handles the flow. Invoices, case files, fees, whatever it is.
- Free-text field doing the job of a structured field. The SaaS has no field for "referring partner" or "secondary business line", so the team puts it in the notes field using an agreed format. When someone slips, it is lost.
- Reports outside the SaaS. The SaaS produces its standard reports. Nobody uses them to decide anything. Decisions are made from a dashboard built in Google Sheets or Power BI on weekly exports.
- Integrations that break once a month. Zapier, Make or a home-made script moves data between the SaaS and three other tools. Once a month it breaks. Someone spends half a day fixing it.
- Forced renaming. The SaaS calls "client" what you call "account", "case file" what you call "matter", "user" what you call "partner". Internal documentation fills up with translations. New hires take longer to get up to speed.
- Simplified business rules. The commission that used to be calculated on three variables (amount, assigned senior, client type) is now flat because the SaaS only allows flat. Nobody complains out loud. It has been accepted.
If you tick three, you are already operating against the tool. If you tick five or more, the tool is operating against you.
The SaaS isn't failing you. It is doing exactly what it promises: imposing the sector's average way of operating.
The real cost of the workaround
This is the figure almost nobody works out before signing and everybody works out afterwards. It can be measured with three numbers.
First number: monthly hours of double entry. Consultoría Fiscal Levante measured it at the month-eight review. 62 hours a month spread across five people. At €35 an hour of loaded internal cost (cost, not the external billing rate), that is €2,170 a month. €26,040 a year in work that isn't billed, adds nothing and can't be removed without breaking the operational loop.
Second number: the cost of the integrations that hold the workaround up. A Zapier team plan, an external developer spending four hours a month repairing connections, a Power BI licence for the operational dashboard, a data store somewhere so the data can be cross-referenced. Consultoría Fiscal Levante added it up to €780 a month. €9,360 a year.
Third number: opportunity cost. The projects that don't happen because the team is busy holding the loop together. There is no invoice here, only margin that never arrived. At Consultoría Fiscal Levante, two new services planned for 2024 were shelved because the team didn't have the capacity to run them on top of the SaaS. Estimated margin not captured: €40,000 in the first year, recurring.
Add the three numbers. Compare the total with the annual SaaS licence.
In the case of Consultoría Fiscal Levante, the licence cost €14,400 a year. The workaround cost €75,400 a year. On paper, the SaaS was the cheap option.
Critical note: nobody spots the workaround until someone measures it. Nobody measures it because nobody owns that cost. It is spread across five people and three tools.
When the SaaS's initial saving disappears in the first year
Vertical SaaS is bought for three reasons that sound sensible at the decision stage: known price, fast implementation, outsourced maintenance. All three are true, and all three can reverse within months.
Known price. The licence is transparent: X euros per user per month. What the sales sheet leaves out is the cost of the workaround, the cost of the integrations, the cost of the projects that never happen and the cost of training when the team starts using it and doesn't understand the model, because the model isn't yours. These four costs stay invisible until month six.
Fast implementation. The SaaS is connected in two weeks. What really takes time is changing your internal process so that your operations fit inside the tool. That means six to twelve months of friction with the team and of decisions made by default, not by design.
Outsourced maintenance. The SaaS updates, patches and provides support. True. What it doesn't cover are the internal workflows, the integrations you've had to build and the data you've had to pull out. Your team maintains those, or a consultant who bills separately. The outsourcing is only partial.
Rule: the nominal saving of the SaaS appears in month 1. It runs out when the three invisible costs together exceed the licence. In operations with significant sector particularities, that happens between month 6 and month 12.
Translation: if your company operates like the sector average, the nominal saving holds and the SaaS is the right decision. If your company operates differently, the saving turns into overspend before the first financial year closes.
Which operations don't fit a standard vertical SaaS
Not all operational particularities are equal. Some can be fitted into a SaaS through configuration. Others break the model. These are the ones that, in practice, no vertical SaaS on the Spanish market ever fully covers.
- Multi-variable fee rules. Splits by partner, by assigned senior, by service line, by client tenure, by billing bands with thresholds. The SaaS usually allows one or two criteria, not four combined.
- Services that span two verticals. If your firm does tax and employment law, or your clinic is both dental and aesthetic, a single-vertical SaaS forces you to run the other side outside it. The data doesn't cross over.
- Subscription or retainer models reviewed during the year. The SaaS bills by the hour or by case file. Recurring services renegotiated every six months don't fit without keeping two sets of books.
- Client groups with accounts consolidated or split across entities. The SaaS manages client by client. Business groups that operate as one for you are five for the SaaS.
- Approval chains with more than three roles. Standard SaaS has a reviewer and a signatory. If your process needs a technician, reviewer, partner, client and external signatory, the SaaS either simplifies it or pushes it outside.
- Document traceability with versioning per work session. The SaaS keeps the latest version. Your process needs to know which version was sent on 12 March, which one the client brought to the meeting on the 20th and which one was signed on 3 April.
- Business-specific operational metrics. Case files per partner adjusted for complexity. Acquisition cost per line. Retention by segment and cohort year. The SaaS doesn't calculate them. They come out of Excel.
If your operations include three or more of these patterns, vertical SaaS will need a permanent workaround. No integration fixes it, because the problem isn't data connection. It is the mental model.
How to assess whether a sector SaaS fits or forces you to change your operations
There is a simple method. It won't help you decide on gut feel. It helps you decide with data.
Take your current operations and describe them as 20 processes. Not 5, not 50. Twenty. Each process with inputs, outputs, who decides and which rules apply. If you don't have this written down, you already know where to start before looking at any SaaS at all.
Run each of those 20 processes through the candidate SaaS. For each one, there are three possible answers:
- Clean fit. The process fits in the SaaS as it is.
- Fit with minor adaptation. The process fits if you change the naming, the order of steps or the field where the data lives. Acceptable if the process isn't differentiating.
- No fit. The process needs functionality the SaaS doesn't have, or would break a business rule the SaaS doesn't allow.
Count. If you have 16 clean fits, 3 minor adaptations and 1 no fit, the SaaS is your tool. If you have 10 clean, 5 adaptations and 5 no fit, the SaaS will cost you double in the second year. If you have 6 clean, 6 adaptations and 8 no fit, the SaaS isn't a tool for you. It is a change of business model dressed up as software.
The key question for each "no fit" process is this: is it differentiating, or is it a particularity we could drop without losing margin? If it can be dropped, go ahead with the SaaS. If it is differentiating, that process is exactly the one that makes you money. Swapping it for the sector standard means levelling yourself down to the average. The sector average doesn't earn the margin you earn. There's a reason for that.
When own vertical software pays off against a sector SaaS
SVP isn't the answer for every company. It is the answer when three conditions are met at the same time. Fewer than three, stay with the SaaS.
First condition: you have at least three significant operational particularities that a standard SaaS doesn't cover and that genuinely set you apart. Setting you apart means they are part of why clients hire you and not a competitor. Not quirks, not habits inherited out of inertia, not something you could live without.
Second condition: the annual cost of the current workaround (double entry, integrations, parallel Excel, uncaptured opportunities) exceeds 40% of the annual cost of the SaaS. Not 10%, not 20%. 40%. Below that, you adjust and carry on. Above it, the maths changes.
Third condition: you can see at least 24 months of operation ahead. SVP pays for itself operationally between month 12 and month 24 depending on company size. If your business horizon is shorter, there's no point considering it.
If all three are met, the question is no longer SaaS or SVP. The question is which SVP provider to choose. In the Spanish market there are options with a published indicative range. Vertebra Gestión puts complete vertical builds at between €15,000 and €60,000 depending on scope. Cero Ideas works in similar ranges with a breakdown by module. Davisa and ASD Solutions publish a phased methodology with open budgets depending on the specification. Pistacho Digital and Efiprox build vertical software on open foundations. Cleverals quotes after a process audit.
Rule: don't ask an SVP provider for a quote until you have the 20 processes written down and the three conditions assessed. A quote without a specification is guesswork.
Common mistakes when comparing vertical SaaS with own vertical software
Mistake 1: Comparing only licence against build. Symptom: the committee looks at €14,400 a year for the SaaS against €45,000 for the SVP and concludes the SaaS is cheaper. Fix: compare the total annual cost of the SaaS (licence plus workaround plus integrations plus uncaptured opportunity) with the annualised cost of the SVP (build amortised over 3 years plus annual maintenance plus hosting). The real comparison is on total cost.
Mistake 2: Assuming the team will adapt to the SaaS. Symptom: the tool is bought on the assumption that the team will change the way it works. Six months later the team works the same way and uses the SaaS to key in the result. Fix: accept that differentiating processes aren't changed by software. They are changed by a business decision made beforehand. If you aren't going to change the process, don't buy software that requires you to change it.
Mistake 3: Counting implementation as "two weeks". Symptom: the SaaS sales rep promises implementation in 15 days and the committee records that as the transition cost. The real transition takes between six months and a year. Fix: budget the transition as a full internal project, with team hours, training, data migration, process adjustment and a share of productivity lost during the adjustment. Reasonable range: at least 20% of the first-year licence cost.
Mistake 4: Choosing SVP because you "don't like" the SaaS. Symptom: the reason for dropping the SaaS is a feeling, not a measurement. SVP is commissioned in the belief that it will solve any particularity. Fix: use the same method as for the SaaS. Write down the 20 processes and assess what the SVP must do, what it must not do and what will be left out. A badly specified SVP costs as much as a badly chosen SaaS.
Mistake 5: Confusing SVP with permanent development. Symptom: a developer is hired to "keep building" the system. A year and a half later there are 12,000 lines of code, three overlapping architectures, no technical owner and a monthly invoice that never goes down. Fix: SVP is an internal product with a defined scope, delivery milestones and a bounded maintenance arrangement. It is not a developer on an open-ended contract.
Frequently asked questions
When does own vertical software pay off against a sector SaaS?
When three conditions are met at the same time: you have at least three differentiating operational particularities the SaaS doesn't cover, the annual cost of the workaround exceeds 40% of the annual cost of the SaaS, and your operating horizon is at least 24 months. Fewer than three, adjust and stay with the SaaS.
Which operations don't fit a standard vertical SaaS?
Multi-variable fee rules with more than two criteria combined, services that span two verticals, subscription models reviewed during the year, client groups with consolidated accounts, approval chains with more than three roles, document versioning per work session and the business's own operational metrics. If your operations include three or more of these, the workaround will be permanent.
What do you lose by using a vertical SaaS when the company operates differently?
You lose the operational particularities that generate margin. Vertical SaaS imposes the sector's average way of operating, by design. If your margin comes from doing something different (a different fee split, a different way of treating clients, a combined service others don't offer), the SaaS either forces you to drop it or forces you to run it outside the system. Either way, what sets you apart erodes.
How do you assess whether a sector SaaS fits or forces you to change your operations?
Describe your operations as 20 processes with inputs, outputs, decision-maker and rules. Run each one through the candidate SaaS. Count clean fits, minor adaptations and no fits. If you have more than five "no fit" and they are differentiating processes, the SaaS is a change of business model in disguise. If they are processes you can drop without losing margin, go ahead with the SaaS.
How much does own vertical software cost in Spain?
Published market range by provider: between €15,000 and €60,000 for complete vertical builds depending on scope, according to figures published by Vertebra Gestión, Cero Ideas and Davisa. Annualised over three years, the cost usually sits below the total cost of the SaaS when the workaround exceeds 40% of the annual licence. Without a process specification, any quote is indicative.
How long does own vertical software take to pay for itself?
Between 12 and 24 months in mid-sized operations with significant particularities. Operational payback is calculated by comparing the total annual cost of the SaaS (licence plus workaround plus integrations plus uncaptured opportunity) with the annualised cost of the SVP (build spread over three years plus maintenance plus hosting). If the difference is positive from month 13, the SVP pays for itself.
Closing
You won't find Consultoría Fiscal Levante online. It is a case built for this article, but every number in it matches the real orders of magnitude of mid-sized Spanish tax advisory firms. The pattern repeats: vertical SaaS isn't bad. Vertical SaaS imposes its model. And some companies earn their margin precisely by operating against the sector's standard model.
Vertical SaaS is the right decision when you operate like the average. Own vertical software is the right decision when operating like the average costs you more than building your own system. Neither one is a strategy. Both follow from having measured first.
If you want this comparison applied to your case, with the 20 processes written down and the three invisible costs quantified on your real operations, read the page on own vertical software compared with bespoke software or book a 30-minute session and we'll work out together where the break-even point between SaaS and SVP sits in your operation.
Sources and references:
