The honest answer is that no single model is best. Day rates suit work you can’t scope tightly. Project fees suit work you can. Retainers suit ongoing demand where you need priority access to a team. The trouble is that most agencies will push you towards the model that best protects their margin, not the one that best fits your work. This piece breaks down where each model genuinely works, where it falls apart, and who carries the risk in each scenario.
What the three models actually look like in practice
A day rate means you’re buying time. The agency charges per day (or half-day) for each person working on your project. You pay for hours spent, regardless of output. The YunoJuno 2025 Freelancer Rates Report (analysing 261,000 contracts) puts the average UK freelance marketing day rate at £347, with the top 10 per cent averaging £788. Agency rates run higher because agencies carry overhead that freelancers don’t: employer National Insurance at 15 per cent from April 2026 (per HMRC’s published rates), pension contributions, management time, and QA. A blended agency day rate of £450 to £650 / $620 to $890 is typical for a mid-size regional firm; London agencies charge 30 to 40 per cent more.
A project fee (sometimes called a fixed price) is a single agreed figure for a defined scope of work. Redesign the site: £25,000 / $34,000. Run a brand strategy project: £12,000 / $16,000. Build a campaign: £8,000 / $11,000. The agency estimates internally, adds margin, and quotes a number. You know the cost upfront. What you don’t always know is how the agency arrived at it.
A retainer is a standing monthly commitment. You pay a fixed amount each month and in return the agency reserves capacity and delivers agreed work. For a single discipline (SEO, PPC, content, or development support), UK retainers typically sit between £1,000 and £3,000 / $1,400 and $4,100 per month. Multi-channel retainers covering strategy, creative, and execution run from £3,500 to £15,000+ / $4,800 to $20,500+, depending on team size and scope. Clutch’s 2025 pricing data tracks similar ranges globally, and retainer prices across the industry have risen sharply since 2023 as agencies absorb higher software costs and compete harder for skilled staff. The scope might be defined in hours, deliverables, or (less usefully) a vague commitment to ‘ongoing support’.
Those are the mechanics. The more useful question is which one protects you and which one protects the agency. That depends entirely on the work.
When day rates work for you
Day rates are transparent in one direction: you can see exactly how much each day costs. They work well when you cannot scope the work precisely upfront, because the risk of scope uncertainty stays with you (you keep paying) rather than being priced into a padded fixed fee.
Three scenarios where day rates genuinely serve the client:
Exploratory or advisory work. If you’re paying a UX researcher to run user interviews, or a strategist to audit your current digital estate, the output is insight rather than a fixed deliverable. Scoping this as a project fee forces the agency to guess how long discovery will take, and they’ll guess high. A day rate lets you buy five days, review what you’ve learned, and decide whether you need five more.
Specialist input alongside an existing team. You already have a team or lead agency running the project, but you need a specialist for a specific phase. Two days of accessibility audit. Three days of CRM integration support. Day rates keep the engagement contained without the overhead of scoping a full project.
Work where trust is already established. If you’ve worked with an agency for a year and you know their pace, day rates become simple. You can estimate cost accurately because you’ve seen them work. The transparency runs both ways.
Day rates fail when trust is low or absent. If you haven’t worked with the agency before, you have no way of knowing whether their £550 / $750 day is efficient or padded. A task that one agency completes in two days might take another four. And day rates create a structural incentive: the slower the agency works, the more they earn. We’re not suggesting most agencies deliberately drag work out. But the incentive exists, and if you can’t judge pace, you’re exposed to it.
The other failure point is budgeting. Day rates make it difficult to give your finance team or board a firm number. ‘Somewhere between £8,000 and £14,000 / $11,000 and $19,000 depending on how it goes’ is not a figure most budget holders will sign off comfortably.
When a fixed project fee protects you
Project fees are the right model when the work has a clear start, a clear end, and a defined set of deliverables. A website build. A rebrand. A paid media campaign with an agreed scope and timeline. You agree the price, the agency delivers, and cost overruns are their problem.
That last part is the key advantage. With a fixed fee, scope risk transfers to the agency. If their estimate was wrong, they absorb the loss. If their developers hit a technical problem, they solve it on their own margin. This is why project fees suit work you can define tightly: when the deliverables are specific, the agency can estimate with confidence, and neither side is guessing.
But here is the catch that most procurement guidance skips over. Agencies know they carry scope risk on fixed fees, and they price for it. A sensible agency will add 15 to 25 per cent contingency to a fixed-price estimate. Some add more. You are paying for certainty, and certainty has a premium. If the project runs smoothly, the agency earns more margin than they would have on day rates. If it runs badly, they absorb the pain. Over a portfolio of projects, fixed fees benefit the agency slightly more often than the client. That’s not a scandal; it’s how risk pricing works. But you should know it.
Fixed fees also fail when the scope isn’t actually fixed. A project that starts as ‘redesign the website’ but evolves into ‘redesign the website, integrate with our new CRM, and add an e-commerce layer’ is not a fixed-scope project. Agencies manage this through change requests, which are legitimate. But if you find yourself signing three or four change requests before launch, the original fixed fee has become fiction and you’re paying project-rate premiums on what is essentially ongoing, evolving work.
One red flag worth watching: an agency that quotes a fixed fee without showing you how they estimated it. If they won’t break the fee into phases, roles, or approximate time allocations, you can’t tell whether the estimate is tight or padded. We’d always ask to see the estimating model, even if the final price is fixed. The agencies confident in their numbers will show them.
When retainers make sense (and who they really benefit)
Retainers work when you have a genuine, consistent, ongoing need for a particular type of work. Monthly SEO. Continuous content production. Ongoing website maintenance and development. If you would otherwise be commissioning the same agency every month through individual project briefs, a retainer saves both sides the overhead of repeated scoping and quoting.
The structural advantage for the client is priority. A retainer client typically gets faster response times and a dedicated or semi-dedicated team. The agency has already allocated capacity for you. When something urgent lands, you’re not joining a queue behind clients whose projects were sold more recently.
The structural advantage for the agency is predictable revenue. This matters more than most clients realise. An agency with 60 per cent of its income on retainers can plan hiring, manage cash flow, and keep its best people rather than cycling through feast-and-famine project work. That stability benefits you indirectly because the team working on your account stays together longer. But it benefits the agency directly, and that’s worth remembering when they push a retainer as ‘better value’. It’s better value for them, too.
Retainers fail in two common ways.
The first is ambiguous scope. A retainer that promises ’20 hours of support per month’ sounds clear until you ask what counts as an hour. Does a 15-minute email exchange round up to 30 minutes? Does internal project management count? Does unused time roll over? The retainer agreements we see most often underprice the agency’s time and then claw it back through vague accounting. If you’re signing a retainer, the scope should be defined in deliverables or outcomes, not just hours.
The second failure is inertia. Retainers are easy to renew and hard to cancel. After 12 months, most clients stop scrutinising whether the retainer is still delivering. The agency keeps billing. The work becomes routine. Nobody asks whether the same outcomes could be achieved at lower cost because nobody wants to disrupt a comfortable arrangement. We’d recommend reviewing any retainer at the six-month mark and asking one question: if we were commissioning this work fresh today, would we choose this agency, this scope, and this price? If the answer is anything other than a confident yes, renegotiate.
How to choose the right model for what you’re buying
The model should follow the work. Not the other way around. Here’s a practical frame we’ve seen work well across different disciplines:
If you can’t define the deliverables precisely, use day rates. Strategy workshops, research phases, technical audits, and advisory work all fall here. You’re buying expertise and time, not a predetermined output.
If you can define the deliverables but the work has a clear end point, use a project fee. Website builds, brand identity projects, campaign production, app development with a fixed feature set. Anything with a specification document and a launch date.
If you need the same type of work every month with no natural end point, consider a retainer. SEO, content, ongoing development sprints, managed hosting, social media management. But only if the monthly volume genuinely justifies a standing commitment. If you need 10 hours of development one month and zero the next, a retainer will cost you for the months you don’t use it.
Some agencies will propose a hybrid: a project fee for the initial build, then a retainer for ongoing work. This is often sensible. The build has defined scope; the ongoing work doesn’t. Pricing them differently acknowledges that reality. What you should resist is an agency that bundles discovery into a retainer (‘we’ll figure out what you need as we go’). That structure removes any incentive for the agency to reach conclusions quickly. Pay for discovery on day rates or as a capped project, then move to a retainer once the ongoing scope is clear.
Four questions to ask before you agree to any pricing model
‘Can I see how you estimated this?’ On a project fee, ask for the breakdown by phase or role. On a retainer, ask what team allocation looks like. On day rates, ask for the seniority mix. An agency that won’t show the working is one you can’t hold to account.
‘What happens when the scope changes?’ Every project changes. On day rates, the answer is simple: more days, more cost. On project fees, you need a clear change-request process with per-change pricing, agreed before you sign the main contract. On retainers, you need a defined mechanism for scope increases.
‘Who carries the risk if this takes longer than expected?’ On day rates, you do. On project fees, they do (unless a change request is triggered). On retainers, it depends on whether the retainer is time-based or deliverable-based. Make sure you know.
‘What does the exit look like?’ Retainers should have a notice period of 30 to 60 days, not six months. Project fees should have stage-gate payments tied to deliverables, so you’re not locked into paying the full amount if the relationship fails at stage two. Day rates should be stoppable at any point. If the exit terms favour the agency disproportionately, the pricing model isn’t serving you.
The agencies worth working with will answer all four without flinching. The pricing model they recommend will match the work, not their cash flow preference. And if they suggest a model that genuinely doesn’t suit your situation, that tells you more about the relationship than any case study on their website.
