Ongoing retainer
What happens aftereveryone else leaves.
Maintenance, performance work and iteration once the build ships. Optional, never bundled in to inflate a quote.
Support is priced on what a system actually needs, so the honest version of this conversation starts with what is going wrong now.
Why this exists
Software decays. Dependencies age out, browsers change, traffic patterns shift, and the person who understood the deploy has moved on.
We keep things running and keep them moving — but as a choice you make after launch, not a clause buried in the build contract.
How it runs
Four steps, and you seework at every one.
- 01
Inherit properly
A documented handover, access audit and a written picture of what is fragile. We do this even for systems we did not build.
- 02
Keep it healthy
Dependency updates, security patches, monitoring and backups verified by actually restoring them.
- 03
Improve what matters
Your monthly capacity spent on whatever you decide — performance, features, or paying down what is slowing your team.
- 04
Report plainly
What we did, what it cost, what we would do next. Cancel whenever it stops being worth it.
What you get
Yours to keep,from day one.
Not deliverables handed over at the end. These exist in your accounts, in your name, while the work is happening.
- Monitoring and alerting configured to your thresholds
- Verified backups with a tested restore procedure
- A documented incident and escalation path
- Dependency and security patching on a schedule
- A monthly written report you can actually read
- No minimum term and no exit fee
Capabilities
The full list, so you cancheck we do your thing.
Keep it running
- Proactive monitoring and alerting
- Security patching and dependency updates
- Backup and disaster recovery
- Incident response
Keep it fast
- Performance profiling and optimisation
- Core Web Vitals work
- Infrastructure and cost review
Keep it moving
- Feature development against monthly capacity
- Technical debt reduction
- Extra engineering capacity alongside your team
How we work together
Pick the shape thatfits the work.
Retainer
Monthly capacity
For ongoing work after launch. A set amount of our time each month, and you decide what it goes on. No minimum term.
Fixed price
One number, agreed up front
For work we can scope tightly. You get a written scope and a price before anything is built, and the price does not move unless the scope does.
Scoping is free in every case, and the written scope is yours whether or not you hire us.
Questions
About support & growth.
Do you support software you did not build?
Yes. We start with a review and an honest assessment of what it will cost to hold it steady — occasionally that assessment is that it needs replacing.
Is a retainer mandatory after a build?
No, and we will not quote as though it is. Plenty of clients take the handover and run it themselves, which is the point of documenting it properly.
What are your response times?
Agreed per retainer against what the system actually justifies. We would rather commit to something we can hold than publish a number that sounds impressive.