Incentive Compensation Apps

Builds a compensation plan through guided configuration rather than formula writing. The admin answers structured questions about how the plan pays: which measures it uses, which calculation type applies (rate table, tiered, matrix, flat amount), what the thresholds and caps are, and how components combine into total target compensation. Plans are effective-dated, so a mid-year change to a rate table preserves what was in force before it.

Shows how each payable element of a plan contributes to a person's total earnings: a quarterly new-logo commission, an annual MBO bonus, a monthly accelerator on renewals. Each component carries its own measure, calculation logic, weighting and payout schedule.

Pick this over the plan-level view when the question is diagnostic. When a salesperson asks why their number moved, the answer is almost always inside one component rather than across the whole plan.

Sets out the calculations behind a salesperson's commission earnings: the credited transactions, the measure values, the rate or tier applied, and the resulting amount for each component. A salesperson can follow the arithmetic from a specific deal through to the line on their statement.

This is where most compensation disputes are won or lost, and the reason to care is operational rather than philosophical. A compensation team that cannot produce the derivation on demand spends its quarter-end reconstructing it in spreadsheets for whoever asked loudest.

Optymyze customers report 90% fewer compensation disputes. A compensation team that cannot produce the derivation on demand spends its quarter-end reconstructing it in spreadsheets for whoever asked loudest.

Compares plan scenarios by aggregate payout cost. This is the finance question, and usually the first one asked.

Compares plan scenarios by what the typical participant experiences. Use it to find out that a change which looks neutral in total is a pay cut for the median participant.

Compares plan scenarios by how participants move relative to each other rather than by cost or average outcome.

Do not skip this one. Run it alongside the other two, not instead of them. A revision can hold aggregate cost flat and median earnings flat while still reshuffling the top decile, and the salespeople who fall are the ones who escalate in February. This is the application that catches that. It is also the one most often skipped.

Tracks earnings against targets and payment progress. The default landing view for most rollouts and the application a salesperson opens first.

Analyzes earnings trends over time and identifies which components are actually driving income.

Pick this over Sales Compensation Overview when the question is about pattern rather than current state.

Shows how an individual's earnings moved between two periods and attributes the change to specific components, accounts or products. Answers why this month is lower than last month with a breakdown rather than a total.

Compares an individual against the average for their position and breaks down what accounts for the gap.

Deploy with your eyes open. Exposing position-average benchmarks makes compensation more transparent and makes some managers uncomfortable, because it surfaces territory quality differences that were previously invisible. Organizations that do not want that conversation should not deploy it. Most that do deploy it find the conversation was already happening, just less accurately.

Combines sales performance and compensation progress across a manager's direct reports. The team-level equivalent of the field-facing applications above, built for the person running one-to-ones rather than the person receiving them.

Analyzes compensation spend against revenue and productivity. Gives sales leadership and finance a shared view of cost of sale, rather than two versions produced separately and argued about at the quarterly business review.

Quantifies the earnings impact of attrition: what leavers were earning, what their territories produced, and what the ramp gap costs while a seat sits open or a replacement builds pipeline.

Most organizations track turnover as a headcount number in an HR system, disconnected from the revenue and payout data that would turn it into a business case. This application connects the two. It is the one on this page most often deployed for a board conversation rather than an operational one.