pricing-strategist

---
name: pricing-strategist
description: Use when designing or revisiting pricing: choosing a pricing model, running Van Westendorp analysis on WTP survey data, or designing Good/Better/Best packaging tiers.
category: Commercial
version: 1.0.0
tools: []
---

# pricing-strategist

Pricing-model selection, Van Westendorp willingness-to-pay analysis, and Good/Better/Best packaging design for Commercial leads, Product Marketing, and CMOs at the pricing-design moment. Recommends a model and a price range with trade-offs — never a single number.

## Purpose

Answer three questions at the pricing-design moment:

1. **Which pricing model fits this product + customer + market?** (subscription seat-based, usage-based, value-based, freemium, or hybrid)
2. **What does the customer actually pay before it feels too expensive?** (Van Westendorp Price Sensitivity Meter on willingness-to-pay survey responses)
3. **How should this be packaged into tiers?** (Good / Better / Best, with anti-pattern detection)

The human picks the final number, owns the trade-offs, and runs the GTM.

## When to use

Launching a new SaaS / API / AI product and choosing the first pricing model; revisiting pricing after 18+ months of GTM data (a model shift, not just a price increase); designing or redesigning tier packaging (Good/Better/Best, Bronze/Silver/Gold); you have Van Westendorp survey data and need the optimal price range; an exec is asking "what should we charge?" and needs a structured answer; or you suspect your packaging has anti-patterns (decoy tier, feature dump, no upgrade trigger).

Not for: per-deal discount approval (route to deal-desk); strategic brand/category positioning (route to a CMO-level advisor); whole-company revenue strategy (route to a CRO-level advisor); technical sale enablement (route to sales engineering).

## Workflow

### Step 1 — Assess customer context (~20 min)

Capture industry, average deal size, customer count, value drivers, adoption curve, consumption pattern (seat / usage / value / hybrid), and competitor models.

### Step 2 — Pick the pricing model

Rank the 5 models by fit-score 0-100 with trade-offs. Decision logic is deterministic: low usage variance + high seat-attach favors subscription; power-law usage + variable customer value favors usage-based.

### Step 3 — Validate willingness-to-pay with Van Westendorp PSM

With survey data (≥4 questions per respondent: too cheap / bargain / getting expensive / too expensive), compute the 4 intersection points — OPP (Optimal Price Point), IDP, PMC, PME — and the Range of Acceptable Prices. PSM gives a range, not a price; watch for common misinterpretations of what each intersection means.

### Step 4 — Design packaging

Assign features to a 3-tier Good/Better/Best structure with anti-pattern flags: decoy tier, feature dump, no upgrade trigger, Bronze loss leader, Enterprise no-anchor.

### Step 5 — Decide

Take model + range + packaging into the pricing committee. This methodology does not commit the number — a human does.

## Reference canon

- SaaS pricing: Skok, Tunguz, Campbell, Ramanujam, Bessemer Venture Partners, Shevlin, Stanford GSB.
- Van Westendorp methodology: the original 1976 paper, the NMS refinement, Conjoint.ly, Sawtooth Software, ESOMAR, Lipovetsky, Decision Analyst.
- Packaging anti-patterns: ProfitWell, OpenView, Bessemer vertical SaaS research, Ramanujam, Poyar, SaaS Capital.

## Assumptions

Pricing decisions are joint: Commercial owns the model and tier shape, Product owns features-per-tier, Finance owns the discount envelope, Legal owns the contract. Van Westendorp PSM is directional — N ≥ 30 minimum, N ≥ 100 preferred; below 30, flag a sample-size warning. "Value-based pricing" requires a measurable value driver (revenue lift, cost saved, time recovered) — without it, don't pick value-based. Industry profiles tune defaults, they don't override your data. Output is a model and a range, never the number.

## Anti-patterns

Recommending a specific number (final price is a human commercial decision involving deal-desk policy, competitive intel, and strategic intent this methodology can't know); using PSM with N < 30 (statistical noise dominates); treating PSM as "the price" rather than a Range of Acceptable Prices to test in market; picking value-based pricing without a measurable value metric (it collapses into "whatever they'll pay," which is just bad usage-based pricing); designing tiers before picking a model; packaging "feature dumps" into the Best tier (if Best has 3x the features for 2x the price, customers buy Better and never upgrade); hiding usage-based pricing inside a subscription tier ("up to 100k API calls/mo, then $X per 1k" is two pricing models in one — customers notice); confusing pricing strategy (the menu) with deal-desk (discounts off the menu) — different decision, different cadence, different owner.

## Forcing-question library

Walk one question at a time, never bundled. Lock 1-3 before opening 4-6.

1. Is your customer paying for outcomes, seats, or usage? Outcomes (value-based) if measurable; usage if marginal cost is variable; seats only if usage is roughly flat per user. (Ramanujam, *Monetizing Innovation* — Mistake #1 of 9: seat-based pricing on a usage-variable product caps TAM at ~20% of willingness-to-pay.)
2. Do you have a measurable value metric, or are you guessing? Instrument the value metric before going to market with value-based pricing. (Patrick Campbell / ProfitWell research — value-based without instrumentation collapses into bad usage-based pricing.)
3. What's the variance in customer usage across your top decile vs. median? Variance > 10x favors usage-based; < 3x favors subscription; in between favors hybrid with usage overage. (Kyle Poyar, *Growth Unhinged* — high-variance products lose 60%+ of revenue on flat-rate plans.)
4. What's your competitor's pricing model, and why are you choosing the same or different? Surface the differentiation hypothesis explicitly — identical pricing is an identical value claim. (David Skok, *For Entrepreneurs* — pricing is a positioning signal.)
5. What sample size do you have for willingness-to-pay analysis, and is it segmented? N ≥ 30 per segment for PSM, N ≥ 100 for conjoint. (van Westendorp 1976 / Sawtooth Software methodology — sub-30 PSM is statistical noise.)
6. What's the ONE feature that forces a tier upgrade? Every Better and Best tier needs a single non-negotiable upgrade trigger. (Ramanujam, *Monetizing Innovation* — Mistake #4: tiers with no clear differentiator make 70% of customers pick the cheapest.)

After all 6 are answered, apply the pricing-model picker, then the willingness-to-pay analyzer, then the packaging designer, in that sequence.