Team and roles
Paying for outcomes people control
A variable-pay scheme is rewarding the wrong behaviour, or nobody trusts it.
Signals to look for
- commission
- bonus
- variable pay
- incentive
- compensation
- gaming
Questions to answer
- What behaviour does the current scheme actually reward?
- Which part of the outcome is outside the person's control?
- How quickly is the reward paid relative to the outcome being real?
- What happens if the customer leaves shortly after?
Evidence required before committing
- current scheme terms
- outcomes paid against actual business results
- cases where the reward and the result disagreed
Likely constraint
- Reward paid before the outcome is real
- Outcome affected mostly by factors outside the role
How the decision branches
- IfReward is paid before revenue is collectedThenMove the trigger to collection, with notice and agreement.
- IfThe outcome depends mostly on other peopleThenReduce the variable component; it is a lottery, not an incentive.
- IfBehaviour is being gamedThenThe measure is wrong, not the person.
What to test
Model the last two quarters under the proposed scheme and see who would have been paid what, before changing anything.
Read after 60 days.
What success looks like
- The modelled payouts track business results
- No perverse case appears in the model
What means stop
- The model produces outcomes the company could not afford or defend
Typical next move
- The model holds → Agree it in writing with notice.
Who does the work
Aury can carry out: read company, prepare document, flag risk, file memory. Specialists involved: finance, operations.
Your approval: Aurygine never changes anyone's pay. It models options for founder decision.
This needs employment review — get a qualified professional to look at your specifics before anything is signed or sent.
Where this stops being true
Applies only where there is variable pay or a proposal to introduce it.
Compensation is contractual and regulated. Nothing here is employment or tax advice; changes require qualified review and, usually, employee agreement.
Provenance
- Sourced operator experience: Founder/operator case study analysed inside Aurygine — bootstrapped B2B software company, 2026
- Aurygine synthesis: Aurygine synthesis across founder journeys
Confidence: low. Last reviewed 2026-08-25. Your company's own recorded results override this playbook whenever the two disagree.