7 Questions to Vet an Enterprise SPM Partner

Large enterprises should vet an SPM consulting partner on seven things: platform independence, who runs operations after go-live, depth of CRM and ERP integration, governance of incentive plans across countries, the audit evidence they produce, where AI acts versus where humans approve, and who actually does the work. Ask each as an open question and listen for specifics.

Why these seven questions

Global incentive programs fail in predictable places. Plans drift apart by region, data arrives from systems nobody fully controls, and the people who understand the calculation logic leave. A partner's sales presentation rarely touches any of that. The questions below are built to make a partner describe their actual working method, which you can then test with references and write into the statement of work.

For each question you will find why it matters, what a good answer sounds like, and a red flag. If you are comparing named firms, our comparison of SPM service partners covers the market, and our SPM consulting for complex compensation plans page explains how Lanshore approaches the same work.

1. Which platforms do you implement, and when would you tell us not to switch?

Why it matters. Many SPM partners are certified on one platform, and their delivery business depends on it. That is not a problem for a client who has already chosen, but it is a problem for an enterprise deciding whether to stay, extend, or migrate. The partner's recommendation should not be shaped by which product they can sell services against.

What a good answer sounds like. The partner names the platforms they have delivered on, explains how they would assess your current system against your plan complexity, data volumes, and IT estate, and can describe a situation where the right advice was to keep the existing platform and fix the configuration. They can explain hybrid patterns too, such as a planning platform for territories and quotas paired with a separate engine for commission calculation.

Red flag. Every assessment ends with the same platform, or the partner cannot describe a case where they recommended against a migration.

2. What happens after go-live, and who runs the monthly cycle?

Why it matters. Implementation is a project; commissions are a monthly operation that never stops. The first year after launch is when plan changes, reorganizations, and data issues pile up, and it is when many in-house teams discover they lack the platform skills to keep up. A partner whose involvement ends at go-live leaves you holding a system nobody fully understands.

What a good answer sounds like. The partner offers a defined operating model after launch: who runs data loads and calculation cycles, who handles exceptions, how plan changes are requested and tested, and what the service levels are. Lanshore, for example, runs comp operations as a managed service for a predictable monthly fee, with agents taking repetitive work and the team handling judgment calls (see SPM managed services).

Red flag. Post-launch support is described only as "hypercare" with an end date, or ongoing changes are handled through new change orders each time.

3. How deep does your CRM and ERP integration work go?

Why it matters. Commission accuracy depends on data the SPM platform does not own. Opportunity splits and bookings live in the CRM. Invoices, cash receipts, and returns live in the ERP. Hierarchies and employment dates live in the HR system. Many payout errors start in those feeds, not in the calculation formulas.

What a good answer sounds like. The partner talks about field-level mapping, validation on every transfer, handling of late or corrected transactions, effective dating, and reconciliation back to the source system. They can describe the tooling they use (native connectors, middleware, RPA, or direct APIs) and explain when each fits. One Lanshore engagement replaced a manual commission data link between financial systems and the CRM with an automated integration that validates every transfer, removing a dependency on the few people who knew the steps (case study).

Red flag. Integration is scoped as "the client provides a flat file," or the partner treats data as someone else's problem.

4. How do you govern incentive plans across countries and business units?

Why it matters. A global program is not one plan; it is a family of plans that share principles and differ by country, currency, role, and local rules. Without governance, regional variants drift, exceptions become precedents, and nobody can say which version of a plan was in force on a given date. In some countries, changes to variable pay also involve employee representatives. In Germany, for example, an establishment's works council has co-determination rights over remuneration principles, new or changed remuneration methods, and performance-related pay (Works Constitution Act, section 87).

What a good answer sounds like. The partner describes a plan governance structure: a global template with controlled local variations, a change approval path with named owners, effective-dated plan versions, plan documents and acknowledgments tracked per participant, and currency and proration rules that are documented rather than buried in formulas. They should be candid about where local legal review is needed and that it is your counsel's call, not theirs. Our guide to global incentive governance covers the structure in more depth.

Red flag. The partner proposes one global configuration with regional overrides added "as needed," with no versioning or ownership model.

In a multi-country rollout for PepsiCo, the governance model set global, regional, and local decision rights. Once regions owned their variants under published rules, override requests escalated to the global committee fell by more than half.

5. What will an auditor see when they test our commissions?

Why it matters. Commissions touch revenue recognition, payroll, and in public companies, financial controls testing. Commission expense also has to be accounted for correctly. Under US GAAP, ASC 340-40 (the cost guidance issued alongside ASC 606) requires sales commissions that are incremental costs of obtaining a customer contract to be capitalized and amortized when the company expects to recover them, with a practical expedient to expense them when the amortization period would be one year or less. IFRS 15 has an equivalent requirement. When an auditor asks how a specific payout was calculated, you need to answer from the system, not from someone's memory.

What a good answer sounds like. The partner can describe the evidence trail end to end: source transaction, crediting decision, rate applied, adjustments with approver and reason, and the final payout, all reproducible for a past period. They mention segregation of duties for plan changes and adjustments, and they have worked with internal audit or SOX teams before. In one engagement Lanshore extended an existing SPM setup with audit-ready calculation logic and transparent reporting for reps and finance, without replacing the systems in place (case study).

Red flag. "The platform has an audit log" is the whole answer. A log of who clicked what is not the same as a reproducible calculation.

6. Where do AI agents act, and where does a human approve?

Why it matters. AI is now part of many SPM conversations, and it can remove a lot of repetitive work: data loads, calculation runs, validations, exception triage, and answering rep questions about statements. But commissions are money with edge cases. An agent that sounds confident and gets a payout wrong does real damage to rep trust and to your controls.

What a good answer sounds like. The partner draws a clear line. Agents run defined, repeatable tasks and flag anomalies; humans keep plan design, approvals, and exceptions that need judgment; nothing that changes a payout reaches payroll without a named approver. Every agent action is logged with its timestamp, inputs, outputs, and approver, and that log can be exported for internal audit. The partner can also tell you which AI models the agents use, under whose accounts, and whether any provider may train on your data. Lanshore's SPM operations pillar is built on this model of logged agent work and human approval.

Red flag. The partner describes AI as "autonomous" without describing limits, or cannot show you what the audit trail looks like.

7. Who does the work, and what do we own when you leave?

Why it matters. The senior people in the sales meeting are not always the people on the project. And SPM programs often end up dependent on whoever configured them, which is exactly the risk you were trying to remove when you hired a partner.

What a good answer sounds like. The partner names the roles that will staff the engagement and their platform experience, explains where delivery teams are located (Lanshore, for example, delivers from the US and Latin America), and commits to documented configuration, documented code for anything custom, and training for your team. You own what they build, and you could hand it to another provider if you chose to.

Red flag. Key logic lives in partner-owned tools or undocumented scripts, or the answer to "who will be on the project" is "we'll staff it after signing."

Ask for references on exactly this point. Lanshore's references on staffing continuity and handover into managed services, including a mid-market SaaS client and a national telecom carrier, are available on request.

How to use the answers

Score each answer on specificity, not confidence. A good partner will describe mechanisms (owners, controls, evidence, tooling) and will volunteer the limits of what they do. Then test the claims: ask references the same questions, ask to see a redacted runbook or audit trail, and write the commitments into the statement of work.

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 has delivered SPM for 15+ years. It has supported global incentive programs spanning more than 20 countries and a dozen currencies, and single programs with more than 10,000 participants. If it helps to hear how we would answer these seven questions for your program, start with an assessment.

Frequently asked questions

What should large enterprises look for in an SPM consulting partner?

Look for platform independence, a clear operating model after go-live, real integration depth with CRM and ERP systems, experience governing incentive plans across countries, a concrete answer on audit evidence, defined human approval points for any AI, and named people with documented handover. Ask the partner to describe how they do each one, then confirm it with references.

Should an SPM partner be tied to one platform?

Not if you want an honest answer on platform fit. A partner that implements only one platform has a structural reason to recommend it. A platform-independent partner can tell you when to stay on your current system, when to extend it, and when a migration is justified, and can put that reasoning in writing.

Why does CRM and ERP integration matter so much for commissions?

Commissions are calculated from data that originates elsewhere: bookings and opportunity splits in the CRM, invoices and cash in the ERP, and people and hierarchy data in the HR system. If those feeds are late, unvalidated, or mapped incorrectly, a correct calculation engine still produces wrong payouts. That is why so many commission errors trace back to data rather than formulas.

How should an SPM partner use AI in commission processes?

AI agents can run repetitive work such as data loads, calculation runs, validations, and exception triage, but they should act inside defined limits, log every action with its inputs and outputs, and route anything that affects a payout to a named human approver. A partner should be able to show you that audit trail, not just describe it.

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