A marketing agency runs two sales engines at the same time. The first is new business, where pitches, referrals and proposals come and go over a few weeks. The second is the account engine, where retained clients renew, expand or quietly drift away. A CRM for marketing agencies has to handle both, and it has to do so without asking account managers to fill in forms that only help someone else.
Many agencies start with a spreadsheet of prospects, a shared inbox and a folder of proposal documents. That works while the business is small. It becomes harder when several people pitch at once, when retainers need monthly reviews and when the director wants to know which clients are at risk before a renewal date arrives. The sections below set out how a CRM can be shaped around those moments.
This guide is for agency owners, business development leads and account directors who want a clearer picture of pipeline and client health. It stays general on software choice, because the right set-up depends on how your agency sells, scopes and delivers its work.
Why a CRM for marketing agencies needs two pipelines
New business is a pipeline of pitches
New business at an agency rarely arrives as a single enquiry form. A prospect may come from a referral, a conversation at an event, a tender list or a former client who has moved to a new company. Each route needs a record that shows the source, the decision maker and the reason the agency is being considered at all.
A pitch also has its own stages, such as an introductory call, a briefing, a shortlist, a presentation and a decision. Teams that force pitches into the same stages as retainers usually end up with reports that say very little.
Existing clients are accounts, not deals
Once a client signs, the relationship changes. Work continues month after month, the scope shifts, people join and leave on both sides, and the renewal date becomes the event that matters most. The CRM should hold the account record, the contract dates, the services in place and the named contacts, so that the account team sees the whole relationship in one view.
When a pitch is won, the new account should be created from the opportunity with its history carried across. That way the team does not have to rebuild the story from memory when the first monthly call comes round.
Proposals that the CRM can track and learn from
Keep each proposal linked to its deal
A proposal is more than a document. It is a set of decisions about scope, timing and options, so the CRM should record which version went to which contact and when. When a client asks what they were offered, the answer should be one click away, not buried in an old email thread.
Present the options as options rather than a single list of items. A core route and a fuller route, each with clear assumptions about what the client must provide, is easier for a buyer to compare and easier for the agency to track later.
Record why proposals are won or lost
Win and loss reasons are often the most useful data an agency has, and they are frequently missing or vague. A short reason in the client's own terms is worth more to the next proposal than a general note. Useful details to capture include:
- The goal the client gave as the reason for change
- The services proposed and the ones the client chose to leave out
- Who reviewed the proposal internally, and when
- The date of the agreed follow-up call
- Whether the decision turned on fit, timing, budget or a competitor
Keep the reasons in plain language. A choice list with a sentence of context is easier to report on than long free-text notes that only the author understands.
Retainers, projects and the scope in between
Write the monthly scope into the account
A retainer is a promise about capacity and results, not a single job. The CRM should record the monthly scope in plain terms: the channels covered, the deliverables, the reporting rhythm and the approval rules. When the scope changes, log it as a change request with a date, instead of letting it be absorbed quietly into the monthly work.
Fields worth agreeing before a retainer goes live include:
- The start date and the renewal date
- Notice terms, as set out in the signed agreement
- The approval contact and the person who signs off work
- The reporting day and the format of the monthly report
- What counts as extra work and who approves it
Projects that lead to retainers
Many agencies win a project first and offer ongoing support afterwards. Linking the project record to the retainer proposal shows how the relationship grew, and it helps the account director see which projects tend to produce ongoing work. If a project was delivered well but no retainer followed, that gap is worth a short note as well.
Client health: spotting risk before the renewal call
Signals that a client is cooling
Account risk in an agency usually shows up in small signals long before a client gives notice. Approvals take longer, meetings are moved, requests change from strategy to simple tasks, and senior people on the client side stop joining calls. None of these signals proves anything on its own. Recorded consistently and together, they show a pattern the account team can act on.
A simple list of signals, each with a date and a short note, is easier to use than one free-text field that only one person reads. The account team can then compare notes at the monthly review.
A health rating the team can agree
A basic rating, such as green, amber or red, reviewed in the monthly account meeting, is often more useful than a complicated score that nobody understands. Each rating should come with a reason and a named owner. Treat it as a prompt for a conversation, not a verdict on the account manager, or people will stop being honest in the record.
Growing existing accounts without turning them into pitches
Spotting the next piece of work
Expansion usually comes from inside the account. A client who trusts the work may ask for another channel, a new campaign or help with a product launch. The account team usually hears about those needs first, so the CRM should give them a simple way to log each one as an opportunity linked to the existing account, rather than as cold new business. That keeps the pipeline honest about where growth is coming from.
Record who raised each expansion idea, who the decision maker is and what the client said in their own words. A short note in the client's language is more useful later than a tidy category.
Keeping expansion from feeling like a pitch
Clients notice when an account manager is chasing a target rather than solving a problem. Raise expansion after a results review, not in the middle of an approval chase, and let the record show what was delivered before any new scope is discussed. If the answer is not yet, log that too, with a date to look again.
Agree who leads the conversation before it starts. Where business development is involved, the account director should make the introduction, and the record should show who owns the next step. Two people approaching the same client with different offers is one of the quickest ways to damage a good relationship.
Renewals and the handover into delivery
Make renewal reviews a managed pipeline
A renewal should not start with a last-minute chase. Set reminders well ahead of the date so the account team can prepare a proper review of results, scope and next steps. Check the notice terms in the agreement, because they decide when the conversation has to happen. The renewal stage should show the date, the owner, the agreed review meeting and the current health rating.
A handover that gives delivery the full brief
A sale is not finished when the client signs. The delivery team needs the original brief, the goals the client agreed, the approval chain, access to the accounts and tools the work depends on, and any commitments made during selling. Without a structured handover, delivery has to ask the client to repeat what they already said, and the first month starts to feel like a restart.
A short kick-off record in the CRM can hold the essentials:
- The goals in the client's own words, with the date they were agreed
- The people who approve work, and the people who must be copied in
- Account and asset access that has been requested and received
- Known constraints, such as brand rules, legal reviews or blackout dates
- Anything promised during the pitch that delivery must honour
Who owns which records in a marketing agency CRM
Ownership is where agency CRMs often go wrong. When everyone can edit everything, nobody is sure which version is right. General products such as HubSpot and Salesforce can usually hold more than one pipeline, so the real question is how the agency divides responsibility before the set-up begins.
Business development owns the new business stages
Business development decides which stage a pitch sits in, the value shown in the pipeline and the next step. Once a pitch is won, ownership of the account moves to the account director, who keeps the record current from that point onwards.
Finance links the invoices, not the story
Invoices, payments and credit control usually sit in an accounting package such as Xero or Sage. The CRM should link to the client record and show the invoice reference rather than copy the figures. That keeps the commercial story in the CRM and the money in the accounts, with one clear home for each.
FAQ
What is a CRM for a marketing agency?
It is a shared system that tracks prospects, pitches, proposals, client accounts, contracts and renewal dates in one place. For an agency, it also connects the sales side with the people who deliver the work, so the client history does not disappear when a project starts. It sits alongside project management tools rather than replacing them.
Should an agency track new business and existing clients in the same pipeline?
Usually it is better to keep them apart. New business is a set of opportunities that can be won or lost, while an existing client is an account with scope, contract dates and renewal points. Linking the two records keeps the history visible without mixing their stages.
How do you track retainers in a CRM?
Start with the monthly scope in plain terms, then add the start and renewal dates, the notice terms and the approval contact. Log every scope change as it happens, so the account history shows what was agreed and when. That makes renewal conversations far easier to prepare for.
What is client health in an agency?
Client health is a simple view of how well an account is going, drawn from signals such as slower approvals, moved meetings and changes in the client's contacts. Keeping the view deliberately simple makes it easier to act on. Every change in rating should carry a recorded reason.
When should a renewal conversation start?
Start early enough to review results, scope and next steps before any notice period matters. The right timing depends on the terms in your own agreement, so check those first. A reminder set well ahead of the renewal date gives the account team time to prepare a proper review.
What should an agency hand over to delivery after a sale?
Hand over the brief as the client described it, the goals they agreed, the people who approve work and the access that delivery will need. Include anything promised during the pitch, because those promises are easy to lose. A short kick-off record in the CRM stops delivery asking the client to repeat themselves.
Final thought
A CRM for marketing agencies earns its place when it keeps two things honest: the pipeline of new work and the health of the accounts already won. Pitches, proposals and renewals stop depending on one person's inbox, and the account team can see risk while there is still time to act on it.
Keep the first set-up modest. Two pipelines, a short list of health signals, renewal reminders and a handover checklist will change how the agency runs. Leave the extra fields and automations for later, once the first set has proved itself in daily use.
If you want to talk through how new business, retainers and handover could share one CRM, Mirex Agency is a London digital agency that builds CRM solutions for UK small and mid-sized businesses. The details are at mirexagency.com/services/crm-solutions.
