How to Onboard a Mid-Market Customer in 45 Days Without Cutting Scope

A 45-day mid-market onboarding is not aggressive, it is efficient. The waiting time in a typical 90-day rollout is where the days live, and compressing them into a 45-day plan is a scheduling problem, not a work problem. Here is the playbook, phase by phase.

What kind of customer fits a 45-day plan?

Be honest about scope before starting.

• Segment. 100 to 500 seats, mid-market. SMB is faster naturally, enterprise usually cannot fit 45 days without scope compromise.
• Data complexity. Standard schema, one source system, historical data optional. Multi-system migrations do not fit 45 days.
• IT dependencies. SSO integration, standard SaaS-friendly IT posture. Air-gapped or highly regulated environments do not fit.
• Sponsor engagement. Named exec sponsor available for kickoff plus two check-ins. Sponsors who cannot commit that time will not sustain the pace.

Roughly 40 to 50% of your mid-market pipeline will fit these criteria. Do not force customers who do not fit into a 45-day plan. Extend the plan honestly for those cases.

What are the five phases?

Five phases, 45 days.

Note the overlap between Configuration and Training. That is intentional. Sequential phases lose 10 days on a 45-day plan.

How does the prep phase work?

The prep phase runs before day one, between contract signature and kickoff. This is the invisible compression.

• Day -7. AE sends closed-won paperwork with data prep checklist and IT access requests attached. Warm handoff email to IM.
• Day -5. IM sends welcome email with kickoff scheduling link. Customer sponsor picks a date.
• Day -3. IM sends prep summary: what to bring to kickoff, who to include, sample of the plan template.
• Day -1. IM confirms kickoff attendees, sends kickoff agenda.

Prep saves 7 to 10 days. Customers who complete the data checklist before kickoff finish 15 days faster on average.

What happens in kickoff?

Kickoff is a 90-minute working session, days 1 to 3.

• Day 1. 90-minute kickoff call. Confirm scope, name customer-side lead, review the shared plan, assign first three customer-side tasks with deadlines. Do not end without a named lead. Refuse this if necessary.
• Day 2. IM has 30-minute working session with named customer-side lead. Walk through the shared plan, confirm tool access, kick off data audit.
• Day 3. Kickoff gate. Named leads on both sides, shared plan active, first tasks in progress. If not met, day 3 is not the end of kickoff. Extend before starting configuration.

Kickoff gate criteria are strict. Skipping them saves time in week one and loses it in week three.

What happens during configuration?

Configuration runs days 4 to 20. This is the longest phase and where most slip lives.

• Days 4 to 7. Data mapping. IM and solutions engineer with customer lead. First data sample from customer.
• Days 8 to 12. Sandbox environment provisioned. First migration run. Customer starts SSO configuration in parallel with their IT.
• Days 13 to 16. Sandbox validation. Customer lead validates data in sandbox, flags issues. SSO configuration completed.
• Days 17 to 20. Fix cycle. Any validation issues resolved. Sandbox signed off by customer sponsor.

Configuration gate: sandbox signed off, SSO working, admin access confirmed. Cannot proceed to training without this.

When does training happen and how do you parallelize it?

Training runs days 15 to 35, overlapping with the last week of configuration.

• Days 15 to 20. Admin training. Customer admin trained on the sandbox while configuration is still stabilizing. Admin becomes the customer-side power user.
• Days 21 to 28. Integrations training. Whoever on the customer team owns integrations gets trained on the integration flows in the sandbox.
• Days 29 to 35. End-user training, in role-scoped sessions of 20 or fewer. Not one giant all-hands.

Training gate: admin certified, integrations owner trained, end-user training completed for at least 80% of users going live.

The parallel structure is what buys the 10 days. Sequential training after configuration ends means training does not start until day 20 and finishes at day 45, which is the go-live date. That does not work.

What happens in go-live?

Go-live runs days 36 to 45. The last 10 days.

• Days 36 to 38. Cutover prep. IM confirms production configuration matches sandbox. Customer sends cutover communications to end users.
• Days 39 to 40. Cutover window. Data moved to production. SSO switched over. Small pilot group logs in.
• Days 41 to 42. Full user activation. All users have access. Admin available for support.
• Days 43 to 45. Hypercare. Daily check-ins with customer lead. Any issues resolved live. Handoff to CSM.

Go-live gate: 80%+ user activation, success criteria met, handoff to CSM completed. Anything short of that extends hypercare.

What signals mean the 45-day plan is not going to hit?

Four early signals, in order of severity.

• Day 1 signal. No customer-side lead named in kickoff. This is a 90% predictor of missed date. Do not proceed on 45 days.
• Day 5 signal. Data audit not started. Missing prep is unlikely to be recovered. Extend to 60 days.
• Day 12 signal. SSO configuration blocked in customer IT queue for longer than 5 days. Renegotiate the timeline directly with customer IT.
• Day 20 signal. Sandbox validation not started. Configuration is running long. Extend by 10 days honestly rather than compress training.

Renegotiate early rather than late. Customers accept an honest 55-day plan on day 15 much better than a slipped 45-day plan on day 42.

How do you run the plan operationally?

Daily digest, weekly review, phase-gate meetings.

• Daily. Automated digest to IM and customer lead. Overdue tasks, tasks due today, projected go-live vs baseline.
• Weekly. 20-minute working call between IM and customer lead. Not a status call, a decision call. Anything blocked longer than three days gets escalated.
• Phase gates. Meeting at each gate transition (kickoff done, configuration done, training done, go-live). Sponsor on both sides included. Any failed gate means the timeline changes, in writing.

If the weekly call turns into a status readout, the shared plan is not being used correctly. The plan should be current before the call.

The mistake to avoid

The mistake is running a 45-day plan on a customer who does not fit. The best-case failure is a 60-day rollout labeled as slipped. The worst-case failure is a customer who feels rushed, disengages, and churns in year one. The 45-day plan is not a target for every deal, it is a template for the ones that fit. Screen honestly in kickoff. For customers who fit, this playbook holds 60 to 70% of the time. For customers who do not fit, run 60 or 90 days and hit that number 90% of the time. Both are wins. Missing a fast plan is not.