A quote for new software covers the build. Questions about the second year are asked less often, and they matter just as much, because a system the business runs on cannot be left alone the way a printed brochure can. Here is what continues after go-live, and what pushes each cost up or down.
What software maintenance cost is made of
| Cost | What it covers | What makes it larger |
|---|---|---|
| Hosting | The server the system runs on, online or in your office | More users, more branches, more stored documents and photos |
| Backups | Copies of the database kept somewhere else, and restore tests | How often copies are taken and how long they are kept |
| Fixes | Putting right anything that does not work as agreed | Rushed testing before launch, and many integrations |
| Changes | New reports, screens and rules as the business moves | How often prices, taxes, approvals or products change |
| Support | Answering staff questions and helping new joiners | Staff turnover, the number of branches, the hours of cover you expect |
Hosting and backups
Hosting is the most predictable line. A system for one office with a few users needs little. One that serves several branches, a customer app and years of scanned documents needs more. If you host on your own server instead, the bill changes shape rather than disappearing: you now pay for the machine, the power backup, the internet line and someone to look after it.
Backups are cheap to take and easy to neglect. What you are really paying for is the assurance that a copy exists outside the main server and that somebody has tried restoring it. Business software security basics explains what a tested backup means.
Fixes are not the same as changes
Most arguments after launch come from mixing these two. A fix is needed when the system fails to do what the approved screens and the quote said it would. A change is needed when the system does what was agreed and you now want something different. Fixes should be covered for a period stated in the quote. Changes are new work and are quoted as such.
Ask for one sentence in the quote that defines each, with an example. It heads off the most common dispute between a client and a software company.
Bills that come from other companies
Some running costs are not the software company's at all. They are charged by outside providers and should be billed straight to you:
- The domain name and its renewal.
- SMS, email and WhatsApp messaging providers, usually charged by volume.
- Payment gateways, which charge on their own terms.
- Google Play and App Store developer accounts, if you have an app.
- Maps, courier services and anything else the system connects to.
Keep these accounts under a company email. You then see every bill, and nothing stops working if you change supplier.
What drives the total
You may hear that upkeep is a set fraction of what the build cost. Treat that as a guess. Two systems built for the same price can cost very different amounts to run, because the drivers have little to do with the build:
- How much the business changes. A distributor adding new schemes every season asks for more than a workshop with settled routines.
- How many things are connected. Each integration is something another company can alter without telling you.
- How well the first build was specified. Gaps in the scope come back later as paid changes.
- How quickly you need a reply. Cover during office hours costs less than cover late on a Sunday night.
- How well staff were trained. Many support calls are questions, not faults.
Settle it before you sign
Ask for the recurring list
Every item that repeats monthly or yearly, and who it is paid to.
Put accounts in your name
Hosting, domain and outside services registered to the company, with the builder given access.
Define fix and change
In writing, with the period during which fixes are covered.
Agree how support works
The channel, the hours and who answers.
Name one requester
A single person on your side collects change requests, so small asks are grouped rather than sent one at a time.
Review once a year
Check what you are paying for against what is still used, and drop what is not.
At Operix, support runs on one WhatsApp number answered by the people who built the system, and payments are tied to milestones in a written quote. We do not publish prices; the figure depends on modules, users, branches and integrations, as what drives ERP software cost explains. For websites, see website maintenance after launch. If you are planning an ERP for a trade such as distribution and want the running costs listed up front, contact us.
Questions people ask
What does software maintenance include?
Hosting, backups, fixes, changes and support. Some suppliers bundle them and some list them separately, so ask which of the five a quote covers.
Is maintenance a percentage of the build cost?
There is no reliable rule. Running cost follows users, data, integrations and how often you ask for changes, and those differ between two systems built for the same price.
Do I pay for bug fixes?
Faults against the agreed scope should be fixed without charge for a period stated in the quote. New requests are changes, and those are quoted separately.
Is hosting on our own server cheaper?
Not always. You avoid a hosting bill but take on the machine, the power backup, the internet line and someone to look after it. Compare both for your number of branches.
How much does software support cost in Pakistan?
It depends on users, branches, integrations and the hours of cover you want. Operix does not publish prices; ask for the recurring items to be listed in your written quote.