Support · Maintenance retainer

Maintenance retainer

Software ages. The 'finished' build at the end of week six is not the same product six months later. Feature requests pile up, edge cases show up, performance creeps, and the dependencies need patching. Without a maintenance plan, you've shipped a slowly-decaying asset.

Most of our active clients are on a monthly retainer. We agree the scope at the start of the month, ship in weekly sprints, and report what landed at the end. No surprise invoices, no scope-creep arguments.

Monthly · 4 sprints
Inside the build

What's actually included.

Bug fixes

Triage on intake: P0/P1 get same-day, P2 within the week, P3 in the next sprint. With a written triage rule, not a guess.

Small features

The list of 'can we add this?' requests that pile up, handled in 1–2 sprint cycles each, with effort estimates before commitment.

Performance tuning

Slow queries, missing indices, N+1s, bundle bloat: the boring work that keeps the app feeling new even 18 months in.

Security patches

Dependency updates, security advisories, certificate rotation, audit log review. Quarterly security checkpoint included.

Backups + recovery drill

Backup verification monthly, full recovery drill quarterly. Documented RTO/RPO. So when something goes wrong, restore is a procedure, not a panic.

Friday demo

Every Friday, a 20-min walkthrough of what shipped that week. Recorded, shareable, easy to forward to your boss.

Who this is for

Companies running custom software (whether we built it or not) who want a single retainer covering ongoing work, with a clear monthly scope. Especially good as a follow-on after a 6–10 week initial build.

How we work

Three stages, no surprises.

01

Discovery

A 30-minute call to map the workflow that's actually broken. We walk you through what we'd build, what we wouldn't, and a written scope with timeline and milestones.

02

Weekly sprints

Working prototype by week 2, MVP in staging by week 4–6. Friday demo every week: you see it before it's done, not after. Slack channel + Linear / Jira board you have access to.

03

Handover + retainer

Go-live with a written playbook, training material per role, and a 30-day office-hours window. Most clients move onto a maintenance retainer for the work that comes after.

Ready to start

Walk us through what's broken.
We'll come back with a plan.

A 30-minute discovery call, free, no deck. We map your workflow, flag what's worth fixing first, and outline a scope with timeline and effort.