A kickoff meeting is the one call where everyone agrees what the project is. Skipped or rushed, it causes the arguments that show up six weeks later: "I thought that was included." Thirty minutes is enough if you have an agenda and send it ahead.

Send the agenda a day before

Send the list below with the call link and ask for one thing: the name of everyone who will approve work. People attend better prepared when they know what will be asked. If you sent a welcome email, this is the second message in the sequence.

The 30 minute agenda

  1. Goals (5 minutes). "What will make this a success for you in 90 days?" Write the answer down in their words.
  2. Scope (8 minutes). Read the scope aloud, what is included and what is not. Ask: "Is anything missing from this list?" This is where surprises surface cheaply.
  3. Who decides (4 minutes). Who approves each stage, and how quickly can they respond? A slow approver is the biggest hidden risk in most projects.
  4. Timeline (5 minutes). Dates for drafts, feedback and final delivery. Add the client's own holidays and busy weeks.
  5. What you need (4 minutes). Logins, files, content, a point of contact.
  6. Risks and next steps (4 minutes). Ask: "What could slow us down?" Then restate the next three actions with names and dates.

Questions worth asking

  • What have you tried before, and what went wrong?
  • Who else will have an opinion once they see it?
  • What does a bad outcome look like?
  • How do you prefer to get updates: email, a call or a shared board?

The third question is the best. People rarely say what they fear unless asked.

Write it up the same day

Subject: Kickoff notes and next steps

Hi Rosa, thank you for the time today. Here is what we agreed.
Goal: 40 online bookings a month by March.
Scope: five pages, the booking form, one round of changes on each page. Not included: new photography.
Approver: you, with 48 hours for feedback.
Dates: first draft Tuesday the 14th, final by the 28th.
Your next steps: logins and photos by Wednesday. Mine: the draft. Reply if anything above is wrong. Tom

A written recap is your protection. If the scope changes later, point to it and agree a change in writing; see email to a client about scope creep.

Handling a client who wants to skip it

Some clients say they are too busy for a kickoff and want you to just start. Offer 15 minutes and explain that it saves them time later: you will not have to ask them the same questions by email over three weeks. If they still decline, send the written recap anyway and ask them to reply "confirmed." That one reply gives you the same protection as a meeting. Keep a record of who said what and when, and do not start work on anything that depends on an answer you have not received.

Schedule the next check-in before the call ends. A recurring 15 minute slot every week or two, with a fixed agenda (done, next, blocked), keeps a project from drifting. Put it in both calendars while everyone is still on the line, because the best intentions to find a time later rarely survive a busy week.

For a short job

A project of a week or two can use 15 minutes: goal, scope, dates. Do not skip it, shrink it.

Run the checklist, not memory

Keep the agenda in a document and use it every time. Use a client onboarding checklist for the rest of the first week.

A kickoff needs a client first. Rocketship finds buyers, emails them from your own Gmail, follows up and books the meeting. Try it for 7 days, card required to begin.