Pillar 2: Onboarding — the pillar that decides if the first renewal happens
Onboarding is finite, has a clear start and end, and is the pillar with the biggest influence on whether the first renewal happens. Trip here and you spend the whole contract catching up — and sometimes you can't.
Most renewals are won or lost in the first 90 days of the contract. Not the last 90. It's in that opening window — Onboarding — that the customer decides, consciously or not, whether the purchase was a hit or a mistake. And the emotional tone of that decision is hard to reverse later.
That's why Wayne McCulloch (The Seven Pillars of Customer Success, 2021) names Pillar 2 — Onboarding as the pillar with the biggest influence on the first renewal. It's not rhetorical overreach. It's operational observation: teams that stumble in onboarding spend the rest of the contract chasing value they promised but didn't deliver on time.
The definition that matters
Onboarding is jointly defining a Customer Success Plan together and proactively guiding a customer to achieve value one in the fastest possible time. — McCulloch 2021, ch. 4
The value verb here is Value Defined. Not "value delivered" — defined. The end of onboarding is not "product deployed." It's "the first business value is named, delivered, and visible to the customer."
Three components matter separately:
- Joint plan. The CSM doesn't write it alone. It's not a slide deck. It's co-construction.
- Proactive guidance. The CSM anticipates obstacles. Doesn't wait for the customer to report a problem.
- Fastest possible time. Time to Value is the leading indicator. Every extra week of onboarding raises the probability of churn at the first renewal.
Onboarding ≠ Adoption
The most common confusion on a CS team: treating onboarding and adoption as the same process. They're not.
| Onboarding | Adoption | |
|---|---|---|
| Duration | Finite | Ongoing |
| Endpoint | Defined | Never |
| Recurrence | Per logo, per new department, per new product | N/A — it persists |
| Headline goal | Value one achieved | Operational dependence + business value |
Onboarding can repeat — a single logo can be onboarded multiple times (new department, new product, new region). But each onboarding event has a clear beginning, middle, and end. Adoption, by contrast, never ends.
This classification mistake has operational consequences: teams that treat onboarding as continuous never declare an end. The customer stays in "eternal onboarding" without ever reaching the point where the CSM can let go. The result is a book that looks big, but where almost no one has reached real value.
The key concept: value one
Value one is the first business result delivered during onboarding. Not "first login." Not "first report generated." A business result.
McCulloch names three types of value one (ch. 4):
- Use case — a specific way the product gets used. Example: "deploy in one airport."
- Desired state — an environment or status achieved. Example: "everyone clear on roles in the new structure."
- Defined value — a specific metric. Example: "X active users in 90 days."
The golden rule: value one must be achievable and fast. The book's classic example: an aviation company wanted to "deploy the solution across all airports we manage in 18 months." The CSM renegotiated to "deploy in one airport." Same direction, realistic scope, fast feedback loop.
Value one is not the totality of value the customer will capture. It's the first slice that proves the bet was right.
Without a named value one, onboarding has no definable endpoint. Without an endpoint, no one knows when to declare success. Without that declaration, the customer ends the first contract believing they're "still implementing" — a terrible position from which to enter renewal.
The 5 steps to exceptional onboarding
McCulloch (ch. 4) breaks down the formula:
1. Focus on the right people
Not the buyer. On who's going to use it: stakeholders, project managers, admins, the customer's own CSM (yes, on their side). The person who signed the contract isn't the person who decides whether the product works. The deciders are the people who need to deliver outcomes with it.
2. Understand the specific goals of those people
Not the company's goals in the abstract. What does Maria, the project manager need to deliver to her boss in 90 days? How does your product make Maria look competent? That's the goal that matters — not "digital transformation of the financial sector."
3. Clear timelines and execution plans
Pilot or massive rollout? How long for each phase? Who does what in each one? Without that clarity, the operation becomes improvisation — and improvisation always slides into "let's wait on IT" and "this wasn't agreed."
4. Deliver value one
The critical step. The previous four exist to make this one possible. If onboarding wraps and value one wasn't named or delivered, onboarding failed — regardless of whether the product is technically "deployed."
5. Design the maturity path
Always think two moves ahead. Where is the customer today? Where do they want to be in 6 months? In 12? Onboarding plants the seed of what becomes the Customer Success Plan that guides adoption, retention, and expansion later.
The CSM as the "easy button"
Onboarding is the pillar where CSM presence makes the most visible difference. McCulloch names three non-negotiable behaviors:
Explode out of the gate
Start the success plan in days, not months. Every week the contract sits without a plan is a week the customer is alone with the product. If your official kickoff is scheduled 3 weeks after signature, the customer has already formed an opinion before the kickoff happens.
Remove obstacles before they appear
Take the history of the last 10 onboardings that ran well and the 10 that stalled. Map the recurring obstacles. "IT typically takes 3 weeks to provision access — let's open the ticket today." "Legal asks for DPA review — let's send the pre-adapted template now." That anticipation separates good onboarding from heroic onboarding.
Learn to listen — including to the competition
McCulloch insists: listen more than you talk. And listen to the competition too — because your customer is listening to them. If you don't know the arguments competitors are using against you, you'll be blindsided by an objection that was already being planted.
The dominant risks during onboarding
Two risks concentrate in this pillar:
- Launch risk. Deployment stalls or goes red. Almost always a CS failure: the customer wasn't told, in advance, what would be needed (database access, technology, people, internal decisions). When the implementation team discovers something missing in week 3, it's already late.
- Adoption risk. Adoption risk forms here, even when it manifests later. Bad onboarding seeds bad adoption. Stakeholders engaged in onboarding become champions in adoption. Stakeholders absent in onboarding become detractors at renewal.
How the toolbox helps in this pillar
- Moments of truth — onboarding is "flooded with moments of truth." Welcome email, kickoff call, first deployment, first login, first report. Each deliberate, not accidental.
- Playbooks — start with the highest-leverage moment. Don't build a playbook you can't run.
- Customer success plan — must include value one, milestones, success measures. Visible to the customer.
- Health score — weight inputs differently: usage is still near zero, so weight relationship and launch progress higher than utilization.
- Segmentation — high-touch vs. low-touch. The same onboarding doesn't fit every customer.
What exceptional onboarding looks like
Five observable signals:
- A Customer Success Plan exists in the first week after signature.
- Value one is named, written down, and visible to the customer.
- The customer hits value one well inside the first contract period — not in the final week.
- Stakeholder change risk is detected — the relationship has spread beyond a single sponsor.
- Handoff to adoption is explicit. There's a moment where everyone agrees "onboarding is done."
That last point is frequently ignored. Without explicit handoff, onboarding becomes eternal. The customer sits in limbo: no longer getting onboarding attention, but never formally "handed off" to the next phase either.
The 90-day rule
There's a rule of thumb that anchors this whole pillar: if your team takes more than 90 days to deliver value one in mid-sized accounts, something is wrong in Pillar 2 — not in the product, the team, or the customer.
Usually it's one of three things:
- Value one was defined too big. Renegotiate. Take the smallest defensible slice.
- Kickoff happens too late. Move it to D+3 from signature, not D+21.
- No written playbook for the 3 most common obstacles. Each onboarding is being reinvented.
Attack those three, and time-to-value plummets. With it, the probability of the first renewal climbs sharply.
Based on McCulloch, Wayne. The Seven Pillars of Customer Success: A Proven Framework to Drive Impactful Client Outcomes for Your Company (2021), ch. 4. Adapted by the Partenero team. This post is part of a series on the 7 Pillars — see also the overview post and the deep dive on Time to Value.