A CRO at a 26,000-person industrial equipment maker recommends how to split next year's $900M across three regions, with any AI chat her company allows.
A short email from the CFO with two conditions, sales ops' three options in one table, the data behind them, and a line from each regional VP. Each option looks reasonable on its own. Side by side, they're built on different foundations.
Here the AI compares options that each claim to be fair. The prompt makes it rebuild them on one basis first.
Use the AI tool your company approves: ChatGPT, Claude, Gemini or Copilot.
Copy the prompt and the four fictional inputs from the appendix into one message.
Add the three regional numbers in each option and compare them with the board's number. Then decide what you'll show on Friday.
I'm Chief Revenue Officer at an industrial equipment manufacturer with three sales regions: North America, Latin America and India. The board has approved next year's bookings number, and I have to recommend how to split it across the regions to our CFO and the three regional VPs on Friday, December 4. Today is Tuesday, December 1. Below are the CFO's email, the three options sales operations prepared, the data behind them, and notes from the regional VPs.
Please give me:
Put every option on the same time basis and the same definitions before you compare them, and say plainly if none fits as proposed. Check the arithmetic. Don't add facts that aren't in the inputs; if you assume something, say so.
Exactly as it came back, not edited. Read it the way Nadia did: check each point against the source it cites.
Recommendation in brief: None of the three options works as proposed. Option A meets both of the CFO's conditions, but it rests on only 9 months of India data. Option B breaks the floor for North America and measures Latin America differently. Option C adds up to $910M, not $900M. A corrected version of Option C is the best starting point, provided the items in section 4 are confirmed before Friday.
Assumptions I've made (please confirm):
| Time period | What it measures | What it counts | NA | LatAm | India | Total | |
|---|---|---|---|---|---|---|---|
| A: history (as proposed) | FY26. NA and LatAm are 12 months; India is 9 months (Apr–Dec) | Share of FY26 bookings | NA 480 / 740 = 64.9%, LatAm 170 / 740 = 23.0%, India 90 / 740 = 12.2% | 584 | 207 | 109 | 900 ✓ found |
| B: potential (as proposed) | 2025 study, not a bookings period | Share of market potential | NA $2.4B total market, India $1.5B total market, LatAm $0.9B serviceable market only (sum $4.8B) | 450 | 169 | 281 | 900 ✓ found |
| C: capacity (as proposed) | FY27 headcount, every rep counted as a full year | Reps × $13.0M (FY26 company average) | 40 / 16 / 14 reps, total 70 | 520 | 208 | 182 | 910 ✗ found |
Arithmetic checks:
The same three options on one basis:
| NA | LatAm | India | Total | How it's built | |
|---|---|---|---|---|---|
| A, annualised | 561 | 199 | 140 | 900 | India's $90M for 9 months becomes $120M for 12 months, which is an assumption. New total base is $770M. |
| B, like-for-like | can't be done | can't be done | can't be done | There is no total-market figure for LatAm. | |
| C, part-year reps, scaled to $900M | 531 | 213 | 156 | 900 | India counts as 8 + 3 × 9/12 + 3 × 6/12 = 11.75 full-year reps. Total is 67.75 reps, so $900M / 67.75 = $13.28M per rep. |
For reference, Option C counted as 70 full reps and simply scaled to $900M gives 514 / 206 / 180. That fixes the total but still counts India's six new hires as full-year reps.
| Adds to exactly $900M? | Every region at or above FY26? | Against the data | |
|---|---|---|---|
| A | Yes | Yes: 584 > 480, 207 > 170, 109 > 90 | The India number rests on 9 months, so it understates India. Annualised, India's share is $140M, not $109M. Pipeline coverage: NA 1.9×, LatAm 1.5×, India 2.4×. NA would need $14.6M per rep, above the $13.0M company average. |
| B | Yes | No. NA gets 450, below its FY26 480. Tom is right. LatAm 169 < 170 by about $1M after rounding (168.75 before). | It mixes total market (NA, India) with serviceable market (LatAm). That understates LatAm against the others, and Lucas is right. India at 281 is above its $260M pipeline (0.93× coverage) and more than 3× its FY26 (9-month) bookings. The study dates from 2025. found |
| C | No: $910M | Yes as proposed (520 / 208 / 182) | It counts India's 6 new hires as full-year reps, though 3 start in April and 3 in July. It allows no ramp-up time. The $13.0M average can't be checked because FY26 rep counts aren't given, and it may be distorted by India's part year. Anjali's "only fair one" is fair only if part-year hires count as full-year reps. found |
Corrected C (531 / 213 / 156):
Note on the floor: On December 1, FY26 can't be closed if the fiscal year is the calendar year. The "FY26 actuals" ($740M) must include November and December figures that are estimates or incomplete. The floor is therefore being tested against numbers that may still move.
Don't approve any option as proposed: found
Proposed working basis for Friday: corrected capacity (C), with NA $531M, LatAm $213M and India $156M. A: bring the range
Present it as conditional, not final, until these items are confirmed: C: a deadline
| To confirm | Who | Why it matters |
|---|---|---|
| The $910M error, how the $13.0M was calculated, FY26 reps by region | Sales operations | The whole capacity method depends on it |
| Start dates of India's 6 hires and the ramp assumption | Anjali Rao, with HR/recruiting | Each part-year rep moves India by several $M. A ramp period would lower India further. |
| Whether FY26 is closed, and India's January–March distributor bookings | Martin Cole / Finance | Sets the floor and the true size of India's history |
| Pipeline on one definition (FY27 close dates, stage, weighting) | Each regional VP, collected by sales ops | Shows whether the coverage figures can be compared |
| Whether "exactly $900M" allows over-assignment below region level | Martin Cole | Affects how much buffer the regions can hold |
If the $13.0M can't be explained by Friday, tell the CFO that, and bring corrected A and corrected C side by side as the range (NA 531–561, LatAm 199–213, India 140–156). Don't pick one figure on the strength of a number you can't explain.
These figures come from the inputs alone. Everything marked as an assumption or "to confirm" should be checked before you present it.
Claude found every planted problem, rebuilt the options on one basis and said none works as proposed. Nadia's edits keep her recommendation within what the evidence supports and decide who hears what, when.
Use it whenever a number has to be split and every option is presented as fair: regional targets, budgets by division, headcount by site, capital by plant.
I'm [your role] at a [industry] company with [the units you're splitting across]. [Who] has approved [the total], and I have to recommend how to split it to [who] on [date]. Today is [date]. Below are [their email, the options, the data behind them, and notes from the people affected].
Please give me: 1. A like-for-like table of the options: for each, the time period, what it measures and what it counts, and the number for each [unit]. 2. Each option tested against [the conditions] and against the data. 3. What's missing that I'd need to decide well. 4. My recommendation, including whether any option works as proposed, and what must be confirmed, by whom, before [date]. 5. What I tell each [person affected], in two sentences each.
Put every option on the same time basis and the same definitions before you compare them, and say plainly if none fits as proposed. Check the arithmetic. Don't add facts that aren't in the inputs; if you assume something, say so.
Copy the prompt, then all four inputs, into one message in a new chat. Everything here is fictional and safe to paste.
I'm Chief Revenue Officer at an industrial equipment manufacturer with three sales regions: North America, Latin America and India. The board has approved next year's bookings number, and I have to recommend how to split it across the regions to our CFO and the three regional VPs on Friday, December 4. Today is Tuesday, December 1. Below are the CFO's email, the three options sales operations prepared, the data behind them, and notes from the regional VPs. Please give me: 1. A like-for-like table of the three options: for each, the time period, what it measures and what it counts, and the number for each region. 2. Each option tested against the CFO's two conditions and against the data. 3. What's missing that I'd need to decide well. 4. My recommendation, including whether any option works as proposed, and what must be confirmed, by whom, before Friday. 5. What I tell each regional VP, in two sentences each. Put every option on the same time basis and the same definitions before you compare them, and say plainly if none fits as proposed. Check the arithmetic. Don't add facts that aren't in the inputs; if you assume something, say so. [1] Email from Martin Cole, CFO Nadia, the board approved $900M in FY27 bookings. The three regional numbers must add up to exactly $900M, and I'd rather no region gets a number below its FY26 actual. Sales ops has put three options together. Please bring your recommendation Friday. [2] Three ways to split $900M (sales operations) | $M | North America | Latin America | India | Basis | |---|---|---|---|---| | Option A: history | 584 | 207 | 109 | Share of FY26 bookings | | Option B: potential | 450 | 169 | 281 | Share of market potential | | Option C: capacity | 520 | 208 | 182 | FY27 reps x $13.0M per rep (FY26 company average) | [3] Sales operations data - FY26 bookings: North America $480M, Latin America $170M, India $90M. Total $740M. - India moved from a distributor to our own sales team on April 1, 2026. Its FY26 bookings cover April to December. - Market potential (strategy team study, 2025): North America $2.4B and India $1.5B are total addressable market. Latin America $0.9B is serviceable market, the segments we sell into today; no total market figure was done for Latin America. - FY27 quota-carrying reps: North America 40, Latin America 16, India 14. India's 14 includes 6 new hires: 3 start in April, 3 in July. [4] Notes from the regional VPs - Tom Reyes, North America: "Option B would give us less than we booked this year. Our FY27 pipeline is $1.1B." - Lucas Ferreira, Latin America: "Option B measures our market differently from everyone else's. Our pipeline is $310M." - Anjali Rao, India: "We'll have 14 reps. Option C is the only fair one. Our pipeline is $260M."I'm Chief Revenue Officer at an industrial equipment manufacturer with three sales regions: North America, Latin America and India. The board has approved next year's bookings number, and I have to recommend how to split it across the regions to our CFO and the three regional VPs on Friday, December 4. Today is Tuesday, December 1. Below are the CFO's email, the three options sales operations prepared, the data behind them, and notes from the regional VPs.
Please give me:
Put every option on the same time basis and the same definitions before you compare them, and say plainly if none fits as proposed. Check the arithmetic. Don't add facts that aren't in the inputs; if you assume something, say so.
Nadia, the board approved $900M in FY27 bookings. The three regional numbers must add up to exactly $900M, and I'd rather no region gets a number below its FY26 actual. Sales ops has put three options together. Please bring your recommendation Friday.
| $M | North America | Latin America | India | Basis |
|---|---|---|---|---|
| Option A: history | 584 | 207 | 109 | Share of FY26 bookings |
| Option B: potential | 450 | 169 | 281 | Share of market potential |
| Option C: capacity | 520 | 208 | 182 | FY27 reps x $13.0M per rep (FY26 company average) |