A VP Sales at a 7,200-person components maker works through her regional VPs' request for more discount authority before the pricing council, with any AI chat her company allows.
A confident email from her two regional VPs, a CRM export, quote times from two systems, notes from customer interviews, a note from finance and one forwarded comment from a buyer. The request reads well. The evidence is thinner.
Here the AI works through a decision your own team is pushing. The prompt asks it to check the reason before the fix.
Use the AI tool your company approves: ChatGPT, Claude, Gemini or Copilot.
Copy the prompt and the six fictional inputs from the appendix into one message.
Put both quote times in the same units and compare them. Then decide what you'd ask finance and the regions for.
I'm VP Sales for North America at an industrial components maker. My two regional VPs want authority to discount up to 18% without approval, because they say we're losing on price. Our CRO decides at the pricing council on Thursday, December 3. Today is Tuesday, December 1. Below are their email, our CRM loss export, the quote turnaround figures, notes from win/loss interviews, a note from finance and the competitor evidence they sent.
Please give me a one-page decision note:
Before you accept any reason for losing, check how that reason was recorded and how much evidence sits behind it. Keep units and periods consistent. 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 Carla did: check each point against the source it cites.
Decision note: regional discount authority (pricing council, Thursday, December 3)
1. The decision Should East and West regional VPs be allowed to discount up to 18% without approval, or does the evidence point to a different fix?
Options:
2. Why we lose
Supported by the evidence
Suggested only
Not shown
3. The options
| Option | Cost (on Q3 won volume of $58.0M; finance says each extra point of average discount costs about $0.65M) | What it would fix | What would have to be true |
|---|---|---|---|
| A. 18% authority | Depends on how far the average rises. If it rose from 11.2% to 15% (an illustration, not a forecast), about $2.5M a quarter. If every won deal went to 18%, about $4.4M a quarter. Margin is given away on deals we would have won anyway. | The 3 of 12 interviewed losses that were about price. Probably some speed too, because these deals would no longer wait 4 days for approval. | Price really is the main reason we lose, and competitors really are about 15% under us on a like-for-like basis. Neither is shown. found |
| B. Narrower or conditional authority | Lower, and capped by design. It cannot be costed until a cap is chosen. | Documented price losses, while protecting margin. Some approval delay disappears. | Regions can produce real competitor quotes. Someone checks how the discount is used. |
| C. Approval and quote speed | Little direct discount cost. The effort is in finance and sales operations (amount not given). | The most common reason customers gave (7 of 12). Also the 4-day approval wait. | The speed gap holds up when won and lost deals are measured the same way. Approval is a large part of the delay. |
| D. Not yet | One cycle of delay. | Avoids locking in a costly policy based on weak evidence. | The missing evidence can be gathered quickly. |
4. My recommendation for Thursday
Not yet on 18%. Don't approve blanket 18% authority on the current evidence. Keep the question open. In the meantime, ask the council to approve option C now, because it costs little and matches what customers told us: a finance approval deadline (for example 1 business day) for discounts from 10% to 18%, and a quote-turnaround target. B: finance agrees first
Revisit 18% at the next council meeting, once these are known: C: one brief to sales ops
If the re-checked data still shows price as the main cause, option B with a clear cap is the safer next step than A. A: give the regions a role
Claude found every planted problem, said "not yet" instead of "no", and found the cheaper fix. Carla's edits are about her own team, who owns the fix, and what the council needs.
Use it whenever your team asks for something to fix a problem they've already diagnosed: more discount, more headcount, a new tool, a policy exception.
I'm the [your role] at a [industry] company. [Who] wants [the request], because they say [the reason]. [Who decides] decides on [date]. Today is [date]. Below are [the request, the data behind the reason, any customer feedback, finance's view].
Please give me a one-page decision note: 1. The decision, in one sentence, and the options, including any nobody has proposed. 2. Why it's happening: what the evidence supports, what it only suggests, and what it doesn't show. 3. Each option: what it would cost, what it would fix, and what would have to be true. 4. My recommendation for [date], or "not yet" with what would settle it.
Before you accept any reason, check how it was recorded and how much evidence sits behind it. Keep units and periods consistent. Don't add facts that aren't in the inputs; if you assume something, say so.
Copy the prompt, then all six inputs, into one message in a new chat. Everything here is fictional and safe to paste.
I'm VP Sales for North America at an industrial components maker. My two regional VPs want authority to discount up to 18% without approval, because they say we're losing on price. Our CRO decides at the pricing council on Thursday, December 3. Today is Tuesday, December 1. Below are their email, our CRM loss export, the quote turnaround figures, notes from win/loss interviews, a note from finance and the competitor evidence they sent. Please give me a one-page decision note: 1. The decision, in one sentence, and the options, including any nobody has proposed. 2. Why we lose: what the evidence supports, what it only suggests, and what it doesn't show. 3. Each option: what it would cost, what it would fix, and what would have to be true. 4. My recommendation for Thursday, or "not yet" with what would settle it. Before you accept any reason for losing, check how that reason was recorded and how much evidence sits behind it. Keep units and periods consistent. Don't add facts that aren't in the inputs; if you assume something, say so. [1] Email from the regional VPs (East and West) Subject: Discount authority Carla, we lost 41 deals over $50K last quarter, 29 of them on price. Competitors are 15% under us. Give the regions authority to discount up to 18% without approval, or we'll miss Q1. [2] CRM export: lost deals over $50K, Q3 41 deals, $23.6M in total. Loss reason: Price 29, Timing 5, Product fit 4, Other 3. Note from sales operations: loss reason is a required field to close a lost deal, and "Price" is the first option in the list. [3] Quote turnaround, Q3 (sales operations) Median time from customer request to quote sent: - Won deals (118): 3.1 business days, from the quoting system. - Lost deals (41): 9.4 calendar days, from CRM activity dates. [4] Win/loss interviews with customers we lost (June to September) 12 interviews completed. Main reason given: - 7: another supplier sent a usable quote first, or met their deadline - 3: price - 2: product specification [5] Note from finance Won deals in Q3: $58.0M booked, at an average discount of 11.2% off list. Discounts above 10% need my approval; the median approval time is 4 business days. Each extra point of average discount on Q3's won volume would have cost about $0.65M. [6] Competitor evidence, forwarded by the East regional VP From a customer's buyer: "Your competitor came in 15% under you on the 200-unit order."I'm VP Sales for North America at an industrial components maker. My two regional VPs want authority to discount up to 18% without approval, because they say we're losing on price. Our CRO decides at the pricing council on Thursday, December 3. Today is Tuesday, December 1. Below are their email, our CRM loss export, the quote turnaround figures, notes from win/loss interviews, a note from finance and the competitor evidence they sent.
Please give me a one-page decision note:
Before you accept any reason for losing, check how that reason was recorded and how much evidence sits behind it. Keep units and periods consistent. Don't add facts that aren't in the inputs; if you assume something, say so.
Subject: Discount authority
Carla, we lost 41 deals over $50K last quarter, 29 of them on price. Competitors are 15% under us. Give the regions authority to discount up to 18% without approval, or we'll miss Q1.
41 deals, $23.6M in total. Loss reason: Price 29, Timing 5, Product fit 4, Other 3.
Note from sales operations: loss reason is a required field to close a lost deal, and "Price" is the first option in the list.
Median time from customer request to quote sent: - Won deals (118): 3.1 business days, from the quoting system. - Lost deals (41): 9.4 calendar days, from CRM activity dates.
12 interviews completed. Main reason given: - 7: another supplier sent a usable quote first, or met their deadline - 3: price - 2: product specification
Won deals in Q3: $58.0M booked, at an average discount of 11.2% off list. Discounts above 10% need my approval; the median approval time is 4 business days. Each extra point of average discount on Q3's won volume would have cost about $0.65M.
From a customer's buyer: "Your competitor came in 15% under you on the 200-unit order."