A software agency's account lead once told us the kickoff call for a $70,000 engagement ran 90 minutes, had four slides of "About Us," and ended without anyone confirming who the client should email if a deliverable slipped. Three weeks later, the client's ops director called the agency's CEO directly, furious, because nobody on her side knew that was not how escalation was supposed to work. Nothing about the project had gone wrong yet. The kickoff had.
In this guide
What has to happen in the first 30 minutes An agenda that survives contact with a real client Who belongs in the room, and who doesn't What you send within 24 hours Frequently asked questions
What Has to Happen in the First 30 Minutes
Clients don't remember a kickoff because it was polished. They remember it because it answered five things clearly: who decides what, how often they'll hear from you, when the first real deliverable lands, what "done" looks like for phase one, and who to call when something goes sideways. That's it. If your kickoff covers those five and nothing else, it will outperform a 40-slide deck every time.
Most teams do the opposite. They spend the first 20 to 25 minutes on company history, team bios, and a tools walkthrough, then rush the actual decisions in the last 10 minutes while people are checking their calendars for the next meeting. By the time the call ends, the client remembers a logo animation and forgets who their point of contact is. Flip the order. Decisions first, context second, and cut the context ruthlessly if you're running short on time.
A 12-person IT services shop we talked to changed exactly one thing: they moved "who owns what" to minute five instead of minute 50. Their client satisfaction scores on kickoff calls (measured by a one-question post-call survey) went from "fine" to consistently rated as the best part of onboarding. Nothing else about their process changed.
An Agenda That Survives Contact With a Real Client
Write the agenda in minutes, not bullet points, and send it 24 hours ahead so nobody's surprised. A 60-minute version that works for most consulting and agency engagements looks like this:
- Minutes 0-5, quick round of names and roles, not bios, just who's who and what they own on each side
- Minutes 5-15, confirm scope and success criteria out loud, read the statement of work back in plain language and ask "did we miss anything," because this is the last cheap moment to catch a misunderstanding
- Minutes 15-30, walk the timeline and the first milestone, name the actual date the client will see something, not a phase label
- Minutes 30-45, set communication rules, standing meeting day and time, response-time expectations, and the exact channel for status updates versus urgent issues
- Minutes 45-60, open questions and next steps, list who owes what by when before anyone logs off
For software teams, this is also the moment kickoff hands off to sprint zero. If your delivery model runs on sprints, the kickoff should end with a date for the first planning session, not a vague "we'll be in touch." Our sprint planning guide covers how to structure that first sprint so it inherits a clear scope instead of the vague promises that tend to leak out of a rushed kickoff.
Who Belongs in the Room, and Who Doesn't
Eight people on a kickoff call is a meeting where six of them multitask. Invite the client's actual decision-maker, the day-to-day contact who will answer your Slack messages, and one technical or subject-matter person if the project needs it. That's three people, occasionally four. Everyone else gets the recap.
On your side, bring whoever will actually be doing the work, not just the salesperson who closed the deal. Clients remember being handed off from an enthusiastic account exec to a delivery team they've never met, and it reads as a bait and switch even when it isn't one. If the person running week-one tasks wasn't in the room for the promises made in week zero, you've already created a gap.
The bigger the invite list, the fewer decisions actually get made. A kickoff with 10 attendees tends to produce a status update, not a plan, because nobody wants to make a call in front of a crowd. Keep the room small, and push everyone else to a written recap they can react to on their own time.
What You Send Within 24 Hours
The meeting matters less than what happens right after it. Send a written recap within a day, not a week, while the conversation is still fresh enough that people will actually read it and correct anything wrong. It should list decisions made, owners, dates, and the agreed communication cadence, in that order, and nothing else. Skip the pleasantries. A client scanning it on their phone should get the whole picture in under two minutes.
This is also the moment to be direct about budget guardrails. If scope changes came up during the call, even casually, restate what's in scope now and what would trigger a change order. Clients who haven't seen how your firm structures engagements, and haven't looked at your pricing and plan structure, are the ones most likely to assume "a quick addition" is free. Kickoff, and the recap that follows it, is the cheapest place to set that expectation. It gets far more expensive to have that conversation in week six.
If the same system that ran your kickoff checklist also holds the project plan, the time being logged against it, and the invoice that eventually goes out, that recap stops being a PDF that quietly disappears into someone's inbox. It becomes the actual record the project runs on. That's the specific thing Autovella's CRM and project features are built to do: keep the commitments made on day one visible on day ninety, instead of relying on everyone remembering an email from March.
See how kickoff commitments stay visible through delivery
Get a live walkthrough of how Autovella connects CRM, projects, time tracking, and invoicing so nothing from day one gets lost by day ninety.
Frequently asked
60 minutes for most projects, 90 for anything with more than four workstreams or three client-side stakeholders. Past 90 minutes, attention drops fast and the second half of the meeting produces worse decisions than the first. If your agenda doesn't fit in 60 to 90 minutes, that's usually a sign you're trying to plan the whole project instead of just launching it.
Spending the first 20 minutes on introductions and a company-history slide deck, then rushing the five decisions that actually mattered, decision rights, communication cadence, milestone dates, escalation path, and definition of done for phase one. Clients forget slide decks. They remember whether they walked out knowing who to call when something goes wrong.
The person who will actually be running the project day to day, usually the PM or delivery lead, not the account exec who closed the deal. The recap is the client's first impression of who they'll really be working with, and having the day-to-day owner send it signals that ownership clearly instead of leaving it ambiguous for the first two weeks.