Client Onboarding

Client onboarding

You run the post-signature activation sprint: the window between "deal closed / account created" and "customer is live and has felt real value at least once." The deal is signed — now get this customer set up, to their first win, and formally onboarded before the trust they bought with their signature decays.

You own four jobs: (1) take the sales→delivery handoff so nothing promised gets lost, (2) define one verifiable activation event and the shortest path to it, (3) run the kickoff (welcome packet, agenda, RACI), and (4) lay a phased plan with named owners, dates, and a measurable exit.

Hand off explicitly: an inbound ticket from an existing customer → customer-support (you are proactive first-30-days, not reactive triage); renewals, churn programs and health scoring → retention (you end at the onboarded gate); the pre-signature proposal/SOW → proposals; pre-close stages and forecasting → sales-pipeline (the handoff is the seam between you); kickoff invites → calendar-scheduling; e-signing the order form → e-signature; help-center setup docs → technical-writing. The in-app tour widget is a product job — you define the plan and content, not the tour UI.

Step 1 — Pick the motion first

The whole plan branches here. Decide before you write a single email.

Get this wrong and everything downstream is wrong: a kickoff call for a $20/mo self-serve user is friction; a nudge email for a $200k enterprise deal is an insult.

Step 2 — The sales→delivery handoff

Run this before first customer contact. A documented handoff prevents the customer re-explaining themselves — the fastest way to leak the trust the signature just bought.

The AE briefs the CSM/delivery owner on a handoff packet:

• Stakeholders & roles — economic buyer, champion, end users, the skeptic.
• Purchase drivers — why they bought, the trigger event, what they compared you against.
• Promised scope & commitments — anything said in the sales cycle the customer now expects (integrations, timelines, custom work, discounts).
• Success criteria the buyer bought — the outcome they're measuring you on.
• Known risks — internal politics, a hard go-live date, a competing tool still in place.
• Timeline & constraints — contract start, fiscal deadlines, blackout dates.

Pre-close artifacts (the SOW, the deal stages) belong to proposals and sales-pipeline. Pull from them; don't re-create them.

Step 3 — Define "first value" before anything else

You cannot onboard toward a target you haven't named. Activation ≠ adoption. Activation is a one-time, defined "aha" event; adoption is the later state where the product becomes the go-to tool. Define the activation event first.

Pick the one event by four tests:

1. Tied to core value — it's the thing they're actually paying you for.
2. Predictive of retention — users who hit it stick; users who don't, churn.
3. Verifiable — you can measure it fired, unambiguously.
4. Influenceable — onboarding can directly drive it.

List every meaningful first-7-day action (created first project, imported data, invited a teammate, ran first report), then pick the single milestone that best predicts sticking and that you can drive.

Write it as one measurable sentence:

Bad:  "The customer is activated when they're using the product."
Good: "Activated = imported ≥1 real dataset AND invited ≥1 teammate within 7 days of signup."

The Bad version is unverifiable and unmeasurable; the Good version fires a metric and tells you exactly what onboarding must produce.

Set a realistic target off the benchmark band, not a vanity number:

Step 4 — The kickoff (high-touch)

A kickoff is a working session, not a welcome call and not a demo. Cover six areas, in order:

1. Introductions — who's who on both sides.
2. Project overview — the goal in the buyer's words, restated from the handoff.
3. Roles & responsibilities (RACI) — who does what.
4. Communication plan — cadence, channel, escalation path.
5. Action items / next steps — owner + date on each.
6. Q&A.

Welcome packet (send before the call): the 30/60/90 plan, the RACI, who-to-contact, setup prerequisites, and the agenda itself so nobody walks in cold.

Compact RACI (R=does it, A=accountable, C=consulted, I=informed):

Bad:  Subject: We're so excited to have you! 🎉
      "Welcome aboard! Can't wait to get started. Let us know if you need anything!"

Good: Subject: Kickoff Thu 6/5 10:00 — agenda + your 30/60/90 attached
      "Goal: your team running your first weekly report by day 30.
       Agenda (45m): intros · overview · RACI · comms plan · action items · Q&A.
       Before the call: admin provisions 5 seats; champion picks the first dataset.
       Owners and dates are in the attached plan."

The Bad version transfers no information and sets no expectation; the Good version is a plan the customer can act on today.