Customer Onboarding Plan: 8-Week Template With Owners and Milestones

8 min read ยท 2026-10-25

A customer onboarding plan is a shared, dated plan that takes a new customer from signed contract to the first result they bought your product for. It lists the phases, the tasks on both sides, who owns each one and the milestone that proves the customer is live and getting value.

The template below runs eight weeks in five phases, which suits most B2B software and service implementations with a few integrations and a team to train. It is written for onboarding managers, customer success managers, implementation consultants and the project managers who run these projects. It covers what most templates skip: owners on the customer side, how to define first value before kickoff, and what to do when the customer stops responding.

The roadmap at a glance

Goal: The customer is live in production, their main users are trained, and they have reached the first value milestone agreed at kickoff, with a smooth handoff to their customer success manager. Duration: 8 weeks

  1. Sales handoff and preparation (Week 1)

    Bring everything the sales team learned into the onboarding plan before you meet the customer.

    • Hold an internal handoff call with the account executive and solutions engineer to review goals, scope, promises and risks.
    • Read the contract and order form for products, seats, deadlines and any custom terms.
    • Draft the success plan: the customer's goals, the first value milestone and a proposed timeline.
    • Send a welcome email that names your onboarding team and asks the customer to name their project owner and admin.

    Milestone: Handoff notes complete, a draft success plan ready and a kickoff date confirmed with the customer's project owner.

  2. Kickoff and success plan (Week 2)

    Agree goals, scope, owners and dates with the customer in one meeting.

    • Run the kickoff with the customer's sponsor, project owner, admin and key users.
    • Confirm the first value milestone in the customer's words, such as first payroll run or first 100 tickets handled.
    • Agree owners on both sides for every workstream and a weekly check-in time.
    • Share the success plan in a place both teams can edit and track.

    Milestone: Success plan signed off by the customer's sponsor, with owners and dates for every phase.

  3. Setup and integration (Weeks 3-5)

    Configure the product and connect it to the customer's systems.

    • Collect the setup inputs: users, roles, settings, data files and integration credentials.
    • Configure the account and run a review session with the customer's admin.
    • Set up single sign-on and integrations with their CRM, ERP or support tools as scoped.
    • Import data, then ask the customer to check a sample against their source system.
    • Log open issues and decisions in a shared tracker reviewed at each weekly call.

    Milestone: Account configured, integrations tested and data import signed off by the customer's admin.

  4. Training and adoption (Weeks 5-7)

    Get the right people able to use the product for their real work.

    • Train admins first, then end users by role, using the customer's own data.
    • Share short guides for the three or four tasks each role does most.
    • Run a pilot with a small group on live work and collect their questions.
    • Fix the configuration issues the pilot reveals before full rollout.

    Milestone: All admins and pilot users trained, with the pilot group completing their main tasks in the product.

  5. Go-live and first value (Weeks 7-8)

    Move the customer to full use and confirm the first value milestone.

    • Agree the go-live date and checklist with the project owner.
    • Roll out to all users and offer extra support during the first week.
    • Confirm the first value milestone with data, such as reports or usage numbers.
    • Hold a closing review: what was delivered, open items and next goals.
    • Hand off to the customer success manager with the success plan and open items.

    Milestone: First value milestone confirmed by the customer's sponsor and the account handed off to customer success.

Define first value before you kick off

Onboarding ends when the customer gets a result, not when the account is set up. Write that result down before the kickoff, using what sales learned. A good first value milestone is specific, measurable and owned by the customer: their first invoice sent from the system, their first campaign launched, their first month-end report from live data.

Bring your draft to the kickoff and ask the sponsor to confirm or change it. Once they agree, every task in the plan should move the customer toward it. If a task does not, push it to after go-live.

Example: a filled-in onboarding plan

Picture a company selling help desk software to a retailer with a 40-person support team. The retailer wants to move off shared inboxes before the holiday season. The first value milestone agreed at kickoff: all customer emails handled in the new help desk, with first response time reported weekly.

Each line has an owner on each side and a check. The customer sees the same plan, so delays on their side are visible without anyone pointing fingers.

  • Week 1 (onboarding manager and account executive): handoff call, contract reviewed, draft success plan. Check: kickoff booked with the support director.
  • Week 2 (onboarding manager and support director): kickoff, first value milestone agreed, owners named. Check: success plan signed off.
  • Weeks 3-5 (implementation consultant and customer IT admin): email channels connected, single sign-on live, macros and routing rules set up, order lookup integration tested. Check: test tickets route to the right queues.
  • Weeks 5-7 (onboarding manager and support team leads): admin training, role training for agents, pilot with eight agents. Check: pilot agents handle live tickets for a week.
  • Weeks 7-8 (support director and onboarding manager): full rollout, first weekly response time report. Check: sponsor confirms milestone, account handed to the CSM.

Who owns what, on both sides

Most stalled onboardings have the same cause: nobody on the customer side owns the project. Ask for named owners in the welcome email and confirm them at kickoff. Write the names into the plan, not just the roles.

Your side needs clear owners too. If the customer has to ask three people for status, the plan is not working.

  • Customer sponsor: agrees the goal, removes internal blockers and confirms the value milestone.
  • Customer project owner: runs the project internally, joins weekly calls and gets decisions made.
  • Customer admin or IT: provides access, data and integration details, and owns the account after go-live.
  • Onboarding manager: owns the plan, the weekly check-in, the issue tracker and the go-live decision.
  • Implementation consultant or solutions engineer: configuration, integrations and data import.
  • Account executive: joins the handoff and kickoff and stays aware of scope changes.
  • Customer success manager: joins the closing review and owns the account from then on.

How to run the weekly check-in and report status

Keep the weekly call to 30 minutes with the same agenda: progress against the plan, decisions needed, blockers and next week's tasks with owners. Send a short written summary the same day, so absent stakeholders stay informed.

For the customer's sponsor and your own leadership, use a one-page status: the five phases with a green, amber or red status, the go-live date, the next milestone and the top risk with what you need. Leave out the task list. If the status is red, say what you are doing about it and what you need from the sponsor.

Metrics to track

Track a few metrics for every onboarding so you can spot problems early and improve the process across customers. Record them in your CRM or customer success tool so you can compare cohorts.

Review them each month with sales and product. Long time to value in one segment often points to a gap in the product, the contract scope or the sales handoff.

  • Time to first value: days from contract signature to the confirmed value milestone.
  • Time to go-live: days from kickoff to full rollout.
  • On-time milestones: share of plan milestones met on the agreed date.
  • Activation: share of licensed users who completed their main task in the first 30 days after go-live.
  • Customer satisfaction at handoff: a short survey sent after the closing review.
  • Early health: usage and support tickets in the first 90 days, as a sign of renewal risk.

What to do when onboarding stalls

The most common stall is silence: the customer stops replying because the project owner got pulled onto something else. Do not wait more than a week. Send a short note that shows the impact, such as the go-live date moving and the value milestone at risk, and propose a 15-minute call.

If that fails, go to the sponsor with the same facts and a clear ask: a new owner, a new date or a reduced scope. Keep the tone factual. The sponsor bought the product to get a result, and a clear status helps them get it.

  • Missing data or access: offer a working session to collect it together.
  • Scope creep: log the request, show its effect on the date and move it after go-live if possible.
  • Low training attendance: record sessions and run short role-based follow-ups.
  • Unclear decisions: write the options and a recommendation, then ask for a decision by a date.

How to adapt the plan

Eight weeks fits a mid-market implementation. Scale the plan to the size of the customer and the product.

Keep the five phases even when the timeline changes. The phases give both teams the same map, and the milestones keep the project honest.

  • Self-serve or low-touch product: compress to two weeks, replace calls with in-app guides and automated emails, and keep one check-in.
  • Enterprise customer: extend to three to six months, add a steering committee, security review and phased rollout by region or team.
  • Professional services or agency onboarding: replace setup with discovery and access requests, and define first value as the first deliverable approved.

Common mistakes to avoid

  • Starting the kickoff without sales context makes the customer repeat themselves, so hold an internal handoff call and read the contract first.
  • Defining success as account setup misses why the customer bought, so agree a first value milestone in the customer's words at kickoff.
  • Assigning tasks only to your own team hides the customer's work, so name owners on both sides for every phase.
  • Letting the plan live in your internal tool keeps the customer in the dark, so share one success plan both teams can see and edit.
  • Training everyone at once before setup is complete wastes the sessions, so train admins first and end users on the finished configuration.
  • Waiting weeks when the customer goes silent pushes the go-live back, so escalate to the sponsor with facts and a clear ask after one missed week.

Frequently asked questions

What should a customer onboarding plan include?

It should include the customer's goals, a first value milestone, the phases with dates, tasks with owners on both sides, the weekly meeting rhythm and the go-live criteria. Add a risk and issue log and the handoff to customer success at the end.

How long should customer onboarding take?

It depends on the product and customer size. Self-serve products may onboard in days, mid-market B2B implementations often take several weeks, and enterprise rollouts can take months. Set the length from the scope at kickoff and track time to first value.

Who owns customer onboarding?

An onboarding manager, implementation lead or customer success manager usually owns the plan on the vendor side. The customer needs a project owner and a sponsor too. The plan works best when both sides have named owners for every phase.

What is the difference between customer onboarding and implementation?

Implementation is the technical part: configuration, integrations and data. Onboarding is wider and includes goals, training, adoption and the first business result. An implementation can be done while onboarding is still in progress.

How do you measure customer onboarding success?

Track time to first value, time to go-live, on-time milestones, user activation and customer satisfaction at handoff. Then watch usage and support tickets in the first 90 days, since a weak start often shows up later at renewal.

Generate this roadmap with AI