A client kickoff meeting is the first working session after the contract is signed. Its job is to settle what the agency will deliver, who decides, what the client owes the team and what happens in the first two weeks. The agenda exists to leave with written owners, not to present slides.
This guide is a template drawn from standard agency practice. The timings and examples are illustrative; adapt them to the project and the expectations agreed with the client.
Before the meeting
Read the signed scope, the intake form and the sales notes. Ask the client to send brand assets and access through approved channels before the call, so the meeting is not spent collecting links.
Invite only people who own a decision or a workstream. If the contract contains a fixed launch date, identify the dependencies that could make it slip and put them on the agenda.
Send the agenda in advance with one sentence on what each attendee needs to decide.
Copyable 45-minute agenda
| Time | Topic | Decision to capture |
|---|---|---|
| 0–5 min | Introductions and roles | Main contacts and final approver |
| 5–15 min | Goals and audience | Priority outcome and how it will be judged |
| 15–25 min | Scope and deliverables | What the team will produce, and what is excluded |
| 25–33 min | Access and client inputs | Owners and due dates |
| 33–40 min | Milestones and reviews | Review channel and response expectations |
| 40–45 min | Risks and next steps | First action for each side |
Do not use the whole call to present slides. Reserve time for the client's questions and write down any disagreement with the signed scope for follow-up.
If the project is large, split the session: a 30-minute scope and decisions meeting, then a separate working session for access and tools. A single 90-minute call with ten people rarely produces clear owners.
Capture decisions, not a transcript
Project and date: [Name, date, time zone]
Attendees: [Name and role]
Primary goal: [One sentence]
Success measure: [Metric, baseline and source if available]
Final approver: [Name and backup]
Agreed deliverables: [List with links to the scope]
Open risks: [Risk, owner, next check date]
| Decision or action | Owner | Due | Status |
|---|---|---|---|
| [Item] | [Name] | [Date] | Open or closed |
A transcript records what people said; a decision log records what the project will do. Keep the log short enough that the client will read it.
Send the recap within one working day
Send the notes while the conversation is fresh and ask the client to correct any material misunderstanding. Include the project workspace link, the first requested input and the date of the next checkpoint.
The recap should answer five questions:
- What did we agree the project will achieve?
- Who approves the work?
- What does the client need to supply, and by when?
- What is the first deliverable and its review date?
- What is still unresolved, and who owns it?
If a new request emerged, describe its scope impact separately before scheduling it. The retainer scope template has a change log you can reuse.
When the meeting reveals a scope disagreement
Stop and name the difference. Confirm what the signed agreement says, record the client's expectation and agree who will resolve it and by when. Do not settle a commercial change in the meeting without the person who can approve it.
If the disagreement is small, note it as an assumption to confirm in writing. If it changes deliverables, dates or fees, treat it as a change request rather than a misunderstanding.
Make the meeting work remotely
- Ask attendees to join from a device where they can open the project workspace.
- Share the agenda and decision log on screen, not just in chat.
- Call on the client approver by name when a decision is due.
- End two minutes early to confirm owners aloud.
Remote kickoffs fail in the same way as in-person ones: too much presentation, too few decisions.
Frequently asked questions
What should a client kickoff meeting cover?
Roles and the final approver, the priority outcome, the agreed deliverables and exclusions, client inputs and due dates, review cadence and the first actions for each side.
How long should a kickoff meeting be?
Forty-five minutes is enough for a small project if the agenda is sent in advance and the scope is already signed. Larger projects need a second working session rather than a longer presentation.
Who should attend?
The client decision-maker, the person who will supply inputs and the agency owner of delivery. Add specialists only for the part of the agenda that needs them.
What should we send afterwards?
A short recap with the decisions, owners, dates, open risks and the next checkpoint, sent within one working day and stored in the project record.
What if the client has not completed the questionnaire?
Use the kickoff to fill the gaps that block the first deliverable, not to answer every question. Assign the rest with owners and dates in the recap.
Should we record the meeting?
Only with everyone's agreement and a stated purpose. A recording is not a substitute for a decision log, and it creates retention and access questions you should settle first.
Related reading
- Client onboarding questionnaire for the answers to collect before kickoff.
- Client onboarding checklist for the steps around the meeting.
- Client communication plan for the cadence you agree here.
- Client portal setup checklist if the project workspace is new.
- Agency retainer scope template for handling new requests after kickoff.
- Client onboarding hub for the full onboarding path.
Next step: copy the agenda and decision log into the project, send the agenda with the scope link, and book 15 minutes after the call to write the recap while the decisions are still fresh.