Enterprise SPM for M&A and Territory Realignment
Lanshore harmonizes sales compensation when an acquisition, a divestiture, or a territory realignment leaves one sales force running on several plan philosophies and more than one commission system. The work runs in a fixed order: establish what each population is paid today, model every consolidation option against real transaction history before anyone approves it, decide which platform survives on the evidence, and keep paying people correctly through the bridge period while that happens.
Doug Erb, Founder & CEO · Updated
Doug Erb founded Lanshore and has designed, built and run sales compensation systems since 2000, from Callidus and Trilogy through Varicent, Xactly, CaptivateIQ, Performio and SAP Commissions. He also leads the firm's AI and automation practice and its energy programs, including program management of a $53M greenfield S/4HANA implementation at PEMEX.
Who it is for
Enterprises that have closed a deal, or are about to, and now owe two or more sales populations a plan. Usually the buyer is a VP of Sales Operations, a Head of Incentive Compensation, or a CFO who has inherited a second commission system and a retention problem at the same time. It also fits companies realigning territories at scale without an acquisition, where the plan has to change for most of the sales force in one cycle. The common condition is a deadline set by the deal or the fiscal calendar rather than by the comp team, and no slack to get the first cycle wrong.
The problems it solves
Two plan philosophies, one sales force
The acquired team may be paid on gross margin where yours pays on revenue, or on a quarterly quota against your monthly one, with different accelerator shapes and different definitions of a booking. Harmonizing is not a merge of two documents. It is a decision about which behavior you want to pay for, taken with the knowledge of what each option costs. Lanshore's sales compensation transformation work names acquisitions that brought several plan philosophies into one sales force as one of the situations it is built for.
Nobody can price the options
The question leadership asks first is what each consolidation option costs, and the honest answer rarely exists, because the two populations sit in different systems with different crediting rules. Modeling a harmonized plan on summary attainment hides exactly the interactions that drive cost. In a design review for a national telecom carrier, Lanshore found that roughly 6 percent of the prior year's new-logo bonus dollars were overpayments, because the CRM had no first-order flag and the legacy system paid the bonus on every order from any account under twelve months old. That class of finding is the normal case, not the exception, and it surfaces only against real transaction history.
Which commission system survives
Deals usually arrive with a second platform attached, and the decision gets made on license cost or on whoever shouts loudest. The question that matters is which system can calculate the harmonized plan, including the hardest components, without custom logic that only its original builder understands. Lanshore implements nine SPM platforms and resells none of them, so the keep-or-migrate decision is tested against your plans rather than against a partnership.
Paying people correctly during the bridge period
Between close and the harmonized plan there is a stretch, often a quarter or more, where two populations are paid under two sets of rules while reporting into one organization. Shared accounts, overlapping territories, and reps who now sell both product lines are where crediting disputes start. The bridge has to be designed deliberately, with crediting rules written down for the overlap cases, rather than handled as a run of manual adjustments nobody can reconstruct later.
Retention risk while the plan is unknown
Sellers on the acquired side read silence about their comp plan as bad news, and the strongest performers have the most options. The practical constraint is that the harmonization timeline is a retention timeline too, which means the sequence has to produce something communicable early, even if the full plan lands later.
How Lanshore delivers it
- 1
Establish the baseline for every population
We document what each group is paid today at the level of crediting rules, not plan summaries: what counts as a booking, how splits and overlays work, how quota is set and retired, how draws and clawbacks behave. This is the artefact the whole program rests on, and on most deals it does not exist on either side in a form the other can read.
- 2
Model the consolidation options against real transactions
Each candidate design is costed against both populations' actual transaction history, option by option, showing total cost, the distribution of payouts across the combined sales force, and who wins and loses under each. Leadership picks a design knowing which sellers see a material pay change, which is the information the retention conversation needs.
- 3
Decide the platform on evidence
We test the surviving design against the candidate systems, starting with the components that break things: multi-level crediting, overlapping territories, retroactive quota changes, restatements. If a migration is the answer, plan rules carry over where the structure allows and are rebuilt where it does not, with statement history moved alongside, because clawbacks and disputes reach back across the close date.
- 4
Design the bridge period explicitly
We write the crediting rules for the overlap cases before they occur: shared accounts, reps selling both lines, territories that change mid-quarter. Exceptions during the bridge are approved and evidenced rather than adjusted quietly, so the first audit after the deal can be answered.
- 5
Build, run a parallel cycle, then operate
The harmonized plan is configured, then run in parallel against the current calculation across a full cycle including a month-end, with every variance resolved to a named cause before cutover. Afterward Lanshore can run comp operations as a managed service, which is where the remaining plan changes from the deal tend to land. An enterprise program of this shape typically runs 6 to 12 months, driven by plan complexity rather than by the platform chosen.
Platforms we deliver on
Related case studies
- Architecture redesign to fix a broken compensation process
Commission process broken for over a year, restored to systematic accuracy
- Reacting to changing business needs for variable compensation
Third-party dependency for every plan change replaced with a flexible model
- Tackling resource challenges with expert advice and managed services
Error-prone manual Excel commission process replaced with managed operations
Related: Enterprise sales compensation transformation · Global incentive governance · SPM managed services · Best sales compensation firms for M&A plan changes
Enterprise SPM for M&A and Territory Realignment: FAQ
- How long does it take to harmonize sales compensation after an acquisition?
- Lanshore publishes 6 to 12 months for an enterprise program of this kind, driven by plan complexity rather than by the platform chosen. The harmonized plan itself usually lands at a fiscal boundary, because moving people mid-year creates proration and quota-retirement problems that cost more than waiting. What does not wait is the bridge period design and the communication to the acquired sellers, which should be underway within weeks of close.
- Should we migrate the acquired company onto our commission platform?
- Decide it on the harmonized plan, not on the org chart or the license renewal. Test both systems against the hardest components of the plan you intend to pay: multi-level crediting, overlapping territories, retroactive quota changes, and restatements. Sometimes the acquired platform is the better fit and the parent migrates onto it. Lanshore implements nine SPM platforms and resells none of them, so the test is not shaped by what we would prefer to configure.
- What happens to commissions between close and the new plan?
- Both populations keep running under their existing rules, and the overlap cases need crediting rules written down before they occur rather than resolved as manual adjustments. The cases that cause disputes are shared accounts, reps who now sell both product lines, and territories that change mid-quarter. Exceptions during this period should be approved by a named person and evidenced at the moment they are made, because the first post-deal audit will sample exactly these.
- How do we know what a harmonized plan will cost before we approve it?
- Model each option against both populations' real transaction history rather than summary attainment, showing total cost, the payout distribution across the combined sales force, and the edge cases. Interactions are where the money goes: an accelerator compounding with an overlay, a cap that never binds because of how crediting splits, a bonus that pays on every order because no system flags a first order.
- Does Lanshore have an M&A-specific case study we can reference?
- Not a published one. Lanshore publishes case studies on commission architecture redesign at a multi-billion-dollar software company, on a procurement technology provider whose plans changed faster than its vendors could respond, and on taking over commission operations as a managed service, along with a PepsiCo incentive rollout across more than 20 countries and a dozen currencies. Ask us for the bridge-period and shared-account crediting approach in writing and judge the method on that rather than on a logo.
Talk to Lanshore
A 30-minute call. We look at your plans, your systems, and where this would change your comp operations first.
