Systems need owners, not just builders
Software does not stay finished: dependencies age, security moves, businesses change. We keep systems updated, monitored, backed up and honestly documented, under a plain monthly retainer with agreed response times in writing.
Plain monthly retainer · agreed response times in writing · no lock-inOurs, and not only ours
Most retainers cover systems we built. The rest cover systems built elsewhere, taken on after a short review so both sides know exactly what we are signing up to.
Systems we built
Warranty-grade care for our own bespoke work and AI agents: updates, monitoring, backups and improvements, from the engineers who wrote it.
Systems built elsewhere
Bespoke systems and AI-built software inherited from other teams. We review first (an audit, in our language), then take ownership with eyes open.
Security and infrastructure
Patching, dependency updates, monitoring with alerts we respond to, backups that are actually tested, and hosting managed where you want it managed.
WordPress and Webflow sites
Business websites kept updated, patched, backed up and fast. Quiet, dependable care for the front door of the company.
Microsoft 365
Administration done properly: user lifecycle, permissions, security baseline and sensible configuration, without a helpdesk maze.
Fixes and improvements
Small changes handled within the retainer; larger pieces of work scoped and quoted separately, so the retainer never quietly becomes a blank cheque.
Quiet, predictable, in writing
A named engineer
Your retainer has a named senior engineer who knows your systems, answers your questions and carries the responsibility. Not a ticket queue with rotating strangers.
Response times agreed in writing
Service levels are set per retainer, matched to how critical the system is, and written into the agreement. We commit to what we will honour rather than advertising what sounds good.
A monthly note in plain English
What changed, what was patched, what we are watching. Short enough to read, honest enough to trust, and proof the quiet months were quiet on purpose.
One simple shape, figures on enquiry
Retainers are priced by what we are looking after and how critical it is, confirmed in writing before anything starts.
A short review of what we are taking on: code, hosting, accounts, risks. Waived for systems we built; the findings are yours either way.
Updates, monitoring, backups, small fixes and the monthly note, with response times agreed in writing. Cancel with notice and keep everything, fully documented.
Improvements beyond the retainer: new features, integrations, migrations. Scoped and priced separately, so support stays predictable.
Asked before every retainer
What response times do you offer?
We agree them per retainer, in writing, matched to how critical the system is: a marketing site and a payments platform do not need the same promise. We would rather commit to numbers we will honour than publish impressive ones with asterisks.
Will you support a system you did not build?
Yes. We start with a short fixed-fee review so we understand the code, the hosting and the risks before we promise to stand behind them. The review prices the retainer honestly, and its findings are yours to keep even if you go elsewhere.
Do you do one-off fixes without a retainer?
Sometimes, scoped and quoted as a small project. But a system that needs a stranger's urgent fix usually needs an owner, and a retainer is almost always cheaper than the second emergency.
What happens if we cancel?
You give notice as set out in the agreement, we hand everything over properly (code, documentation, credentials, backups) and we part on good terms. Support is renewed because it is good, not because leaving is painful.
Tell us what needs looking after
We reply within one working day with how we would take it on and what the retainer would cover.