Implementation vs Onboarding
Implementation vs onboarding: the short answer
Implementation is the initial build. It configures the system, connects the data, builds the plans, validates the output, and ends at go-live.
Onboarding is everything that happens after that: adding a new rep, revising a rate, running the annual plan refresh, absorbing an acquisition. It never ends.
One is a project. The other is an operating activity. They are routinely sold under a single word, and the resulting confusion is not the buyer's fault.
The comparison
Where the confusion comes from
This is not an abstract distinction. It shows up live, in sales calls, in a very specific pattern.
On a Visdum discovery call, a prospect confirmed his understanding that the platform fee covered the initial build, which the vendor called the implementation. He had it exactly right. His very next question was what would happen if he added a second company in a later year, and whether that would fall to him.
That question is the whole problem in one sentence. He had heard one word, applied it to everything that sounded like setup, and had no way of knowing that adding an entity in year two sits in a completely different category from the build in year one. Nobody misled him. The vocabulary did.
There is a third category that gets swept into the same confusion, which is ongoing administration: running the monthly calculation, clearing data exceptions, managing approvals. That is neither implementation nor onboarding. It is simply operating the system, and it belongs to whoever owns commission.
What this means?
For a buyer, three questions settle it, and they should be asked before signing rather than after the first new hire:
What exactly does the implementation fee cover, and when does it end? Go-live is the natural boundary. If the vendor defines it differently, that is worth knowing now.
Who adds a new rep in month four, and what does it cost? If the answer is a support ticket with a turnaround measured in days, that is a real operational cost that appears nowhere on the price sheet.
Is a new entity onboarding or a second implementation? It is almost always the latter. Establish that before an acquisition, not during one.
For RevOps, the practical test is simpler. A system where routine change requires the vendor has not removed the bottleneck; it has renamed it. The annual plan refresh is where that becomes obvious, because it is the moment every plan and every rep changes at once. See change management for the cost that sits alongside all of this and never makes it into the model.
How Visdum draws the line
Visdum states the boundary up front rather than leaving it to be discovered. Implementation is the defined engagement that connects the data, builds the plans as they actually operate, migrates the history, and validates the output against a period you have already closed. It ends at go-live.
After that, the ongoing work is designed to stay with the team that owns the plans rather than returning to the vendor. Adding a rep, applying a ramp, adjusting a rate, or versioning a plan is administration, not configuration, which means it does not require a ticket and does not wait on someone else's queue. That is the difference the scope line is meant to protect: implementation is something a vendor does for you, and onboarding should be something you can do yourself.
Take a self-guided product tour to see this in action, or read the Salesforce implementation guide.
Related terms
Implementation (ICM) · Onboarding (Sales Comp) · Change Management · ICM · Ramp Period
Calculate your OTE in 30 seconds
Frequently asked questions
What is the difference between implementation and onboarding?
Implementation is the initial engagement that configures the commission system and ends at go-live. Onboarding is the ongoing work that follows: adding reps, revising plans, handling leavers, and refreshing quotas each year. One is a project with an end date. The other is a permanent operating activity that never finishes.
Why do buyers confuse implementation with onboarding?
Because both are sold under one word. A prospect told that the platform fee covers the initial build will reasonably assume it also covers adding a company in year two. It does not, but nothing in the vocabulary signals that. The confusion is a naming failure rather than a buyer failure.
Is adding a new rep implementation or onboarding?
Onboarding. Implementation ends at go-live. Everything after that, including assigning a plan to a new hire, setting their quota, applying a ramp, and giving them statement access, is onboarding. The important question is whether your team can do it directly or whether it requires a vendor ticket every time.
Is a new business entity onboarding or a second implementation?
Almost always a second implementation. A new entity brings its own plans, possibly its own CRM, and possibly its own currency. Treating it as a routine addition is how teams lose a quarter to something they budgeted a week for. Establish this before an acquisition rather than during one.
What questions should a buyer ask about implementation scope?
Three. What does the implementation fee cover and when does it end. Who adds a new rep in month four and what does that cost. And whether a new entity counts as onboarding or as a second implementation. The answers describe very different costs of ownership, and none of them appear on the price sheet.
What is ongoing administration, and is it the same as onboarding?
No. Ongoing administration is operating the system: running the monthly calculation, clearing data exceptions, managing approvals. Onboarding is adding new participants and plans to it. Both happen after go-live, which is why they get conflated, but they are different work and often belong to different people.