Fixes, updates and improvements after launch
We look after your system once it is live: fixing faults, updating dependencies, watching alerts and making small improvements, with response times agreed by contract.
Who it's for
For companies with a system in production and no in-house team to look after it day to day.
What it solves
- The company that built the system has gone, and every bug becomes an emergency.
- Updating a library feels too risky, so nobody does it.
- Small improvements wait for months, because the team is tied up with the new product.
- Requests arrive by WhatsApp, email and phone, with no priority or history.
- A change to a tax document layout or a bank's API takes everyone by surprise.
What we do
- Fixing faults
- Bugs traced to their cause, fixed with a test and released through the normal pipeline.
- Priority classes
- Each request classified by impact; the response times for each class are set in the contract.
- Updates
- Libraries, language runtime and operating system updated regularly, before they become a risk.
- External changes
- New tax document layouts and new API versions from banks and suppliers, tracked and applied.
- Small improvements
- A queue of improvements prioritised with you, delivered alongside the fixes.
- Watching alerts
- The system's alerts watched, with the action taken recorded for each one.
What you get
- An inventory on takeover: code, access, dependencies and risks
- A request queue with priority, owner and history
- A plan for updating dependencies
- Release notes with every release
- A regular report on what was done and what comes next
How we do it
Takeover
Code, access, documentation and risks reviewed before we take on support.
Support agreement
Priority classes, response times and channels agreed by contract.
Stabilisation
The biggest risks first: critical dependencies, alerts and backups.
Routine
Fixes, updates and improvements at a pace agreed with you.
Regular review
A report and a conversation about what changed and what to prioritise.
Technology examples
- Git
- Renovate
- Dependabot
- Sentry
- OpenTelemetry
- Grafana
Related services
FAQ
Will you take on a system another company built?
Yes, after an initial review of the code, access and risks. That review shows what can be taken on straight away and what needs sorting out first.
What are the response times?
They are set in the contract for each priority class, once we understand the system and the impact of each kind of failure. We do not publish a single figure, because it depends on the case.
Do new features come under maintenance?
Small improvements do, within the agreed volume. A large feature becomes a separate project with its own scope.
What if we later want to bring maintenance in-house?
The code, documentation and request history belong to your company. We prepare the handover to your team whenever you decide.
Write to Balkan
Talk to us about your project