How to structure a CRM for an agency
Agencies break the standard CRM shape because the client relationship outlives the deal. The four objects that fix it, and where retainers and referrals belong.
Syncek Team · CRM reference library
/ 4 min read / Art. #23
An agency CRM needs four objects rather than the usual three: company, person, deal, and project. The standard shape assumes a deal ends when it closes. In an agency the relationship starts there and produces the next deal, so a structure with nowhere to put delivered work loses the history that wins repeat business.
Why the default shape does not fit
A product sale is a transaction. An agency engagement is a relationship with several overlapping transactions inside it: you pitch a new scope while delivering the current one and invoicing the last.
Force that into company, person and deal and one of two things happens. Either every project becomes a deal, so the pipeline fills with work you already won, or projects live outside the CRM and the account history has a hole exactly where the value is.
The four objects
Company is the client and the durable record. Everything else hangs off it.
Person is the contact. Agencies churn contacts fast, so keep leavers on the record: a marketing manager who moves is a warm lead at a new logo, which is the most reliable source of agency new business.
Deal is one scope you are trying to win, and it leaves the pipeline when won or lost. Nothing already won stays there.
Project is delivered or in-delivery work: start date, end date, value, owner, status. This is the object most agencies are missing.
Retainers sit between the two. Treat the renewal as a deal and the ongoing work as a project with a rolling end date, so renewals appear in the pipeline where you can forecast them.
Two fields that earn their place
Record the referral source on the company, as a field rather than a note. Agencies run on referrals, and "where does our work come from" is unanswerable when the answer sits in notes in nine spellings. Same argument as a structured lost reason.
Record the last delivery date on the project. It tells you a client has gone quiet while still technically active, which a pipeline view cannot show.
Keep the pipeline about new work
The most common agency pipeline problem is that it contains delivery. A board where "in production" is a stage cannot be forecast, because half the cards are revenue you already hold.
Keep stages about winning work, and let projects carry delivery status. If a scope is signed, it leaves the pipeline the day it is signed, and it should leave when the buyer signs, not on Friday.
Attio and Syncek let you define custom objects directly, HubSpot needs a paid tier for them, and Airtable or Notion give you the shape without much sales structure. A clean starting dataset matters more than the tool, so prepare the import file first: four objects full of duplicate companies is worse than three that are accurate.
Frequently asked questions
How should an agency structure its CRM?
Use four objects: company, person, deal, and project. Company is the durable client record, person is the contact, deal is one scope you are pitching, and project is work you have already won and are delivering. The fourth object is what most agency setups lack, and without it delivered work either clogs the pipeline or disappears from the client history entirely.
Should agency projects live in the CRM or a project tool?
The delivery detail belongs in your project tool, but a lightweight project record belongs in the CRM: client, value, start date, end date, owner, and status. That record is what connects revenue to the account history and tells you when a client last had work. Without it, the CRM shows only what you tried to sell, never what you actually delivered.
Where do retainers fit in an agency CRM?
Split them. Treat each renewal as a deal so it appears in the pipeline and can be forecast, and the ongoing work as a project with a rolling end date. Modelling a retainer purely as a permanent deal leaves it in the pipeline forever and inflates the forecast; modelling it purely as a project hides the renewal until it arrives.
Should you delete contacts who leave a client?
No. Mark them as a former contact and keep them linked to the old company. In agency new business, a contact who moves to a different company is one of the most reliable warm leads available, because they already know how you work. Deleting the record loses both that lead and the history of who made decisions on past projects.
How do you track where agency work comes from?
Put a referral-source field on the company record and make it a select rather than free text. Agencies rely heavily on referrals and repeat business, and the question "where does our work come from" is unanswerable when the answer lives in notes written several different ways. A structured field turns it into a report you can run in seconds.
Does an agency need a separate pipeline for new and existing clients?
Often yes, because the two have genuinely different stages. New business needs qualification and a proposal step; existing-client work usually skips both and moves from scoping to approval. Running them as one pipeline forces stages that fit neither. Two pipelines with their own stages stay accurate, and most CRMs support more than one without extra cost.