Buy a project when the question has a defined endpoint, such as a positioning decision or audit. Buy a retainer when someone must keep making tradeoffs, guide people and adjust the plan as evidence changes. Neither model includes execution by default; write down who will do the work.
Identify the work that repeats
A project is a good fit when the output can be accepted or rejected at a specific point. A buyer-interview sprint, a channel diagnosis and a positioning brief have a natural finish line. A retainer is more suitable when the founder needs a recurring leader to choose priorities, review evidence, coordinate people and make the next decision. If the work only sounds like “improve growth”, neither scope is clear enough to buy.
Write the handoff before discussing fees
List three decisions due in the next quarter. For each, record who supplies the evidence, who decides, who executes and who measures the result. If the same senior judgment is required every week, consider a retainer. If the senior judgment ends after one recommendation and your team can carry it out, a project may be enough. The scope guide gives a fuller list of responsibilities to test.
A bounded example
Imagine a seed-stage SaaS founder whose website attracts traffic but few qualified demos. A fixed project could inspect visitor intent, interview sales and rewrite the offer hierarchy. If the company then needs someone to direct a marketer, brief paid specialists and change priorities as pipeline data arrives, the ongoing job has become leadership. The first deliverable is not evidence that the second one was included.
Set a review point
For a project, define the decision, evidence reviewed, deliverable, acceptance criteria and final handoff. For a retainer, define authority, meeting rhythm, available execution capacity and a review date. Do not use a short project to disguise an open-ended operating role, or a retainer to avoid specifying what progress would look like. Revisit the model when the team or constraint changes.
A scope worksheet the founder can fill in
Write one row for each task you expect to buy. Use four columns: decision, evidence required, person who acts and date the task can be judged. A positioning project might end when a buyer segment, message and proof hierarchy are approved; the team then owns rollout. A retainer might continue through weekly prioritisation, creative reviews and sales feedback, with no single final artifact. Mark a task “recurring” only if the decision genuinely changes with new information.
Then write a dependency beside every row. If the provider can recommend a new message but your product team must verify a claim, the approval is a company dependency. If the provider can choose a channel but nobody can build the landing page, execution is missing. Ask both candidates to price the same rows and state exclusions. The cheaper proposal is not necessarily the cheaper path if the founder will spend hours closing gaps. Choose the smallest model that covers the work and leave a named review date for expansion.
Frequently asked questions
Can a project turn into a retainer?
Yes. A bounded diagnosis can establish priorities and reveal whether the team needs an ongoing decision-maker. Set a separate decision point rather than assuming renewal.
Does a monthly retainer include campaign production?
Only if the agreement says so. Leadership, management and specialist production are different work; name the owner and cost of each.
Unsure whether you need a diagnosis or ongoing leadership?
Bring the decisions waiting on your desk and the people available to execute them. We can scope a focused diagnostic or a continuing leadership role around the actual gap.
Talk through the problem ↗See how we could work together
