Lanshore: Advancing Intelligence

Solutions

SPM Platform Selection and Evaluation

Lanshore runs SPM and incentive compensation platform selections as a scored evaluation rather than a demo tour: requirements gathered separately from sales operations, finance, and IT, a weighted comparison framework agreed before any vendor presents, demos scripted against your own hardest plan components, and a shortlist with a written recommendation your steering committee can audit. Lanshore implements Varicent, Xactly, CaptivateIQ, SAP SuccessFactors Incentive Management, Anaplan, Salesforce Spiff, Performio, Akeron and Incentivate, and resells none of them, so the recommendation reflects fit rather than a reseller relationship.

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

Teams choosing an incentive compensation platform for the first time, replacing one that no longer fits, or consolidating several after an acquisition. Usually a VP of Sales Operations or Head of Incentive Compensation running the evaluation, with finance and IT holding veto rights and a board or steering committee expecting a defensible recommendation. It fits teams who have sat through four demos that all looked impressive, teams whose vendor has announced a price or roadmap change, and teams who have been told to justify the spend against alternatives.

The problems it solves

Every platform demos well

Vendor demos run on vendor data, with plans chosen to show the product at its best. They are not a test of anything. The differences that matter show up on multi-level crediting, overlapping territories, retroactive quota changes and restatements, and none of those appear in a standard demo unless you put them there.

The advice usually comes from someone who sells one

Most firms offering to help you choose also implement one or two platforms preferentially, or hold a reseller agreement. That does not make their advice wrong, but it does mean the evaluation has a thumb on the scale, and you cannot see where. The question to ask any advisor is simple: which of these do you resell, and what do you earn if we pick it.

Requirements get written by one function

When sales operations writes the requirements alone, the payroll interface and the audit trail get underweighted. When finance writes them, usability for comp analysts does. Gathering requirements separately by function and reconciling them openly surfaces the disagreements before a contract rather than during implementation.

Scoring happens after the demos, not before

If the weighting is agreed after everyone has seen the products, it gets shaped by which demo people enjoyed. Agreeing the criteria and their weights in advance is the single practice that most reliably keeps a selection honest, and it is also what makes the decision survive the people who made it.

The platform decision hides the real cost

License price is the visible number. The cost that moves is implementation and the cost of change afterward: whether your own administrator can make a routine plan change, or whether every change becomes a professional services request. A platform that is cheaper to license and more expensive to live in is a bad trade that selections routinely make.

How Lanshore delivers it

  1. 1

    Gather requirements function by function

    We interview sales operations, finance, payroll, IT and a sample of comp administrators separately, then reconcile what they asked for into one list with the conflicts visible rather than smoothed over. Plan complexity, payee count, data sources and integration points are documented, because they drive both fit and implementation cost.

  2. 2

    Agree the weighted framework before any vendor presents

    Criteria and weights are set and signed off first: plan expressibility, crediting model, integration, reporting and audit, administrator self-sufficiency, support model, and total cost over a realistic horizon. Nothing in the framework changes once demos begin, which is the point.

  3. 3

    Script the demos against your hardest plans

    We give each vendor the same scenarios drawn from your actual plans, including the components that break things, and ask them to show the configuration rather than the result. A vendor who needs custom logic to express one of your core rules has told you something a feature matrix will not.

  4. 4

    Score, shortlist, and write the recommendation down

    Scores are recorded against the agreed weights with the reasoning attached, gaps are documented rather than rounded away, and the output is a written recommendation to the steering committee that someone who was not in the room can follow.

  5. 5

    Support the negotiation and hand over a delivery plan

    We help test the commercial terms against what the evaluation found, particularly around implementation scope, support coverage and the cost of future plan changes. The selection ends in a delivery plan built from the same requirements, so the implementation starts from evidence rather than from a fresh discovery phase.

Get an assessment

Platforms we deliver on

Related case studies

Related: SPM consulting for complex compensation plans · Mid-market SPM implementation services · Sales commission recovery services

SPM Platform Selection and Evaluation: FAQ

Do you resell any of the platforms you would recommend?
No. Lanshore is a services firm. It implements and operates Varicent, Xactly, CaptivateIQ, SAP SuccessFactors Incentive Management, Anaplan, Salesforce Spiff, Performio, Akeron and Incentivate, and resells none of them, so platform recommendations are based on fit with your plans, data and team. Ask the same question of every advisor you talk to, and ask what they earn if you pick a particular product.
How long does an SPM platform selection take?
The evaluation itself is normally weeks rather than months, and the limiting factor is availability for requirements interviews and scripted demos rather than analysis time. What extends it is discovering during the evaluation that the plans themselves are undocumented, which is common and is worth the delay, because selecting a platform against plans nobody has written down is how the wrong one gets chosen.
Can you evaluate whether we should keep the platform we have?
Yes, and staying is a legitimate outcome. The same scored framework applies, with your current system entered as a candidate. Often the finding is that the platform can express the plans and the problem is how it was configured, in which case a rebuild in place costs far less than a migration. We will say so rather than produce a recommendation to move.
What should a demo actually test?
Your own hardest plan components, scripted identically for every vendor, with the configuration shown rather than the output. Multi-level crediting, overlapping territories and overlays, retroactive quota changes, restatements, draws and clawbacks. Also ask each vendor to make a plan change live in the demo, because the cost of change afterward is usually larger than the difference in license price.
What do we own at the end of the evaluation?
The requirements by function, the agreed weighted framework, the scores with the reasoning, the documented gaps for each candidate, and a written recommendation. That package is what lets the decision be explained to a board or an auditor later, and it is yours whether or not Lanshore does the implementation.

Talk to Lanshore

A 30-minute call. We look at your plans, your systems, and where this would change your comp operations first.

832-466-8069Book a call