Software Maintenance Costs in Nigeria: What to Budget
Most Nigerian businesses budget carefully for building software and barely at all for keeping it alive. The result is predictable: two years after go-live, the system that runs stock, invoicing or customer records is behind on updates, nobody has restored a backup, the developer who built it has moved on, and the first serious incident costs more than three years of support would have.
Maintenance is not an optional extra on custom software. It is the price of continuing to own a working system. This guide sets out what maintenance actually covers, what it costs in naira, what drives the number up, and how to read a maintenance quotation properly.
How much does software maintenance cost in Nigeria?
The standard commercial frame is a percentage of the build cost per year. Simple internal tools sit near the bottom of the range; systems with payment integrations, multiple user roles, regulatory obligations or heavy data volumes sit at the top.
Indicative 2026 ranges, excluding hosting and third-party licences. Actual quotes vary with scope, vendor and exchange rate.
| System size and type | Indicative build cost | Yearly maintenance | Monthly equivalent |
|---|---|---|---|
| Small internal tool, single team | ₦2,000,000–₦4,000,000 | ₦300,000–₦800,000 | ₦25,000–₦67,000 |
| Departmental system, few integrations | ₦4,000,000–₦8,000,000 | ₦600,000–₦2,000,000 | ₦50,000–₦167,000 |
| Business-wide system with payments | ₦8,000,000–₦15,000,000 | ₦1,200,000–₦3,750,000 | ₦100,000–₦313,000 |
| Multi-branch or multi-role platform | ₦15,000,000–₦30,000,000 | ₦2,250,000–₦7,500,000 | ₦188,000–₦625,000 |
| Regulated or mission-critical platform | ₦30,000,000+ | 20–25% of build, often higher | Quoted individually |
Some vendors quote a flat monthly retainer instead of a percentage. That is fine, provided the retainer states clearly how many support hours or requests it covers and what happens when you exceed them. A flat fee with unlimited scope is either mispriced or will be renegotiated within a year.
What software maintenance actually includes
Maintenance is not one activity. It is four, and a good quotation separates them because they behave differently.
Corrective maintenance: fixing what is broken. Bugs found in production, failed integrations, data errors, incorrect calculations. Typically the smallest share of the cost in a well-built system, and the most visible.
Adaptive maintenance: keeping up with the outside world. Operating system and framework updates, security patches, changes forced by payment gateways, banks, tax requirements or browsers. This work is unavoidable and is not triggered by anything you did. It is the reason a system left alone for two years stops working even though nobody touched it.
Perfective maintenance: improving what exists. Small features, report changes, new fields, workflow adjustments, performance tuning. Usually the largest share of a healthy retainer, because a system in active use generates a steady stream of sensible small requests.
Preventive maintenance: reducing future cost. Refactoring problem areas, improving test coverage, cleaning up data, upgrading dependencies before they reach end of life, documenting undocumented behaviour. The easiest to cut and the most expensive to skip.
A retainer that only covers corrective work is a warranty, not maintenance. Ask which of the four categories a quotation includes.
What drives the cost up or down
| Factor | Pushes cost up | Pushes cost down |
|---|---|---|
| Integrations | Many external systems, payments, banks, SMS | Self-contained system |
| Users and roles | Multiple roles, branches, permission rules | Single team, one role |
| Data volume | Millions of records, heavy reporting | Modest, stable data |
| Uptime expectation | 24/7 with fast response commitments | Business hours, best-effort |
| Code quality and tests | Undocumented, untested legacy code | Documented, tested, modern stack |
| Technology choice | Rare stack with few local developers | Mainstream, widely supported stack |
| Regulatory exposure | Financial, health or personal data at scale | Internal operational tooling |
| Rate of change | Frequent process or pricing changes | Stable processes |
| Vendor arrangement | Agency with team, QA and cover | Single freelancer, no cover |
| Currency exposure | Dollar-priced hosting, licences and APIs | Locally hosted, few paid services |
The two that most often surprise buyers are technology choice and code quality. A system written in an unusual stack costs more to maintain for the rest of its life because fewer developers can work on it, and switching vendors becomes expensive. That decision is made on day one of the build, not at maintenance time.
One-off versus recurring: the full cost of ownership
Separate these lines in every budget. Indicative 2026 figures for a mid-sized Nigerian business system.
| Cost line | One-off | Recurring | Notes |
|---|---|---|---|
| Design and development | ₦4,000,000–₦15,000,000 | No | Business Software Development Cost in Nigeria covers build costs |
| Data migration and setup | ₦300,000–₦2,000,000 | No | Often underestimated |
| Training and rollout | ₦150,000–₦1,000,000 | Occasionally | Repeat as staff turn over |
| Maintenance retainer | No | 15–25% of build yearly | The subject of this article |
| Cloud or VPS hosting | No | ₦150,000–₦800,000+ yearly | Scales with users and data |
| Database backups and storage | No | ₦50,000–₦400,000 yearly | Offsite copies included |
| Third-party licences and APIs | No | Varies, usually USD | SMS, mapping, identity, email |
| Security certificates | No | ₦0–₦100,000 yearly | Often included in hosting |
| Major version upgrades | Every 3–5 years | No | Budget separately |
| Internal administration time | No | Staff time | Someone must own the system |
A practical planning rule for Nigerian SMEs: assume the true five-year cost of a custom system is roughly double the build price. If the build is ₦8,000,000, plan for something near ₦16,000,000 across five years including maintenance, hosting, licences and one significant upgrade. If that number is unaffordable, the honest conversation is about scope or about buying existing software, which When Should You Buy Existing Software? covers.
Support tiers and what each one buys
| Tier | Typical monthly cost | What you get | Suits |
|---|---|---|---|
| Pay-as-you-go | ₦0 plus hourly rate | No commitment, no priority, no patching | Stable, low-risk internal tools |
| Basic support | ₦50,000–₦120,000 | Bug fixes, security updates, backups checked | Small departmental systems |
| Standard retainer | ₦120,000–₦350,000 | Above plus defined hours for changes, monitoring, response times | Most business-wide systems |
| Managed service | ₦350,000–₦900,000+ | Above plus infrastructure, on-call cover, reporting | Payment-handling or multi-branch platforms |
Indicative 2026 figures; scope and response commitments vary widely between vendors.
Pay-as-you-go looks cheapest and frequently is not. When something breaks, you join a queue behind retained clients, the developer needs time to re-familiarise themselves with the code, and the work is billed at full rate. For anything a business depends on daily, a retainer buys priority and continuity more than it buys hours.
The recurring costs businesses forget to budget
- Exchange-rate movement. Cloud hosting, email services, SMS gateways, mapping and identity-verification APIs are dollar-priced. Your naira bill changes without any change in usage. Review annually and keep some headroom.
- Data growth. Storage, backup size and query cost all rise with transaction volume. A system that costs ₦25,000 a month to host at launch may cost several times that at year three.
- Licence renewals. Paid libraries, reporting tools and components renew yearly, often silently on a card.
- Key-person risk. If one developer holds all the knowledge, their unavailability is a cost, whether you pay it in downtime or in emergency rates. Documentation is cheaper.
- Compliance work. Changes to tax treatment, reporting formats or data-protection obligations create work you did not plan. Verify current requirements with the relevant body, such as FIRS for tax matters or the Nigeria Data Protection Commission for personal data.
- Integration breakage. When a bank, payment provider or courier changes an API, you must follow. This is adaptive maintenance and belongs in the retainer.
- Staff turnover. New users need training. Budget a refresher session each year rather than assuming knowledge transfers informally.
Example (hypothetical): a distribution system's annual running cost
Example (hypothetical). A building-materials distributor in Ibadan runs a custom system covering stock across three warehouses, sales orders, credit limits, van dispatch and management reporting. It was built for approximately ₦9,000,000 eighteen months ago.
| Line | Indicative annual cost |
|---|---|
| Maintenance retainer at 18% of build | ₦1,620,000 |
| Cloud hosting and database | ₦520,000 |
| Offsite backup storage | ₦160,000 |
| SMS and email notifications | ₦240,000 |
| Paid reporting component licence | ₦180,000 |
| Annual staff refresher training | ₦150,000 |
| Contingency at 10% | ₦287,000 |
| Indicative total | ₦3,157,000 |
That is roughly ₦263,000 a month to keep a ₦9,000,000 system reliable, current and improving, equating to about 35 per cent of the build cost per year once infrastructure and licences are included. The figure looks large until it is compared with the alternative: the distributor estimates that a full day of system downtime during peak season disrupts dispatch across all three warehouses. Framed that way, the retainer is insurance with a productivity dividend attached.
The distributor's second observation is more useful. Nearly two-thirds of the retainer hours in the past year went on perfective work, mostly report changes and workflow adjustments requested by the sales team, not on fixing faults. That is what a healthy maintenance relationship looks like.
How to compare maintenance quotations
Ask every vendor to answer the same questions in writing, then compare like with like. How to Review a Software Development Proposal covers reviewing a software development proposal more broadly; this list is the maintenance subset.
- Which of the four maintenance categories are included: corrective, adaptive, perfective, preventive?
- How many hours or requests per month are covered, and what is the rate beyond that?
- What are the response and resolution targets, by severity, and during what hours?
- Who is the named contact, and what cover exists when that person is unavailable?
- Are security patches and dependency updates included, or billed separately?
- Are backups included, where are they stored, and how often is a restore tested?
- Is infrastructure management included, or only application code?
- Who pays for third-party licences and hosting, and in which currency?
- What reporting will you receive, and how often?
- What is the notice period, and what happens to your code and data on exit?
- Are major version upgrades included or quoted separately?
- How are emergency out-of-hours incidents handled and charged?
A quotation that cannot answer the severity, response-time and exit questions is not a maintenance agreement; it is an invoice with hope attached.
What changes for Nigerian businesses
Currency exposure is structural, not incidental. A meaningful share of your recurring cost is dollar-denominated. Build that into the budget explicitly and revisit it each year rather than treating a higher renewal as an unpleasant surprise.
Power and connectivity affect support delivery, not just uptime. If your vendor is a two-person team, an outage on their side delays your fix. Ask directly what cover exists. This is one of the clearest arguments for an agency retainer over a single freelancer for systems that matter.
The local developer pool shapes your leverage. Mainstream technologies mean more vendors can quote, which keeps maintenance pricing competitive. Niche stacks lock you to one supplier. This is worth weighing at build time.
Informal arrangements dominate at SME level. Many businesses run critical systems on a WhatsApp relationship with one developer and no written agreement. It works until it does not. A two-page support agreement covering response times, hours, backups and exit is inexpensive and changes the outcome of every future dispute.
Data protection obligations are continuous. If the system holds customer or staff personal data, the Nigeria Data Protection Act 2023 applies throughout its life, not only at build. Access control, retention and breach response are maintenance activities. Verify current requirements with the Nigeria Data Protection Commission.
Payment and banking integrations change locally. Gateways and banks update APIs and settlement processes. Whoever maintains your software must track those changes, and that work should be inside the retainer rather than billed as a surprise.
How to reduce maintenance cost without adding risk
- Choose a mainstream stack at build time. The single biggest lever on lifetime maintenance cost, and it is only available once.
- Insist on documentation and tests as delivery milestones. Undocumented systems cost more forever.
- Keep the code and infrastructure in your own accounts. Switching vendors becomes a commercial decision rather than a rescue operation. Who Owns Custom Software Code? covers ownership of custom software code.
- Batch small change requests. Ten changes released together cost less than ten separate releases.
- Cut unused features. Every screen nobody uses still has to be tested, patched and hosted.
- Right-size the hosting. Many Nigerian SMEs over-provision at launch and never revisit it.
- Train an internal owner. Someone who can handle user administration, basic data fixes and first-line questions removes a steady trickle of billable requests.
- Schedule preventive work deliberately. A planned dependency upgrade costs less than an emergency one after a security advisory.
- Review third-party services yearly. Unused licences and oversized plans accumulate quietly.
- Do not cancel the retainer to save money. Restarting after a lapse usually costs more, because the accumulated updates must be done at once.
Mistakes to avoid
- Treating maintenance as optional. Adaptive work happens whether you budget for it or not; the only choice is planned or emergency.
- Accepting an unlimited flat fee. It will be renegotiated or quietly rationed. Define the scope.
- Ignoring hosting and licences. They are frequently a third of the true running cost.
- Paying for support with no response commitments. Availability, not hours, is what you are actually buying.
- Letting the vendor own the infrastructure accounts. It removes your ability to move.
- Skipping restore tests. A backup nobody has restored is an assumption.
- Cutting preventive maintenance first. It is the line that quietly increases every future line.
- Having no internal owner. Systems without an internal owner accumulate workarounds instead of fixes.
- Not budgeting for a major upgrade. Every system needs a significant modernisation every few years. Plan for it.
Conclusion
Budget an indicative 15 to 25 per cent of the build cost per year for maintenance of custom software in Nigeria, then add hosting, backups and third-party licences, which together often take the realistic total closer to 30 to 35 per cent. Over five years, plan for total ownership cost of roughly twice the build price, including one significant upgrade.
Buy the right things with that money: adaptive work that keeps the system compatible, preventive work that stops cost compounding, defined response commitments rather than vague availability, and monthly reporting that shows where the hours went. Keep your code, data and infrastructure in your own accounts so that changing vendors stays a commercial decision. Handled that way, maintenance is not a drain on a software investment; it is what turns a one-off build into a system the business can rely on for years.
If you are budgeting for a new system or reviewing what you currently pay to keep one running, Linestech provides structured software support with defined scope, response commitments and monthly reporting, and can audit an existing system before recommending a tier. Tell us what the system does and where it currently hurts.
Frequently asked questions
Is software maintenance really 15 to 25 per cent of build cost every year?
It is the common commercial range for custom business software, but treat it as a planning anchor rather than a rule. Simple internal tools with few integrations can run lower; systems handling payments, several branches or regulated data often run higher once hosting and licences are added. Ask any vendor to justify their percentage against the four maintenance categories.
Can I skip maintenance for a year to save money?
You can, but the saving is usually borrowed rather than earned. Security patches, dependency upgrades and integration changes accumulate, and restarting support after a lapse typically costs more than continuous coverage because the backlog must be cleared at once. If budget is genuinely tight, reduce the scope to security, backups and monitoring rather than stopping altogether.
What is a reasonable response time to expect?
It depends on severity and what you pay for. A common structure is a few hours for critical faults that stop the business, one business day for significant issues with a workaround, and a few days for minor items. Response time is when someone starts work, not when it is fixed. Both should be stated in the agreement, along with the hours they apply to.
Should maintenance be handled by the original developer?
Usually yes, if the relationship works, because they know the system. It is not essential where the code is documented, the repository and infrastructure are in your accounts, and the stack is mainstream. Keeping those three conditions true is what gives you the option to change vendors without a crisis.
Does maintenance include new features?
Only if the agreement says so. Most retainers include a defined allowance of small changes, with anything substantial quoted as a project. Get the boundary written down: what counts as a change request within the retainer, what counts as a project, and who decides. Ambiguity here damages otherwise good vendor relationships.
How do maintenance costs compare with off-the-shelf software?
Off-the-shelf software replaces maintenance with subscription, typically priced per user per month in dollars, and the vendor handles updates and infrastructure. Custom software costs more to maintain but does not scale its price with headcount. For a business with many users and simple needs, off-the-shelf usually wins on total cost; for distinctive processes or large teams, custom can be cheaper over five years.
What happens to maintenance cost as the system grows?
It rises, mainly through hosting, data storage and the volume of change requests from active users. Expect the retainer to be reviewed annually. A well-run vendor will show you where the hours went before proposing an increase, which is a good reason to insist on monthly reporting from the start.
Who should own the system internally?
A named person with enough authority to prioritise requests and enough access to handle routine administration. In smaller Nigerian businesses this is often an operations manager rather than a technical specialist. What matters is that requests are filtered and prioritised internally, instead of every staff member messaging the developer directly.
Sources and further reading
Figures, platform rules and regulations change. These are the primary references behind this article and the places to check before you act on it.
