Everything is urgent. Something still has to be first.

An agency retainer is an ongoing engagement for businesses that expect useful work to keep changing. Instead of defining a separate project for every request, the client and the agency keep shared context and move recurring work through an agreed, prioritised scope. A one-off project is usually cleaner when the outcome can already be described in full.

When two requests compete, the questions are the same each time: what stops if this is not done, whose date is it, does anything else in the queue depend on it, and is work already in progress that would be wasted by switching. The answer gets said out loud rather than decided quietly.

The practical advantage of an ongoing engagement is that each new request begins with context that already exists — the brand rules, the components already built, the decisions made and rejected before, who signs things off and what they always ask for. Most of the cost of a small project is establishing that, and in a retainer it is established once.

Work moves through the same steps whatever it is: the request gets clarified into something buildable, it is made against the context already in place, it is reviewed with whoever asked for it, changes are applied, and it ships — at which point the next item in the queue becomes the current one.

Recurring and evolving work belongs in the queue: campaign pages, creative adaptations, content, SEO execution, conversion changes, design support and the reporting around them. A large new initiative — a full rebrand, a new product, a platform rebuild, a migration — deserves its own discovery and its own scope, and hiding one inside a monthly relationship is how both the project and the retainer go wrong.

A retainer generally covers evolving work — new pages, new creative, new content, changes that come from the business moving. Maintenance covers keeping an existing site healthy: updates, security, speed, backups and fixing what breaks. Some businesses need one, some need both, and the boundary is set by what the engagement includes rather than by the words.

A retainer is a way of working rather than a service in itself. The disciplines it delivers each have a page of their own, and those pages are the right place to start if the need is a specific piece of work. This page is the right place to start if the need is that work of that kind keeps coming and there is no good way to run it.

Retainer scope is set by the kinds of work involved, how often requests actually arrive, how many disciplines are in play, how many brands or products are active, how many people raise and approve work, how much context already exists, and whether large initiatives sit inside or outside the arrangement.

These are delivery projects, listed as delivered. What they show is the range a single ongoing engagement moves across — the work itself, rather than the commercial arrangement it was bought under.

What is an agency retainer?

A standing arrangement rather than a purchase. What you are actually buying is not a quantity of work but the removal of a step — the scoping conversation that would otherwise sit in front of every small piece and cost more than the piece itself.

When does a retainer make sense?

A useful signal: count how many small things your team has been meaning to get done for over a month. If that list keeps refilling faster than it empties, the constraint is not capacity in one push, it is not having a standing route for work of that size.

What is the difference between a retainer and a project?

A project has a defined outcome and an end; you agree what is being built and it finishes. A retainer has an ongoing queue and no defined end state, because the requirements keep arriving. Neither is better, and most businesses use both at different times.

What is the difference between a retainer and maintenance?

Ask what would happen if nobody did it for three months. Maintenance work produces something broken — an expired certificate, a form that stopped sending. Retainer work produces something missing: the campaign page that never launched. Different failure, different arrangement.

What work can go into a Branditify retainer?

Growth strategy and roadmap, website updates and landing pages, SEO execution, blog content, ad and social creative, campaign planning, conversion optimisation, brand design support, marketing collateral, automation support, and performance reporting and analytics review.

Is every Branditify service included in a retainer?

No. What an engagement covers is agreed at the start and reflects the work that actually keeps recurring for your business. A retainer can span several disciplines at once, which is the point of one relationship rather than five, but it does not grant automatic access to everything Branditify does.

How are requests prioritised?

On what stops if it is not done, whose deadline it is and whether it is external, what else in the queue depends on it, and what is already in progress that switching would waste. Each position in the queue has a reason attached to it.

Can priorities change?

Yes, and reordering costs nothing while an item is still in the queue. It costs something once work has started, which is worth knowing before you ask — usually the honest answer is that switching now wastes half a day, and sometimes that is still the right call.

What happens when something genuinely urgent appears?

It moves to the front and something else moves back. The queue reorders rather than expanding, and the item that got displaced is named along with what that costs — a date getting tight is said on the day it becomes true, not afterwards.

Are requests unlimited?

No. Anyone offering unlimited is either rationing invisibly through a queue you cannot see, or has priced in the assumption that you will not use it. Raise as many requests as you like; the honest part is being told where each one sits.

Does a retainer include a fixed number of hours?

There is no published hour or credit allowance for Branditify retainers, and this page does not invent one. Engagements are scoped around the kind and frequency of work involved, which is agreed directly rather than sold as a tier.

How quickly is work completed?

The part you control is usually bigger than the part we do: how fast review comes back is the single most common reason something sits. No turnaround figure is published here because an honest one would be a range wide enough to be useless.

What happens to a large new project?

It gets its own scope. A rebrand, a new product, a platform rebuild or a migration needs discovery and a defined outcome, and burying one inside a monthly queue goes badly for both. The retainer carries on with everything else while that runs separately.

Do we have to explain our brand again for every request?

No — and the thing that carries over which nobody expects is the record of what was rejected. Knowing the three directions your team has already turned down saves more time than any style guide, and it is the part that never survives a change of supplier.

What determines the size of a retainer?

Less the volume than the variety. Twenty similar requests a month is a smaller engagement than eight that span content, design, web and reporting, because each discipline brings its own review, its own dependencies and its own way of getting stuck.

What happens when the engagement starts?

The first useful output is usually uncomfortable: your existing backlog, in an order, with reasons. Most teams discover that several things described as urgent have been waiting on somebody internal for weeks, and that is worth knowing before anyone starts making anything.

What if an ongoing arrangement stops being useful?

Then it should stop, and the signal is visible in the queue itself: when the same few items sit at the bottom for weeks because nothing new is arriving above them, the ongoing arrangement has stopped earning its place and individual projects are cleaner.