TL;DR
- Every comp program has moving variables. The programs that hold up are the ones that decide on purpose which ones to pin down and which to let float.
- Public-company controls add work no private-company timeline accounts for: audit trails, separation of duties, and reviews that run in parallel but never compress.
- Multi-currency payout design forces its own fix-or-float call: quota currency versus payout currency, and when the exchange rate gets locked.
- CX compensation breaks most of what an AE plan assumes: no simple commission rate, quotas that can run negative, data that doesn't live in the CRM, and adjustment policies with more nuance than any AE plan carries.
- Sprout Social picked its CX metrics deliberately, not by default. Which metrics matter less than the discipline behind picking them.
- The migration ran on a hard 90-day clock that started the day the contract was signed, because the comp cycle doesn't wait for the project plan.
Kimberly Fairchild, Senior Director of Sales Operations at Sprout Social, walked Sales Comp '26 through moving the company's entire comp program under a set of constraints that don't usually show up in the same migration story: a public company, hundreds of quota-carrying reps across AE and CS teams, payouts running through seven currencies, and a 90-day clock that started the moment the contract was signed. Jose Aleman, VP of GTM Excellence at Everstage, hosted.
Where Sprout Social started: managing a growing global sales organization with multiple compensation plans, currencies, and a monthly pay cycle, while relying on Excel for commission calculations and an ICM system for statements.
What "public company" adds to a migration
Being public adds requirements a private-company timeline never has to plan around: an in-depth security review, internal and external audit controls, detailed budgeting and forecasting, and calculations that have to be reconstructable after the fact, not just correct in the moment. None of that compresses under deadline pressure. It runs in parallel with everything else, and it holds the critical path.
CX compensation didn't make that January deployment. The team cut it from initial scope on purpose, and deployed it six months later, once the harder design work was ready.
The multi-currency problem, and the first fix-or-float call
Sprout Social’s reps sit in seven currencies, all paid out of one comp program, against an exchange rate that never sits still. The design question up front is quota currency versus payout currency, and when the rate actually locks in. Get that wrong and the math can be technically correct while a rep running the numbers themselves on the side swears the payout is off.
The same failure mode showed up everywhere else in the program, not just here: a calculation holds up on paper right up until a variable underneath it moves and nobody decided that was allowed to happen.
Fix it or float it
Every comp program's real design question, per the session: which moving variables do you pin down, and which do you let float, and who owns the ones you let float. Multi-currency raises that question first. By the time CX compensation comes up, it's no longer theoretical.
Comp for CX: the half without a playbook
CX comp covers customer success managers, renewal managers, solutions architects, and CX execs and ops leaders, and one plan design doesn't stretch across any of them. What breaks when a team tries to force it: no simple commission rate, quotas that come out as rates or negative numbers, data that can't be read directly from the CRM, and adjustment policies with more nuance than any AE plan carries.
The metrics decision
Sprout Social's CX comp runs on a small set of revenue-retention metrics, chosen deliberately over some more familiar ones in the category. The design principle mattered more than the metric list: pick ones your data can actually support, not the ones everyone else defaults to.
Renewal rate itself is retained revenue divided by available-to-renew, and available-to-renew moves throughout the period.
The data architecture underneath
Everything above runs through one pipeline: CRM to data lake to ICM. The comp team has to own every handoff in that chain, the session argued, not just the final output. Before the first CX payout run, get real answers from the data team about which of those inputs comp doesn't actually own yet. That's usually where the first errors show up.
Five decisions that made the build survivable
Solid bytes from the room
A few lines worth screenshotting, straight from the session materials:
"Every comp migration story sounds the same until you add the constraints."
"A calculation can be correct and a payout still be wrong, whenever a variable underneath it moves."
"You can't pay on what you can't see."
Every decision in this session traced back to the same question: which variables did you decide to pin down, and which ones did you knowingly let move. The 90-day clock, the currency lock, the renewal-rate denominator, the CX metrics list, all of it comes down to whether that decision got made on purpose or by default.
This is the first entry in Boston Notes, Everstage's live coverage of Sales Comp '26. A few more sessions are still on the agenda this week.
