Outsourcing
Maintenance & support
Proactive maintenance for products we built or inherited. Dependency upgrades, security patching, monitoring, incident response and a monthly report that says what changed and why it matters.
What is included
- Dependency and security patch cadence
- Monitoring, alerting and on-call rotation
- Incident response with post-mortems
- Migration and refactoring of inherited codebases
How we would start
Discovery
Two weeks with the people who will use the system. We interview them, map the process, and write down what exists and what is missing.
Written scope
Requirements, acceptance criteria and explicit exclusions. A number attached, so you can compare it against other options.
Build and ship
A dedicated pod, weekly working software, and a demo of something real every sprint rather than a status report.
Operate and improve
Monitoring, maintenance and a monthly conversation about what to change next. We stay on the system we built.
Questions
What clients ask about Maintenance & support
The questions that come up before this kind of project starts. The same answers are published as structured data, so search and answer engines can quote them.
Do you maintain software you did not build?
Yes. We take on inherited codebases after a written assessment of the code, the deployment process and the test coverage, so you know what you are buying into before you commit.
What is in the monthly maintenance report?
What changed, which dependencies and security issues were patched, what incidents occurred and what they cost, plus the risks we see coming. If a month was quiet, the report says so.
How do you handle production incidents?
Alerts route to an on-call rotation with agreed response times, and every incident produces a post-mortem that names the cause and the fix rather than the person.
Let's build together
Tell us what you are building. We will tell you honestly whether we are the right team for it.
Send a paragraph about the problem. You will get a reply from an engineer, not a form letter, within one business day. If we are not the right fit, we will usually know someone who is.
What happens next
- 1 We reply with initial questions, a rough range and whether we are the right fit.
- 2 A call or a workshop with the engineers who would actually do the work.
- 3 A paid discovery phase produces a written scope and a number we can stand behind.