How to Run a Customer Kickoff Call (Agenda Included)

Here is how I run a customer kickoff call.

In short: A customer kickoff call is the first structured meeting between your onboarding team and the customer's project team after signature, and it should fit in 60 minutes. It should end with three things agreed in writing: the customer's success criteria, a dated first value milestone and named owners on both sides. Hold it soon after signature and track kickoff lag = kickoff date − contract signature date.

Start from a pre-filled customer success plan template, so the call edits a draft instead of starting from a blank page.

This is Part 3 of The Customer Onboarding Playbook. Part 2 defined seven customer onboarding metrics. This part covers the meeting that sets most of them in motion.

What is a customer kickoff call for?

Skip the second demo. Use the hour to turn the reasons the customer bought into a shared, dated plan. A good kickoff produces:

• Success criteria in the customer's own words.
• A first value milestone with a date, the one you will measure time to value against.
• Named owners on both sides: sponsor, project lead and technical contact.
• Risks: access, data and approvals that could slow things down.

What should you prepare before the kickoff call?

Most of the result is decided before anyone joins.

1. Read the sales handoff. Note the goals, people and promises.
2. Draft the success plan. Pre-fill the customer success plan with what you already know.
3. Confirm attendees. Ask for the sponsor for at least the first 15 minutes.
4. Send technical prerequisites with the invitation. SSO details, credentials and sample data requests, so setup can start right after the call.
5. Share the agenda with time boxes, at least a day ahead.

What is a good customer kickoff call agenda?

Keep the order: goals before the plan, the plan before next steps.

Time	Block	Outcome
0–5 min	Introductions and roles	Everyone knows who owns what
5–20 min	Goals and why they bought	Goals restated in their words
20–30 min	Success criteria and first milestone	Milestone and date agreed
30–45 min	Onboarding plan	Dated milestones with owners
45–50 min	Risks and prerequisites	Blockers listed with owners
50–60 min	Next steps and check-in rhythm	Actions, dates, a recurring call

Agenda time boxes

Where the 60 minutes go

Clarivoxx analysis

0 min8 min15 min

Introductions
5 min

Customer goals
15 min

Success criteria
10 min

Onboarding plan
15 min

Risks
5 min

Next steps
10 min

40 of 60 minutes spent on goals, criteria and the planShare of call on planning = (15 + 10 + 15) ÷ 60 × 100 = 67%

Keep the customer talking in the goals block; your team leads the plan block.

Forty of the 60 minutes go to goals, criteria and the plan. Some tips for those blocks:

• Goals: ask "What would make this a success for your team by the end of the quarter?" and write the answer down word for word.
• Success criteria: push for something you can see. "Better reporting" becomes "the weekly operations report built in the product and sent to 15 managers."
• Risks: ask directly, "What could slow this down on your side?"

What mistakes should you avoid on a kickoff call?

• Talking about yourself. Company history and roadmap slides eat the goals block.
• Vague milestones. "Go live in Q1" is not a milestone. A named outcome with a date is.
• A late kickoff. Every day between signature and kickoff adds to time to value.
• No sponsor. Without the person who signed, the goals you hear are the project team's, not the business's.

How do you measure kickoff quality?

Kickoff lag (business days) = kickoff date − contract signature date
Kickoff on-time rate        = kickoffs held within target lag ÷ total kickoffs × 100
Recap completeness         = recaps with a dated first value milestone ÷ total kickoffs × 100

target lag = the maximum number of business days you allow between signature and kickoff

Say a team ran 25 kickoffs in a quarter with a target lag of 7 business days. If 18 were on time, the on-time rate is 18 ÷ 25 × 100 = 72%. If 21 of the 25 recaps included a dated first value milestone, recap completeness is 21 ÷ 25 × 100 = 84%.

Kickoff quality

One quarter of kickoffs in four numbers

Clarivoxx analysis

Kickoffs held25

Median kickoff lag6 business days

Kickoff on-time rate72%

Recaps with dated milestone84%

The formulas

Kickoff lag = kickoff date − contract signature date. Kickoff on-time rate = kickoffs within target lag ÷ total kickoffs × 100 = 18 ÷ 25 = 72%. Recap completeness = 21 ÷ 25 × 100 = 84%.

A late or incomplete kickoff tends to show up later as a slipped milestone and a lower completion rate, two of the onboarding KPIs from Part 2. The customer onboarding checklist puts the kickoff and its follow-ups in one dated list.

What goes in the kickoff recap?

Within one business day, send a short recap and update the shared plan with:

• The success criteria and first value milestone, in the customer's words.
• The dated plan with owners on both sides.
• Open risks with owners and due dates.

24-hour recap

What the follow-up must lock in

Clarivoxx analysis

Success criteria agreed on the callWritten in the customer's words in the success plan within 1 business dayCSMOwner assigned

First value milestone setMilestone and target date confirmed by the customer project leadCSM and customer project leadOwner assigned

Technical prerequisites openEach prerequisite has an owner and due dateOnboarding or solutions engineerOwner assigned

No meeting rhythm yetFirst recurring check-in on both calendarsCSMOwner assigned

Ask the project lead to reply and confirm or correct it. That one reply turns your plan into a shared commitment.

What I've seen in practice

The worst kickoff I ran was early in my career. I spent forty minutes on slides about our company and our roadmap, and the partner's project lead barely spoke. Two weeks later we found out their real goal was faster refund handling for one market, which none of my slides covered. Since then I talk less and write down more.

With partners in MENA, I learned to ask about holiday periods and approval chains in the risks block. Those two answers explained most of our later delays, and asking on day one let us plan around them instead of discovering them in week six.

A kickoff dashboard for each quarter

I review kickoffs once a quarter with these five rows. This quarter's numbers come from the example above.

Metric	Target	This quarter	Last quarter	Change
Median kickoff lag (business days)	7	6	8	−2
Kickoff on-time rate	90%	72%	64%	+8 pts
Recaps with dated milestone	95%	84%	77%	+7 pts
Recap sent within 1 day	100%	88%	82%	+6 pts
Sponsor attended	80%	68%	59%	+9 pts

On-time rate is the weakest row. Seven of 25 kickoffs missed the 7-day target even though the median is fine, so I look at those seven by name, not at the average.

What to do this week

Check your last five kickoffs: how many met your target lag, and how many recaps had a dated milestone? Then rewrite your agenda so the first 20 minutes belong to the customer's goals.

Frequently asked questions

Who should attend a customer kickoff call?

On the customer side: the sponsor, the project lead and a technical contact. On your side: the CSM or onboarding lead, and a solutions engineer if setup is technical. The account executive can join for introductions.

How soon after signing should the kickoff happen?

Within a week if you can. I set a target lag in business days and track every kickoff against it, because the gap after signature is often the easiest delay to remove.

Should I demo the product at the kickoff?

Only a short view tied to the first milestone. The customer has already seen the demo. The hour is for goals, the plan and owners.

How long should a kickoff call be?

Sixty minutes works for most mid-market accounts. Large enterprise projects with many teams may need a longer session or a second technical call.

Sources

• Project kickoff, Atlassian Team Playbook: preparing and running a kickoff, with a sample agenda.
• Sales to customer success handoff, Rocketlane: how the handoff leads into the customer kickoff, with time-to-kickoff as a KPI.