Website Design OutsourcePowered by StealthAgents

How to Set a Maintenance Retainer Boundary Between Fixes and New Features

A practical way to separate included repairs from new feature work in an outsourced website maintenance retainer, with triage questions, clause examples, and a quarterly review.

Visual guide for How to Set a Maintenance Retainer Boundary Between Fixes and New Features
On this page
  1. Why an unwritten boundary costs both sides
  2. Define a fix with four tests
  3. Define a new feature with a visible output
  4. Triage gray-zone requests with three questions
  5. Put the boundary into the retainer agreement
  6. Price the gray zone before it arrives
  7. Review the boundary every quarter

Why an unwritten boundary costs both sides

A maintenance retainer works only while both sides agree on what it buys. The client expects small repairs, content help, and the occasional urgent fix, while the delivery team expects a stable scope it can staff and price. When the line between a fix and a new feature stays unwritten, every request becomes a negotiation. The account manager spends more time defending the invoice than improving the site.

The cost lands on the relationship rather than one project. A client who feels overcharged for a banner change stops asking for useful improvements, and a team that absorbs every request quietly loses margin. Neither side can point to a rule, so both sides keep a private ledger of grievances. A written boundary replaces that ledger with a decision both sides can check.

Define a fix with four tests

A fix restores behavior the site was already meant to have. Test one asks whether the correct behavior appears in the brief, the design file, or a previous release. Test two asks whether the change touches only the component that failed. Test three asks whether the work can be checked against an acceptance condition that already exists. Test four asks whether the client can point to the expectation that the current build breaks.

Content edits usually pass these tests when the page structure stays the same. Replacing a headline, correcting a phone number, or swapping an approved image is a fix because the template and layout do not move. Adding a new section, a new template, or a new form field changes the page model and should leave the fix lane. The distinction protects the retainer from slow scope growth.

Define a new feature with a visible output

A new feature adds a capability the site never had, even when the request sounds small. A new pricing table, a booking step, a language switcher, or a calculator all need design, copy, build, and test work that the retainer did not budget. The visible output is larger than the request because each feature touches templates, analytics, accessibility, and sometimes integrations. Naming those surfaces helps the client see why the request belongs in a project quote.

Use the output test rather than the word count of the request. A one-line request for a sticky header can hide a navigation redesign, while a long list of copy corrections may stay inside the retainer. Ask what the client will see when the work is done and which pages change. If the answer includes a new layout or a new interaction, treat it as a feature.

Triage gray-zone requests with three questions

A short triage script keeps the answer consistent across account managers. Ask whether the site once worked this way, whether the request changes an approved design, and whether the change can ship without a new approval round. Three yes-or-no answers place most requests in the fix lane, the feature lane, or a small paid change. Record the answers in the ticket so the decision can be reviewed later.

The script also gives the client a predictable next step. If the work is a fix, the team schedules it in the maintenance queue. If it is a feature, the account manager sends a short scope note with an estimate and a start date. If the answer is unclear, the team books a paid assessment instead of guessing. Each path keeps the retainer intact and the request moving.

Put the boundary into the retainer agreement

The retainer agreement should list the work included, the work excluded, and the review process for anything in between. Use plain examples rather than abstractions, so plugin updates, minor template repairs, and approved content edits are named as included, while redesigns, new integrations, and campaign landing pages are quoted separately. This follows the same logic as the scope control guide used on fixed projects. State the monthly hour cap and what happens when it is reached. Name the person who can approve an exception and the notice required before work begins.

Attach a change-order template to the agreement so the feature path is ready before the first request arrives. The template should capture the request, the affected pages, the estimate, the acceptance check, and the release window. A client who sees the same form each time learns that the boundary is a process rather than a mood. It also gives the delivery team a clean record for the next retainer review. Public contracting follows a similar habit, and FAR Part 43 requires a written modification before changed work begins.

Price the gray zone before it arrives

Some requests sit between repair and new work, such as a layout adjustment that fixes an overlap but also changes the design. Offer a small paid assessment with a fixed number of hours and a written recommendation. The assessment can end in a fix, a feature quote, or a decision to leave the page alone. Charging for the assessment prevents free design work while keeping the answer fast.

Publish a minimum block for change work instead of billing in tiny increments. A two-hour minimum covers the setup, the review, and the release check that every change needs. Clients then bundle small requests instead of sending them one at a time. The team gets a predictable unit of work and the site gets fewer rushed releases. Put the minimum in the rate card so no one has to negotiate it during a busy week.

Review the boundary every quarter

Review the boundary every quarter against the tickets that actually arrived. Count how many requests moved to the feature lane and which ones caused debate. If the same ambiguity appears three times, rewrite the clause with that example. The review should take less than an hour and should produce one concrete edit. Keep the edited clause beside the old one so the client can see what changed.

Bring the client into the review with a short summary of what the retainer covered and what it did not. That conversation is easier when the record already shows the decision and the reason. Use the findings to adjust the hour cap, the exclusions, or the assessment rate. The monthly maintenance report audit gives the review a factual base. A boundary that is reviewed stays credible, and a credible boundary keeps the maintenance relationship calm.

Turn the guidance into a reviewable handoff

Record the owner, input, acceptance condition, evidence, and escalation point before production begins. That small contract makes the work easier to inspect and approve.

Plan a website production handoff

Move one website project from backlog to a reviewed handoff.

Share the pages, platform, current assets, deadline, and approval owner. We will help determine the right production lane and the decisions your team should keep.

Plan the handoff