Briefing a CRM agency: what to hand over on day one

Kickoff is at ten on a Monday. The brief is a forty-slide deck about brand positioning. Three of the four platform logins do not work. The analyst who knows how the customer table is built is on leave until the following week.

By Friday the agency has produced a list of questions. By the end of the month it has produced an audit, which is a polite way of saying it has spent four weeks finding out what the client already knew. The retainer clock has been running the whole time.

This is the normal shape of a CRM engagement, and it is avoidable. Almost everything that makes the first month slow is a thing the client already has, in a form nobody thought to hand over.

The brief that costs a month

Most briefs describe ambition and omit constraint. They say the programme should be more personalised, more automated and better measured, which no agency will disagree with and none can act on.

What an agency needs on day one is the opposite: the specific shape of the situation. What exists, what it is wired to, what has already been tried, what is not allowed, and what has to be true by when.

A useful brief is short. Two pages of decisions plus a folder of artefacts beats forty slides of aspiration, because the artefacts are what the work is actually built from.

Write the objective as a sentence with a number and a date, then list what has already been attempted against it and what happened. The failed attempts are the most valuable part of the document and the part most often left out.

Access is the critical path, so start it before kickoff

Access always takes longer than anyone expects. Every week of delay is a week of the engagement spent on something other than the work.

Start the requests two weeks before kickoff, and treat the list as a project with an owner:

• The engagement platform, at a permission level that allows building, not only viewing.
• The analytics and reporting tools, including the raw data warehouse if there is one.
• The read-only database or warehouse schema behind the customer record.
• Whatever handles consent and preferences, plus the records that prove it.
• The domain registrar or DNS, or a named person who can publish a record within a day.
• Ticketing and documentation, so the agency can see what the engineering team is already committed to.

DNS is the one that reliably bites. Authentication changes need a record published, the registrar is often owned by a different department, and a two-day task becomes a three-week one.

Add a named contact per system, not a shared inbox. Access requests that go to a queue arrive after the work they were needed for.

Hand over the numbers you already argue about

Every organisation has a handful of numbers that get re-derived in different ways by different teams. An agency will walk into that argument blind in about week two.

Give them the definitions up front, along with the disagreement. Active customer. Repeat purchase rate. Contactable base. Revenue attributed to CRM. What counts as a new customer after a two-year gap.

This is the practical value of a single customer view, even an imperfect one. If a document exists that says which system owns identity and how records are joined, hand it over on day one. If it does not exist, say so plainly, because that changes the first month's plan considerably.

The same applies to field-level definitions. A data contract listing the attributes the programme depends on, their refresh frequency and their owner is worth more than any brief. Where one exists, it removes weeks of inference.

Then add the awkward numbers. Current deliverability by mailbox provider, complaint rates, the share of the list that has not opened anything in a year. Agencies find these in the first fortnight anyway, and sharing them early buys a month of honest planning.

Say what is fixed and what is negotiable

The fastest way to waste an agency's first month is to let them design against constraints that were never stated. Write the constraints down, in three groups.

Fixed: the platform contract with two years left, the legal review that every send must pass, the fortnightly release train, the brand rules that cannot move. These bound the solution space and should be stated without apology.

Negotiable: things that could change with a business case, such as a template system, an approval step or a data feed frequency. Naming these tells the agency where to spend effort arguing.

Open: everything nobody has decided yet. Being explicit that something is open is more useful than a vague answer that gets treated as settled.

Budget belongs in the fixed list. An agency that knows the annual number will propose work that fits it, and a roadmap finance will actually fund is built from the same information. Withholding the budget produces proposals nobody can approve.

Commercial constraints count too. If certain segments cannot receive discounts, or a category carries a margin the programme must protect, say so at the start. That is the same discipline we described in loyalty and margin, and it is far cheaper to apply before a mechanic is designed than after.

Name who decides, and how approval works

Engagements stall on approval more often than on capability. The work is built, then waits ten days for sign-off from someone who was not at kickoff and disagrees with a decision made in week one.

Put four names in the brief. The single person who can approve creative and mechanics. The person who owns the data side and can commit engineering time. The legal or compliance reviewer. And the person who breaks a tie when the first two disagree.

Then write the approval path as a sequence with durations. Who sees the work, in what order, and how long each step takes. If legal review takes five working days, that is a fact the plan has to be built around rather than a surprise to be discovered.

One more thing, easy to give and rarely given: the last two years of programme history. Which campaigns were tried, what the results were, and which ideas have already been rejected internally and why. Without it an agency will confidently propose something that failed in 2024.

What day thirty should look like

If the handover is done properly, the first month produces shipped work rather than a discovery document. A reasonable expectation is one journey rebuilt or launched, one measurement problem fixed, and a ranked backlog everyone has argued over.

Agree that expectation in writing before the engagement starts. An agency that knows it is judged on what shipped in the first month will ask for access in week minus two, which is the behaviour you wanted anyway. Our own CRM strategy engagements are set up on exactly that basis.