Activity-based onboarding is the most common failure
The most common onboarding plan in B2B is a list of activities. Week 1: kickoff meeting. Week 2: integration call. Week 3: training session. Week 4: go-live. The list goes on for 12 weeks. At the end of 12 weeks, the implementation team declares success because all the activities were completed.
The customer does not agree. The customer does not experience success because they checked boxes. The customer experiences success because they can do something they could not do before. If that something is not happening by day 90, the activities were not the point.
The book calls the alternative results-oriented onboarding. The plan is built around the outcomes the customer is trying to achieve, not the activities the vendor is trying to complete. The 90-day plan is structured as a list of results, with dates, owners, and metrics.
The three results of a 90-day onboarding
A results-oriented onboarding plan has three results. Not five, not ten. Three.
The first result is first value. The customer does something with the product that produces a measurable business outcome for the first time. This is not "the system is configured." This is "the first report ran" or "the first transaction was processed" or "the first user signed in and completed a workflow." First value usually happens between day 14 and day 30.
The second result is adoption. Real users, in real workflows, are using the product at a frequency and depth that predicts retention. The metric is not "users logged in this month." The metric is "users completed a primary workflow this week." Adoption usually stabilizes between day 45 and day 75.
The third result is value confirmation. The customer can articulate, in their own language, the value they have experienced so far, and the value they expect to experience in the next 90 days. This is the foundation of the renewal conversation. Value confirmation usually happens at the 90-day mark.
What the plan looks like
Each result has three columns: the result, the metric that proves it, and the date it must be achieved. The plan is one page. The activity list that supports each result is a separate document, owned by the implementation team, and not shared with the customer.
The reason the activity list is not shared is subtle. The customer does not care about the vendor's activities. The customer cares about the results. Sharing the activity list creates two problems: it makes the customer responsible for the vendor's work, and it makes the vendor accountable for activities instead of outcomes. Both make the renewal harder.
The plan is reviewed weekly with the customer. The review is short — 30 minutes — and follows a fixed agenda: results achieved, results at risk, decisions needed. The review is not a status update. It is a value confirmation meeting in miniature.
The 90-day meeting
The 90-day meeting is the moment of truth. By day 90, the customer has experienced the product long enough to form a real opinion. The meeting has one purpose: to confirm that the value the customer expected is the value they are experiencing.
The meeting is run by the customer, not the vendor. The vendor is in the room to listen and to take notes. The customer's leadership team attends — not the project manager, the leadership. The customer is asked three questions: what is working, what is not, and what would make this engagement worth renewing in 12 months.
The answers to those three questions are the input to the next 270 days. They are also the input to the renewal conversation. If the customer cannot answer the third question, the renewal is at risk and the next 270 days are a recovery project.
Frequently asked questions
How do you define first value in a 90-day onboarding?
First value is the first measurable business outcome the customer experiences with the product. It is not a configuration milestone. It is not a training completion. It is the first time the product does something that produces a number the customer cares about — a report, a transaction, a workflow output.
What if first value takes longer than 30 days?
The 30-day target is for products with a short time-to-value. For products with longer cycles (enterprise software, hardware, complex integrations), first value may be 60 or 90 days. The principle is the same: name the first value, set a date, measure it. The customer should know, on day 1, when the first value is expected.
How many users should be active for "adoption"?
It depends on the customer's organization, not on the product. The adoption metric is set in the expectations document, based on the customer's own definition of who needs to be using the product for the engagement to be considered successful. A 5,000-person company and a 50-person company have different adoption metrics.
What is the most common onboarding failure?
Confusing activity with outcome. The implementation team reports "all training sessions completed." The customer reports "nobody is using it." Both are true. The gap is that the activities were completed but the outcomes were not. The fix is to build the plan around outcomes, then design activities to support them — not the other way around.
Who runs the 90-day meeting?
The customer runs it. The vendor attends, takes notes, and asks clarifying questions. If the vendor runs the meeting, the customer becomes the audience, and the customer will not say in front of the vendor what the customer will say in private. The 90-day meeting is a listening exercise, not a presentation.
Conclusion
Onboarding is not a list of activities. It is a list of outcomes. The 90-day onboarding plan has three outcomes — first value, adoption, value confirmation — each with a metric, a date, and an owner. The activities that support those outcomes are internal, not shared with the customer. The 90-day meeting is the moment the customer confirms the value they expected is the value they are experiencing.
The next chapter covers what happens after onboarding: the follow-up meetings that keep the value visible to the customer when their own attention has moved on.
Buy the full book on the store | USD 5
About the author: Reginaldo Osnildo is a journalist, professor, and author of works on sales, technology, and communication strategies. His work connects academic research, practical business experience, and storytelling to deliver clear, didactic, and applicable knowledge.
Photo by RDNE Stock project on Pexels.
Comments