Sprint Studio / Capabilities / Site care
The unglamorous half of running a website or web app — maintenance, security patches, version updates, the small changes that pile up — handled by the engineers who shipped it. Or by us, on a site somebody else shipped, after a one-week onboarding audit.
Maintenance, security, and updates aren't a single line on an invoice — they're three different bodies of work with three different cadences. We do all three properly, or we don't do them.
The boring work that stops your site degrading. Done monthly, logged in writing, so nothing piles up to the “it's now a rescue” moment.
Patches against disclosed vulnerabilities, regular sweeps for the things that haven't been disclosed yet, and a real incident path when something does land. Auth audited, headers honest, CSPs real.
The small changes that don't warrant a sprint engagement — copy, imagery, a new page, a tweaked form, a new integration. Done within the month, scoped from the request.
Monthly retainers, paid in advance. Cancel with 30 days' notice, no minimum term beyond the first month. Unused hours roll forward up to one month so you don't lose what you paid for.
For sites that mostly just need to keep running. Patches landed, dependencies current, uptime watched, monthly note.
Watchtower plus a real monthly allowance for small changes — the things that used to take you a week of chasing.
For products with real users and continuous evolution. A senior engineer on call alongside the small-change allowance, with a structured roadmap conversation each month.
When something does go wrong
Every care plan comes with a defined incident path: the channel, the on-call name, the SLA. The same senior engineer who knows your codebase — not a triage team three contracts down.
We'll write a one-page post-incident note within 48 hours of resolution. Plain English, what happened, what we did, what we're changing so it doesn't happen again. You can show it to a board, a regulator, or a customer with no rewrite.