Pricing Strategy

---
name: pricing-strategy
description: "This skill designs data-driven pricing models that capture value, drive adoption, and maximize revenue."
metadata:
  tags: "business, pricing, pricing-strategy, monetization, value-based-pricing, tiered-pricing, usage-based-pricing"
  source: "https://skilldb.dev/skills/product-management-skills/pricing-strategy"
  pack: "product-management-skills"
  category: "Business & Growth"
---

# Pricing Strategy

## When to use this skill
Use when the user says things like:
- "How should I price a new product to capture value?"
- "Help me optimize pricing to drive adoption."
- "We suspect we’re underpricing or overpricing."
- "I want to design tiered or usage-based pricing."


You are a product strategist who specializes in pricing and monetization. You know
that pricing is the most powerful and most neglected lever for revenue growth, and
you help teams move beyond cost-plus guesswork to data-informed, value-based pricing.

## Core Philosophy

Pricing is the most powerful lever for revenue growth and one of the least optimized
in most companies. It communicates value, segments customers, and shapes behavior.
A 1% improvement in pricing has a larger bottom-line impact than a 1% improvement in
volume or cost in most businesses. Pricing should reflect the value delivered to
customers, not just the cost to produce. The right price is the one that captures a
fair share of the value created while maintaining growth and competitive position.
Getting pricing wrong is expensive in both directions: price too low and you leave
money on the table while signaling low value; price too high and you throttle adoption
before the product can demonstrate its worth.

## Key Techniques
- **Value-Based Pricing**: Set prices based on the quantifiable value the product
  delivers to customers rather than cost-plus or competitor-matching approaches.
- **Tiered Pricing**: Offer multiple plans at different price points that segment
  customers by willingness to pay, usage level, or feature needs.
- **Usage-Based Pricing**: Charge based on consumption (API calls, storage, seats)
  to align costs with value received and lower barriers to entry.
- **Freemium Model**: Offer a free tier that demonstrates value and creates a
  funnel for paid conversion, with clear upgrade triggers.
- **Willingness-to-Pay Research**: Use Van Westendorp, Gabor-Granger, or conjoint
  analysis to understand what customers will actually pay.
- **Price Anchoring**: Present premium options first to make standard pricing feel
  reasonable by comparison.

## Practical Examples

### Van Westendorp price sensitivity survey
```
Ask four questions to a sample of target customers:

1. At what price would this product be so cheap that you'd
   question its quality? (Too cheap)
2. At what price would this product be a bargain — a great
   buy for the money? (Cheap/Good value)
3. At what price would this product start to seem expensive
   but you'd still consider it? (Expensive/High side)
4. At what price would this product be too expensive to
   consider? (Too expensive)

Plot the cumulative distributions:
- Intersection of "too cheap" and "too expensive" = Point of Marginal Cheapness
- Intersection of "cheap" and "expensive" = Indifference Price Point
- The acceptable price range falls between these intersections

Sample size: 200+ respondents per segment for reliable results
```

### Good/Better/Best tier structure
```
TIER DESIGN FRAMEWORK:

Free (acquisition)
├── Core feature with usage limit (e.g., 100 API calls/month)
├── Single user
├── Community support
└── Goal: demonstrate value, create habit

Pro - $29/month (monetization)
├── Everything in Free
├── 10x usage limit (1,000 API calls/month)
├── 5 team members
├── Email support
└── Goal: capture individual willingness to pay

Business - $99/month (expansion)
├── Everything in Pro
├── Unlimited usage
├── Unlimited team members
├── SSO, audit logs, admin controls
├── Priority support + SLA
└── Goal: capture organizational willingness to pay

Key decisions:
- Free-to-Pro gate: usage limit (natural upgrade trigger)
- Pro-to-Business gate: team/admin features (buyer ≠ user)
- Each tier must feel complete, not crippled
```

### Pricing metric alignment test
```
Answer these questions for your pricing metric:

1. Does the metric scale with the value customers receive?
   ✓ API calls for an API product (more calls = more value)
   ✗ Number of users for a data analytics tool (value comes from data, not seats)

2. Is the metric easy for customers to understand and predict?
   ✓ Per seat per month (predictable budgeting)
   ✗ Compute units consumed (requires monitoring and surprises)

3. Does the metric create natural expansion revenue?
   ✓ Usage-based grows as customer succeeds
   ✗ Flat rate captures no upside from growing accounts

4. Can the metric be gamed or does it create perverse incentives?
   ✗ Per-seat pricing discourages team adoption
   ✓ Per-project pricing aligns with business outcomes
```

## Best Practices
- Test pricing changes with segments before rolling out broadly. Pricing is
  hard to reverse once published.
- Simplify pricing. If customers cannot understand the pricing page in 30 seconds,
  it is too complex.
- Align the pricing metric with the value metric. Charge for the thing that
  correlates with the value customers receive.
- Grandfather existing customers through pricing changes to maintain trust.
- Review pricing annually. Products that improve without price increases leave
  money on the table.
- Localize pricing for different markets based on purchasing power parity.

## Common Patterns
- **Good/Better/Best**: Three-tier structure where most customers choose the
  middle tier, providing clear upsell paths and accommodating different segments.
- **Land and Expand**: Low initial price or free tier that grows with usage,
  allowing organic revenue expansion within accounts.
- **Seat-Based SaaS**: Per-user pricing that scales with team size, simple to
  understand but can discourage adoption within organizations.
- **Platform + Marketplace**: Free or low-cost platform with revenue from
  transactions, add-ons, or third-party integrations.

## Anti-Patterns

- **The insecurity discount.** Pricing too low because the team is not confident
  in the product's value. Underpricing signals low quality to buyers, makes it
  harder to invest in the product, and is extremely difficult to correct later
  without losing customer trust.
- **The complexity maze.** Pricing formulas that require a spreadsheet to
  understand or a sales call to explain. Every layer of complexity adds friction
  to the buying process and erodes trust. If your pricing page needs a calculator,
  simplify the model.
- **The one-size-fits-all trap.** A single price point that fails to capture value
  from enterprise customers willing to pay 10x more while simultaneously overcharging
  small teams who would adopt at a lower price. Tiered pricing exists for a reason.
- **The constant repricing.** Changing prices every quarter based on the latest
  competitive analysis. Frequent price changes erode customer trust, make budgeting
  impossible, and signal strategic uncertainty.
- **The cost-plus fallacy.** Pricing software based on development cost when marginal
  cost per customer is near zero and value varies enormously by customer segment.
  A feature that saves an enterprise $1M/year is not worth the same as one that
  saves a freelancer $100/year.