Pricing Monetization Strategy

Standing Mandates

• ALWAYS identify the value metric before designing tiers or pricing levels.
• ALWAYS validate willingness-to-pay signals before committing to a pricing model.
• NEVER design pricing without understanding the customer's buying process and budget cycle.
• NEVER recommend a pricing model change without analyzing impact on churn and expansion revenue.

Purpose

Pricing is a product decision, not a finance decision. It signals value, shapes who buys, and determines growth mechanics. This skill answers:

1. What model fits how customers receive value? (pricing model)
2. What is the right value metric? (what you charge for)
3. How do we structure tiers? (packaging)
4. What should we charge? (price point)
5. What are we optimizing for? (growth, margin, ARR, retention)

This skill produces a Pricing Model Recommendation and a Packaging Structure.

When to Use This

• When building a GTM plan — feeds ../go-to-market-planning/SKILL.md
• When competitive pricing benchmarks are needed — input from ../competitive-analysis/SKILL.md
• When customer research reveals willingness-to-pay signals — input from ../customer-research-synthesis/SKILL.md
• When pricing is a core component of the PRD — references ../prd-development/SKILL.md

When NOT to Use This

• For pricing a services engagement or consulting project (different dynamics)
• As a substitute for actual WTP research — this gives you the framework; you still need to talk to customers
• When pricing is locked by leadership or legal contract — focus on packaging instead

Step 1 — Understand the Value Exchange (20 min)

Before picking a model, understand how value is delivered and consumed.

Value Delivery Questions

1. When does the customer first experience value? (immediately on signup? after setup? after a threshold of use?)
2. How does value scale for the customer? (more users? more data? more integrations? more output?)
3. Is value delivered continuously or in discrete events?
4. Who is the economic buyer vs. the end user? (they may differ — price to the buyer, sell to the user)
5. How long does it take a customer to realize value? (time-to-value affects trial vs. freemium choice)

Step 2 — Select the Pricing Model (20 min)

Pricing Model Taxonomy

Decision Framework

Answer these four questions to narrow the model:

Step 3 — Choose the Value Metric (15 min)

The value metric is what you charge for. It should:

• Correlate directly with the value the customer receives
• Scale naturally as the customer gets more value
• Be easy for the customer to understand and predict their bill
• Be hard for competitors to undercut (not pure commodity)

Common Value Metrics by Category

Value Metric Validation Test

A good value metric passes all three:

1. The customer understands it — can they predict next month's bill?
2. It grows with customer success — more value = more usage = more revenue
3. It aligns incentives — you win when the customer wins, not when they fail

Step 4 — Design the Packaging Structure (30 min)

Packaging = how you group features and value metrics into tiers.

The Three-Tier Framework (Most Common SaaS)

Packaging Design Principles

1. Each tier should have one natural buyer. If two different personas both buy the middle tier, you may have a missing tier or a misaligned value metric.
2. Put the feature that drives conversion in the first paid tier, not free. The free/starter tier shows value; the paid tier captures it.
3. Enterprise tier should have at least one feature that only enterprise buyers care about (SSO, audit logs, SLA, custom contracts). This prevents enterprise buyers from getting stuck in mid-tier.
4. Avoid "feature salami" — don't split a single feature across tiers as artificial gatekeeping. Users will resent it.
5. Limit tiers to three or four. More than four tiers adds cognitive load and slows purchase decisions.

Packaging Template

## [Product Name] Pricing Structure

### [Free / Starter Tier] — $[X]/mo
Target: [Who]
Value prop: [One sentence]
Includes:
- [Core capability — enough to show value]
- [Value metric limit: e.g., "up to 3 users" / "1,000 API calls/mo"]
Excludes (requires upgrade):
- [Key paid feature 1]
- [Key paid feature 2]

### [Growth / Pro Tier] — $[Y]/mo per [unit]
Target: [Who]
Value prop: [One sentence]
Includes everything in Starter, plus:
- [Feature that drives conversion]
- [Feature]
- [Value metric limit: e.g., "up to 25 users" / "100,000 API calls/mo"]

### [Enterprise / Scale Tier] — Custom / $[Z]/mo
Target: [Who]
Value prop: [One sentence]
Includes everything in Growth, plus:
- [SSO / SAML]
- [Audit logs / compliance]
- [Dedicated support / SLA]
- [Custom contracts / invoicing]
- Unlimited [value metric]

Step 5 — Research Willingness to Pay (20 min)

Don't guess the price point. Use structured research.

WTP Research Methods

Van Westendorp Price Sensitivity Meter (Fastest)

Ask 4 questions to 15-30 target customers:

1. At what price would this product be so cheap you'd question the quality?
2. At what price would this product be a bargain — great value?
3. At what price would this product start to feel expensive, but you'd still consider it?
4. At what price would this product be too expensive and you'd rule it out?

Plot responses to find the Acceptable Price Range (between "too cheap" and "too expensive" intersections).

Conjoint / Trade-off Research

Ask customers to choose between feature/price configurations. Reveals which features drive WTP and which don't.

Competitor Benchmarking

From ../competitive-analysis/SKILL.md:

• Where do competitors price?
• What segment do they over/under-serve?
• Can you charge a premium for a differentiated capability, or must you match?

Sales/CS Interviews (Fastest for B2B)

Ask: "Have you ever lost a deal because of price? What was the threshold?" — even 5-10 conversations give strong signal.

Step 6 — Common Pricing Anti-Patterns