How to scope a consulting retainer before setting a price
A retainer needs recurring work and clear limits. Define the work you control, estimate delivery time, reserve capacity for communication, and test your price with prospective buyers. A monthly fee is not a promise of recurring demand.
Choose recurring work, not a recurring invoice
A one-off cleanup does not automatically need a retainer. A recurring review may fit if the client repeatedly needs the same report, check or maintenance task. Ask what changes each month and who will act on your deliverable.
A fictional monthly package
The example below is a scope hypothesis for an operations specialist. The record volume and review time must be agreed after inspecting a representative sample.
Monthly pipeline support: four weekly report updates, one monthly handoff review, one 30-minute review call and one consolidated revision per report. Client provides an agreed CRM export and names a decision-maker. New software integrations, sales outreach and unlimited record cleanup are excluded.
Do the capacity arithmetic
Estimate work using your own trial delivery rather than copying an industry rate. For illustration, four updates at 90 minutes each plus a two-hour review, a half-hour call and two hours of coordination total 10.5 hours. The real figure may differ. Add a contingency appropriate to the unknowns before deciding how many clients you can serve.
Define when a deliverable is accepted
A useful acceptance criterion can be checked by both parties. It should refer to the agreed asset, not a result controlled by other people.
Proposed criterion: the report contains the agreed columns, covers the approved export period, and identifies missing fields and next-action owners. Client reviews within an agreed window and sends one consolidated set of corrections.
Set a price hypothesis and a change process
Compare the work with your costs, available capacity and the buyer's alternatives. Discuss willingness to pay; do not infer it from the size of the client's business. New work should be described, estimated and approved before it begins. The example is a planning aid, not a contract or legal advice.
Before you use it
- Is the need genuinely recurring?
- Are deliverable count and revision limits explicit?
- Does the workload include communication and contingencies?
- Is someone responsible for providing access and approving work?
- Can both sides identify an out-of-scope request?