The Retainer Is Not a Recovery Plan

A monthly agreement can keep people available. It cannot decide what is stuck, who owns it or what finished looks like.

Many stalled projects quietly become retainers. The launch is incomplete, but the relationship continues and the unresolved work is folded into monthly support.

The same questions return: which decisions are final, which content is missing, which integration is blocking release and who can approve the next step?

The client pays for availability while the agency spends senior time carrying project residue. Neither side gets a clear view of what the monthly spend is resolving.

A retainer feels safer than a difficult reset. But continuity without a recovery plan can make an unfinished project look normal.

Ask for the remaining outcome, open decisions, owners, dependencies and acceptance checks. Then separate recovery work from ongoing support.

If the agency can turn the retainer into a visible recovery plan, continue with confidence. If not, the arrangement may be preserving the problem rather than solving it.

What the work should actually look like

Define the outcome. State what the customer or staff member should be able to do.
Name the affected page or workflow. Make the boundary visible.
Find the blocker. Identify missing copy, approval, access, data or a technical decision.
Assign the owner. Give every open decision one person who can complete it.
Run the acceptance check. Test the result under the agreed conditions.
Release and hand over. Record what changed, what remains limited and who owns it next.