Setting Client Expectations at Kickoff (The Conversation Most Agencies Skip)
Short answer: Nearly every difficult client conversation — scope disputes, revision spirals, complaints about responsiveness, invoice queries — traces back to something that wasn't established in week one. Kickoff usually covers goals and timeline and skips the operational agreements. Seven things said clearly at the start prevent most of the friction that arrives at month three.
The seven
1. How and where requests should come in
One channel, named. If you don't specify, requests arrive by email, text, on calls and in passing — and some get lost, which the client experiences as unreliability.
2. What your response times actually are
Not aspirational. If you reply within a working day, say a working day. Clients build their behaviour around what you tell them, and an unstated expectation defaults to "immediately."
3. How many revision rounds are included
A number, in writing, at the start. This single item prevents more friction than anything else on the list, and it's almost never said until round four.
4. What "done" means
Whether deliverables need formal sign-off, who gives it, and what happens if it doesn't come. Without this, finished work can be reopened indefinitely.
5. What's out of scope, specifically
Naming exclusions is more useful than listing inclusions, because it's the ambiguous cases that cause problems and inclusion lists can't anticipate them.
6. How additional work gets handled
Say at kickoff that extras get a short change order. Then when it happens in month two, it's the process rather than a reaction.
7. When they'll hear from you and where they can look
A predictable cadence, and somewhere they can check without asking. This is the item that determines how many status requests you field for the next year.
How to say it without sounding defensive
The reason agencies skip this is that it feels like negotiating against yourself at the moment of maximum goodwill.
Two things make it easy. First, frame it as how you work rather than what you're protecting: "Here's how we run things so nothing gets lost." Second, say it once, briefly, and put it somewhere they can re-read — a page they keep beats fifteen minutes on a call they'll forget.
The client isn't offended by structure. They're reassured by it, because it's evidence you've done this before.
Where to put it
Not buried in the SOW — nobody re-reads a contract. A short operating page the client can access throughout the engagement, covering these seven items in plain language. Half a page.
The value isn't the document. It's that when something ambiguous happens in month four, there's a shared reference that was agreed when nobody was annoyed.
Frequently asked questions
What should be covered in a client kickoff?
Beyond goals and timeline: the request channel, your real response times, included revision rounds, what "done" means, specific exclusions, how extra work is handled, and where they can check status.
Isn't setting boundaries at kickoff off-putting?
Framed as how you work rather than what you're protecting, it reads as competence. Clients who've worked with disorganised agencies find it reassuring.
Where should expectations be documented?
Somewhere the client can return to, not buried in the contract. A short plain-language operating page beats a clause nobody re-reads.
What if a client ignores the agreed process?
Redirect gently and immediately — accept the request, then point at the channel. Waiting until it's a pattern makes it a confrontation instead of a correction.
The short version
Seven items, said in week one, written somewhere they can re-read. Channel, response times, revision rounds, definition of done, exclusions, how extras work, and where to look.
That last one does the most work over a year. See what "somewhere to look" can be — 7 days for $1.