Software development
Website and app maintenance after launch
Live software needs updates, security patches, monitoring and the small changes every business asks for. We maintain what we build, and we take over software built by other teams after a code review.
What a maintenance plan covers
- Framework and dependency updates, tested on staging first.
- Security patches, applied on a timetable agreed by severity.
- Uptime monitoring, with alerts to you and to us.
- Backups, with restores tested on an agreed schedule.
- Bug fixes and small changes, within the hours in your plan.
- A monthly report: what changed, what we found, what's next.
What you set in your plan
- How many hours of changes a month.
- Response times for each level of severity.
- Which days and hours are covered.
- Who on your side approves changes.
Taking over software built by another team
A code review first
We start with a written review: how the software is built, what's out of date, what's at risk and what we'd fix first.
Updates in small steps
Where updates have been skipped for years, we apply them in small steps on staging before anything reaches production.
Every account accounted for
We list every account the software depends on, from hosting and domain to app stores and third-party services, and make sure your company has admin access to each.
What maintenance doesn't cover
- New features and redesigns. We scope those as separate projects.
- Hours beyond your plan, unless you approve them first.
- Software we haven't reviewed yet. A takeover starts with the code review.
Need someone to maintain your site or app?
Tell us what it's built with and when it was last updated.
