Skip to content

sidchaudhary/gtm-skills / skills/account-executive/price-negotiation

price-negotiation

Unverified

Preps the negotiation strategy for one specific deal - anchor, concession ladder, walk-away point, and the questions that surface what the other side actually needs. Use before a pricing or terms conversation, not after it's already gone sideways. Pairs with opportunity-scoring and objection-handling.

references/pricing-frameworks.md

View on GitHub
# Pricing Frameworks


> **Provenance.** The numbers in this file are **pack benchmarks**, not the reader's own data, and
> most carry no named study behind them. When you state one in output, label it inline as a pack
> benchmark so nobody mistakes it for a figure derived from their business. Where a number is doing
> real work in a decision and you cannot name a source for it, write `[NEED: source]` instead of the
> number. House rule 4b covers this and binds every skill that reads this file.

Reference for value metric selection, tier structure, pricing research methods, and price-increase timing.

---

## The Three Pricing Axes

Every pricing decision breaks down into three independent choices:

| Axis | Question | Example decision |
|------|----------|-------------------|
| Packaging | What's included at each tier? | Features, usage limits, support level |
| Value metric | What do you charge for? | Per seat, per usage, flat fee |
| Price point | How much, in dollars? | $49 vs $79 vs $199 |

**Value-based pricing anchor:** price sits between the next-best alternative (the floor) and the customer's perceived value (the ceiling). Cost to serve is a sanity check, not the basis for the number.

## Choosing a Value Metric

A value metric is good if the answer to "as the customer uses more of this, do they get more value?" is yes. If no, the metric doesn't align price with value.

| Metric | Best for | Example |
|--------|----------|---------|
| Per seat/user | Collaboration tools | Slack, Notion |
| Per usage | Variable consumption | AWS, Twilio |
| Per feature/module | Modular products | Add-on pricing |
| Per contact/record | CRM, email tools | Mailchimp |
| Per transaction | Payments, marketplaces | Stripe |
| Flat fee | Simple, low-complexity products | Basecamp |

## Good-Better-Best Tier Structure

| Tier | Role | Pricing logic |
|------|------|---------------|
| Good (entry) | Get them in the door | Core features only, tightest usage limits, lowest price |
| Better (recommended) | Where most customers should land | Full features, reasonable limits, this is the anchor price |
| Best (premium) | Capture the top of willingness-to-pay | Everything + advanced capability, typically 2-3x the Better price |

Differentiate tiers with feature gating, usage limits, support level (email → priority → dedicated), or access (API, SSO, custom branding), never differentiate on more than 2-3 of these at once or the comparison table becomes unreadable.

## Pricing Research Methods

**Van Westendorp Price Sensitivity Meter**, ask four questions per persona:
1. At what price would this be too expensive to consider?
2. At what price would this be so cheap you'd question the quality?
3. At what price is it expensive, but you'd still consider it?
4. At what price is it a bargain?

Plot the four curves; the intersections mark the acceptable price range and the optimal price point.

**MaxDiff**, show respondents sets of features, ask which matters most and which matters least. Aggregate results rank every feature's relative importance and directly inform tier packaging (put the highest-ranked features in Better, not Best).

## Signals It's Time to Raise Prices

| Category | Signal |
|----------|--------|
| Market | Competitors have raised prices; prospects don't flinch at the current price; "it's so cheap!" feedback |
| Business | Conversion rate above ~40%; monthly churn below ~3%; strong unit economics |
| Product | Meaningful value added since the last pricing change; product materially more mature/stable |

**Price increase strategies, in order of customer-friendliness:**
1. Grandfather existing customers, new price applies to new customers only
2. Delayed increase, announce 3-6 months out
3. Tie the increase to added value, raise price alongside a feature release
4. Full plan restructure, new tiers entirely, used when packaging itself is broken, not just the number

## Pricing Psychology on the Page

- **Anchoring**, show the higher-priced tier first so the middle tier looks reasonable by comparison
- **Decoy effect**, structure the middle tier to be the objectively best value, not just the default recommendation
- **Charm vs round pricing**, $49 reads as value-focused; $50 reads as premium/confident. Match to positioning, don't default to charm pricing everywhere

## Underpricing Is a Failure Mode

Pricing work is usually framed as the risk of charging too much. Charging too little fails in ways
that are harder to see, because the symptom looks like a different problem.

- **Price is a quality signal.** For anything whose value the buyer cannot verify before purchase,
  a low price is read as low capability. Dropping the price can lower conversion, not raise it.
  When a price cut fails to move conversion, treat "too cheap to be credible" as a live hypothesis
  rather than cutting again.
- **It selects the wrong customers.** The cheapest tier attracts the buyers with the least budget,
  the highest support load, and the fastest churn. Cost-to-serve rises as price falls.
- **It caps everything downstream.** Paid acquisition, a sales motion, and real support are all
  affordable only above some price floor. Underpricing forecloses the go-to-market options before
  anyone gets to choose between them.
- **Raising later is harder than starting higher.** An increase has to be justified to an installed
  base that anchored on the old number, which is a materially worse conversation than launching at
  the right price.

Diagnostic: if almost nobody objects to the price and almost nobody churns on cost, the price is
probably below where it should be. Zero price objections is a finding, not a win.

---

## Pricing Ethics: Lines Not to Cross

Some pricing tactics reliably lift a short-term number and are either unlawful or corrosive
enough that they should not be recommended. Naming them is part of the job, because they get
requested by name.

| Tactic | Why not |
|---|---|
| **Drip pricing** | Revealing mandatory fees only late in checkout. Regulated in several jurisdictions, and the standard increasingly requires the total up front. |
| **Hidden or surprise fees** | Same problem, and it moves churn and disputes rather than removing them. |
| **Decoys designed to mislead** | A decoy tier is legitimate when it is a real option someone could rationally buy. A tier that exists only to be rejected, priced so nobody would ever choose it, is manipulation. |
| **Fabricated price-increase urgency** | "Price goes up Friday" when it does not. This is the fastest way to lose a buyer who checks back. |
| **Fake reference prices** | Anchoring to a "was" price that was never really charged. Directly regulated in many markets. |
| **Auto-renewal without clear consent** | Especially where cancellation is harder than signup. See the cancellation-ease rules in the churn playbook. |
| **Charging different prices for a protected characteristic** | Unlawful. Segmentation by usage, volume, or firm size is fine. By protected class it is not. |

If the user asks for one of these, say plainly that it is out of bounds and offer the legitimate
version of what they were reaching for: a real anchor tier, a genuine deadline, a transparent
total. Note that specifics vary by jurisdiction and that this is not legal advice.

---

## Pricing Decision Record

Pricing is a dated decision made under stated assumptions, not a permanent answer. Record it so
the next review has something to check against, otherwise the reasoning is lost and the next
change starts from scratch.

Every pricing recommendation ships with:

- **Decisions**, value metric, tiers, price points, and the annual discount, each with the one
  reason it was chosen.
- **Assumptions to monitor**, the numbers the decision rests on, each with the value used and
  where it came from. Any figure the user could not supply is listed as an assumption, never as a
  fact.
- **What would change the answer**, the specific movement in an assumption that would trigger a
  revisit. "If cost-to-serve on the entry tier passes X" is checkable; "if things change" is not.
- **First review date**, an actual date. Default to 90 days after a new price goes live, or one
  full renewal cycle for annual plans, whichever is longer.

---

## Pre-Launch Checklist

- [ ] Target personas defined (from prior customer research, if any exists)
- [ ] Competitor pricing researched
- [ ] Value metric identified and stress-tested against "more usage = more value?"
- [ ] Willingness-to-pay research conducted (Van Westendorp or MaxDiff) or explicitly flagged as not yet done
- [ ] Features mapped to tiers with no more than 2-3 differentiation axes
- [ ] Annual discount strategy set (typical range: 17-20% off monthly)
- [ ] Enterprise/custom tier planned or explicitly deferred

---

## Discounting: What the Data Shows, and What It Does Not

**The observed numbers.** On closed-won enterprise B2B SaaS deals, median price realisation runs about
**78%** of list (a median discount near **22%**), with the top decile of deals discounted **41%+**.
Median win rate on qualified opportunities sits near **21%**, and win rates fall as deals grow: roughly
25-35% under $50K, 18-28% at $50-250K, 12-22% above $250K, 10-18% above $1M.

**The correlation that gets misread.** Deals receiving **15%+ discounts closed at about 19%**, while
deals receiving **0-5% discounts closed at about 34%**. The tempting conclusion is that discounting
loses deals, so discount less and win more.

**Do not draw that conclusion.** The relationship is almost certainly confounded, and the direction of
causation runs mostly the other way:

- Deals that need a heavy discount are usually **already weak**, competitive, price-sensitive, poorly
  qualified, or championed by someone without budget authority. The weakness produces both the discount
  request and the loss.
- A rep discounts when they feel the deal slipping. The discount is a **symptom of the slip**, recorded
  before the loss it appears to cause.
- Strong deals close at list because they were strong, not because nobody offered a discount.

So the honest reading is: **a large discount request is a diagnostic signal about deal quality**, not a
lever to withhold. When a deal needs 20% off to move, the question is what is actually wrong with it , 
qualification, champion strength, competitive position, or fit, and whether the discount is buying a
close or delaying a loss.

What follows for practice:

- **Never present "discount less to win more" as causal.** It is not supported by this data, and a rep
  who withholds a discount on a genuinely price-constrained deal loses it anyway, with worse terms
  learned for next time.
- **Treat a discount request above the median as a qualification review**, not a pricing decision.
- **Track price realisation as a portfolio metric**, not a per-deal scorecard. Punishing individual
  discounts pushes discounting off-book into terms, scope and free periods, which is harder to see and
  more expensive.
- **Concede structure before price.** Term length, payment timing, scope, and success criteria are all
  cheaper to give than a rate cut, and none of them reset the reference price for the renewal.
- **A discount given without an exchange trains the buyer** that the number moves when they push. If
  something is given, get something: a longer term, a case study, a faster signature, a reference call.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall