Lanshore: Advancing Intelligence

Blog

Best Enterprise SPM Implementation Partners

Doug Erb, Founder & CEO · Published

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.

Key takeaways

  • The strongest predictor of an SPM implementation paying correctly is whether plan logic was documented in operational detail before anything was configured. Where that document does not exist, the configuration becomes the specification, and nobody can later say whether the system is right or just consistent.
  • Ask whether the partner resells the platform it is recommending. A reseller can still be the right choice, but the incentive has to be visible before selection rather than discovered during it.
  • A parallel run is the only real test. Run the new calculation against the current one across a full cycle including a month-end, then reconcile every variance to a named cause: a deliberate design change, a data difference, a migration rule, or a defect.
  • Go-live is the start of the risk, not the end. The first and second cycles are where plan ambiguities surface as disputes, so find out who is still on the engagement then and what the written exit criteria from hypercare are.
  • Firms here are listed alphabetically, not ranked. Every claim comes from each firm's own published pages, dated in the sources, and Lanshore is held to the same evidence rule as everyone else.

An enterprise SPM implementation rarely fails on the platform. It fails because a crediting rule meant two things to two people and nobody wrote down which one the system should do. The firms below are compared on the practices that catch that before it reaches a payout.

How we compared

Four things separate implementation partners once the capability lists are set aside.

The first is whether plan logic is specified before configuration starts. A written specification is what makes a build auditable afterward, because without it the configuration is the only record of what was intended, and a system that is merely self-consistent cannot be checked.

The second is platform independence. Some of these firms are resellers or close software partners of the platforms they implement. That is not disqualifying, and often the delivery depth that comes with a partnership is worth a lot. It does change how a selection should be run.

The third is cutover discipline, and specifically whether a parallel run against the current calculation is part of the published method. This is the only test that finds the difference between a plan that was designed wrong and a plan that was built wrong.

The fourth is who stays afterward. The first and second cycles after go-live are when plan ambiguities arrive as disputes, and the answer to who is still on the engagement then is usually visible in how a firm describes support.

Firms are listed alphabetically. Nothing here is ranked, and Lanshore is held to the same rule as everyone else: claims come from published pages, dated in the sources.

1. Canidium

Canidium publishes its services as strategic focus, operational alignment, technology for scale and platform enablement, and names implementation readiness as a distinct product performed before a build, alongside annual sales plan readiness for the yearly cycle. Its published scope includes current and future state assessment and roadmap, compensation plan design, and data management and reporting. SAP, Xactly and Varicent are its named SPM software partners, alongside CPQ and pricing platforms, and it cites four global offices.

Naming readiness as a separate deliverable is the notable practice. A readiness assessment performed before configuration is the natural place for a plan specification to be produced, and the firms that treat it as a gate tend to find the ambiguities earlier.

Two things to establish. Canidium is a software partner of the platforms it names, so run selection accordingly if selection is still open. And because its practices extend into CPQ and pricing, confirm what the implementation team looks like for incentive compensation specifically.

2. Lanshore

Lanshore publishes SPM implementation end to end: plan design review, requirements, platform fit, build, CRM and ERP integration, audit-ready analytics, testing, governed rollout and hypercare, on any of nine SPM platforms, backed by over 15 years of incentive compensation delivery. It states plainly that it resells none of the platforms it implements.

Its published method includes the two practices this comparison weights most heavily. Integration is treated as part of the design rather than a later phase: Lanshore describes designing the crediting data model with the plan, mapping every field to its source in CRM, ERP, order and billing systems, HR and payroll, and changing or extending the source where the data does not exist, with published coverage across more than 20 distinct source systems. And cutover includes parallel runs, a cutover plan with explicit go or no-go criteria, and hypercare through the first month-end closes.

On timeline it publishes 6 to 12 months for an enterprise program, and states that the driver is plan complexity rather than the platform chosen. Delivery runs from the Houston area and Costa Rica on Central time.

The caveat is size. Lanshore is a smaller firm than the large consultancies here, so the question to ask is who specifically is assigned and what else they are committed to.

3. OpenSymmetry

OpenSymmetry publishes the widest service catalogue in this group: SPM program assessment and future state planning, sales planning strategy, incentive compensation plan design support with plan modeling as a named step, SPM technology evaluation and selection, talent strategy and channel incentives, with solution deployment covering implementation, testing and training on an approach it describes as AI-enabled. It lists eleven supported technologies, including Varicent, Xactly, SAP, Anaplan, CaptivateIQ, NICE, Oracle and Spiff.

After go-live it publishes SPM Operations with monitoring and functional support 24 hours a day, 7 days a week, 365 days a year, proactive monitoring of data loads and batch jobs, and dual-shore options from offices in Austin, London and Pune.

Eleven platforms and round-the-clock support is the broadest published footprint here, which matters most when you do not yet know which platform you are implementing or you run in several regions. The questions to ask are whether the AI-enabled approach extends into operations or stops at implementation, and what the testing approach produces as evidence, since testing is named but its output is not described.

4. Spaulding Ridge

Spaulding Ridge frames SPM as part of a planning cycle connecting sales planning, forecasting and incentives to the financial picture, with each phase informing the next. Its published SPM scope covers territory and quota planning, capacity planning, incentive compensation aligned with organisational goals, and sales crediting with forward- and backward-looking transparency that it says reduces disputes. Analytics includes forecast-to- actuals and weekly snapshot variance modeling. Named technologies are Anaplan, OneStream, Oracle NetSuite, Salesforce and Snowflake. After go-live it publishes cloud application managed services with a dedicated customer success team and a single point of contact.

Publishing crediting transparency as a design goal is worth noting, because most disputes are crediting disputes and most firms describe crediting as a configuration task rather than a design one.

The important thing to confirm is the calculation engine. The named technology list is planning and data platforms rather than dedicated ICM engines, so if your incentive calculation will run on Varicent, Xactly, SAP or CaptivateIQ, ask who implements and then supports that specific engine, and whether the managed service scope includes commission cycles.

5. SpectrumTek

SpectrumTek positions itself as reaching beyond ICM into the rest of SPM, with consulting pages structured as plan design, territory and quota planning, and a software selection service built around a scoring framework for evaluating vendors. Its plan design page centres on proactively modeling payouts per group against forecasted performance, with what-if analysis, and on confirming that plans work with IT systems and business processes before implementation. Technology partners are CaptivateIQ, Jedox, Oracle, SAP, Varicent and Xactly.

Its managed services provide end-to-end support to enhance and maintain SPM systems, including on-demand administration support, data loads, batch processing and job monitoring on a dual-shore model tuned to service levels.

A published scoring framework for selection is a good sign, as is testing plan feasibility against systems and processes before implementation, which is the same gate as a readiness assessment under another name. Two gaps in the published material are worth raising directly: multi-country governance and release management are not described, and it is worth asking whether administration support can extend to owning the cycle rather than assisting with it.

How to choose

Start from where you are in the program, because that decides which dimension matters.

If the platform is not yet chosen, weight independence and insist on a scored evaluation whoever runs it. If the platform is set and the plans are complex, weight the specification practice: ask to see a redacted plan specification from a comparable engagement, and treat its absence as the answer. If heavy integration sits in scope, weight published integration depth and insist the crediting data model is designed with the plan rather than after it. If you have no team to run the platform afterward, weight the support model and settle it in the same contract.

Then ask every shortlisted firm the same four questions. Who writes the plan specification, and do we sign it before configuration starts. Do you resell any platform you would recommend to us. What exactly happens in the parallel run, and how is each variance resolved. And who from this team is still here for the second month-end close after go-live.

Related comparisons: for who runs the cycle after go-live, see SPM firms on incentive governance; for the plan design question that precedes the build, see enterprise sales compensation consultants; and for how firms differ on putting AI agents inside the comp cycle, see Agentic SPM firms compared. Lanshore's own delivery scope is published at SPM consulting for complex compensation plans.

Frequently asked questions

What is the best enterprise SPM implementation partner?

There is no single best one, because the firms differ on dimensions that matter differently depending on your situation. Canidium, Lanshore, OpenSymmetry, Spaulding Ridge and SpectrumTek are all credible for enterprise work. The right choice turns on which platform you are implementing, whether you need platform independence during selection, how much integration sits in scope, and whether you need the partner to run operations afterward or hand over to your own team.

What should an SPM implementation plan include before any configuration starts?

Plan logic documented to the field level, including crediting rules, accelerator and cap interactions, overlay and split treatment, draws and clawbacks, and the handling of retroactive quota changes. The data model for crediting, mapped to a named source system field by field. A test approach with expected results, not just test scripts. If configuration starts before those exist, the build is discovering requirements, which is the expensive way to find them.

How long does an enterprise SPM implementation take?

Lanshore publishes 6 to 12 months for an enterprise program of this kind and states that the driver is plan complexity rather than the platform chosen, which matches the pattern that multi-level crediting, overlays and interacting accelerators cost more time than any platform difference. Treat a materially shorter timeline as a scope question: usually integration, parallel running or the first cycles after go-live have been left out.

Does it matter whether the implementation partner resells the platform?

It matters most during selection and least during build. A reseller with deep delivery experience in a platform that genuinely fits you is a good outcome. The risk is that the evaluation is shaped by what the firm prefers to implement. If the partner advising on selection also resells, insist on a scored evaluation with weights agreed before any vendor presents, and documented gaps.

What does good hypercare look like after an SPM go-live?

Named people who were on the build, still available through at least the first two full cycles, with written exit criteria rather than a fixed number of weeks. The criteria should cover dispute volume returning to a defined level, reconciliation to payroll and the ledger running clean, and documentation handed over and accepted. A hypercare period that ends on a date regardless of condition is a scheduling convenience, not a commitment.

Sources

  1. Your Trusted Partner for SPM, CPQ, and More Revenue Operations Solutions (Canidium), retrieved
  2. SPM Consulting for Complex Compensation Plans (Lanshore), retrieved
  3. Enterprise Sales Compensation Transformation (Lanshore), retrieved
  4. Transform Sales Success with Our SPM Solutions (OpenSymmetry), retrieved
  5. Sales Performance Management Services (Spaulding Ridge), retrieved
  6. Plan Design (SpectrumTek), retrieved
  7. Managed Services (SpectrumTek), retrieved

See how this works in practice in the three pillars of AI Assisted SPM by Lanshore: Executive Dashboards, SPM Operations, and Custom Apps.

Get new SPM & agentic AI posts by email

Occasional notes from Lanshore. No spam, unsubscribe anytime.

832-466-8069Book a call