How do I run a client kickoff that sets delivery up right?

A good kickoff turns the proposal into the plan your team and client will actually use. Confirm the deliverables, revision rounds, effort assumptions, timeline, and the person who can say yes on the client side. Then write it down and build the tasks and milestones from that agreement. Otherwise everyone leaves smiling, production starts, and week five delivers the traditional surprise: three people thought they were approving the homepage. Settle those assumptions in week one, while they are still cheap and easy to fix.

What a kickoff is really for

Too many firms treat kickoff like a welcome call with better lighting. Everyone says hello, the client repeats the goal, the team promises to get moving, and the operating questions remain fuzzy. Friendly is good. Friendly without a shared plan is how drift gets a head start.

A proposal often compresses detail. It describes the shape of the engagement, but not every handoff, approval, or review step. Once the Job moves from sales into delivery, the team needs the working version: what gets produced, how much iteration is included, when the client must respond, and whose decision is final.

By the end of the meeting, both sides should be able to answer one question: what plan are we agreeing to run? If the answers differ, the kickoff is not done yet.

Confirm deliverables and revision rounds out loud

Read the deliverables out loud and ask the client to confirm them. Do not assume that a line in the proposal created the same picture in every head. “Homepage design,” “messaging support,” and “launch assets” can each stretch in six directions once real people start discussing them.

Revision rounds deserve the same treatment. Your team may mean one round of consolidated feedback. The client may mean comments arriving whenever another executive opens the file. Nobody has to be difficult for that arrangement to go sideways. They only need different assumptions.

Walk through each deliverable and the rounds attached to it. Ask whether anything the client expects is missing from the list. If something new appears, good. You found it before production began. That is the same reason a useful project brief works: the work becomes concrete before the team is neck deep in it.

Surface the effort and timeline assumptions

Most kickoff agendas include dates. Fewer explain what makes those dates possible. If the schedule assumes consolidated feedback within two business days, source files by Friday, or no bonus exploration round between concept and approval, say so.

This is not an invitation to parade your internal process in front of the client. It is a plain explanation of the critical path. When the client can see what the timeline depends on, they can help protect it instead of accidentally walking through it with muddy shoes.

Those shared assumptions also make later conversations calmer. If feedback comes late or a new approval layer appears, you can point back to what both sides agreed. Clear timeline and turnaround expectations work better than a surprised email after the deadline has already moved.

Name the client’s decision-makers and approval path

If you lock in only one thing, lock in who decides. Plenty of Jobs slip while the delivery team is doing perfectly good work because nobody knows whose approval counts or how client feedback becomes final.

The day-to-day contact is not always the approver. A founder may weigh in after the second round. Legal may appear near launch as if summoned by a special calendar alert. None of that is unusual. Finding out late is the problem.

Ask who reviews first, who combines comments, who signs off, and how long each review normally takes. Ask whether another stakeholder enters at a particular stage. Then put those answers into the milestones. Hope is lovely, but it is not an approval workflow.

Turn the agreement into tracked tasks and milestones

The agreement has to survive the meeting. Deliverables become tracked work. Revision rounds become explicit steps. Review dates become milestones. Dependencies sit beside the work they affect instead of hiding in somebody’s notes.

This is where a good kickoff often evaporates. The conversation goes well, but nobody translates it into the team’s daily system. The producer remembers one version. The designer remembers another. The client assumes the meeting settled it. Then the workflow carries none of it.

A workflow management system like Net Net gives the team one working picture. If the kickoff established two review rounds, one final approver, and a milestone that depends on receiving copy, those facts should appear where the team plans and delivers the Job.

Write down what is out of scope before work starts

Teams usually list what is included and get quieter around what is not. That hesitation creates very predictable trouble. Out of scope is not rude. It is the edge of the agreement.

A website Job may include design and build but only light copy editing. A brand engagement may include the identity system but not the sales deck. Research may include interviews and synthesis but not a second discovery round. If the boundary feels obvious inside your firm but never reaches the client, it is not a boundary yet.

Writing exclusions down helps both sides plan. When a new request arrives, the team can compare it with the agreed Job and discuss the added effort. That is much easier than inventing a nervous “no” while the request is already sitting in production.

FAQ

Who should be in the kickoff?

Include the people who will do and approve the work on both sides. Bring your delivery lead, not only the person who sold the Job, and ask for the client’s real decision-maker, not only the day-to-day contact. The meeting works when the doers and approvers hear the same agreement.

What is the single most important thing to lock in?

Lock in the approval path. Agree on who reviews, who combines feedback, who has the final say, and how quickly responses come back. Work often waits on sign-off longer than it waits on production, so build those expectations into the plan.

How long should a kickoff take?

Take enough time to leave with a shared plan. For many Jobs that is a focused hour or two. The useful test is not the clock. It is whether both sides agree on deliverables, review rounds, timing assumptions, and who decides.