Skip to main content
Rasad

Blog

Blog Overview

A care plan after launch: what a monthly retainer should cover

PublisherAbwab Admin
Published OnNov 15, 2026
Reading Duration7 min read
Last UpdateNov 15, 2026
A care plan after launch: what a monthly retainer should cover

Care is not a ticket queue. This article separates what a monthly retainer should cover, what should stay outside it, and how to measure response and resolution before you sign.

The first month after launch is when the small problems appear: a date field breaks after a browser update, a payment provider changes a name in its interface, a client asks for one more column in a report. None of them is a project on its own, and together they decide whether people trust the system or quietly stop using it.

A care plan is the answer to that period. It is not a support contract that starts with a ticket; it is a standing arrangement with a team that knows the code, the data model and the integrations. This article explains what a monthly retainer should cover, what should stay outside it, and how to evaluate a proposal before signing. It does not put figures here; the care bands are published on the pricing page, and a number alone does not tell you what you are buying.

What the retainer should cover

The best definition of care is: everything that keeps the working system working, not everything you want after today. That definition sounds narrow, but it makes the contract priceable and clear to both sides. A system carrying real work needs five things every month, and each one can be measured.

LineWhat it includesHow its quality is measured
MonitoringChecks on important pages and endpoints, and an alert that reaches a personDid the team know before the client did?
Bug fixesAny behaviour that differs from what was agreed in writingWas the bug closed inside the month?
Small enhancementsA field, a filter, a report, a wording changeDid it ship inside the month, or become a queue?
Security updatesFramework and library upgrades, with regression testingAre they applied on a schedule, or after an incident?
Monthly reportWhat changed, what broke, what was fixed, what is recommendedDoes the person who signs the invoice read and understand it?

Response is not resolution

Many care contracts sell “same-day response” and leave the fix open. Response matters: the client needs to know someone heard them. But what actually matters is when the system works again. Write two levels into the contract: time to first response, and time to restore or fix by severity. Define severity with examples, not general words.

A practical example: a failure that blocks login or payment is a first priority and deserves continuous work until service returns. An error in a monthly report is a second priority, fixed in the next release. A wording change is a third priority, handled inside small enhancements. If the contract does not know these differences, everything becomes urgent, or nothing does.

The bug and the new feature

The most common care dispute is: is this a bug or a feature? The definition belongs in the contract: a bug is behaviour that differs from what was agreed in writing in the scope or acceptance criteria. A feature is behaviour nobody agreed to yet. The first is inside care; the second is either a small enhancement inside the month or a separate scope, and the agency should tell you which before starting.

This definition protects both sides. It protects the client from an agency that calls every request “a new project”, and protects the agency from a scope that grows without limit. Because the original scope was not written down on many projects, the first thing good care does is fix the acceptance criteria: what should happen, on which device, in which language, and how it is tested.

What the retainer should not cover

From reading to shipping

Want this built, not just explained?

Bring us the problem behind the article. We will tell you what it takes, what it costs, and whether we are the right team.

Saying no before the first invoice is cheaper than arguing after it. Care is not:

• A new module or a redesign: that is a project with scope and a date.

• Hosting, domain, SMS, email or licences: billed at cost or paid directly.

• A system the team did not build: it can be taken on after a paid review, because maintaining unknown code without reading it is how outages happen.

• Support for people: training staff or answering your customers is a separate service. Care keeps the software running, not the front desk.

These boundaries are not stinginess; they are what makes the price possible. A contract that promises everything cannot promise anything. A contract that defines its coverage precisely can define response time and quality, because the team knows what it will work on. If you need a new module, agree its scope, date and budget separately.

How to evaluate a care proposal

Do not compare the monthly price alone. Compare what is included, what is excluded, how it is measured, and who does the work. Use the following list in the meeting and ask for answers in writing.

  1. Scope: which five lines are included, and which are explicitly excluded?

  2. Response: what is the first-response time, and does it differ between an outage and a question?

  3. Resolution: what is the target restore time per severity, and who decides the severity?

  4. Ownership: who owns code, access and monitoring, and do they all transfer to you?

  5. Reporting: what does the monthly report contain, and who is it written for?

  6. Security: are security updates scheduled, and who runs regression tests after them?

  7. Exit: how does care move to another team without losing knowledge?

  8. Measurement: which metrics are reviewed each month, and what counts as failure?

Handover that reduces dependency

Good care does not make you hostage. It transfers knowledge continuously: an operating note, a change log, access to monitoring, and an explanation of what happens during an outage. If you decide to move to another team, the move should be possible. An agency that hides knowledge protects itself from competition, not your system.

Ask about account ownership: who owns the domain, the hosting account, the error monitoring, and access to the payment gateway. These assets should be in your name or under your control, not the agency's. If the agency manages them, ask for a written exit procedure that guarantees transfer on a specific day. If you are planning a redesign during care, Redesigning without losing traffic gives you the migration checklist that protects what you built.

Frequently asked questions

When should care start? Before launch, not after. Monitoring and the response plan should be ready on launch day, not after the first outage.

Is care mandatory? No. But if the system carries real work, who answers when it breaks? Care is the organised answer, and leaving it out means relying on luck.

What if we do not use the whole month? A fixed hour bank can create an unused balance. Better to define the scope clearly and review what shipped each month, rather than turn care into a bank of hours.

Can we request large changes? Yes, but they are a separate scope. Care is for small enhancements closed inside the month, not for rebuilding a module.

Do you take on a system you did not build? After a paid review. We do not promise to maintain code we have not read, because that creates promises we cannot keep.

How do we know care is working? By measures: did the team know before the client, were bugs closed, did enhancements ship, and does the report explain what happened.

Sources

Cover image: Jeff Sheldon ugmonk, CC0, via Wikimedia Commons.

Get in Touch

We'd love to hear from you. Fill out the form and we'll get back to you soon.