Retainer vs. Project-Based: How to Choose the Right Agency Engagement Model
Price tends to determine a company's choice between a retainer and a project. The right model, however, is the one that matches the shape of work. Choosing the wrong one shows up either in capacity you pay for and don't use, or a scope negotiation every time something changes.
Choose a project when the work has a defined scope, a clear end, and a deliverable you can describe up front. Choose a retainer when the work is ongoing, changes with your roadmap, and improves as the agency builds context on your product. Many B2B teams start with a project and move to a retainer once the work becomes continuous. The decision should be made depending on the shape of the work. A retainer spent on one-off work pays for capacity you don't use, and a project stretched over ongoing work turns every change into a negotiation.
A project buys an outcome, a retainer buys capacity
A project-based engagement pays for what gets delivered and buys a defined outcome, such as a fixed scope, a timeline, and a deliverable, with a clear end. A retainer pays for access and continuity and buys reserved capacity, or a team available over an ongoing period, working through priorities that shift as your needs change.
That difference shapes everything that follows. On a project, the scope is the contract, so changes go through a formal change process. On a retainer, the backlog is the contract, so priorities get reordered in the open without renegotiating anything. Cost depends less on the model itself and more on how well it matches the work.
Choose by the shape of the work
Start by asking if the work has an end you can describe today. A rebrand, a website build, or an MVP has a defined finish, so a project fits. Ongoing product design alongside development, continuous site optimization, and post-launch support have no finish line, so a retainer fits.
Three follow-up questions sharpen the call. Will priorities change once the work starts? Does the team get better as it learns your product? Do you need the same people available on short notice? Yes to most of these points to a retainer. A discovery phase is the cleanest example of a project, with a defined start, a set of outputs, and an end. A product team shipping every two weeks for the next two years is the cleanest example of a retainer.
Each model fails in a predictable way
Projects fail through scope creep. The brief moves, every change needs approval, and the engagement turns into a negotiation. Retainers fail through drift. Priorities stay vague, hours go unused or get spent on whatever is loudest, and nobody can say what last month produced.
The mechanics behind this have been studied for decades in advertising, where the trade-off is consistent. Paying for hours tends to favor time spent over results, while a fixed fee for a deliverable means every change to the brief has to go through its own control process. Each trade-off becomes a problem only when the model is applied to the wrong kind of work.
A few straightforward habits prevent most of this friction. For a project, put the scope in writing and agree how changes are handled before work begins, which starts with a strong brief, as our guide to briefing a B2B design agency explains. For a retainer, keep a standing priority list, review what shipped against what was planned every month, and define outputs.
Many teams start with a project and move to a retainer
A common sequence is a scoped project first, then a retainer once the work turns continuous. The project proves the working relationship and produces thedesign system, codebase, or documented brand that the retainer needs to run well. The retainer then carries the work forward without a new scope every quarter.
AIf you keep opening small follow-on projects, calling the same team, and approving change order after change order, a retainer is probably a better fit. The same logic works in reverse, so if a retainer’s backlog keeps running dry or one large initiative deserves its own scope, a project may fit better for that stretch. If neither model is working, our guide to exiting an agency relationship without stalling your roadmap covers how to sequence the transition.
If you keep opening small follow-on projects, calling the same team, and approving change order after change order, a retainer is probably a better fit.
Agree on what good looks like before you pick either
The model matters less than the agreement behind it. Whichever you choose, write down what good looks like, how it will be measured, and what happens when priorities change. Engagements with those three things settled tend to survive a change of model.
The same advertising research reaches the same conclusion. Success depends more on shared definitions of value and agreed measurement than on the pricing structure itself. In practice, that means a project agreement should name the deliverables, the acceptance criteria, the milestones, and the change process. A retainer agreement should name the services covered, who sets priorities, what you receive each month, how unused capacity is handled, the review cadence, and the notice period. This isn't legal advice, so have counsel review the final terms.
Match the engagement to the work
If you're not sure which model fits, that's a scoping conversation. At BRIGHTSCOUT, we take on scoped projects with a clear deliverable, and flexible support for teams whose work continues after launch, so we can tell you honestly which one fits yours.
FAQs
What is the difference between a retainer and a project-based agency engagement?
A project-based engagement covers a defined scope, timeline, and deliverable, and it ends when the work is delivered. A retainer reserves an agency team's capacity over an ongoing period, and the work is steered by a backlog of priorities that can change. A project pays for an outcome. A retainer pays for access and continuity.
When should you choose a retainer over a project?
Choose a retainer when the work is continuous, priorities will change, and the team gets better as it learns your product. Typical examples are ongoing product design alongside development, continuous website optimization, and post-launch support. If you can't describe the finished deliverable today, a retainer is usually the better fit.
When is a project the better choice?
A project fits work with a defined scope and a clear end, such as a rebrand, a website build, a discovery phase, or an MVP. It gives you a bounded commitment and a deliverable you can evaluate against agreed criteria. The risk is scope creep, which a written scope and a change process are meant to contain.
Is a retainer more expensive than a project?
Neither is expensive or cheap by nature. A retainer is usually a larger total commitment over time because it covers ongoing work, while a project is bounded by its scope. What matters is fit. A retainer used for one-off work pays for unused capacity, and a project stretched over ongoing work generates repeated scope negotiations.
Can you start with a project and move to a retainer later?
Yes, and it's a common path. A scoped project proves the working relationship and produces the assets a retainer builds on, such as a design system, a codebase, or a documented brand. Signals that it's time to switch include a stream of small follow-on projects, repeated change orders, and relying on the same team month after month.
What happens to unused hours on a retainer?
It depends on the agreement, so settle it before signing. Common approaches are that unused capacity expires each month, rolls over for a limited period, or is reallocated to the backlog. The better question is why capacity is going unused, which usually points to vague priorities or a retainer that no longer fits the work.
How do you prevent scope creep on a project?
Put the scope in writing, with named deliverables, acceptance criteria, and milestones, and agree on how changes are handled before work begins. A change process means new requests are priced and scheduled as changes. A strong brief up front prevents most of the disputes.
How do you stop a retainer from drifting?
Keep a standing priority list with a named owner, review what shipped against what was planned each month, and define the expected outputs. Check every quarter whether the work is still continuous enough to justify a retainer. If it isn't, move the remaining work to scoped projects.
Should a retainer be based on hours or deliverables?
Hours measure effort and deliverables measure results, and each has a place. Hours-based retainers suit unpredictable work where you want flexibility, while output-based retainers suit recurring work you can define. Many agreements blend them, with a fixed monthly capacity and priorities set against a list of agreed outcomes. In advertising, where agency pay has been tracked for decades, time-based fees remain the most common model.