borghei/Claude-Skills / business-growth/deal-desk
deal-desk
VerifiedDeal desk: reviews, approves, and structures non-standard sales deals. Use when standing up a deal desk, building approval-threshold matrices, designing deal-review packets, routing deals, or auditing deals for compliance.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 19.9 KB |
| references/approval-thresholds-and-routing.md | markdown | 13.0 KB |
| references/deal-desk-charter-and-process.md | markdown | 13.5 KB |
| references/discount-and-concession-playbook.md | markdown | 16.7 KB |
| scripts/deal_review_packet.py | script | 14.7 KB |
| scripts/deal_velocity_analyzer.py | script | 11.7 KB |
| scripts/discount_authority_router.py | script | 11.9 KB |
references/discount-and-concession-playbook.md
View on GitHub# Discount and Concession Playbook
Reference for evaluating discount requests, structuring concessions, identifying legitimate reasons for each, finding alternatives to discounting, and structuring performance-based deals that earn the discount instead of giving it away.
---
## The concession taxonomy
A "discount" in sales conversation is shorthand for many different concessions. Recognizing the type guides the right response.
| Concession type | What it is | Cost to us | Customer value |
|-----------------|-----------|------------|----------------|
| **Price discount** | % off list | High (cash margin) | High (cash savings) |
| **Contract length flex** | Month-to-month vs annual | Medium (LTV uncertainty) | Medium (flexibility) |
| **Payment terms** | Net 60/90 vs Net 30 | Low-Medium (cash flow) | High (cash flow) |
| **Ramp** | Pay growing fee over time | Medium (deferred revenue) | High (cash flow + scaling) |
| **Pilot / POC** | Free/discounted trial period | Medium (engineering time) | High (de-risk) |
| **Custom SLA** | Better uptime / response | Medium-High (operational cost) | Variable |
| **Custom security** | Bespoke security commitments | Medium (engineering + audit) | High (compliance) |
| **MFN clause** | We guarantee best price | Future cost (constrains pricing) | High (long-term) |
| **Liability cap increase** | Higher liability exposure | Medium (insurance + risk) | Medium |
| **Source code escrow** | Code held in escrow | Low (one-time setup) | High (risk mitigation) |
| **Termination flexibility** | Easier exit | Medium (churn risk + revenue uncertainty) | High |
| **Custom integration** | Specific feature build | High (engineering opportunity cost) | High |
| **Free implementation** | Waived setup fees | Medium (services revenue) | Medium |
| **Reference discount** | Discount for public reference | Low (marketing cost is recovered via reference) | Low-Medium |
| **Stock / equity** | (For partner deals) | Variable | Variable |
Pick the concession that costs you least and the customer values most. That's deal-desk's value-add.
---
## Legitimate reasons for each concession
### Price discount — when it's legitimate
- **Competitive scenario**: customer has a credible alternative at lower price; matching is the only way to win
- **Volume / strategic logo**: discount in exchange for size or reference value
- **Multi-year commit**: discount in exchange for longer contract (calculate that net LTV is still favorable)
- **Bundled purchase**: discount on bundle vs individual products
- **Renewal compression**: customer wants to consolidate multiple contracts at favorable rate
- **Market reality**: when your published pricing is genuinely off-market in this segment
### Price discount — when it isn't
- **Customer asked, end of conversation.** Default response is no; ask why.
- **Rep needs to close this quarter.** Rep urgency isn't a discount justification.
- **"We always discount" (rep tribal knowledge).** Reset expectations.
- **No real alternative.** If customer has no real competitor, discount = give-away.
- **Vague "strategic value."** Specify it: which logo? which vertical? what reference? Or it's not strategic.
### Contract length flex — when it's legitimate
- Customer is genuinely testing fit (POC didn't fully resolve)
- Customer's procurement cycle requires monthly billing
- Customer is at a regulated stage requiring shorter commitment
### Contract length flex — when it isn't
- Customer wants "flexibility" with no specific reason → likely shopping for exit
- Customer is a startup that "might not exist in a year" → tell them you welcome the deal at standard terms and they can renew if still around
### Payment terms — when it's legitimate
- Enterprise customer with standardized Net 60 process; not deal-specific
- Customer with quarterly budget cycles; payment aligned to their fiscal
- Customer in industry with longer cash cycles (manufacturing, construction)
- Customer offering meaningful prepayment for net-30 (e.g., pay 12 months upfront)
### Payment terms — when it isn't
- "We always pay Net 90" (with no scale justification) → push back
- Customer is a startup with cash-flow issues → consider, but understand the credit risk
### Ramp — when it's legitimate
- Customer's actual usage will grow over the contract (we have visibility into this)
- Multi-team rollout: starting with one team, expanding to N teams over months
- Replacement of legacy contract that doesn't expire until month 6
### Ramp — when it isn't
- Rep wants smaller year-1 ACV to hit close target → re-think
- Customer wants ramp to fit budget but not because usage will actually scale → just a discount in disguise; price it like a discount
### Custom SLA — when it's legitimate
- Customer's business genuinely requires higher SLA (financial trading, healthcare ops)
- Customer is willing to pay a premium for it (matches the operational cost)
- Engineering / operations team confirms feasibility
### Custom SLA — when it isn't
- Customer asks for 99.99% as a "checkbox" without operational need → educate on standard SLA's actual reliability
- Custom SLA with penalties for failure (uptime credits) without operational confidence → high risk
- Sales asks for it "to differentiate from competitor" → likely competitor doesn't offer it either; educate
### MFN — when it's legitimate
- Strategic anchor customer; significant ACV; long-term partnership intent
- Customer's negotiating leverage is high enough that they will likely get it via other means
### MFN — when it isn't (which is most of the time)
- Almost never. MFN clauses ratchet future pricing flexibility and create cascading "well they got it" demands.
- If you must, scope tightly: same product, same volume, same geo, same term length, public-disclosure-only
### Liability cap increase — when it's legitimate
- Customer's risk genuinely exceeds standard cap (regulated industry; PHI; financial data)
- Insurance can cover the additional exposure
- Legal-reviewed and CFO-approved
### Liability cap increase — when it isn't
- "Our procurement standard requires 5x" → push back; many procurement standards are negotiable
- No actual customer-side risk analysis → discuss what's actually at stake
---
## Alternatives to discounting
Before granting a discount, exhaust alternatives:
### Trade non-monetary for monetary
| Customer wants | Alternative |
|----------------|-------------|
| 20% off | Same price, 6-month ramp |
| 20% off | Same price, 3 months free implementation services |
| 30% off | Same price, dedicated CSM tier upgrade |
| 25% off | Same price, faster response time on support |
### Trade for commitment / scope
| Customer wants | Trade |
|----------------|-------|
| 20% off | Public case study within 90 days |
| 20% off | 3-year commitment |
| 20% off | Reference call for 3 prospects in 12 months |
| 25% off | Multi-product bundle (add Product B at standard rate) |
| 30% off | Logo rights for marketing use |
| 30% off | Speaking commitment at our user conference |
### Trade for partnership
| Customer wants | Trade |
|----------------|-------|
| 30% off | Joint go-to-market or co-marketing commitment |
| 30% off | Public press release announcing the deal |
| 30% off | Beta access to new product (mutual benefit) |
### Earn-back / performance discounts
| Structure | Example |
|-----------|---------|
| Tiered discount based on annual ACV | 0% off at $500k; 5% off at $1M; 10% off at $2M |
| Volume rebate quarterly | Pay full price; rebate based on usage |
| Achievement bonus | Discount earned if customer hits adoption metric |
| Reference earn-back | Discount applied retroactively after case study delivered |
This is psychologically different: customer sees discount as something they earn (sticky), not something they extract (entitlement).
---
## How to evaluate the discount request
Standard framework, applied to each discount request:
### 1. What's the real ask?
Customer says "we need 20% off." But the underlying ask might be:
- "Our budget is $X, your price is $Y, gap is Z"
- "I need this signed this quarter and need cover for the size"
- "Your competitor is cheaper and we don't have a strong reason to pick you"
Sales rep should identify the real ask; deal desk should ask if it's not clear.
### 2. What's customer leverage?
Real leverage:
- Multiple credible alternatives (procurement-validated)
- Hard budget constraint (rarely strictly true; usually negotiable)
- Existing relationship with competitor (sunk cost)
Soft leverage:
- "We always negotiate" — universal; not specific to you
- "Other vendors are cheaper" — without naming or detail
- "We won't sign without 20% off" — often bluff
### 3. What's customer value to us?
Quantify:
- Annual gross profit on this deal at requested price
- Projected LTV (years × annual GP)
- Reference / strategic value (rough estimate: how much would we pay for this logo?)
- Vertical / market positioning value
If LTV + reference + strategic value > total discount giveaway, deal makes sense.
### 4. What's the precedent risk?
- Will competitors / customers find out (sales people talk, customers compare notes)?
- Will internal sales team see this as "the new baseline"?
- Is the customer big / loud enough that the deal will be referenced for years?
If high precedent risk, structure as one-time / single-instance with explicit non-precedent language in the contract.
### 5. What's the cost of saying no?
- Lose this deal entirely (likelihood × value)
- Lose competitive position in the segment
- Damage to customer relationship for future expansion
Often the cost of saying no is lower than reps believe. Walking away from bad deals strengthens future negotiations.
---
## Discount structuring patterns
How you give the discount matters as much as how much.
### Pattern A: Time-bound (most common)
"20% off if signed by <date>." Forces decision; protects margin if customer drags.
### Pattern B: Volume-tiered
"5% off above $250k ACV; 10% above $500k; 15% above $1M." Encourages bigger deals; defensible publicly.
### Pattern C: Commitment-tied
"15% off for 3-year commit; 10% for 2-year; 5% for 1-year." Trades cash for retention.
### Pattern D: Performance-tied (earn-back)
"Standard price; 10% rebate at end-of-year if customer hits X usage target." Customer earns the discount through behavior we want.
### Pattern E: Bundle
"Buy Product A + Product B + Product C as bundle at 25% off." Multi-product anchoring; cross-sell.
### Pattern F: Ramp
"Year 1: 50% off (ramp period). Year 2: 25% off. Year 3: full price." Customer growth pays for early discount.
### Pattern G: Single-instance (precedent-breaker)
"This is a one-time pricing arrangement contingent on <specific reason: launch customer, beta program, etc.>. Standard pricing applies at renewal." Explicit non-precedent language.
### Pattern H: List price + extras
"Customer pays full list. We throw in: 30 days extra implementation, dedicated CSM for first quarter, custom training." Maintains pricing integrity; gives perceived value.
---
## Discount structuring anti-patterns
- **"Just take it off the top."** Customer sees full discount on every invoice forever. Mathematically same but psychologically less defensible.
- **Discount cumulative with later concessions.** "20% off + free implementation + custom SLA" with no quid pro quo each.
- **Negotiation by repeated discount.** Customer comes back, "I need another 10%." If you said 20% was final, hold the line. Otherwise discount-on-discount becomes the norm.
- **Verbal "we'll discount at renewal."** Always document; rep turnover means promises get lost.
- **Discount without expiration.** Customer comes back in 6 months expecting same.
- **Discount without conditions.** Discount + zero customer obligation = pure giveaway.
- **Hidden discount via "credit" or "promotional rate."** Looks better on the books but is the same economically; finance audit will catch it.
---
## Concession negotiation worked examples
### Example 1: Customer wants 25% off
**Sales reports:** Customer is a 500-employee SaaS company, ACV $300k standard. They have one competitor evaluated; we are technically preferred but ~25% more expensive. Decision-maker is the CFO.
**Deal-desk analysis:**
- Competitor genuinely cheaper: ✓
- 25% off → $225k ACV → ~$X gross margin
- Customer strategic value: medium (SaaS vertical foothold)
- Precedent risk: medium (vertical-watched company)
**Recommendation:** Counter with a structured deal:
- 15% off list ($255k) + 2-year commit
- OR full price + 3 months free implementation services + waived first-year support upgrade
- OR 20% off + customer commits to public case study + reference for 5 prospects in vertical
Rationale: Earn the discount with commitment; avoid setting a single-instance 25% precedent in the vertical.
### Example 2: Customer asks for MFN clause
**Sales reports:** $2M ACV enterprise customer. Procurement insists on MFN ("most favored nation" — customer guaranteed best price). Won't sign without it.
**Deal-desk analysis:**
- MFN ratchets future pricing flexibility
- Will affect every future deal we want to do at higher price
- Customer leverage real (large strategic deal) but MFN cost is open-ended
**Recommendation:** Decline standard MFN. Counter with scoped MFN:
- Same product, same volume, same term length, same geo
- Disclosure-only (we tell you if we beat your price for an equivalent customer; you can match)
- Excludes one-time pilot pricing and acquisition-related pricing
If customer rejects scoped MFN, decline and escalate to CRO + CFO. MFN is one of the few "should be very rare" concessions.
### Example 3: Customer wants free implementation
**Sales reports:** $500k ACV deal. Customer says "we need implementation included or we can't justify it internally."
**Deal-desk analysis:**
- Standard implementation cost: $50k (10% of ACV)
- Customer pricing tolerance unclear (rep asked for full waiver, didn't try partial)
**Recommendation:** Counter:
- "Implementation included with 2-year commit" — trade for length
- OR "First $30k of implementation included; customer pays incremental scope" — trade scope
- OR "Implementation included with quarterly business reviews + executive sponsorship" — trade for engagement that helps adoption / retention
Rationale: Customer wants concession; structure it to bring value back.
---
## Concession audit (quarterly)
Every quarter, review:
1. **Distribution of concessions by type** — which are most-requested? Are we under-offering certain types (e.g., free implementation) and over-discounting?
2. **Win rate by concession type** — does free implementation win deals better than equivalent-cost discount?
3. **Customer behavior after concession** — did the customer fulfill conditions (case study, reference)? If not, that informs future deals.
4. **Net impact** — gross margin trend; LTV trend on discounted vs full-price deals.
5. **Sales perception** — which concessions do reps think are most effective? Compare to data.
Adjust playbook based on findings.
---
## Cheat sheet by customer ask
| Customer says | Default response |
|---------------|------------------|
| "We need 20% off" | "Help me understand — is that a budget constraint, competitive pressure, or something else?" |
| "Your competitor is cheaper" | "Tell me about that quote — same scope? same term? what's included?" |
| "We need MFN" | "Standard MFN is rarely available. What's the underlying concern?" |
| "We need Net 90" | "Why? What's your standard for vendors at this size?" |
| "We need pilot first" | "What would success look like? Let's structure that explicitly." |
| "We need 5x liability cap" | "What's the customer-side risk that drives this? Let's understand it." |
| "We need custom SLA" | "Tell me about your reliability requirements. What's the business impact of an hour of downtime?" |
| "We want it free for the first year" | "Let's structure a ramp deal that aligns your usage growth with payment." |
Each conversation flips the dynamic from "discount or no deal" to "let's understand the underlying need and structure something that works."
---
## Summary
| Question | Answer |
|----------|--------|
| Discount on every deal? | No. Start with no; require justification. |
| What's the cheapest concession to us? | Often: contract length, ramp, payment terms, free implementation (services have lower margin impact than ACV discount) |
| What's the most expensive concession? | MFN, customer audit rights, liability cap increase, non-precedent-bound discount |
| What should we always trade for a concession? | A specific commitment from the customer: reference, case study, length, volume |
| What if customer insists no trade? | The discount isn't really needed; or the deal isn't really there |
| When do we walk? | When the LTV doesn't support the concession + strategic value doesn't compensate; precedent risk too high; or customer signals bad-faith negotiation |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |