Operations guide
The real cost of business software, well beyond the monthly price
Seats, add ons, implementation, migration, training and the internal time nobody budgets for. A method for costing it before you sign.
The monthly price is the smallest number in a software decision. Everything else is implementation, migration, training, add ons and the time of your own people, and almost none of it appears in a quote.
The lines a quote contains
Subscription or licence, number of seats, and any modules priced separately. That is usually the whole quote, and it is genuinely useful for comparing like with like at the entry point.
It is also where the comparison usually stops, which is why businesses are surprised in year two rather than in month one.
The lines it does not
Implementation or setup, data migration from whatever you run now, training for the people who will use it, integrations to the other systems it must talk to, and any add on that fills a gap the core product leaves.
Then the ongoing ones. Support beyond what is included, the annual uplift most vendors apply, and the cost of moving up a tier when you outgrow a limit on invoices, contacts or users.
The line nobody budgets
Your own people. The person who knows how your stock actually moves, or how your commission is really calculated, is the only one who can tell an implementer what the system must do, and they already have a full time job.
On an ERP project this is frequently the single largest cost in the true total and it never appears in a proposal. Estimate the days honestly and cost them at what those people are worth. A business case that ignores this is not a business case.
A method that takes an hour
Build three columns for three years. Year one carries subscription plus implementation plus migration plus training. Years two and three carry subscription plus an assumed uplift plus the tier increase you expect as you grow.
Add the add ons you know you will need. For accounting that usually means payroll and document capture. For CRM it usually means the automation tier. Then compare products on the three year total rather than on the monthly price.
Ask what leaving costs
Before you sign, ask what happens if you leave. Can you export everything in a usable format, how long do you have, and what does the provider keep.
A product with a poor export has a switching cost built into it, and that cost is real even if you never pay it. It belongs in the comparison alongside the price.
Watch the annual uplift clause
Most subscription agreements allow the vendor to raise the price each year, often by a stated percentage or by an inflation measure. Over three years that compounds into a meaningful difference between two products that looked identical on day one.
Ask what the uplift has been for the last two years rather than what the contract permits. The permitted ceiling and the actual behaviour are usually different, and the second one is what you will pay.
Common questions
01What is total cost of ownership for business software?
Everything you spend over the life of the system. Subscription or licence, implementation, migration, training, integrations, add ons, support, price increases and the internal time your own staff spend on it.
02How much should I budget for implementation?
For cloud accounting or payroll, often little beyond your own time. For an ERP, implementation commonly equals or exceeds the first year of licence, and internal time is usually larger again.
03How far ahead should I model software cost?
Three years. It is long enough to capture tier increases and annual uplifts and short enough that your assumptions about the business are still credible.
Editorial note
This guide is general buying guidance and not accounting, legal or tax advice. Amounts and deadlines set by SARS change, so confirm the current figures for your own business before you rely on them.