Blog

Blue Horizons Group: 10 Questions to Ask an ICM Partner

blog hero logo

Selecting an incentive compensation management implementation partner is an unusually high-stakes undertaking, and with good reason: an ICM platform is only as good as what’s built inside it. Someone has to configure your plans, your crediting rules, your payees, your data, and your business logic for it to work correctly. When this complex process is done poorly, you’re producing incorrect paychecks that directly affect your reps, increase your legal exposure, and erode trust.

An implementation partner must deeply understand how your incentive plans work in practice and have profound experience in programming your solution so they can build a scalable model that meets your needs.

But how can you identify that partner? How can you engage in a sales conversation and identify who is, as they say, blowing sunshine up your spreadsheet?

To assist you in this critical process, we have put together the questions you need to ask when interviewing your finalists. We’ve outlined what a good answer looks like and described caution flags so you can spot them in the wild.

  1. How many implementations have you completed on this specific platform, and in the last 18 months specifically?

Total count matters less than recent count. ICM platforms release meaningful updates frequently, so a firm that completed 40 Varicent implementations but none in the last two years may be working from outdated knowledge. You want recency, not just volume.

  • A credible answer is specific. If they hesitate or give a range, that’s a flag.
  • Ask what percentage of their current book of business is on this platform. A firm that does one or two implementations per year on your platform is a different animal than one for whom it’s a core competency.
  • Watch for partners who lump related platforms together to pad the number. Varicent experience doesn’t transfer cleanly to Xactly, and vice versa.
  1. Do you employ in-house sales compensation practitioners who have administered comp programs, or only technical configurators?

This is one of the most important questions on the list. A technical configurator can build what you hand them. A practitioner knows whether what you handed them is going to cause problems when it hits a real payroll cycle.

  • The best implementation partners have at least one person on staff who has sat in the comp admin seat: managed disputes, processed adjustments, run month-end close, fielded calls from reps who think they were shorted. That lived experience changes how they configure.
  • A strong answer names specific people and describes their practitioner backgrounds. A weak answer talks about “deep domain expertise” without any specifics.
  • If they say “our configurators have learned comp through doing implementations,” that’s not the same thing.
  1. Who specifically will be on our project, and what are their individual credentials and relevant implementation counts?
  • Ask for a staffing plan with named resources and roles.
  • Ask who the project manager is and whether they have PMP certification or equivalent structured methodology training.
  • Find out who has final authority over configuration decisions. Is there a senior architect reviewing the work or is a junior configurator operating without oversight?
  1. Do you use subcontractors or offshore resources? If so, in what capacity and for what portions of the work?

The use of offshore resources or subcontractors is common, but you need to know upfront because it affects communication cadence, time zone overlap, escalation paths, and accountability.

  • A straight answer is fine. Evasion is not. If a partner is reluctant to tell you their staffing model, that’s a problem.
  • Ask whether subcontractors are bound by the same contractual obligations as the partner’s direct staff: NDA, data handling, deliverable standards.
  • Communication cadence can easily suffer when dealing directly with offshore resources. Ask how the partner will mitigate the scheduling risks associated with that staffing model.
  1. Walk me through your implementation methodology from requirements through go-live. How is it documented and how do you keep us accountable to it?

A credible implementation partner has a named methodology, documented phases, and clear handoff criteria between stages.

  • You want to hear named phases (discovery, requirements, design, build, testing, UAT, go-live, hypercare), defined deliverables at each phase gate, and documented sign-off criteria before moving to the next phase.
  • Ask specifically what happens if requirements are incomplete or disputed before the build phase begins. Strong partners hold the line; weak ones build anyway and deal with the fallout later.
  • Ask how scope changes are documented and priced mid-project. Change order processes should be explicit and fast, not a source of ongoing negotiation.
  • “How do you keep us accountable” is a leading question. It’s asking whether they have the spine to tell you when your team is the bottleneck. A good partner will name specific mechanisms: RAID logs, weekly status meetings, escalation paths, decision logs.
  1. What does your testing methodology look like? Who is responsible for UAT, and how do you structure it?

Testing is where most ICM projects fall apart. Insufficient testing before go-live is the single most common cause of payroll errors post-launch.

  • Ask whether they provide a formal test script library or whether they expect your team to develop test cases from scratch. A mature partner has a starting library of scenarios that gets customized to your plan design.
  • Clarify who is responsible for what: the partner should own unit testing (confirming the configuration works as built). System integration testing will likely be a shared responsibility. UAT belongs to your business users, but the partner should help you structure it, not hand you a blank spreadsheet and say “go test.”
  • Ask how defects are tracked, prioritized, and resolved during UAT. Is there a formal defect log? What’s the criteria for a go/no-go decision? This is a bit of a trick question, because the correct answer from the implementation partner should be: “You tell us. How are you, Customer, going to manage this? We know best practices, but we cannot impose the methodology.”
  1. Do you offer plan design advisory as part of this engagement, or only technical configuration?

Many implementation partners will configure exactly what you hand them, including a broken plan, because it’s not their job to tell you it’s broken. That’s not malicious; good project management requires scope management. But the result is the same: you go live with a plan that creates unintended payouts, disputes, or administrative nightmares.

  • A strong answer distinguishes clearly between the two services and offers to scope plan design advisory separately if it’s not included.
  • The most sophisticated partners will do a preliminary plan review as part of scoping and flag obvious design risks before the SOW is signed.
  1. What is your point of view on governance and controls? Will you help us build an audit trail and a dispute/exception process?

If your implementation partner employs in-house sales compensation practitioners, rest assured that they have a very strong point of view on governance and controls, but most clients don’t realize they will need it until after the build is complete. The time to build audit trails, exception workflows, and dispute resolution processes into the system is during the resolution of the SOW, not after. A partner who is looking out for you will suggest these as you put together the agreement.

  • A sophisticated partner wants you to include workflows for payout approval, manual adjustment documentation, and inquiry management; plan document distribution and acceptance, and audit log configuration into the build.
  1. How do you document the configuration in a way our internal team and future partners can actually use?

Configuration documentation is one of the most underdelivered items in ICM implementations. Most clients discover the gap when they try to make a change two years later and have no record of why something was built the way it was.

  • You want: a technical design document that maps each plan component to its configuration logic, a data dictionary for any custom fields or tables, documented calculation logic in plain language alongside the technical build, and a change log.
  • Ask to see a redacted sample from a previous client. If they don’t have one to show you, that’s your answer.
  • Insist that documentation be a named project deliverable with a defined format.
  1. Can you provide three references from comparable implementations (similar platform, similar participant count, similar plan complexity) in the last two years?
  • Ask references specifically: Did the project come in on time? On budget? Were the people who were presented in the sales process actually the ones who did the work? Would you use this partner again?
  • Ask whether you can speak with someone below the project sponsor level, such as a comp admin or system admin who used the configured system day-to-day. Sponsors often have a different experience than the people running month-end close.
  • Ask about challenges and issues that popped up during the implementation. How were they resolved? Was the partner transparent during that resolution?

Bonus Question

“What do you need from us to make this successful — and what happens if we can’t provide it?”

Most implementation failures can be traced to unavailable subject matter experts, data that isn’t clean, plan designs that keep changing, and stakeholders who won’t make decisions. A good partner will tell you this directly and have a plan for navigating it. A partner who says “we just need your time and cooperation” is not being straight with you.

Want to discuss further? Let us know at marketing@bluehorizonsgroup.com!

Questions to Ask

Elizabeth has over twenty years experience in sales compensation management, including over ten years overseeing incentives for a Fortune 500 company. She also brings over thirty years experience in overall rewards management across a variety of industries. Her strong background in solutions design and process improvement has helped her consistently establish effective and productive relationships with her customers.

Share This Information

FacebookXLinkedInWhatsAppTumblrPinterestEmail