What does a SaaS customer onboarding timeline look like?
A 30-day SaaS onboarding timeline has 6 stages across two parallel tracks: Main track — pre-kickoff (Days 0–3), kickoff call (Days 3–5), setup (Days 5–18), first value milestone (Day 10–12), training (Days 18–25), go-live (Days 25–30 with 5-day buffer). Parallel IT track — starts Day 5, runs concurrently with setup through go-live. IT dependencies should never be on the critical path.
In this article
The 30-Day Onboarding Timeline
| Days | Stage | CSM tasks | Client tasks | Exit criterion |
|---|---|---|---|---|
| 0–3 | Pre-kickoff | Welcome email, intake form, handoff review, provision access | Complete intake form, identify IT contact | Intake received, access provisioned |
| 3–5 | Kickoff | Lead kickoff, send MAP recap within 2 hours | Confirm go-live date, accept task ownership | Go-live date locked, owners assigned |
| 5–18 | Setup + IT parallel | Configure product, coordinate IT integration | IT: SSO/integration. Client: data export, seat invites | Client confirms setup correct |
| 10–12 | First value milestone | Guide client to first meaningful workflow | Complete first real product workflow | TTV date recorded |
| 18–25 | Training | Admin training, end-user training, share resources | Attend training, acknowledge resources | Client confirms training complete |
| 25–30 | Go-live + buffer | Final check, coordinate sign-off | Written go-live sign-off | Sign-off received, 30-day review scheduled |
Key Principles for Timeline Design
Run IT in parallel, always
IT approvals for SSO and integrations typically take 5–14 days. If you wait for IT before starting setup and training, every onboarding is 2 weeks longer than necessary. Start the IT track at kickoff and run it in parallel. Identify all IT dependencies on the kickoff call, get the IT contact's details, send a technical brief the same day. For IT block protocols, see our blocked tasks guide.
Build buffer before go-live
Plan a 30-day onboarding over 25 days. The 5-day buffer absorbs the inevitable — a data migration that takes longer, an IT approval that slips, a training session rescheduled. Without buffer, every delay pushes the go-live date. With buffer, most delays disappear invisibly.
Front-load the first value milestone
Move the first value milestone to the setup stage — Day 10–12 in a 30-day plan. A client who has experienced value before training is far more committed to completing the rest. Our time to value guide explains why this matters for retention.
Adapting for Different Timelines
14-day onboarding: Compress pre-kickoff to 1 day. Kickoff and first value milestone in week one. IT, training, and go-live in week two. No buffer — tight timelines require perfect upfront preparation.
60-day onboarding: Expand setup to weeks 1–3, training in weeks 3–6, first value milestone end of week 2. Build 10-day buffer. This works for complex products with data migration or multi-department rollout. See our enterprise onboarding guide.
For the KPIs that track whether your timeline is performing, see our onboarding KPIs guide. For the full task-level structure at each stage, see our CS onboarding template.
Frequently Asked Questions
Stop flying blind on your accounts.
Lyniro gives CS leaders real-time visibility into every account — with completion verified by the client, not your team.
Become a Founding Design Partner — Free