Running a Client Kick-Off Meeting That Actually Sets Expectations

A client kick-off meeting is expected to produce agreement, not enthusiasm: what the engagement will deliver and what it will not, who signs off decisions, what access you need and by when, how findings will reach the client, and how often you meet. If none of that is written down afterwards, it was a briefing.

This is written for independent consultants and small firms. The generic mechanics of running the session are covered elsewhere. What follows is the consulting-specific part, where you are an outsider on a fixed fee, with no line authority and a client who has already formed a private picture of what you are for.

What is expected in a kick-off meeting?

A kick-off is expected to convert a signed proposal into a working agreement. Six things should be true when people leave the room:

• The problem is stated in one sentence that the client repeats back without correcting it.
• Deliverables are countable. Three workshops, one findings report, one prioritised recommendation set with indicative costs. Not “strategic support”.
• Exclusions have been said out loud, not merely printed in the contract.
• One person owns sign-off, and everyone knows who that is.
• Access has dates against it. Interviews, systems, documents, the finance extract.
• The cadence is fixed. Who meets whom, how often, and what gets written down each time.

Agenda timings, facilitation and who speaks when work the same way here as on any internal project, and the general project kick-off guide covers the agenda and facilitation mechanics. The sections below deal with the five things consulting engagements get wrong: the scope boundary, the unstated expectations, access, decision rights, and what happens to findings nobody wants.

What the client will get, and what they will not

Say both, out loud, in the kick-off. The exclusions in your contract have been read by procurement and possibly by nobody else, and the people sitting in the kick-off are rarely the people who signed.

The format that works is a pair of lists on one slide. “By the end of this engagement you will have” on the left, “this engagement will not” on the right. The second list is the one earning its place. Concrete exclusions sound like this:

• This engagement will not produce a business case for the replacement platform.
• This engagement will not cover the two regional subsidiaries.
• This engagement will not include implementation support once recommendations are accepted.

Watch faces while you read the right-hand list. Surprise at an exclusion is the gap between what was sold and what was heard, and it is far cheaper to find it in week one than in the final presentation. Clients rarely remember your scope section. They remember the sentence in the room where you said no.

If the exclusions are still soft at kick-off, the scoping work was not finished, and scoping a consulting project properly happens before this meeting, not during it.

What are the five common customer expectations?

There is no canonical list of five, whatever the search results suggest, and the number moves depending on who is selling the training. Five do recur in consulting engagements, and what they share is that clients hold them firmly and state none of them.

1. That you already understand their business. They assume the pitch reading is done and resent being asked basics in week three. Ask the basics in the kick-off instead, framed as confirmation.
2. That the senior people from the pitch will do the work. If a junior analyst will run the interviews, say so now, with their name and what they are good at.
3. That the work will not create work for them. It will. The access table is where you break that assumption gently.
4. That you will not embarrass them internally. Whoever hired you has staked some credibility on it. This is why the route for unwelcome findings matters more than the findings.
5. That the fee is a ceiling rather than an estimate. Say plainly whether it is fixed, capped or time and materials, and what triggers a change note.

None of these are unreasonable. They only become expensive when they stay unspoken for six weeks.

What is the role of a customer in the ideal kick-off meeting?

The client’s role is to supply what only they can supply: the real objective, the political constraints, the decision rights and the access. They are not an audience. A kick-off where the consultant talks for fifty minutes has confirmed nothing except that you can present.

Three questions reliably turn a passive client into a participating one:

• What would make you regret commissioning this?
• Which recommendation would be impossible to act on, whatever the evidence says?
• Who has looked at this before, and what happened to their report?

The third question is the most useful thing you can ask in the first hour. If a previous review exists and was shelved, you need to know why before you write a word of your own.

Access is a dependency, and it needs a date

Access agreed in principle is not access. A named person, a specific system and a date is access. Bring a table to the kick-off with the last column empty and fill it in live.

What you need	Granted by	Date agreed	What stalls without it
Interviews with eight operations staff	Operations director		Findings section, all of it
Read access to the ticketing system	IT service owner		Volume analysis and baseline
Last two years of cost data	Finance business partner		Any recommendation with a number on it
Attendance at the monthly ops review	Sponsor		Understanding how decisions really get made
The previous consultancy’s report	Sponsor		Avoiding repetition of work already done

Dependencies the client agreed to in a meeting and then missed produce a conversation about their delay. Dependencies you never raised produce a conversation about yours. That is the entire reason the table exists.

Include what the access is worth in time. “Two weeks late on the cost data moves the final report by two weeks” is a sentence the sponsor can act on. “We will need finance data at some point” is not.

Who is the real sponsor, and who can actually decide?

The sponsor is whoever can stop the engagement without asking anybody’s permission. That is often not the person who briefed you, and almost never the person coordinating your diary.

Three roles need separating in the kick-off, and clients routinely blur them:

• The sponsor. Owns the budget and the consequences. Sees findings first.
• The day-to-day contact. Arranges access, chases documents, knows where everything is. Cannot approve scope changes, however helpful they are being.
• The decision-maker for the recommendations. Sometimes the sponsor, sometimes a committee, sometimes a person who has not been mentioned yet.

Ask the direct version out loud: if the recommendation is to close the Leeds site, who signs that off? The answer tells you who the report is really written for. Write it down and repeat it back before moving on.

Sponsors change. If yours does mid-engagement, treat it as an event rather than an administrative detail and run a twenty-minute version of this meeting with the new one. Inherited engagements are the ones that get cancelled.

Agree now how unwelcome findings will travel

Decide in the kick-off exactly how you will tell the client something they will not enjoy hearing. The failure is rarely that consultants are too blunt. It is that the first time a client hears an uncomfortable finding is in a room containing the person responsible for it.

Agree three things:

• The no-surprises rule. The sponsor sees anything difficult in draft before anyone else does, with enough notice to think rather than react.
• The format. Findings separated from recommendations, evidence attached, no individual named unless the client asks for that and understands why.
• The route. Whether a difficult finding goes to the sponsor alone, to the steering group, or into the report only.

State clearly that you will not soften a finding to keep the room comfortable, and that you will never present one the sponsor has not seen. Those two commitments together are what makes an uncomfortable report survivable. Structuring the presentation of findings is a separate craft, but the permission to deliver them is granted here, in week one, while everyone is still relaxed.

Do not let the engagement become extra delivery capacity

Consulting engagements get quietly reclassified as staff augmentation, and the reclassification starts with requests that are easier to accept than to refuse. Nobody announces it. It arrives as a favour with a deadline attached: could you sit in on the supplier call, could you draft the paper for Thursday’s board, could you take the minutes since you are here anyway.

Inoculate in the kick-off with an operating principle stated in your own words. “We advise on the target operating model. We do not run the transition programme” takes four seconds and gets referenced for the next three months.

Then give extra requests somewhere to go. A change note, priced, approved by the sponsor, is not bureaucracy; it is the only alternative to saying no repeatedly to a client you like. The test that settles most cases in seconds: if you removed the request from the engagement, would any agreed deliverable be weaker? If not, it is not your work, however small it looks.

What are the 3 C’s of engagement?

No canonical set of three exists for consulting engagements. The phrase circulates mainly in employee engagement writing, where different authors expand it differently, so quoting it as established doctrine would be inventing authority you do not have.

If you want three words to hold a kick-off against, these are the ones worth using, offered as shorthand rather than as a framework anybody teaches:

• Clarity. Deliverables and exclusions both stated aloud, in language the client uses rather than the language of your proposal.
• Cadence. A fixed rhythm of contact, so information does not travel only when something has gone wrong.
• Candour. An agreed route for bad news, established before there is any.

The three-letter version is memorable, which is its only real advantage. The underlying commitments are what a client will hold you to.

How to make an engagement plan?

Turn the kick-off outputs into a short engagement plan within two working days, while people still remember agreeing to things. It is a working document, not a contract annex, and it should be readable in five minutes.

1. Restate the objective in one sentence, plus the decision the client will make with your output.
2. List deliverables with dates and the named person who accepts each one.
3. Convert the access table into dated dependencies with a client owner beside each.
4. Set the cadence and the escalation route. Weekly update, fortnightly sponsor check-in, and who you call when something is blocked.
5. Record assumptions, including the ones the fee depends on. Availability of interviewees is usually the first to break.
6. Name the change process and who is authorised to trigger it.
7. Circulate it and ask for corrections, not approval. People will correct a document they would never get round to approving.

Capture the answers during the meeting rather than reconstructing them from memory afterwards, because reconstruction is where the exclusions quietly soften. One tool for that is Projan, which puts the kick-off questions to the group in Slack or Microsoft Teams, holds the agreed answers against each one, and writes the result out to Confluence or Asana. Building the plan out into full deliverable definitions is the next job after this meeting.

Frequently asked questions

What are the 4 principles of engagement? There is no agreed set of four for consulting work, and lists claiming otherwise come from unrelated fields. Four things do need settling before delivery starts: who decides, what is out of scope, when access is granted, and how bad news reaches the sponsor. Agree those and the number you call them stops mattering.

What should you send out before a client kick-off? Send the agenda, the draft deliverables list with the exclusions attached, the access table with blank dates, and the names you want in the room. Sending it two working days ahead gives the client time to notice a missing name. It also means objections arrive by email rather than as a silence you misread as agreement.

How long should a consulting kick-off run? Ninety minutes covers scope, exclusions, sponsor, access and cadence for most engagements. Half a day is justified when the client team is large or the work spans several business units, and then only if the extra time is spent on their constraints rather than your credentials. Anything under an hour tends to skip the exclusions.

What if the client wants to skip the kick-off? Treat it as a signal rather than an efficiency. Clients skip kick-offs when they think the answer is already known or when the sponsor does not want to be pinned to a decision. Offer a shorter session, insist the sponsor attends, and send the confirmations in writing afterwards regardless. Silence on that email is worth having on record.

Should the kick-off summary be signed? A signature is unnecessary for most engagements, but written confirmation from the sponsor is not. Send the summary, ask for corrections by a stated date, and note that you will proceed on that basis. If the engagement is fixed-price or politically exposed, ask for an explicit reply rather than treating silence as agreement.

A kick-off that ends in agreement rather than goodwill is worth an hour of anyone’s time. Name the exclusions aloud, put dates against access, find the person who can stop the project, and agree how bad news will reach them before there is any.