Pricing Strategy
You are an expert in SaaS pricing and monetization strategy with access to pricing research data and analysis tools. Your goal is to help design pricing that captures value, drives growth, and aligns with customer willingness to pay.
Before Starting
Gather this context (ask if not provided):
1. Business Context
2. Value & Competition
3. Current Performance
4. Goals
---
Pricing Fundamentals
The Three Pricing Axes
Every pricing decision involves three dimensions:
1. Packaging — What's included at each tier?
2. Pricing Metric — What do you charge for?
3. Price Point — How much do you charge?
Value-Based Pricing Framework
Price should be based on value delivered, not cost to serve:
┌─────────────────────────────────────────────────────────┐
│ │
│ Customer's perceived value of your solution │
│ ────────────────────────────────────────────── $1000 │
│ │
│ ↑ Value captured (your opportunity) │
│ │
│ Your price │
│ ────────────────────────────────────────────── $500 │
│ │
│ ↑ Consumer surplus (value customer keeps) │
│ │
│ Next best alternative │
│ ────────────────────────────────────────────── $300 │
│ │
│ ↑ Differentiation value │
│ │
│ Your cost to serve │
│ ────────────────────────────────────────────── $50 │
│ │
└─────────────────────────────────────────────────────────┘
Key insight: Price between the next best alternative and perceived value. Cost is a floor, not a basis.
---
Pricing Research Methods
Van Westendorp Price Sensitivity Meter
The Van Westendorp survey identifies the acceptable price range for your product.
The Four Questions:
Ask each respondent:
1. "At what price would you consider [product] to be so expensive that you would not consider buying it?" (Too expensive)
2. "At what price would you consider [product] to be priced so low that you would question its quality?" (Too cheap)
3. "At what price would you consider [product] to be starting to get expensive, but you still might consider it?" (Expensive/high side)
4. "At what price would you consider [product] to be a bargain—a great buy for the money?" (Cheap/good value)
How to Analyze:
1. Plot cumulative distributions for each question
2. Find the intersections:
- Point of Marginal Cheapness (PMC): "Too cheap" crosses "Expensive"
- Point of Marginal Expensiveness (PME): "Too expensive" crosses "Cheap"
- Optimal Price Point (OPP): "Too cheap" crosses "Too expensive"
- Indifference Price Point (IDP): "Expensive" crosses "Cheap"
The acceptable price range: PMC to PME
Optimal pricing zone: Between OPP and IDP
Survey Tips:
Sample Van Westendorp Analysis Output:
Price Sensitivity Analysis Results:
─────────────────────────────────
Point of Marginal Cheapness: $29/mo
Optimal Price Point: $49/mo
Indifference Price Point: $59/mo
Point of Marginal Expensiveness: $79/mo
Recommended range: $49-59/mo
Current price: $39/mo (below optimal)
Opportunity: 25-50% price increase without significant demand impact
MaxDiff Analysis (Best-Worst Scaling)
MaxDiff identifies which features customers value most, informing packaging decisions.
How It Works:
1. List 8-15 features you could include
2. Show respondents sets of 4-5 features at a time
3. Ask: "Which is MOST important? Which is LEAST important?"
4. Repeat across multiple sets until all features compared
5. Statistical analysis produces importance scores
Example Survey Question:
Which feature is MOST important to you?
Which feature is LEAST important to you?
□ Unlimited projects
□ Custom branding
□ Priority support
□ API access
□ Advanced analytics
Analyzing Results:
Features are ranked by utility score:
Using MaxDiff for Packaging:
| Utility Score | Packaging Decision |
|---------------|-------------------|
| Top 20% | Include in all tiers (table stakes) |
| 20-50% | Use to differentiate tiers |
| 50-80% | Higher tiers only |
| Bottom 20% | Consider cutting or premium add-on |
Willingness to Pay Surveys
Direct method (simple but biased):
"How much would you pay for [product]?"
Better: Gabor-Granger method:
"Would you buy [product] at [$X]?" (Yes/No)
Vary price across respondents to build demand curve.
Even better: Conjoint analysis:
Show product bundles at different prices
Respondents choose preferred option
Statistical analysis reveals price sensitivity per feature
---
Value Metrics
What is a Value Metric?
The value metric is what you charge for—it should scale with the value customers receive.
Good value metrics:
Common Value Metrics
| Metric | Best For | Example |
|--------|----------|---------|
| Per user/seat | Collaboration tools | Slack, Notion |
| Per usage | Variable consumption | AWS, Twilio |
| Per feature | Modular products | HubSpot add-ons |
| Per contact/record | CRM, email tools | Mailchimp, HubSpot |
| Per transaction | Payments, marketplaces | Stripe, Shopify |
| Flat fee | Simple products | Basecamp |
| Revenue share | High-value outcomes | Affiliate platforms |
Choosing Your Value Metric
Step 1: Identify how customers get value
Step 2: Map usage to value
| Usage Pattern | Value Delivered | Potential Metric |
|---------------|-----------------|------------------|
| More team members use it | More collaboration value | Per user |
| More data processed | More insights | Per record/event |
| More revenue generated | Direct ROI | Revenue share |
| More projects managed | More organization | Per project |
Step 3: Test for alignment
Ask: "As a customer uses more of [metric], do they get more value?"
Mapping Usage to Value: Framework
1. Instrument usage data
Track how customers use your product:
2. Correlate with customer success
3. Identify value thresholds
Example Analysis:
Usage-Value Correlation Analysis:
─────────────────────────────────
Segment: High-LTV customers (>$10k ARR)
Average monthly active users: 15
Average projects: 8
Average integrations: 4
Segment: Churned customers
Average monthly active users: 3
Average projects: 2
Average integrations: 0
Insight: Value correlates with team adoption (users)
and depth of use (integrations)
Recommendation: Price per user, gate integrations to higher tiers
---
Tier Structure
How Many Tiers?
2 tiers: Simple, clear choice
3 tiers: Industry standard
4+ tiers: More granularity
Good-Better-Best Framework
Good tier (Entry):
Better tier (Recommended):
Best tier (Premium):
Tier Differentiation Strategies
Feature gating:
Usage limits:
Support level:
Access and customization:
Example Tier Structure
┌────────────────┬─────────────────┬─────────────────┬─────────────────┐
│ │ Starter │ Pro │ Business │
│ │ $29/mo │ $79/mo │ $199/mo │
├────────────────┼─────────────────┼─────────────────┼─────────────────┤
│ Users │ Up to 5 │ Up to 20 │ Unlimited │
│ Projects │ 10 │ Unlimited │ Unlimited │
│ Storage │ 5 GB │ 50 GB │ 500 GB │
│ Integrations │ 3 │ 10 │ Unlimited │
│ Analytics │ Basic │ Advanced │ Custom │
│ Support │ Email │ Priority │ Dedicated │
│ API Access │ ✗ │ ✓ │ ✓ │
│ SSO │ ✗ │ ✗ │ ✓ │
│ Audit logs │ ✗ │ ✗ │ ✓ │
└────────────────┴─────────────────┴─────────────────┴─────────────────┘
---
Packaging for Personas
Identifying Pricing Personas
Different customers have different:
Segment by:
Persona-Based Packaging
Step 1: Define personas
| Persona | Size | Needs | WTP | Example |
|---------|------|-------|-----|---------|
| Freelancer | 1 person | Basic features | Low | $19/mo |
| Small Team | 2-10 | Collaboration | Medium | $49/mo |
| Growing Co | 10-50 | Scale, integrations | Higher | $149/mo |
| Enterprise | 50+ | Security, support | High | Custom |
Step 2: Map features to personas
| Feature | Freelancer | Small Team | Growing | Enterprise |
|---------|------------|------------|---------|------------|
| Core features | ✓ | ✓ | ✓ | ✓ |
| Collaboration | — | ✓ | ✓ | ✓ |
| Integrations | — | Limited | Full | Full |
| API access | — | — | ✓ | ✓ |
| SSO/SAML | — | — | — | ✓ |
| Audit logs | — | — | — | ✓ |
| Custom contract | — | — | — | ✓ |
Step 3: Price to value for each persona
---
Freemium vs. Free Trial
When to Use Freemium
Freemium works when:
Freemium risks:
Example: Slack
When to Use Free Trial
Free trial works when:
Trial best practices:
Credit card upfront:
Hybrid Approaches
Freemium + Trial:
Reverse trial:
---
When to Raise Prices
Signs It's Time
Market signals:
Business signals:
Product signals:
Price Increase Strategies
1. Grandfather existing customers
2. Delayed increase for existing
3. Increase tied to value
4. Plan restructure
Communicating Price Increases
For new customers:
For existing customers:
Subject: Updates to [Product] pricing
Hi [Name],
I'm writing to let you know about upcoming changes to [Product] pricing.
[Context: what you've added, why change is happening]
Starting [date], our pricing will change from [old] to [new].
As a valued customer, [what this means for them: grandfathered, locked rate, timeline].
[If they're affected:]
You have until [date] to [action: lock in current rate, renew at old price].
[If they're grandfathered:]
You'll continue at your current rate. No action needed.
We appreciate your continued support of [Product].
[Your name]
---
Pricing Page Best Practices
Above the Fold
Tier Presentation
Common Elements
Pricing Psychology to Apply
---
Price Testing
Methods for Testing Price
1. A/B test pricing page (risky)
2. Geographic testing
3. New customer only
4. Sales team discretion
5. Feature-based testing
What to Measure
---
Enterprise Pricing
When to Add Custom Pricing
Add "Contact Sales" when:
Enterprise Tier Elements
Table stakes:
Value-adds:
Enterprise Pricing Strategies
Per-seat at scale:
Platform fee + usage:
Value-based contracts:
---
Pricing Checklist
Before Setting Prices
Pricing Structure
Validation
---
Questions to Ask
If you need more context:
1. What pricing research have you done (surveys, competitor analysis)?
2. What's your current ARPU and conversion rate?
3. What's your primary value metric (what do customers pay for value)?
4. Who are your main pricing personas (by size, use case)?
5. Are you self-serve, sales-led, or hybrid?
6. What pricing changes are you considering?
---
Related Skills
相关技能
- A
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
- A
analytics-tracking
When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," or "tracking plan." For A/B test measurement, see ab-test-setup.
- A
atxp
Access ATXP paid API tools for web search, AI image generation, music creation, video generation, and X/Twitter search. Use when users need real-time web search, AI-generated media (images, music, video), or X/Twitter search. Requires authentication via `npx atxp login`.
- B
better-auth-best-practices
Skill for integrating Better Auth - the comprehensive TypeScript authentication framework.
- B
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.