# Bonuses

Commercial planning

Offers, messages, prices, guarantees, and delivery targets are proposals to validate. They do not establish available features, customer results, or contractual commitments. Confirm implementation and supporting evidence before using a proposal externally.

Bonuses should solve adjacent customer problems. They should accelerate value without weakening the core price.

## Recommended bonus stack

| Bonus                           | Problem resolved                                         |
| ------------------------------- | -------------------------------------------------------- |
| Historical opportunity backfill | Past events and exposed customers remain unresolved      |
| Storm response playbook         | Roles, thresholds, and handoffs remain informal          |
| Team storm drill                | Managers and field users have not practiced the workflow |
| First live event war room       | The first production event carries execution risk        |
| Executive post-event review     | Leaders cannot identify delays and improvements          |
| Branded property dossier        | Customer-facing evidence lacks a consistent package      |

## Delivery rules

Each bonus needs a defined scope, owner, acceptance condition, and fulfillment cost. Capacity-limited support must have a real customer limit.

Displayed replacement values remain hypotheses. Replace them with defensible values based on actual service cost and comparable professional work.

## Bonus test

A useful bonus should improve at least one outcome:

- Faster activation
- Higher confidence
- Lower customer effort
- Stronger operational proof
- Better ongoing adoption

Do not add bonuses that create unrelated work or hide an unclear core offer.