A SaaS customer implementation kickoff should end with written agreement on who decides what on each side, what success means, what is in and out of scope, what the customer must provide and by when, and how weekly updates and escalations will run. The agenda below is built to produce those agreements. It comes with a decision-rights table, a customer dependency list, a kickoff record to fill in during the meeting, and a follow-up email you can send the same day.
Common kickoff templates, such as Asana's kickoff meeting template and Craft's client kickoff agenda, cover introductions, goals, roles, timeline, and next steps. The part that decides whether the rollout keeps moving is the governance set in this meeting: who on the customer side can approve what, how quickly they answer, and what the weekly update looks like before the first one goes out.
What should a SaaS implementation kickoff agenda include?
A SaaS implementation kickoff agenda should include introductions with decision rights, success criteria carried over from sales, scope with explicit exclusions, technical readiness, milestones with owners, risks and dependencies, what the customer must provide, and the update and escalation rules. Each item should end in a recorded agreement, not just a discussion.
Copyable agenda
| Time | Item | Lead | Output you leave with |
|---|---|---|---|
| [min] | Introductions, roles, and decision rights | [Vendor lead] | Completed decision-rights table |
| [min] | Why the customer bought: goals and success criteria from sales | [Customer sponsor] | Success criteria the sponsor confirms in their own words |
| [min] | Scope and explicit exclusions | [Vendor lead] | In-scope and out-of-scope list, read aloud |
| [min] | Technical readiness: data, integrations, SSO and access, security review, environments | [Vendor technical lead] + [Customer IT lead] | Owner and date for each readiness item |
| [min] | Milestones and owners through go-live | [Vendor lead] | Milestone list with a named owner on each, and a written go-live definition |
| [min] | Risks and dependencies | [Vendor lead] | First entries in the risk and dependency log |
| [min] | What we need from you | [Vendor lead] | Customer dependency list with owners and dates |
| [min] | Weekly update format and escalation rules | [Vendor lead] + [Customer sponsor] | Agreed update day, format, response window, and escalation path |
| [min] | Recap of decisions and next steps | [Vendor lead] | Read-back of every agreement made in the meeting |
How to time it. Asana's sample kickoff agenda runs 60 minutes, and its guidance puts kickoff meetings at 30 to 90 minutes, which is a sensible frame for most customer rollouts. Rocketlane's onboarding kickoff agenda runs 115 minutes and includes a block for rules of engagement and another for the steering committee. Set your own timings by deal size and fill them into the template, weighting the rows like this:
- Protect the decision-rights, need-from-you, and recap rows. They produce the agreements you will rely on later.
- Give technical readiness the largest block when the rollout involves integrations or data migration.
- When time is short, shorten scope and risk first, and finish the detail in a follow-up working session.
In the milestones block, define go-live in the customer's terms and write it down: "Go-live means [condition], confirmed by [owner]." For the checks that lead up to that point, a go-live readiness checklist such as ALA Consulting's is a useful next step.
Run the recap even when time is short. Reading the agreements back while everyone is still in the room is what turns a pleasant meeting into a working plan.
What should you prepare before the kickoff meeting?
Before the kickoff, collect the sales handoff, map the customer's stakeholders, and hold a short internal pre-kickoff so your own team agrees on scope and risks. Send a pre-read with the draft agenda, draft decision-rights table, and draft dependency list so the customer arrives ready to confirm, not to start from blank.
Rocketlane lists what to get from sales (goals and objectives, stated functional requirements, and the value or ROI metrics highlighted to the customer) and from sales engineering (new features or functionality, known constraints, and past issues). The same guide suggests mapping the customer team, including the sponsor, business owner, project manager, IT, infosec, and architect. Kipwise recommends scheduling the kickoff as soon as the deal closes and inviting someone from the customer's IT team if setup needs their help.
Pre-kickoff checklist:
- Sales handoff notes reviewed, with any promise you cannot deliver flagged for the internal meeting
- Stakeholder map drafted, with gaps marked as questions for the customer
- Draft scope with exclusions written out in plain language
- Draft decision-rights table and dependency list attached to the invite
- Sponsor attendance confirmed, not assumed
How do you set decision rights with the customer at kickoff?
Set decision rights at kickoff by walking through the decisions the project will need and naming one customer owner for each, plus how fast they will answer. Fill the table live on screen. Where the customer cannot name an owner yet, record that as an open item with a date, not a blank.
Decision-rights table
| Decision | Customer owner | Vendor owner | How it is given | Answer within |
|---|---|---|---|---|
| Scope changes | [Name, role] | [Name, role] | [Email / meeting] | [Agreed window] |
| Configuration sign-off | [Name, role] | [Name, role] | [Method] | [Agreed window] |
| Data mapping approval | [Name, role] | [Name, role] | [Method] | [Agreed window] |
| Security review approval | [Name, role] | [Name, role] | [Method] | [Agreed window] |
| User acceptance sign-off | [Name, role] | [Name, role] | [Method] | [Agreed window] |
| Go-live approval | [Name, role] | [Name, role] | [Method] | [Agreed window] |
Wording to use in the meeting: "For each of these, we need one person who can say yes. If that person is away, who answers for them?" Ask for the backup name too. Without a backup name, a decision can wait until the owner is back.
What should the customer provide in the 'need from you' list?
The 'need from you' list names every input the rollout depends on from the customer: data, access, approvals, people's time, and technical setup. Each line gets a customer owner and a date. Agreeing the list at kickoff lets you show later, with evidence, where a delay started.
Technical readiness deserves its own lines. Kipwise's kickoff template mentions IT only as someone to invite if setup needs their help, so cover the technical work item by item:
- Data migration: source systems, export owner, data sample by [date], cutover approach
- Integrations: systems to connect, API credentials or admin contact, test environment access
- SSO and user access: identity provider admin, user list, roles and permissions
- Security and IT review: questionnaire owner, data processing agreement, allowlisting or sending domain setup
- Environments: sandbox or test access, who can approve moves to production
- People's time: subject-matter experts for configuration workshops and testers for acceptance
Phrase it as a shared list, not a demand: "These are the things we can't do without you. Let's agree who owns each one and when it's realistic."
Keep the risks and dependencies you raise here in one place after the meeting. A RAID log works well for that; ProjectManager's RAID log template is one starting point.
How do you agree the weekly update and escalation rules?
Agree the weekly update by fixing its day, recipients, and format at kickoff, then show the customer a sample. Agree escalation by naming the trigger, the path, and the response window. Settling both before work starts means the first status report and the first escalation feel expected rather than alarming.
Weekly update format to show at kickoff
Subject: [Customer] implementation update, week of [date]
Overall status: [On track / At risk / Off track], because [one-line reason] Done this week: [deliverable or milestone, with evidence] Next week: [planned work] Needed from you: [decision, review, or help], owner [name], by [date] Risks: [new or changed risk and what we're doing about it]
For more on structuring the weekly report itself, see Workhint's weekly status report template.
Escalation rule to agree aloud
"If a decision or input on the need-from-you list is past its date and blocks the next milestone, [vendor lead] raises it with [customer project manager] first. If it is still open after [agreed window], it goes to [customer sponsor] with the options and the effect on the go-live date."
Write this rule into the follow-up email so it is on record. Unblockd sends asks to the sponsor by email with one-tap answers (no account), or answered by replying to the email.
How should you record what the kickoff agreed?
Fill in this kickoff record during the meeting, one line per agenda item, so each agreement is written down while the people who made it are still in the room. The record holds success criteria, scope, decision owners, readiness dates, milestones, risks, and the update rule, and it becomes the body of your follow-up email.
Kickoff record: [Customer] x [Your company], [date]
Success criteria (confirmed by [sponsor name]): [criterion in the customer's words], measured by [measure], checked at [milestone]. In scope: [module or workflow], [module or workflow]. Out of scope: [item], [item]; changes go through [scope owner]. Decision owners: see table; backup for [sponsor name] is [backup name]. Readiness: data sample from [customer owner] by [date]; SSO admin [name] by [date]; security questionnaire returned by [date]. Milestones: [milestone] owned by [name], due [date]; go-live target [date]. Go-live means: [condition], confirmed by [owner]. Risks: [risk], owner [name], next step [action]. Updates: every [day] to [recipients]; escalation path agreed as written above.
What should the kickoff follow-up email say?
The kickoff follow-up email should restate the agreements, list the customer's first dependencies with owners and dates, and confirm the update and escalation rules. Send it the same day while the meeting is fresh, and invite corrections by a stated date so everyone works from the same record.
Subject: [Customer] kickoff: what we agreed and next steps
Hi [names],
Thank you for the time today. Here is what we agreed, so we're all working from the same page.
Success criteria: [list] Scope: [in scope]. Not included: [exclusions]. Go-live means: [condition], confirmed by [owner] Decision owners: [attached table] Needed from you first: [item], [owner], by [date]; [item], [owner], by [date] Next milestone: [milestone], [date] Weekly update: every [day] to [recipients], in the format we reviewed. Escalation: [agreed rule, one sentence]
Please reply by [date] if anything differs; otherwise we'll work from this. [Recording link if recorded.]
[Your name]
Kipwise and Dock both build a recap and recording into the kickoff, which is a habit worth keeping.
When should you shorten this kickoff agenda?
Shorten the kickoff for smaller, low-risk rollouts with a single decision maker and little technical work. Keep the decision-rights line, the need-from-you list, and the update rule even then; cut detail from scope and risk instead. Governance is easier to agree early than to negotiate mid-project.
A fair objection is that a new customer may resist response windows and escalation rules in the first meeting. Frame them as protection for the customer's go-live date, propose them as drafts, and let the sponsor adjust them. An agreed rule the customer helped shape is far more useful than a stricter one they never accepted. Some decision owners also won't be known on day one; record those as open items with a date rather than guessing.