Why the kickoff matters
The kickoff is the first meeting after the contract is signed, and it sets the tone for everything after. It is where the customer meets the people who will actually deliver, and where the promises made during the sale become a plan.
Customers notice two things in a kickoff. Do the people across the table know what was discussed during the sale, or are they starting from scratch? And does the meeting end with a clear plan, owners, and dates? Getting both right builds confidence that is hard to create later.
Who should attend
Kickoffs fail when the wrong people are in the room, or the right ones are missing.
From the customer:
- the executive sponsor, at least for the first part
- the project lead who will own the rollout day to day
- representatives of the main user groups
- anyone needed for technical setup, such as IT or integration owners
From your side:
- the account executive who ran the sale, to hand over context in front of the customer
- the customer success manager or onboarding lead who will own the relationship
- a technical specialist, if setup involves integration
Finding a time that suits this many people takes planning. See how to schedule a meeting with multiple people.
Before the meeting
- Hand over internally first. The person taking the account should know why the customer bought, what they were promised, who the stakeholders are, and any concerns raised during the sale. Our guide to the sales meeting handoff covers what that note must contain.
- Bring the plan from the sale. If there was a mutual action plan, its final steps are the starting point for onboarding.
- Ask the customer what success looks like in a short call or email before the meeting, so the kickoff confirms rather than discovers.
- Send an agenda with the invitation, and ask whether anything is missing.
A 60-minute agenda
| Minutes | Item | | --- | --- | | 0–10 | Introductions, roles on both sides, and the purpose of the meeting | | 10–20 | Why they bought, and what success looks like, in their words | | 20–35 | The onboarding plan: phases, milestones, and dates | | 35–45 | What we need from them: access, data, people, and decisions | | 45–52 | Risks and constraints: deadlines, holidays, competing projects | | 52–60 | Agree owners, next steps, and how we will communicate |
Keep the sales presentation out of it. The customer has already bought. The meeting agenda builder can turn this into a timed agenda for your own length.
What to agree before you leave
A kickoff should end with decisions, not just introductions. Before the meeting closes, agree:
- the success measures, and how and when you will check them
- the first milestones, with dates and owners on both sides
- who does what, by name
- how you will communicate: a regular check-in, a shared channel, a named escalation contact
- the next meeting, booked before everyone leaves
Write these into the follow-up, not just your notes.
The week after
- Send the summary within a day: success measures, milestones, owners, and the next meeting. Our guide to AI meeting follow-up covers turning notes into a clear summary quickly.
- Complete your own first actions quickly. Early momentum matters, and the first promise you keep sets expectations.
- Set up the regular check-in rhythm, so the relationship does not depend on the customer asking for help. See how often to meet customers.
- Confirm the executive sponsor is still engaged. Send them a short note of their own, not just a copy of the project summary.
CallShark is being built so the context from the sale, who attended, what was promised, and what was agreed, travels with the account into its first meetings as a customer. The product is temporarily down.