How to run a client kickoff meeting for a creative project

Most of the arguments in a creative project are settled, or started, in the first meeting. A kickoff that covers who decides, how many rounds and what happens when a review is late saves weeks later.

6 min read

By · Updated

The short answer

Hold the kickoff after the quote is signed and before any production work. Keep it to 45 minutes with a written agenda: confirm the scope and deliverables, name the decision maker and who else gives notes, walk through the stages and review rounds, agree the dates including the client's review days, list the files and access you need, and agree how you will communicate. Send a written summary the same day and ask for a reply confirming it.

Before the meeting

A kickoff only works if you arrive with the plan already drafted. Prepare three things:

  1. The deliverables list from the signed quote, one line per deliverable.
  2. A draft schedule with every stage and every client review as a dated item.
  3. A list of what you need from the client: files, brand assets, access, references, contacts.

Send the agenda and the draft schedule the day before. Clients who have seen the dates in advance come with the conflicts already spotted ("the board meets on the 14th, can the review move to the 13th?"), and the meeting becomes a decision rather than a discovery.

The agenda

Kickoff: [project], [date], 45 minutes

1. Goals and audience (5 min)
2. Deliverables and what is out of scope (5 min)
3. Who decides, who comments (5 min)
4. Stages and review rounds (10 min)
5. Schedule and review days (10 min)
6. Files, access and assets we need (5 min)
7. How we communicate, and next steps (5 min)

1Goals and audience

Ask what the work is for and who will see it. A product film for a trade show stand is cut differently from one for paid social. An archviz set for planning approval is judged differently from one for sales. The answer often changes small decisions you would otherwise guess at, and it gives you something to point to when a late note contradicts the goal.

2Deliverables and scope

Read the deliverables list from the quote out loud. It sounds pedantic and it is the most useful five minutes of the meeting. "Three exterior stills and one interior, 5000 pixels wide, plus a 30-second flythrough" is a sentence the client can correct now, cheaply. Then say what is not included: "Extra views, additional formats and changes to the design after camera approval are quoted separately." People remember what they heard in the meeting better than what they signed.

3Who decides, who comments

Ask two questions and write the answers on the project:

  • Who gives the final approval at each stage?
  • Who else needs to see the work before that approval?

Then ask for one combined set of notes per round, collected by the decision maker. This one request prevents the most common feedback problem in studio work: three people sending conflicting notes on the same version on the same day. If the client cannot name one decision maker, that is worth knowing now. Plan an extra round, or price one.

4Stages and review rounds

Walk through the stages and what each one locks. For a motion piece: styleframes lock the look, the animatic locks the timing, blocking locks the movement. For archviz: the cameras are approved first, then materials and lighting. Say how many review rounds each stage includes, what a round is (one consolidated list of notes on one version), and what an extra round costs.

Explain that a change to an approved stage is a change to the brief, not another round. Most clients agree readily when it is explained at the start. The same sentence said in week four sounds like an excuse.

5Schedule and review days

Show the draft schedule. Point at each review and say how many working days the client has for it, and what happens if the notes are late: the delivery moves by the same number of days. Ask about holidays, board meetings, launch dates and anything else that blocks their side. Adjust the dates in the meeting if you can.

This is where a timeline view earns its keep. A client who can see that their two-day review sits between your animation and your final render understands why a late review moves the delivery. Creative project timeline template has a layout you can reuse.

6Files, access and assets

List what you need, with a date for each: logo files, fonts, brand guide, CAD or plan files, product samples, scripts, music licences, access to a shared drive. Name who on the client side sends each one. Missing inputs are the most common reason a studio project starts late, and they are rarely chased until they are already late.

7Communication and next steps

Agree three things: where files and notes go (one place, not email plus chat plus a drive), how often you send updates and on which day, and who to call if something urgent comes up. Then read out the next steps with owners and dates. The first one is usually yours: "We send the schedule and this summary today."

The written summary

Send it the same day. Keep it short: deliverables, decision maker, rounds per stage, the schedule with review days, the list of inputs with dates, and the next three steps. Ask the client to reply to confirm. That reply, stored on the project, is the record you will point to if scope or dates are questioned later. The project kickoff email guide has a template for it, and the client onboarding checklist covers the admin around it: contract, deposit and access.

Remote kickoffs

Most small studios run kickoffs on a video call. Share your screen with the deliverables list and the schedule, not a slide deck. Record the call if the client agrees, so the summary can be checked against what was said. Keep the camera on for the first few minutes; it is the first time many clients meet the team, and it makes later calls easier.

Doing this in OIO

OIO is project management for small studios, so the kickoff output goes straight onto the project. The deliverables become tickets with dates on the timeline, client reviews included, so you can share the schedule from the meeting rather than a separate file. The decision maker and the round count are written on the project, where the whole team can read them. Kickoff calls can be recorded with a transcript on paid plans, so what was agreed is written down on the project.

The client gets a client space at a status link with their deadlines and the tickets you share with them. Freelancers joining later get a link to their own ticket with the brief, with no account and no seat. The quote and the deposit invoice come from the same project. More on OIO for agencies.

Questions

What should be on a client kickoff meeting agenda?

Goals and audience, deliverables and what is out of scope, who decides and who comments, stages and review rounds, the schedule with the client's review days, the files and access you need, and how you will communicate.

How long should a kickoff meeting be?

About 45 minutes for most studio projects. Send the agenda and a draft schedule the day before so the meeting is spent deciding, not discovering.

When should the kickoff meeting happen?

After the quote or contract is signed and before any production work starts. Ideally after the deposit is paid, so the schedule you agree is one you can start on.

What do I send after a kickoff meeting?

A short written summary the same day: deliverables, decision maker, rounds per stage, the schedule, the inputs you need with dates and the next steps. Ask the client to reply and confirm it.

Free tools for this

OIO for agencies and studios

More guides