Skip to content
Antoine Le LouëtIndependent senior developer (Home)
Back to the Journal

Advice3 min read

How much does web application maintenance cost?

Separate initial takeover, recurring maintenance and running costs to prepare an estimate with visible assumptions.

Four budget items: initial takeover, recurring support, infrastructure and agreed enhancements.
Separating takeover from ongoing support lets you compare the same expenses over the same period.

A price assumes a scope

Two applications with the same number of screens can require very different support. An order blocked on Saturday and a viewing tool used on weekdays call for different commitments. To request a budget, start with uses and the periods when an interruption causes problems.

Price then depends on the project's observable state: whether it can run, useful tests, supported dependencies and the delivery procedure. Missing elements add takeover work and uncertainty. A credible fixed price cannot be calculated from the page count alone.

Separate expenses in the proposal

  • Initial takeover: access, understanding a journey, a working environment, assessment and initial safeguards. Define deliverables and exclusions.
  • Recurring support: incident handling during agreed hours, fixes, update checks and risk monitoring. Specify planned capacity and how overruns are handled.
  • Enhancements: new requests, estimates before commitment and business validation. A new feature is not implied by a hosting subscription.
  • Operations: servers, storage, backups and third-party services, with their account holders and billing units.

Show who pays for and administers each service. A hosting provider may run infrastructure without checking that your business export produces the correct document. Responsibility for that check must be assigned.

An educational calculation to replace with a quote

Text · fictional assumptions
Premier mois = reprise + suivi + infrastructure + services
Mois suivants = suivi + infrastructure + services + évolutions validées
Exemple : 3 jours de reprise + 2 jours de suivi
Valorisation fictive : 600 € HT / jour
Infrastructure fictive : 80 € HT / mois
Premier mois : (3 + 2) × 600 + 80 = 3 080 € HT
Puis, hors évolution : 2 × 600 + 80 = 1 280 € HT / mois

These numbers serve only to demonstrate the formula. They are neither Antoine Le Louët's rates, a market average nor an estimate for your application. The scenario includes no on-call coverage and assumes third-party services are included in the fictional 80 euros. Moving from two to four support days per month adds 1,200 euros monthly here. That capacity change must be discussed before comparing amounts.

The information needed to compare two estimates

  • Describe the users, an essential journey and the consequences of an outage.
  • Attach the state of access, known versions, deployment procedure and recent incidents, without secrets.
  • State desired coverage hours, expected response time and the person who prioritises requests.
  • Ask what is included, deferred or billed separately, and agree a date to revisit assumptions.

A service objective connects a use to an indicator and target; it does not by itself create a contractual guarantee. To compare two proposals, first align those assumptions. A smaller budget with reduced coverage hours does not necessarily meet the same need.

Sources and useful links

Share on LinkedIn (new tab)

Keep reading
All articles in this category