The shape of it
Every stage after launch feeds the next one. This is the part of a system's life where most of its value is actually realised, and it is the part most projects skip.
The system gets designed and written.
It goes live, with the people who use it ready for it.
Access, data and dependencies reviewed against real use.
Bugs, friction and the things nobody predicted.
The next part of the business it should cover.
And round again — for as long as it is useful
Why it matters
It gets slowly further from the company using it. The business changes — a new service line, a different approval, twice the volume, a rule that used to be an exception — and the system does not.
Meanwhile the ground underneath it moves. Libraries accumulate published vulnerabilities. Platforms deprecate the APIs it depends on. Certificates expire. None of that announces itself.
Eighteen months later the workarounds are back, and the business is having the same conversation it had before the project — except now there is a system to rewrite as well. The monthly cost of keeping software current is a fraction of the cost of replacing it.
The arrangement
Typically £1,000 to £5,000 a month, scaled to how much the system matters and how fast it needs to move. The number is agreed in advance and reviewed openly, not indexed to how busy we happen to be.
Ownership
This is not generosity. A supplier who is hard to leave stops having to earn the relationship, and that is the point at which the software starts getting worse.
Reasonable questions
A quiet month still contains dependency updates, monitoring, backups and the review that keeps them meaningful. Where there is genuinely nothing to do we would rather bank the development time than invent work, and we will tell you if the arrangement has stopped earning its place.
No. You own the code, the data and the infrastructure, and the documentation is written for somebody who has never met us. A monthly arrangement that can be ended is the only kind worth having — it means we have to keep being worth it.
Then you should, and we will hand over properly. Plenty of businesses use us until an internal team makes sense; some keep us afterwards for the security and infrastructure work a small team should not have to carry alone.
Yes, and it is a common way to start. It begins with a review of what is there and an honest answer about whether it is worth keeping — occasionally it is not, and that is worth knowing before you spend another year on it.