Keep the software dependable.
Once software is live, small faults turn into daily interruptions. We look after the application, keep a clear list of what needs attention, and agree how urgent problems and new requests are each handled.
Not every issue is urgent.
A display glitch and a broken checkout should not wait in the same queue. We agree categories like these at the start.
Requests reach us on the channel we agree with you, often WhatsApp or email, and go into a tracker both teams can see. What helps us most is enough detail to reproduce the problem on the first attempt.
Coverage, response expectations and access are written down before we take responsibility, so your staff know what to expect when something breaks late on a Sunday, and so do we.
Alongside requests, we keep the software healthy in the background: libraries updated before they fall out of support, certificates renewed before they expire, and warnings in the logs looked into before they turn into outages.
From report to release.
Log and acknowledge
The issue gets an entry, a category and an owner on our side, and you can see it has been picked up.
Investigate
We reproduce the problem, find the cause and explain what the fix involves, including anything else it touches.
Fix and test
Changes are reviewed and tested in a separate environment before they reach production.
Release and confirm
We release at an agreed time, check with you that the problem is gone, and note the cause so a repeat gets caught.
Inside the arrangement.
- Bug fixes within the agreed scope
- Security patches and dependency updates
- Compatibility with new browser and phone versions
- Hosting and certificate renewals, where we manage them
- Alerts on the flows that matter most
- A running list of known issues and their status
Can you maintain software someone else built?
Yes, after reviewing the code, hosting and whatever documentation exists. That review tells both of us what we are taking on and what needs fixing first. The software takeover page covers the handover from a previous team.
Does maintenance include new features?
Not by default. Fixes and updates keep what exists working. New features are scoped separately, or drawn from a development allowance built into the ongoing arrangement, so one never quietly crowds out the other.
What if we just need an occasional fix?
That can work for stable software with few users. The trade-off is that each request starts from a colder picture of the code, so we will be clear about what a lighter arrangement covers and what it doesn't.
What do you need from us to begin?
Access to the code repository, hosting, domain and third-party services, ideally in accounts your business owns. If a former developer holds them, recovering them is the first job. See ownership and handover.
Need someone to look after live software?
Tell us what it runs on and what tends to break, and we will propose a support arrangement.