Maintenance & evolution
A product kept current, watched and fixed, with someone who answers when it breaks.
- Deliverable
- A monthly engagement: fixes, security updates and evolutions, with a written response time.
- Typical duration
- Monthly engagement, no minimum term
- From
- €1,500 per month
The problem
A delivered product is not a finished product. Dependencies age, platforms change their rules, and real usage reveals what no test anticipated.
Maintenance covers that: fixes with a written response time, security updates applied as they come, monitoring that alerts before the customer calls, and an evolution budget so the product keeps moving.
What is included
- Defect fixes, with a written response time by severity
- Dependency security updates, applied and verified
- Uptime and error monitoring, with alerting
- A monthly evolution budget, carried over within the quarter
- A monthly report: what was done, what is coming, what is worrying
How it works
- 01
Take over
An audit of the code and its operations, even if we wrote it. Products live and drift.
- 02
Instrument
Without measurement, an outage is discovered by a customer. Alerts should come before complaints.
- 03
Keep current
Security updates are applied as they come, not stockpiled until the painful migration.
- 04
Report
Every month, a report readable by someone who does not write code.
Frequently asked
Will you maintain a product you did not build?
Yes, after an audit. Sometimes we conclude that taking it over costs more than a partial rewrite — we say so before committing.
What if the evolution budget goes unused?
It carries over within the quarter. Beyond that it is lost: unlimited rollover turns maintenance into a savings account and distorts the sizing.
Is there a minimum term?
No. One month's notice is enough. A long engagement should be earned by the service, not enforced by a contract.