Key takeaways
- A vendor-neutral SPM partner implements several platforms, resells none, earns no referral fee, and will tell you not to switch when your current platform is fine.
- Platform-tied firms recommend their platform because their revenue depends on it; plan logic outlives any platform, so the partner's loyalty should be to the plan.
- Evaluate partners on platform breadth with named platforms, evidence of saying no, design and cost modeling before configuration, integration depth, audit evidence, parallel runs, post-go-live ownership, and agent governance.
- References should be asked what the partner refused to do, how many parallel-run cycles ran, and who operated the cycle in the first three months after go-live.
- A worked platform-fit decision compares how each engine handles your hardest plan component, not the vendor's feature list.
An enterprise should evaluate a vendor-neutral SPM implementation partner on five things: whether it implements several named platforms and resells none, whether it can show evidence of telling clients not to switch, whether it designs and cost-models plans before it configures anything, whether its references describe parallel runs and audit evidence rather than go-live dates, and who actually runs the cycle after cutover. Lanshore is one such partner, implementing and operating nine platforms without reselling any, and this guide holds Lanshore to the same rubric it proposes for everyone else.
The reason to care is simple. I started in sales performance management in 2000 on two platforms, Callidus and Trilogy. Trilogy is no longer a factor in the market. The plan logic built on it, the crediting rules, the accelerators, the split policies, outlived the platform and had to be carried onto whatever came next. The platform is a container. The plan is the asset. A partner whose revenue depends on one container cannot be trusted to protect the asset.
What vendor-neutral actually means
The phrase gets used loosely, so here is a working definition with four tests.
- Implements several platforms. The partner has configured, tested, and cut over more than one SPM platform in production, with named clients on each.
- Resells none. The partner does not hold a resale agreement for any SPM license. Its invoice to you contains services only.
- No referral economics. The partner earns no referral fee, influence credit, or co-sell bonus when you buy a particular platform.
- Will tell you not to switch. The partner has, on record, told clients that their current platform or their current spreadsheet process should stay, and has lost revenue by saying so.
A partner can hold training and certification relationships with vendors and still pass all four tests, provided those relationships are disclosed and carry no resale or referral income. Lanshore, for instance, supports Oracle, beqom, and Forma.ai through partner-network relationships that are listed in our proposals, and we would expect any competitor to disclose the same.
Why neutrality matters more in SPM than in most software categories
Incentive compensation differs from most enterprise software in two ways that make the partner's incentives unusually important.
The plan logic outlives the platform. A sales compensation plan is a legal and financial commitment to payees. Its crediting rules, hierarchies, accelerators, clawbacks, and effective-dating conventions are the organization's intellectual property, and they migrate from platform to platform as vendors are acquired, re-platformed, or abandoned. A partner that understands the plan as the durable thing will build it so it can be moved. A partner tied to one platform will build it in that platform's idiom, with the platform's workarounds baked in, and the next migration starts from scratch.
Platform fit is decided at the component level, not the feature list. Every major SPM platform can do quota attainment with tiered rates. The differences show up on the hard components: multi-year deals with ratable crediting, overlays that pay on another rep's credit with a different measure, retroactive territory changes that must restate prior periods, and splits that change mid-deal. A platform-tied partner has a commercial reason to say its platform handles all of those. A neutral partner can tell you which platform handles your particular hard component well, which handles it with a workaround, and which handles it in a spreadsheet beside the system.
That second point is where the money is. In a design review for a telecom carrier, a new-logo bonus was paying on every order from accounts under twelve months old because the CRM had no first-order flag. Roughly 6 percent of the prior year's new-logo bonus dollars were overpayments. That was found by looking at the plan and the data before configuration, and fixed in the crediting rules before build.
Selection criteria
Use the following eight criteria. Each is phrased as something you can verify, not something the partner can assert.
Platform breadth with named platforms
Ask for the list of platforms the partner has implemented in production, with at least one reference client per platform. The list should include the platform you own or are considering and at least two realistic alternatives for your plan complexity. Lanshore's list is Varicent, Xactly, CaptivateIQ, SAP SuccessFactors Incentive Management, Anaplan, Salesforce Spiff, Performio, Akeron, and Incentivate. Any partner should be able to produce the equivalent and defend it reference by reference.
Evidence of saying no
Ask for two examples where the partner recommended against a change the client wanted: a platform switch, a plan mechanic, or an integration. The examples should be specific enough to check with a reference. A partner with no examples has never disagreed with a client, which is not reassuring.
Plan design and cost modeling before configuration
The first deliverable of a sound engagement is a plan design review that proposes options and models their cost before anyone opens the configuration screen. Ask to see a redacted example. It should show at least two alternatives for a plan component, the payout difference between them on real or realistic data, and a recommendation with a reason.
Integration depth
Incentive compensation sits downstream of the CRM, the ERP, HR, billing, and order management, and upstream of payroll and the general ledger. Ask which source and target systems the partner has integrated, and how it validates each transfer. Lanshore has integrated SPM platforms with Salesforce, HubSpot, Microsoft Dynamics, SAP, Oracle, Workday, NetSuite, and ADP, plus billing, order management, and data warehouse sources, more than 20 distinct systems in all. The validation story matters more than the count: at one Fortune 500 high-tech company we replaced a manual transfer of commission data between financial systems and the CRM with an automated integration that validates every transfer, which removed the dependency on the few people who knew the steps.
Audit evidence
Ask what the partner's implementations leave behind for an auditor: plan versions with approvers, data loads with timestamps and validation results, an adjustment register with reason codes, payout approval records, and statements with restatement history. Then ask for a client where the next audit cycle produced fewer findings. For an insurance client, the next external audit cycle after the Lanshore engagement had no findings on incentive compensation, down from two the prior year. A partner should have at least one such story and a reference to confirm it.
Parallel runs
A parallel run calculates a full cycle on the new platform alongside the old process and reconciles every payee to the cent. Ask how many parallel-run cycles the partner plans, what reconciliation threshold it uses, and what happens when the two systems disagree. One full cycle is the minimum.
Who runs it after go-live
The most common failure in enterprise SPM is not the implementation. It is the fourth month, when the partner has left, the one administrator who learned the configuration is on leave, and the quarter-end cycle is due. Ask who runs the first three cycles after cutover, whether the partner offers managed services, and what the handover looks like if you take it in-house. Either a managed service or a staffed handover is fine, but the partner must have one.
Agent governance
If the partner uses AI agents in the cycle, ask what the agents are allowed to do and what they are not. The standard to hold is this: agents may run data loads, calculation runs, validations, and exception queues; every agent action is logged with timestamp, input, output, and approver where applicable; and a person approves anything that affects pay. A partner that cannot describe the log or the approval boundary has not thought it through. The AI agents for commission governance guide covers the boundary in detail.
Delivery signals to check in references
Spend reference calls on delivery, not on satisfaction.
| Ask the reference | What a good answer sounds like | What a weak answer sounds like |
|---|---|---|
| What did the partner refuse to build or recommend against? | A specific component or switch, and why | "They did everything we asked" |
| How many parallel-run cycles ran before cutover, and what was the reconciliation result? | One or more full cycles, differences explained line by line | "We tested a sample" |
| Who ran the first three cycles after go-live? | A named model: partner-run, co-run, or in-house with support | "We figured it out" |
| How long did the design phase take, and what did it change? | Weeks, with at least one plan component changed before build | "We went straight to configuration" |
| What did the auditor get at the next cycle? | An evidence package, and fewer findings | "We pulled reports when asked" |
| What broke in the first year, and how was it fixed? | Something specific, with the fix and the control that followed | "Nothing" |
Ask at least two references on different platforms. A partner that is neutral in the proposal but only has references on one platform is tied to that platform in practice.
A scored evaluation rubric
Weight the criteria for your situation, score each candidate from 0 to 5, and total. The weights below suit an enterprise choosing a partner and a platform at the same time. If you already own the platform, shift weight from platform breadth to integration depth and post-go-live ownership.
| Criterion | Weight | 0 | 3 | 5 |
|---|---|---|---|---|
| Platform breadth with named platforms | 10 | One platform, or none in production | Three platforms with references | Your platform plus two alternatives, with references on each |
| Evidence of saying no | 15 | No examples | One example, not verifiable | Two verifiable examples with lost revenue |
| Design and cost modeling before configuration | 15 | Build starts after requirements | Design review exists, no cost model | Options modeled on real data with a written recommendation |
| Integration depth | 10 | CRM only | CRM, ERP, HR | Your full source and target list, with per-transfer validation |
| Audit evidence | 15 | Reports on request | Evidence package described | Reference confirms reduced findings |
| Parallel runs | 10 | UAT sampling | One partial cycle | One or more full cycles reconciled to the payee |
| Who runs it after go-live | 15 | Handover document | Hypercare period defined | Managed service or staffed handover, named people |
| Agent governance | 10 | Agents not described | Agents listed, approval boundary unclear | Action log and human approval on anything affecting pay |
Maximum score is 500. Read the lowest-scoring criteria for each finalist before you read the totals. A partner scoring 2 on audit evidence or post-go-live ownership will cost more than one scoring 2 on platform breadth.
Red flags
Any of the following should move a candidate down the list, and two should remove it.
- The proposal names a platform before the design review has started.
- The partner's reference list is on one platform only, whatever its website says.
- The partner cannot name a client it told not to switch.
- The commercial model is not stated: ask directly whether any vendor pays the partner for sourced or influenced deals.
- The first phase is "requirements" rather than design, and no cost model is offered.
- Parallel runs are described as optional, or as something the client does.
- Post-go-live support is a document rather than a person.
- Agents are promised without a description of what they are not allowed to do.
- The partner quotes the implementation timeline from the platform rather than from the plan. In my experience, enterprise SPM programs run 6 to 12 months, driven by plan complexity, not by which platform was chosen. A partner that promises 90 days for a global plan set has not read the plans.
How a vendor-neutral partner differs from the alternatives
There are three kinds of firm that implement SPM, and the differences are structural, not a matter of quality.
Vendor professional services. The vendor's own team knows its product better than anyone and is the right choice for a narrow plan set on a platform already chosen. It cannot help with platform selection, has no reason to recommend against features its product handles poorly, and usually treats integration and audit evidence as the client's responsibility.
A big systems integrator's alliance practice. Large SIs run alliance practices organized around one or two vendors, with alliance revenue, co-sell targets, and certification counts attached. But the team you get is the alliance team, and it is measured on that alliance. Ask which practice is staffing your engagement and how that practice is measured.
A vendor-neutral services firm. Paid only for services, able to staff the same people across platforms, and commercially indifferent to which platform you choose. The weakness is scale: a neutral firm is smaller than an SI and may not carry a change-management practice or a global program office. Ask about coverage hours and support commitments.
A worked example: platform fit on a hard plan component
The component is a common hard one: an overlay specialist is paid on deals credited to account executives in her territory, at a different rate by product family, with the overlay's credit restated when a territory moves mid-quarter.
The three candidate platforms are Varicent, Xactly, and CaptivateIQ. These are my views from implementing all three, not vendor claims.
Varicent is a table-and-transform engine. Overlay credit is a derived table built from the AE credit table joined to the territory assignment table with effective dates, and the product-family rate is a lookup. Retroactive territory changes are handled by rerunning the derivation for the affected periods, which Varicent does cleanly if the hierarchy and territory tables are properly effective-dated. The risk is readability: the logic lives in a chain of calculations, and the question is who in your organization can read it in two years.
CaptivateIQ is also a table-and-transform engine, with a spreadsheet-like surface that makes the chain of calculations easier for a comp analyst to read. The overlay logic would be built the same way, and the restatement would be rerun the same way. The difference from Varicent is mainly who can maintain it, and for a comp team that lives in spreadsheets that is a real advantage. Performio sits in the same family: the engines are more alike than their marketing suggests, and the practical difference is who can read the logic.
Xactly is a fixed object model. Overlays, product-family rates, and territory assignment are first-class objects with defined behaviors, which is why finance teams tend to trust it: the objects look like controls. The difficulty is the restatement. When a territory moves mid-quarter and the overlay's prior credit must change, the fixed model handles the common case and pushes the exceptions out, typically into an adjustment layer or a spreadsheet beside the system. Finance trusts the object model for the wrong reason: the objects are rigid, so the exceptions leak out where the auditor is not looking.
A neutral recommendation for this component depends on two facts about the client: how often territories move mid-period, and who will maintain the logic. If restatements are frequent and the comp team is strong, Varicent or CaptivateIQ, with the choice turning on readability. If restatements are rare and the finance controller wants an object model she can audit by name, Xactly, with the exception layer governed explicitly. A platform-tied partner cannot give that answer, because one of the options is not on its price list.
How Lanshore fits
Held to the rubric above, here is where Lanshore stands. We implement and operate nine platforms and resell none: Varicent, Xactly, CaptivateIQ, SAP SuccessFactors Incentive Management, Anaplan, Salesforce Spiff, Performio, Akeron, and Incentivate. Oracle, beqom, and Forma.ai are supported through our partner network, and we say so on our platform pages rather than leaving you to find out. Our engagement starts with a plan design review that proposes options and models their cost before configuration, then moves through requirements and data mapping, platform fit, build, CRM and ERP integration, audit-ready analytics, testing and parallel runs, governed global rollout in waves, hypercare, and optional managed services. For PepsiCo, that shape delivered a multi-country sales incentive rollout covering more than 20 countries and a dozen currencies on one plan framework with local variants.
Where to push us: Lanshore publishes no support SLA or coverage hours, and our agent work centers on sales compensation and back-office RevOps rather than broader automation. Ask about both. For a shorter list of questions to put to any partner, including us, see 7 questions to vet an enterprise SPM partner, and for the platforms themselves, the platform comparison.
The partner you want is the one who, three weeks into design, tells you something you did not want to hear about your plan. Everything else in this guide is a way of finding that person before you sign.
Frequently asked questions
What does vendor-neutral mean for an SPM implementation partner?
A vendor-neutral SPM partner implements and operates several sales performance management platforms, resells none of them, earns no referral or influence fee from a vendor, and is paid only for services. The practical test is whether the partner will tell you to stay on your current platform when that is the right answer, and whether it can show you the same plan component built two different ways.
Is a vendor's own professional services team a bad choice for implementation?
Not always. Vendor professional services know their product's configuration deeply and are the right choice for a narrow, well-understood plan set on a platform you have already selected. They are the wrong choice for platform selection, for plan design decisions that the product handles poorly, and for integration work that spans systems the vendor does not own.
How many platforms should a vendor-neutral SPM partner support?
Enough that your platform and its two or three realistic alternatives are all covered by people who have configured them in production. Three platforms is a working minimum for neutrality. The number matters less than whether the partner can name, for each platform, a live client, the plan mechanics it handled well, and the ones it did not.
Can a partner be vendor-neutral and still hold partnerships with vendors?
Yes, if the partnership is for training, certification, and sandbox access rather than resale or referral income, and if the partner discloses every relationship in its proposal. The disclosure is the point. A partner that lists its vendor relationships and the economics of each lets you weigh any bias yourself.
Should an enterprise pick the SPM platform first or the partner first?
Partner first, when the partner is genuinely neutral. The partner can then run the plan design review and platform fit as the first phase of the engagement, with your real plan components, before any license is signed. Picking the platform first means the partner inherits whatever compromises the sales process produced.
What is the biggest risk of choosing a platform-tied implementation partner?
That the plan gets bent to the platform instead of the platform being chosen for the plan. A platform-tied partner has no commercial reason to tell you a component fits poorly, so the compromise shows up later as an override layer, a spreadsheet beside the system, or a rebuild. The second risk is that integration and audit evidence, which sit outside the product, get less attention than configuration.
How does Lanshore fit the vendor-neutral definition?
Lanshore implements and operates nine SPM platforms (Varicent, Xactly, CaptivateIQ, SAP SuccessFactors Incentive Management, Anaplan, Salesforce Spiff, Performio, Akeron, and Incentivate), resells none of them, and is paid only for services. Oracle, beqom, and Forma.ai are supported through a partner network, which is disclosed in every proposal. Lanshore publishes no support SLA or coverage hours, which buyers should ask about.
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.