Onboarding (Sales Comp)
What is onboarding in sales compensation?
Onboarding is the ongoing work of adding new participants and new plans to a commission system after it has gone live. A new rep joins and needs a plan, a quota, and access to their statement. A plan gets revised at the start of the year. The business acquires an entity with its own comp structure. Each of those is an onboarding event.
The defining property is that it never ends. Implementation is a project with a completion date. Onboarding is a permanent operating activity, and it is the work you will be doing every month for as long as you own the system.
This is a live source of confusion in the buying process, and it is not the buyer's fault. In a discovery call, a prospect who had just been told the platform fee covered the initial build immediately asked what happens if he adds a second company in a later year. He had heard one word, implementation, and reasonably assumed it covered everything that sounded like setup. It does not.
What onboarding actually covers
Two of those rows deserve flagging. The annual plan refresh is not a small task: it touches every plan and every rep at once, and it lands at the busiest possible moment in the finance calendar. And a new entity or acquisition is not really onboarding at all. It is a second implementation wearing an onboarding label, and it should be scoped and priced as one.
What this means?
For a buyer, this is the question to settle before signing, and it is rarely asked: who does the onboarding work, and is it included? If the vendor does it, what is the turnaround when a rep starts on the 1st and needs a plan by the 5th? If your team does it, can they, without the vendor, without a support ticket, and without knowing the internals? Those two answers describe two completely different total costs of ownership, and neither one is on the price sheet.
For RevOps, the honest test of a commission system is not whether the initial build went well. It is whether you can add a rep, revise a rate, or version a plan without opening a ticket. A system that requires vendor involvement for routine changes has moved the bottleneck rather than removed it, and the annual plan refresh is where that becomes painful.
Common mistakes
1. Assuming onboarding is included because implementation was
Two different things sold under one word. Get the scope line in writing before signing, not after the first new hire.
2. Underestimating the annual plan refresh
It touches every plan and every rep simultaneously, and it arrives at year end alongside everything else. It is the single largest recurring onboarding event and it is almost never planned for.
3. Treating an acquisition as onboarding
A new entity with its own plans, and possibly its own CRM, is an implementation. Scoping it as a routine addition is how a quarter gets lost.
4. Onboarding a rep without ramp
A new rep on a full quota from day one will miss it, and their attainment number will be wrong in a way that distorts every report they appear in. See ramp period.
How Visdum handles onboarding
The question that matters is whether routine change requires the vendor. In most legacy ICM tools it does, because plans are effectively coded rather than configured, and so every new rep, rate change, and plan version becomes a small professional services engagement.
Visdum is built so that the ongoing work stays with the team that owns the plans. Adding a rep, assigning them to a plan, applying a ramp, and giving them statement access is administration rather than configuration. Plans are versioned, so a mid-year change is recorded rather than overwritten, and the audit trail shows what changed and when, which matters when someone asks why an attainment figure moved. The annual refresh is a plan operation rather than a rebuild. Where implementation ends and onboarding begins is stated at the outset, so the scope line is written down rather than discovered at the first new hire.
Take a self-guided product tour to see this in action, or read how to build a SaaS sales compensation plan.
Related terms
Implementation (ICM) · Implementation vs Onboarding · Ramp Period · Change Management · Commission Statement
Calculate your OTE in 30 seconds
Frequently asked questions
What is onboarding in sales compensation?
Sales comp onboarding is the ongoing work of adding new reps, plans, and entities to a commission system after go-live. A new hire needs a plan and a quota. A plan gets revised each year. An acquisition brings its own structures. Unlike implementation, which is a project with an end date, onboarding never finishes.
What is the difference between onboarding and implementation?
Implementation is the initial build: a defined project that configures the system and ends at go-live. Onboarding is everything after: adding reps, revising plans, handling leavers, refreshing quotas each year. They are frequently sold under one word, which is how buyers discover after signing that routine changes were not included.
What does sales comp onboarding involve?
Assigning plans and quotas to new reps, applying ramp periods, handling role and territory changes, processing leavers including any unearned draw, running the annual plan refresh, versioning mid-year plan changes, and adding new entities. The annual refresh is the largest of these, because it touches every plan and every rep at once.
Who should do the onboarding work, us or the vendor?
Settle this before signing, because the two answers describe very different costs of ownership. If the vendor does it, ask what the turnaround is when a rep starts on the 1st and needs a plan by the 5th. If your team does it, confirm they actually can, without a support ticket and without knowing the internals.
Why is the annual plan refresh so difficult?
Because it touches every plan and every rep simultaneously, and it lands at year end alongside everything else Finance is doing. It is the largest recurring onboarding event in the calendar and it is almost never planned for as a distinct piece of work, which is why it consistently consumes more time than anyone expected.
Is adding a new business entity just onboarding?
Not really. A new entity with its own plans, possibly its own CRM and its own currency, is a second implementation wearing an onboarding label. It should be scoped and priced as a project rather than treated as a routine addition, which is how teams lose a quarter to something they budgeted a week for.