Software Maintenance
Bug Fixing
Defects diagnosed to root cause and closed with a test that stops them returning.
What we usually find
The same bug has been fixed three times. Each fix treated a symptom, because nobody had time to find out what actually caused it.
What the work covers
Scope is agreed in writing before anything starts. If a line here is not relevant to you, it comes out of the plan and out of the price.
- Triage with agreed severity levels and response times
- Reproduction and root cause analysis before any patch
- Regression test written with every fix
- Fixes shipped through the normal pipeline, not by hand
- Monthly summary of what broke, why, and what prevents it now
Typical tooling
Indicative, not fixed. The stack follows your constraints and your team, not our habits.
- Sentry
- GitHub
- Playwright
- Jest
- Linear
More in Software Maintenance
This sits under Cloud, DevOps & Data. See the full picture there, or browse every service.
Need Bug Fixing?
Bring us the problem rather than a spec. We will tell you what it takes, what it costs, and what we would leave out.