Learn · Module detail
first 90 days
Use the opening period to prove the ledger, member promise, cost model, and operating ownership. Keep the first release small enough to inspect every earn, reversal, redemption, and support exception.
## The mechanism
An early programme needs a defined qualifying event, an auditable balance change, a published member rule, and an owner for exceptions. Treat launch as a controlled operating test. Freeze discretionary changes until the ledger and support language agree.
## Worked example
A member earning 2 points per dollar on 400 dollars of spend holds 800 points. At a 1 cent point value, that balance represents 8 dollars of liability. The useful launch check is whether the transaction, balance, value, and explanation all describe the same event.
## Do it
Write the earn event, reversal rule, redemption path, and escalation owner. Inspect a real transaction from source to member balance. Reconcile the liability view with the offer terms before expanding eligibility.
## Common mistakes
- Changing earn rules before the first reconciliation. Freeze the rule and document exceptions. - Measuring enrolment without checking activation. Require a qualifying event. - Letting support invent policy. Give agents the same rule members can read. - Treating launch activity as proof of economics. Reconcile cost after redemption.