Prepared by
For
Web application maintenance
Bug fixes, security updates, broken integrations and small improvements for applications that are already live.
What’s delivered
- A maintenance plan. What’s covered, how you send requests, how they’re prioritised and how much time is set aside, agreed in writing.
- Regular updates. Framework and package updates, with security fixes first. Where there’s a test server, updates are checked there before going live.
- Fixes and small improvements. Worked through from a shared list, in the order you choose.
- A change log. A plain-English summary of what changed and why, ready to forward to your team or your client.
What’s needed to start
- Access to the code and hosting
- One place for requests
- Someone who sets priorities
- Access to any monitoring
What affects the cost
- How big and complicated the application is
- How often you need changes
- How many integrations need looking after
- How far behind its software updates are
- Whether we built it or are taking it over
Usually included
- Bug fixes and small feature changes
- Security, framework and package updates
- Fixing integrations when other services change
- Monitoring and investigating errors
Not included unless agreed
- Large new features, which are quoted separately
- Round-the-clock cover, unless agreed
- Content editing in a CMS
- Hosting costs and third-party subscriptions
Dependencies
When the problem is inside another company’s service, the fix depends on them. Outages at your hosting provider are out of our hands too, though monitoring helps spot them quickly.
Indicative summary. Scope, timeline and cost are confirmed in a written quote for each project.