Skip to content

The Maintenance Iceberg

By Tomasz Lewandowski · 15 Oct 2026 · 7 min read

The Maintenance Iceberg
The Maintenance Blueprint — Total Cost of Ownership

Why the First Quote Is Not the Full Cost

A software build quote can feel like the main financial decision. It is visible, specific and often substantial. Yet it is only the tip of the iceberg. Beneath it sit the continuing costs of hosting, support, security, backups, updates, bug fixes, user management, training, integrations, device changes and future improvements. If these are not planned, the system may become more expensive, less secure or harder to maintain than expected.

This does not mean software is a poor investment. It means it should be budgeted like a business asset, not a one-off purchase. A maintenance system is closer to a vehicle fleet than a printed brochure. It needs upkeep. It will be used daily. It will face changing conditions. It will occasionally need repair. A responsible budget looks beyond launch and considers the full life of the system.

Understanding Hosting, Support and Security

If your system is cloud-based, it must live somewhere. Hosting costs may vary depending on user numbers, storage, traffic, backups and performance needs. Support costs cover the human help required when users are locked out, bugs appear, data needs correcting or small changes are required. Security costs may include updates, monitoring, access control, penetration testing or compliance work, depending on the sensitivity of the data.

These items are easy to overlook because they are less exciting than features. Yet they protect the system's reliability. A maintenance app may contain client data, site access notes, asset histories, staff details and commercial information. It deserves proper care. Ask early: who hosts it, who monitors it, who applies updates, who restores backups, who responds if something breaks, and what service level is included? Clear answers prevent unpleasant surprises.

What Technical Debt Really Means

Technical debt is the future cost created when corners are cut in the present. Sometimes it is a sensible trade-off. A business may choose a quick workaround to launch a pilot and learn from real users. The danger comes when shortcuts are taken without being recorded, understood or repaid. Over time, the code becomes harder to change, bugs become more likely and every improvement costs more than it should.

The term is useful because it behaves like debt. A shortcut can save time today, but it may accrue interest. For example, building a feature quickly without proper structure may work for 20 users but fail for 200. Skipping documentation may be harmless until the original developer leaves. Ignoring automated tests may speed the first release and slow every release after that. Technical debt is not always bad. Unmanaged technical debt is the problem.

The Risk of Cheap Development

A cheap build can be tempting, especially when budgets are tight. Some low-cost options are perfectly suitable for simple needs. The risk is choosing on price alone without understanding what has been omitted. Has the developer included testing? Documentation? Security updates? Backup routines? Error handling? User permissions? Future support? Clean code structure? If not, the initial saving may become expensive later.

The cheapest quote may also rely on building exactly what is requested with little challenge or discovery. That can be dangerous if the requirements are incomplete. A stronger development partner will ask awkward questions, clarify workflows and warn about future consequences. This may cost more at the start, but it can prevent costly rework. In maintenance terms, cheap development can resemble fitting the wrong part because it was on the shelf. It may run for a while, but confidence is limited.

Budgeting for the Life of the System

A practical budget should separate build costs from running costs. Build costs include discovery, design, development, testing, migration and launch. Running costs include hosting, support, maintenance, updates, security, backups and minor improvements. There may also be periodic costs for larger enhancements, integrations, reporting changes or new user groups. Thinking in annual terms helps. What will this system cost to operate in year one, year three and year five?

This longer view supports better decisions. A feature that is cheap to build but expensive to maintain may be less attractive than one that costs more upfront and remains stable. A custom integration may be valuable, but only if the business can support it when the other system changes. A sustainable budget is not pessimistic. It is what allows the system to remain useful after the launch enthusiasm fades.

Ownership After Launch

One of the most important questions is who owns the system after launch. Ownership includes more than paying invoices. Someone must decide priorities, approve changes, manage users, review data quality, monitor support issues and maintain the relationship with the developer or supplier. Without ownership, small issues accumulate until the system feels neglected.

This owner does not need to be technical, but they do need authority and curiosity. They should understand the business process, listen to users, track recurring problems and make sensible decisions about improvements. They should also keep documentation and supplier details accessible. If the person who commissioned the build moves on, the business should still know how the system works, who supports it and what obligations exist. Good ownership protects continuity.

Planning for Change and Growth

Your maintenance operation will change. You may win larger contracts, add engineers, introduce new service lines, change reporting requirements or integrate with accounting, stock or client systems. A system built only for today's exact shape may struggle tomorrow. This does not mean overbuilding from the start, but it does mean asking how the system can grow.

Discuss scalability with the developer. Can it handle more users and assets? Can fields be added without breaking reports? Are integrations possible? Is the database structured sensibly? Is the code documented? Are permissions flexible? These questions help distinguish a quick tool from a durable platform. The aim is not to predict every future need. It is to avoid choices that make reasonable future needs unnecessarily difficult.

Seeing the Whole Iceberg

The maintenance iceberg is not a warning against digital investment. It is a warning against partial budgeting. A well-designed system can reduce chaos, improve evidence, strengthen client reporting and save substantial time. But it must be treated as a living part of the business. It needs care, funding and ownership.

Before committing, ask for the whole picture. What is included in the build? What is excluded? What will it cost to run? How will it be supported? What technical debt is being accepted? What happens when changes are needed? These questions may seem less exciting than screen designs, but they are essential. The visible quote matters. The hidden costs matter too. Sensible owners look below the waterline before setting sail.

A Common Mistake to Avoid

The common mistake is to compare suppliers only on build price. A lower quote may exclude items that another supplier has included: testing, support, documentation, backups, security updates, migration help or post-launch fixes. Without comparing like with like, the cheaper option may not really be cheaper. It may simply push cost into the future.

Ask every supplier for a full cost picture. What is included in year one? What happens in year two? How are changes priced? What support response is guaranteed? Who owns the code and data? How are backups restored? What happens if the supplier relationship ends? These questions may feel cautious, but they are normal business due diligence. A digital maintenance system deserves the same scrutiny as any other long-term asset.

The Practical Next Step

Create a five-year cost table before approving the project. Include build, hosting, support, security, updates, training, migration, integrations, devices and an annual improvement allowance. Some numbers will be estimates, but the exercise will expose assumptions. It will also help you compare options more fairly.

Then ask what happens if the system succeeds. More users, more assets and more clients can increase storage, support and feature demands. A system that works well will be used more heavily, so plan for growth rather than only launch. Looking below the waterline before you commit is not negativity. It is responsible ownership.

A Measure of Progress

A useful measure of progress is whether system costs become predictable rather than surprising. The business should know what it pays monthly, what support includes, what improvements are planned and what risks are accumulating. Review technical debt in plain language at least twice a year. Ask what shortcuts exist, whether they still make sense and what should be repaid before growth makes them more expensive.

The Business Owner's Takeaway

The business owner's takeaway is that the first quote is only part of the decision. Budget for hosting, support, security, change and ownership across the life of the system. A cheaper launch can become an expensive burden if the hidden costs are ignored. Look below the waterline before committing.

How to uncover the true total cost of ownership before approving a software project

  1. Separate build costs from running costs. Split the budget into build costs (discovery, design, development, testing, migration and launch) and running costs (hosting, support, maintenance, updates, security, backups and minor improvements), and account for periodic costs for larger enhancements, integrations, reporting changes or new user groups.
  2. Build a five-year cost table. Before approving the project, create a five-year cost table that includes build, hosting, support, security, updates, training, migration, integrations, devices and an annual improvement allowance. Some numbers will be estimates, but the exercise exposes assumptions and helps you compare options more fairly.
  3. Ask suppliers for a full cost picture. Ask every supplier what is included in year one, what happens in year two, how changes are priced, what support response is guaranteed, who owns the code and data, how backups are restored, and what happens if the supplier relationship ends, so you compare like with like rather than build price alone.
  4. Confirm hosting, support and security responsibilities. Ask early who hosts the system, who monitors it, who applies updates, who restores backups, who responds if something breaks, and what service level is included, because clear answers prevent unpleasant surprises.
  5. Plan for growth, not just launch. Ask what happens if the system succeeds, since more users, assets and clients increase storage, support and feature demands. Discuss scalability with the developer: can it handle more users and assets, can fields be added without breaking reports, are integrations possible, is the database structured sensibly and are permissions flexible?
  6. Assign an owner for after launch. Name someone with authority and curiosity to decide priorities, approve changes, manage users, review data quality, monitor support issues, keep documentation and supplier details accessible, and maintain the relationship with the supplier.
  7. Review technical debt in plain language twice a year. At least twice a year, review accumulating technical debt in plain language by asking what shortcuts exist, whether they still make sense and what should be repaid before growth makes them more expensive, aiming for system costs that are predictable rather than surprising.

Frequently asked questions

Why is the software build quote not the full cost of the system?

The build quote is only the visible tip of the iceberg. Beneath it sit ongoing costs such as hosting, support, security, backups, updates, bug fixes, user management, training, integrations, device changes and future improvements. If these are not planned for, the system can become more expensive, less secure or harder to maintain than expected.

What is technical debt and is it always bad?

Technical debt is the future cost created when corners are cut in the present, and it behaves like financial debt because a shortcut can save time today but accrue interest later. It is not always bad; choosing a quick workaround to launch a pilot and learn from real users can be a sensible trade-off. The danger is unmanaged technical debt taken without being recorded, understood or repaid, which makes code harder to change and every improvement more expensive.

Is a cheap software build a good idea for a small business?

Some low-cost options are perfectly suitable for simple needs, so cheap is not automatically wrong. The risk is choosing on price alone without understanding what has been left out, such as testing, documentation, security updates, backup routines, error handling, user permissions, future support or clean code structure. A cheap quote may also build exactly what is requested with little challenge or discovery, which is dangerous if the requirements are incomplete, so the initial saving can become expensive later.

How should I budget for a maintenance software system?

Separate build costs from running costs. Build costs include discovery, design, development, testing, migration and launch, while running costs include hosting, support, maintenance, updates, security, backups and minor improvements. Think in annual terms and ask what the system will cost to operate in year one, year three and year five, because a feature that is cheap to build but expensive to maintain may be less attractive than one that costs more upfront and stays stable.

Who should own a software system after it launches?

Every system needs an owner who does more than pay invoices. That person decides priorities, approves changes, manages users, reviews data quality, monitors support issues and maintains the relationship with the supplier. They do not need to be technical but they do need authority and curiosity, and they should keep documentation and supplier details accessible so the business still knows how the system works if the original commissioner moves on.

What questions should I ask suppliers before approving a software project?

Ask for the whole picture rather than comparing on build price alone. Find out what is included and excluded from the build, what it will cost to run, how it will be supported, what technical debt is being accepted, and what happens when changes are needed. Also ask what is included in year one, what happens in year two, how changes are priced, who owns the code and data, how backups are restored, and what happens if the supplier relationship ends.

Share Follow
Avoiding Scope Creep
The Maintenance Blueprint

Avoiding Scope Creep

Most software projects do not fail because of one bad decision. They drift off course through a hundred small additions that seemed harmless at the time.

24 Sep 2026 · 7 min read
Speaking Developer
The Maintenance Blueprint

Speaking Developer

A developer can build what you ask for, but not necessarily what your maintenance business needs. The difference lies in the brief.

17 Sep 2026 · 7 min read
When Excel Starts to Leak
The Maintenance Blueprint

When Excel Starts to Leak

Excel is often where good maintenance systems begin. It is also where they start to fail when too many people, versions and assumptions creep in.

3 Sep 2026 · 7 min read