Client Kickoff Meeting Agenda: 8 Timed Items for the First Hour
By Danial Pourgolab · 10 min read · November 2026

The contract is signed, the deposit has cleared, and eight people are on the call. Your team introduces itself, the client's marketing lead shares a mood board nobody had seen before, someone asks whether the blog migration is included, and the hour ends with everyone agreeing it was a great chat. Two weeks later you find out the CEO, who was not on the call, expects a launch date you never agreed to.
That is what happens when a kickoff is run as a polite introduction. Nothing went wrong in the meeting itself. It just never decided anything, and every gap it left open comes back later, when closing it costs real time.
This post gives you a 60-minute agenda with eight timed items. It also covers who to invite, what to send beforehand, and the short list of decisions that must be locked in before anyone opens a design file or writes a line of code. Copy the agenda, adjust the times to your project, and run it the same way every time.
A kickoff is not a discovery call
Most kickoffs go wrong because they try to do two jobs at once. Discovery happens before the contract. You are working out what the client needs and whether you are the right agency to build it. The kickoff happens after the contract. The scope is agreed on paper, and the job of the meeting is to make sure both sides understand that agreement the same way, then attach owners and dates to it.
If you are still uncovering basic requirements at kickoff, the problem started earlier. Our guide to running a client discovery call that surfaces real requirements covers that stage. The kickoff assumes discovery is done and turns its output into commitments.
That distinction changes the tone of the meeting. You are not asking open questions and seeing where they lead. You are reading back what was agreed, checking it out loud, and closing gaps while the people who can close them are in the room.
Who to invite
Keep the invite list small enough that everyone speaks. A useful rule: anyone who will approve, block or do the work in the first month should be there. Anyone who only wants to stay informed can read the recap.
- 1The client decision-maker. This is the person who can say yes to scope, budget and dates. If they cannot attend, move the meeting. A kickoff without the final approver produces agreements that can be overturned by email a week later.
- 2The day-to-day contact. This person will answer your questions, chase their colleagues for content and send feedback. They need to hear the plan directly, not in a forwarded summary.
- 3Every other approver. If legal, brand or an internal IT team has to sign anything off, find out now. Invite a representative, or at least name them in the meeting. An approver who first appears in week six can undo a month of work.
- 4Your project or account lead. They run the meeting, own the agenda and keep the clock. On a small team this is often the owner, which is fine, as long as they are not also taking notes.
- 5Your lead practitioner. This is the designer, developer or strategist who will do the work. Technical constraints come up now instead of in the first review, and they hear the client's priorities in the client's own words, which no handover note fully captures.
- 6A dedicated note-taker. This should be someone other than the facilitator. Their only job is to capture decisions, owners and dates as they are spoken.
What to send beforehand
Send a short pre-read two or three working days before the call. The goal is that nobody hears the scope for the first time in the meeting. When people read the statement of work live during a kickoff, the meeting tends to turn into a renegotiation.
- 1The agenda, with times. Seeing that scope gets ten minutes and introductions get five tells the client this is a working session, not a social one.
- 2A one-page scope summary. Include what is in scope, what is out of scope and the key assumptions, taken from the signed proposal or statement of work. Write it in plain language, not contract language.
- 3A draft milestone plan. List the deliverables in order with proposed dates, and mark the client inputs each date depends on.
- 4The open questions list. List every unanswered question from discovery, each with a suggested owner on the client side. This is often the most useful page in the pack, because it shows the client exactly what is blocking you.
- 5An access and assets request. List the logins, brand files, existing content and analytics access you need, each with the date you need it by.
Getting real answers to those open questions before the call is where the manual process usually breaks. If you are gathering that input through a static tool like Google Forms, expect thin answers to the questions that matter most. A form cannot ask a follow-up question when the client writes "modern and clean" and moves on.
This is the gap ReqBrief was built to close. It interviews your client one question at a time before the kickoff, follows up on vague answers, and turns what they say into a structured brief. The meeting then starts from a written record instead of a blank page.
The 60-minute kickoff agenda
There are eight items in sixty minutes. The times are deliberately tight. If an item overruns, park the detail, note an owner and move on. A kickoff that covers all eight items briefly is better than one that spends forty minutes on the homepage.
- 1Introductions and roles (5 min, starts 0:00). Each person gives their name, their role on this project and what they will be responsible for. Skip the company history. The point is that the client leaves knowing who to ask about what, and your team leaves knowing who signs off.
- 2Goals and success measures (10 min, starts 0:05). Ask the decision-maker to say, in their own words, why this project exists and how they will judge it in six months. Write the answer down word for word. "More enquiries from the contact page" is a measure you can design for. "A fresh look" is not, so ask what would make the fresh look count as a success.
- 3Scope read-back (10 min, starts 0:15). Walk through the one-page summary: what is in, what is out, and what you have assumed. Read the out-of-scope list out loud. It feels awkward, but this is often the most valuable minute of the meeting, because it is where someone says "oh, we thought the blog migration was included" while the gap is still cheap to resolve.
- 4Deliverables and milestones (8 min, starts 0:25). Show the milestone plan: what gets delivered, in what order and on which dates. Tie each date to a client dependency where one exists. For example, the first design review depends on brand files arriving by a stated day.
- 5Owners and approvals (7 min, starts 0:33). Confirm who gives feedback, who gives final approval and how many rounds of revisions each deliverable includes. Agree a feedback window, such as three working days per review, and what happens to the schedule if it is missed.
- 6Communication rhythm (5 min, starts 0:40). Choose the channels and the cadence: where questions go, how often status updates arrive and when the regular check-in happens. One channel for decisions works better than three, because decisions scattered across email, chat and calls are hard to find later.
- 7Risks, dependencies and access (8 min, starts 0:45). Ask both sides what could stop this project from hitting its dates. Typical answers are a content owner going on holiday, a third-party integration with no documentation, or a legal review with an unknown turnaround. Note each risk with an owner. Then go through the access list from the pre-read and put dates against anything still missing.
- 8Recap and next steps (7 min, starts 0:53). The note-taker reads back every decision, owner and date captured during the hour. Anyone who disagrees says so now. Close by naming the next three actions, who owns each one and when they are due, and tell everyone when the recap email will arrive.
How to run the scope read-back without a fight
Item three is the one owners dread, because it is where expectation gaps come out. That is exactly why it belongs in the kickoff. A disagreement about the blog migration takes a five-minute conversation to settle today. The same disagreement in week eight means a rebuild, a discount or a strained relationship.
Frame it as a check, not a defence. You might say: "Before we start, I want to read back what we agreed so we are building the same thing. Stop me if anything sounds different from what you expected." Then read it slowly.
When something does not match, do not settle it on the spot unless it is trivial. Note it, name an owner and agree a date to resolve it. If the answer turns out to be extra work, it goes through your change process instead of quietly joining the plan.
If you do not have a change process yet, a simple change request template gives the client a clear, non-confrontational way to ask for more, and gives you a record of what was added and what it cost.
The decisions to lock in before any work starts
You can adapt the agenda however you like. Just do not end the call until each of these is either settled or assigned to a named owner with a deadline.
- 1The success measure. One or two outcomes, in the client's words, that the project will be judged on.
- 2The final approver. One name. Not a committee, and not "the team".
- 3The in-scope and out-of-scope list. Read back and confirmed, with any disputed items logged as open questions with owners.
- 4The first milestone date. Include the client inputs it depends on and the day each input is due.
- 5The feedback window and revision rounds. With these agreed, a slow review moves the schedule instead of eating your margin.
- 6The change process. How new requests are raised, estimated and approved, and who on the client side can approve them.
- 7The decision channel. The one place where decisions are recorded, so nobody has to search three inboxes to find out what was agreed.
Five ways kickoffs go wrong
- 1Turning it into a pitch. The client has already bought. A long credentials deck uses up the minutes you need for the scope read-back.
- 2Doing design critique live. Someone shares a competitor's site and half the hour disappears. Capture the reference, name it as an input and schedule a separate creative session.
- 3Running it without the decision-maker. Everything agreed becomes provisional. Reschedule instead of hoping the summary gets forwarded and read.
- 4Leaving the notes to the facilitator. Nobody can run a meeting and record it accurately at the same time. Decisions get lost in the gap.
- 5Ending without dates. "We will get those files over soon" is not a date. Ask for the day, write it down and read it back.
What to do after the call
Send the recap the same working day, while everyone remembers the call the same way. Keep it short: decisions, owners, dates, open questions and the next check-in. Ask the client to reply if anything is wrong, and say that if you hear nothing by a stated date, the recap stands.
Then update your working documents so the recap is not the only record. That means the brief, the milestone plan and the open questions list. If your project brief is still the version written for the proposal, update it now, because the kickoff will have changed or sharpened at least part of it.
The kickoff is one step in a longer handover from signed contract to first deliverable. Our client onboarding checklist for agencies sets out the steps around it, from collecting access to confirming the first review.
Run this agenda the same way on every project and it stops feeling like a meeting you have to get through. It becomes a process your team can rely on. A kickoff that ends with confirmed scope, named owners and real dates shows the client that the next few months will be well organised. It also leaves you with a written record to point to when someone asks, in week six, whether the blog was included.
ReqBrief interviews your client before the kickoff and hands you a structured brief, so the hour goes on decisions instead of first answers. Try it on your next project.
Try ReqBrief free →Frequently asked questions
What should be on a client kickoff meeting agenda?
A practical kickoff agenda covers eight items: introductions and roles, the project goals and how success will be measured, a read-back of what is in and out of scope, deliverables and milestone dates, who gives feedback and final approval, how the two teams will communicate, risks and dependencies including access to accounts and assets, and a closing recap of every decision with owners and dates. Timed into a single hour, that works out at roughly five to ten minutes per item.
How long should a client kickoff meeting be?
For most agency projects, 60 minutes is enough, as long as the client received a pre-read beforehand with the agenda, a one-page scope summary and a list of open questions. Larger projects with several stakeholder groups may need 90 minutes or a second session. Even then, it usually works better to keep the kickoff to an hour and schedule separate working sessions for creative direction or technical detail.
Who should attend a client kickoff meeting?
On the client side, invite the decision-maker who can approve scope, budget and dates, the day-to-day contact, and any other approvers such as legal, brand or IT. On the agency side, invite the project or account lead who runs the meeting, the lead practitioner who will do the work, and a separate note-taker. Keep the list small enough that everyone speaks, and send the recap to anyone else who needs to stay informed.
What is the difference between a discovery call and a kickoff meeting?
A discovery call happens before the contract is signed. Its purpose is to understand what the client needs and whether the project is a good fit. A kickoff meeting happens after signing. Its purpose is to confirm that both sides understand the agreed scope in the same way, then assign owners and dates to it. If basic requirements are still being uncovered at kickoff, discovery was not finished.