Deciding between hourly and retainer pricing is a business decision, and if you haven't made it yet, Hourly vs. Retainer: Which Should You Use? already covers how to choose. This post picks up after that decision is made. Once you know you're running a retainer instead of a project, three sections of the contract have to be rewritten from the ground up — not just relabeled.
1. Scope: a bounded deliverable vs. a committed capacity
A project contract defines scope as a finish line — a specific deliverable, or list of deliverables, that ends the engagement once accepted. A retainer has no finish line to define instead, it defines a capacity: a number of hours or a set of recurring services made available each month. Writing retainer scope the way you'd write project scope — as a fixed list of deliverables — is the single most common mistake, because it quietly caps a relationship that was supposed to be ongoing.
Project contract: "Consultant will deliver a completed brand messaging framework, including positioning statement, three message pillars, and a one-page brand voice guide, for a total fee of $6,000." Retainer agreement: "Consultant will make available up to 15 hours per month of marketing strategy work, as directed by Client, for a monthly fee of $2,400. Hours not used in a given month do not roll over."
2. Termination and renewal: a natural end vs. an explicit one
A project contract ends itself — once the deliverable is accepted and the final invoice is paid, there's nothing left to terminate. A retainer never ends on its own, which means the contract has to say how it ends: a term length, whether it renews automatically or requires a new signature, and a notice period either side can use to exit before the next term starts. Skip this clause and a retainer either runs forever by default or ends on a disputed date, neither of which you want to be negotiating over email.
"This agreement covers an initial term of three months, beginning September 1, 2026. After the initial term, it renews automatically for successive one-month periods unless either party gives 30 days' written notice of non-renewal or termination."
3. Payment schedule: milestone-based vs. recurring
Project contracts typically tie payment to progress — a deposit, a milestone payment, a final payment on delivery — because there are discrete moments to attach an invoice to. A retainer has no milestones, so payment has to be tied to the calendar instead: a fixed amount, due on a fixed date, every period, regardless of exactly how the hours were used that month. Leaving the payment clause written in milestone language on a retainer is how consultants end up chasing an invoice because the contract never actually said when it was due.
Project contract: "50% deposit ($3,000) due on signing, remaining 50% ($3,000) due on delivery of final files." Retainer agreement: "Client will pay $2,400 on the 1st of each month for the duration of this agreement, invoiced in advance. Payment is due regardless of actual hours used within the included allowance."
What stays the same
Confidentiality, IP ownership of deliverables, liability limits, and dispute resolution clauses don't need to change between the two formats — the difference is concentrated entirely in scope, termination, and payment. If you're converting an existing project client into a retainer client, those three clauses are the only ones you actually need to rewrite.
Trying to retrofit a project contract into a retainer by editing the fee line is how the scope and termination gaps above end up in signed agreements. The free Retainer Agreement Generator starts from the retainer structure directly — recurring fee, term, and renewal already built into the document, instead of bolted onto a project template.