What Drives the Cost of Maintaining a Custom Web App

MicroPyramid 6 min read

What Drives the Cost of Maintaining a Custom Web App

The cost of maintaining a custom web app depends on eight things: how big and how old the codebase is, how much of it is covered by tests, how many outside services it depends on, how often you release, the support hours you need, how far behind its frameworks are, how much new feature work you want each month, and how sensitive the data is. Two apps that look alike from the outside can differ several times over on these, which is why maintenance quotes vary so widely.

The useful question is not "what does maintenance cost?" but "where does my app stand on each driver?" Once you know that, quotes become comparable, and you can see which drivers are worth reducing.

The eight cost drivers

Driver Costs more when Costs less when
Size and age of the codebase It is large, old, and written by several teams in different styles It is small, recent and consistent
Test coverage Nothing is tested, so every change is checked by hand Key flows have automated tests that run on every change
Integrations It depends on many payment, email, SMS, AI, partner and data APIs It has a few well-documented integrations
Release pace You ship several times a week, each needing review and checks You release on a predictable monthly cycle
Support hours Someone must respond outside business hours or across many time zones Business-hours support is enough
Framework age Django, Python, Node or other core parts are near or past end of life The stack is on supported versions
Feature work You want a steady flow of new features alongside upkeep You mainly need fixes and updates
Data sensitivity It handles health, financial or personal data with audit needs It holds low-risk data

1. Size and age of the codebase

More code means more to understand, more to update and more places for bugs. Age matters as much as size: older code tends to use patterns and libraries the current team has to learn, and it often carries workarounds nobody remembers the reason for.

2. Test coverage

Tests are the biggest single lever on maintenance cost. Without them, every change has to be checked by hand, and every upgrade is a risk. With good tests on the important flows (sign-up, payments, the core workflow), changes are faster and safer, and the cost of each fix drops.

3. Integrations

Every outside service is something that can change without warning: a payment provider retires an API version, an email service changes its limits, an AI model is deprecated. Each integration adds monitoring and occasional rework, so an app with fifteen integrations costs more to keep running than one with three.

4. Release pace

Shipping often is good for the product, but each release needs review, testing and a deploy someone watches. A predictable release rhythm with automated deploys keeps this cost low; ad hoc releases done by hand keep it high.

5. Support hours

Business-hours support costs less than cover outside business hours. Many apps need fast response only for real outages, not for every minor bug, so it pays to define severity levels and agree response targets for each rather than buying the highest level of cover for everything.

6. Framework age

An app on supported versions needs routine updates. An app on a framework or runtime past its end-of-life date first needs an upgrade project, and until then carries security risk that security reviews will flag. Planning upgrades ahead of end-of-life dates is cheaper than doing them in a hurry.

7. Feature work

Maintenance in the narrow sense means keeping the app working. Most companies also want it to keep improving. The split between upkeep and new features is usually the largest factor in a monthly retainer, and it is the one you control most directly.

8. Data sensitivity

Apps that handle health, financial or personal data need more care: access controls, audit logs, encrypted backups, careful handling of test data and more review before changes go live. That care is worth paying for, but it should be visible in the scope rather than hidden in the price.

How to compare maintenance quotes

Quotes are only comparable when they cover the same things. Ask each provider:

  • What is included? Fixes, security patches, dependency updates, framework upgrades, monitoring, backups with tested restores, and new features. Many quotes cover only some of these.
  • What happens to unused time? Whether hours roll over, expire, or can be moved between upkeep and features.
  • How are urgent issues handled? Severity levels, response targets and support hours, in writing.
  • What do you get in writing? A runbook, an access map and regular reports, so you are not dependent on one person.
  • What are the terms? Minimum term, notice period, and what happens to your code and accounts if you leave.

How to bring the cost down without cutting corners

  • Add tests around the parts that change most. This pays back faster than any other investment.
  • Upgrade before end of life, on a schedule, rather than in a crisis.
  • Remove what you no longer use: old features, unused integrations and abandoned servers all cost money to keep safe.
  • Automate deploys and backups, so routine work stops needing an engineer's attention.
  • Agree severity levels so you pay for fast response only where it matters.

How we price maintenance at MicroPyramid

We do not publish a price list, because the drivers above differ so much between apps. Instead, a fixed-scope Takeover Assessment measures where your app stands on each driver, and ends with a fixed monthly fee for the retainer, so you know the cost before the retainer starts. The retainer runs month to month with 30 days' notice. Read more about how our software maintenance and support works, or how to hand over an app from another developer.

Frequently Asked Questions

What affects the cost of software maintenance the most?

Test coverage and the split between upkeep and new features usually matter most. An untested app makes every change slower and riskier, and a retainer that includes steady feature work naturally costs more than one limited to fixes and updates.

Why do maintenance quotes for the same app vary so much?

Because they often cover different things. One quote may include only bug fixes in business hours, another may include upgrades, monitoring, tested backups and feature work. Compare what each includes, how urgent issues are handled, and what you get in writing before comparing prices.

Is it cheaper to maintain an old app or to rebuild it?

Usually it is cheaper to keep and maintain it, especially after adding tests and upgrading the framework. A rebuild makes sense only when the stack can no longer be supported or the product has outgrown it, and an assessment can show which is true for your app.

How can we reduce our maintenance costs?

Add automated tests around the most-changed parts of the app, upgrade frameworks before they reach end of life, remove unused features and integrations, automate deploys and backups, and agree severity levels so fast response is reserved for real outages.

Does a maintenance retainer include new features?

It can. Many retainers combine upkeep (fixes, updates, upgrades, monitoring) with new features from your backlog, and you decide each month how the time is split. Check that any quote you compare says clearly which it covers.

Should maintenance be paid hourly or as a monthly retainer?

Hourly works for occasional, small changes. A monthly retainer works better when the app needs steady upkeep and improvement, because the team stays familiar with the code, plans upgrades ahead, and can respond to issues without negotiating each one. Look for a retainer you can leave with reasonable notice.

Share this article
Facebook X LinkedIn

Start with a discovery call.

  1. 01 · TODAY Book a free 30-minute call Tell us what you run and where it hurts.
  2. 02 · WITHIN 24 HOURS We reply From the engineers you would work with.
  3. 03 · ON THE CALL Your first step A fixed-scope sprint or audit, not an open-ended retainer.
Book a Free Discovery Call
Email
hello@micropyramid.com
Phone
+91 99591 66266
Offices
Plano --:--Hyderabad --:--Sharjah --:--
You own
All code & IP, from day one

We reply within 24 hours