Design / 01
Choose a focused pilot
Program context. Add team size, sales cycle length, current compensation and the behavior you want to change.
Start with one cycle and one clear goal.
- Open the Excel workbook and save a working copy. Review the fictional examples before clearing them.
- Fill the amber inputs in Setup. Agree the earning rules, then replace the sample Team, Events and Payments inputs. Formula cells are pale green.
- Use the rule-design and test prompts before announcing the program. The included rates are fictional starting examples, not compensation benchmarks.
- Review the Earnings exceptions and payment records. Approvals and payments are human steps recorded in the workbook.
- Copy the value of Setup B29 into the context field below. Open a prompt, add its inputs, and copy the full prompt to your AI assistant.
Your program context
Paste the generated context from Setup B29, or replace the placeholders below. Add an appeal contact if you want participant communications.
This local file has no network calls or tracking. Inputs stay in the open page and are not saved after closing it. Only copy anonymized data to your chosen AI tool.
Choose the job you need to do.
Each prompt includes the shared context, your extra inputs, the requested output and checks for missing information. AI output is a draft to review against your policy and source records.
Design / 02
Turn a policy into workbook rules
Program context and your draft policy or approved compensation terms.
Customize and copy this prompt
Design / 03
Check affordability before launch
Program context, candidate Rules rows and a representative anonymized deal sample.
Customize and copy this prompt
Prepare / 04
Map CRM, PSA and finance data
Program context plus export headers and a few anonymized sample rows.
Customize and copy this prompt
Prepare / 05
Test rules and edge cases
Program context, fully specified Rules rows and one sample event per rule.
Customize and copy this prompt
Launch / 06
Write participant terms and launch messages
Program context, approved Rules rows, approved exclusions and an appeal contact.
Customize and copy this prompt
Operate / 07
Review a weekly reward batch
Program context, Rules, Team, Events, Earnings and Payments exports with headers.
Customize and copy this prompt
Operate / 08
Explain a seller's earnings
Program context and Rules, Events, Earnings and Payments rows for one seller.
Customize and copy this prompt
Operate / 09
Resolve an appeal or reversal
Program context, disputed Event ID, original evidence, policy version and payment history.
Customize and copy this prompt
Improve / 10
Review the pilot without overstating impact
Program context, pilot results and a comparable baseline with definitions and dates.
Customize and copy this prompt
Improve / 11
Plan learning and recognition rewards
Program context, available certifications and the behaviors managers can verify.
Customize and copy this prompt
Improve / 12
Build a path beyond spreadsheets
Program context, current volumes, exception counts, administration time and planned growth.
Customize and copy this prompt
What the workbook calculates
| Reward basis | Calculation | Use |
|---|---|---|
| Annual GP | Incremental MRR x gross margin x MIN(contract months, 12) x rate | New contracts, expansion or renewals |
| MRR | One month of incremental MRR x rate | A focused service promotion |
| One-time GP | Net project revenue x gross margin x rate | One-time projects |
| Fixed | Flat award | Verified certification or recognition |
A per-event cap applies after calculation. Zero cap means uncapped. Date, eligibility, service, event type, margin, term and collection gates must pass. Fixed awards still require evidence and approval.
Use one currency and one cycle per copy. Capacity is 100 events, 100 payment records, 20 rules and 30 team members. Choose one rule for each event. The workbook does not automatically detect the same deal under different Event IDs, enforce approval authority, freeze rule history, enforce the total budget, or send payments.
Tier accelerators, pooled rewards, points, automated split attribution, negative earnings and clawbacks need an additional operating design. For a split, agree credit first and use separate unique events with the split amounts. Resolve reversals with finance and preserve the original cycle.
Service lists can be adapted, but keep rule and event labels identical. To use a new cycle, update Setup and the rule dates, assign new rule versions and clear the previous cycle's event and payment inputs. Recalculate in Excel and test your own examples before launch.
When the program needs a stronger foundation
If manual rule changes, disputes or payment reconciliation are slowing your team down, use prompt 12 to describe the actual workload and requirements.
Bring your program to Sepals with one audience, one sales behavior and one commercial measure.