The first 30 days with a new client shape everything that follows. At Choco Media, we have onboarded enough clients to know that most friction — the kind that causes late-night messages, scope arguments, and early churn — is not caused by poor strategy or weak creative. It is caused by information gaps and misaligned expectations in the first four weeks. This is the client onboarding process we have landed on after iterating through what did not work.
This post is for account managers, strategists, and agency owners who are tired of the first month feeling like a fire drill. If you handle fewer than 20 clients per year, you should still have a written onboarding process. Without one, every new engagement starts from scratch, and the team re-learns the same lessons on the client’s time — and your margin.
What follows is the week-by-week sequence we follow with every new retainer client. Some of it will feel obvious. The parts that feel obvious are usually the parts that get skipped under pressure, and skipping them is where things go wrong.
Why the first 30 days are higher-risk than any other period
A new client is operating on trust they have not yet earned from you, and you are operating with context you have not yet gathered from them. Both sides are filling gaps with assumptions, and assumptions compound. By week six, you can find yourself producing work against a brief that was never actually validated, for an audience that has since shifted, with a tone of voice that the founder hates but has not said so yet.
The problems that surface at month three were almost always seeded at week one. The sales handover was too thin. The kick-off call covered logistics but not strategy. Nobody asked about previous agency relationships and why they ended. The client’s internal approval process was not mapped, so every round of feedback arrives as a surprise.
- Unclear decision-making authority on the client side causes revision cycles to multiply
- A shallow brief produces generic work, which produces skepticism, which produces micromanagement
- Undocumented expectations about availability and response times create friction before any work is delivered
- Missing context about what has already been tried leads to repeating approaches that have already failed
None of this is the client’s fault. Clients do not know what information agencies need. That is the agency’s job to extract — systematically, not opportunistically.
The sales-to-delivery handover: the highest-risk moment
Most onboarding failures start before the first client call. They start in the handover between the person who sold the engagement and the person who will deliver it.
In a small agency, this might be the same person, which reduces but does not eliminate the problem. When it is two different people — and especially when there is any time gap between the sale closing and delivery starting — context gets lost. The delivery team inherits a client they did not qualify, with expectations they did not set.
What the handover document should cover
We use a short internal handover document that the salesperson completes before the kick-off call. It takes 20 minutes to fill in and saves hours of downstream confusion.
- Why the client bought: what specific problem were they trying to solve?
- What they have already tried: previous agencies, internal efforts, tools
- What they are nervous about: every client has a fear — surface it early
- Who are the real decision-makers: not just the contact, but who signs off on work
- What was promised: every verbal commitment made during the sale, however casual
- Any red flags noticed during the sales process
If you cannot answer most of these questions, the sale was not closed with enough information. That is fixable, but you need to fix it before the kick-off, not during it.
Week 1: listen before you produce anything
The first week has one job: gather information. Nothing ships in week one. No campaigns launch, no copy gets written, no designs are produced. This is a hard line for some agencies that feel pressure to demonstrate value immediately, but early output produced without proper context is almost always reworked — costing more time than the delay would have.
The brief you have at the start of week one is not the brief you will work from. The real brief emerges from the questions you ask in the first five days.
The kick-off call agenda
- 30 minutes on business context: what does success look like in 12 months? What does failure look like? Who are the customers, how do they buy, what do they care about?
- 20 minutes on brand: what does the brand sound like? What does it not sound like? What have they produced that they are proud of, and what makes them cringe?
- 20 minutes on history: what has been tried before? What worked, what did not, and why?
- 20 minutes on process: who approves work? What does the feedback cycle look like? How fast do approvals typically move?
- 10 minutes on logistics: tools, communication channels, billing, reporting cadence
Send the agenda 48 hours before the call. Ask the client to come prepared with three examples of marketing from any brand — not necessarily theirs — that they think is doing a good job. The examples tell you more about their taste than any brand questionnaire.
What to do after the kick-off call
Within 24 hours, send a written summary of what you heard. Not a meeting recap — a synthesis. “Here is what we understand about your situation, your goals, and your constraints. Please correct anything that is wrong.” This document becomes the first version of your shared brief, and it signals that you were actually listening, not just presenting.
Week 2: build the brief and confirm the plan
Week two is where the information you gathered gets structured into something the team can work from. This means producing a written brief that everyone on the delivery side has read — not just the account manager.
We use a brief format that covers eight fields: audience, positioning, tone of voice (with examples), goals, constraints, previous approaches, competitive context, and success metrics. Each field should have enough substance that a new team member could produce on-brand work without needing to ask follow-up questions. If a field cannot be filled in yet, that is a gap to close before production starts — not a reason to start anyway.
- Audience: specific, not demographic. What does this person think about before they buy? What are they afraid of? What have they tried before?
- Tone: include examples. “Professional but approachable” means nothing. A paragraph from the client’s best-performing email means something.
- Success metrics: agree on these before work starts, in writing. Ambiguity about what counts as success is a churn risk.
At the end of week two, hold a short alignment call — 30 minutes — to walk through the brief with the client. Ask them to correct it, not approve it. “Approval” implies they are doing you a favour. Correction implies shared ownership.
If your agency runs regular quarterly reviews with retainer clients, this brief becomes the baseline document you return to each quarter to measure drift and re-align priorities.
Week 3: first work, with tight feedback loops
Week three is when production starts, and when the brief quality is tested. Good briefs produce first drafts that are directionally right and need refinement. Poor briefs produce first drafts that miss the mark, trigger a full revision, and cause both sides to question whether the engagement was a mistake.
Whatever you produce in week three should be smaller in scope than what you would normally produce. Not because you lack the capability, but because the first round of feedback from a new client is high-value information about their taste, their process, and their communication style. You want to gather that information quickly, on a small piece of work, before it affects something major.
How to structure the first feedback cycle
- Deliver with a written explanation of the choices you made and why — do not make the client reverse-engineer your reasoning
- Ask specific questions: “Does this tone match what you had in mind?” is more useful than “Let us know what you think”
- Separate revision rounds from revision scope: one round can include many changes, but each round should produce a document that represents the client’s consolidated view, not a stream of individual comments
- Set a time limit for feedback, not as a pressure tactic, but as a project management expectation — “we work best with feedback within 48 hours”
If the first-round feedback reveals that the brief was wrong, that is useful information. Update the brief before continuing. Do not just fix the immediate work and carry the underlying misalignment forward.
Week 4: establish the recurring rhythm
By week four, the goal is to have the engagement running on a predictable cadence that neither side has to think about. Predictability is what transforms a new client relationship into a stable one.
The cadence we use with retainer clients includes a weekly written status update (not a call — an async document), a biweekly check-in call of 30 minutes, and a monthly report that covers results, observations, and the next month’s priorities. This might seem like a lot of communication for a lean agency, but most of it is templated, and it prevents the much more expensive reactive communication that fills the void when clients do not hear from you.
- Weekly status update: what was done this week, what is planned for next week, any blockers or decisions needed
- Biweekly check-in: open discussion — what is working, what is not, anything shifting on the client’s side
- Monthly report: results against the metrics agreed in week two, trend observations, and the next period’s focus
The weekly status update is the highest-leverage communication habit in an agency. Clients who do not hear from their agency fill the silence with doubt. Clients who receive a consistent, honest update every Friday spend less time worrying and less time generating reactive requests. If you want to understand how to filter for clients who will work well with this model, that filtering starts at the sales stage — not after the contract is signed.
The onboarding document: your single source of truth
Everything described above works better when it lives in one place. We create an onboarding document for each new client at the start of the engagement. It is a shared Notion page (or Google Doc, depending on client preference) that contains: the brief, the agreed-upon success metrics, the communication cadence, the decision-making process, contact information, and a running log of the most important decisions made during the engagement.
This document is not a project tracker. It does not contain tasks or deadlines. It is a reference document — the answer to “what did we agree?” when memory is fuzzy or when someone new joins the account.
- The brief section is updated whenever the brief changes materially
- The decisions log is updated whenever a significant direction is agreed or changed
- The metrics section is updated monthly with actuals against targets
The onboarding document also serves a practical purpose: when the engagement eventually ends, or when team members change, there is a record. This is relevant to how we approach client handovers at the end of an engagement — a topic we cover in detail in our post on bespoke retainer engagements.
Common failure modes and how to prevent them
After running this process across many engagements, the failure modes are consistent enough that we now brief against them explicitly.
The over-eager start
Pressure to show early value leads agencies to skip the brief-gathering phase and move straight to production. The work ships fast and misses the mark. The client loses confidence. The agency doubles down by producing more, faster — and the relationship deteriorates before it has had a chance to form.
Fix: make week one explicitly a non-production week. Set this expectation with the client before the engagement starts. “We spend the first week gathering context before producing anything” is a line that most clients receive well. It signals rigour, not delay.
The verbal brief
Some clients resist written briefs. They want to talk through things on a call and trust that the agency will interpret correctly. This works when the agency has deep familiarity with the client’s world — which they do not have at the start. A verbal brief that is not followed by written synthesis creates plausible deniability for both sides: “That is not what I said” and “That is what I heard.”
Fix: every call is followed by a written summary. This is not extra work — it is the agency’s interpretation of what was agreed, and it is the client’s opportunity to correct any misunderstanding before it costs anyone time.
The single point of contact problem
When the agency’s relationship with a client runs through one person — on either side — any disruption (illness, holiday, role change) breaks the information flow. We have seen engagements destabilise because the agency’s account manager took a two-week holiday and no one else on the team knew the brief.
Fix: the onboarding document solves this on the agency side. At least one other person on the delivery team should read the brief and attend the month-one check-in, not to participate actively, but to have context.
What to do when the first 30 days do not go to plan
Sometimes the client changes priorities in week two. Sometimes the brief reveals that the scope of work agreed during the sale is not matched to the budget. Sometimes a key contact leaves. When these things happen early in an engagement, the instinct is to handle them informally and hope the issue resolves. That instinct is wrong.
Early problems deserve early, direct conversations. A 30-minute call in week three that acknowledges a mismatch between brief and scope is infinitely less damaging than a six-month engagement that delivers work nobody wanted. Use the onboarding document as the anchor for the conversation: “Here is what we agreed. Here is what we have learned since. Here is what needs to change.”
- Scope changes go back to the agreement stage — document them, reprice if necessary, get written confirmation
- Brief changes update the brief — do not carry two versions of the brief in different people’s heads
- Relationship disruptions (contact changes, internal reorganisation) trigger a repeat of the information-gathering process, not an assumption that existing context is still valid
The 30-day milestone: a deliberate review
At the end of the first 30 days, we run a short structured review — 45 minutes, with the key stakeholders on both sides. The agenda is simple: what is working, what is not, and what would we do differently if we were starting today.
This review is not a performance review. It is a process review. The goal is to catch anything that was set up wrong at the start — communication cadence, brief quality, team fit, tooling — and fix it while the engagement is still new enough to reshape.
In client work we have found that the engagements which include this explicit 30-day review perform better at month six than those that do not, even when the first 30 days were smooth. Deliberately pausing to assess creates a habit of honest conversation that makes the hard conversations at month four or month nine easier to have.
If you want to think through how your agency handles ongoing client relationships, or whether your current onboarding process is fit for the type of work you do, reach out and we can talk through it — we work with a small number of agencies as well as directly with brands.