Pricing Strategist
Expert pricing strategy and monetization guidance for SaaS and digital products — from psychology-driven pricing to enterprise negotiation tactics.
Philosophy
Pricing is the most powerful lever in your business:
- Price is a signal — It communicates value, market position, and customer fit
- Packaging is product — How you bundle features shapes perceived value
- Simplicity wins — Confused buyers don't buy
- Test everything — Intuition about willingness-to-pay is usually wrong
How This Skill Works
When invoked, apply the guidelines in rules/ organized by:
psychology-* — Behavioral economics, anchoring, framing, decoy pricingpackaging-* — Tier structure, bundles, good/better/best frameworksmetrics-* — Value metrics, usage-based, per-seat, flat-rate modelspage-* — Pricing page copy, design, and conversion optimizationenterprise-* — Enterprise pricing, negotiation, custom dealslifecycle-* — Discounts, promotions, price increases, grandfathering
Core Frameworks
The Pricing Stack
┌─────────────────────────────────────────────────────────┐
│ VALUE CREATION │
│ What problem do you solve? How well? │
├─────────────────────────────────────────────────────────┤
│ VALUE COMMUNICATION │
│ How do you convey value through pricing? │
├─────────────────────────────────────────────────────────┤
│ VALUE CAPTURE │
│ How much value do you extract as price? │
└─────────────────────────────────────────────────────────┘
Pricing Model Comparison
Value Metric Selection
Your value metric should be:
The Willingness-to-Pay Curve
High WTP │ ●●● Enterprise
│ ●●●●●
│ ●●●●●●● Pro
│ ●●●●●●●●●
│●●●●●●●●●●● Starter
Low WTP │●●●●●●●●●●●●●
└────────────────────
Few Many
Customers
Capture value at each segment with differentiated packaging.
Pricing Psychology Principles
Packaging Framework
Good/Better/Best Structure
Feature Fencing Strategies
Annual vs Monthly Framework
Anti-Patterns
- Race to bottom — Competing on price alone destroys margins
- Complexity overload — 6+ tiers confuse buyers
- Feature stuffing — More features ≠ higher perceived value
- Discount addiction — Training customers to wait for sales
- One-size pricing — Leaving money on table from high-value customers
- Hidden fees — Surprise charges destroy trust
- Anchoring backwards — Showing cheapest option first
- Ignoring segments — Same price for SMB and enterprise
Supporting file: rules/_sections.md
1. Pricing Psychology (psychology)
Impact: CRITICAL
Description: Behavioral economics principles, anchoring, framing, decoy pricing, charm pricing, and cognitive biases that influence purchasing decisions.
2. Packaging Strategy (packaging)
Impact: CRITICAL
Description: Good/better/best tier design, bundle strategies, feature fencing, and plan differentiation.
3. Value Metrics & Models (metrics)
Impact: CRITICAL
Description: Per-seat, usage-based, flat-rate, hybrid models, and choosing the right value metric.
4. Pricing Page Optimization (page)
Impact: HIGH
Description: Pricing page copy, layout, conversion optimization, plan comparison design, and CTA strategy.
5. Enterprise Pricing (enterprise)
Impact: HIGH
Description: Custom pricing, negotiation tactics, contract terms, and high-value deal structures.
6. Discounts & Promotions (discounts)
Impact: MEDIUM-HIGH
Description: Discount strategies, promotional frameworks, annual incentives, and avoiding discount addiction.
7. Price Lifecycle (lifecycle)
Impact: MEDIUM-HIGH
Description: Price increases, grandfathering, price change communication, and migration strategies.
8. Competitive Pricing (competitive)
Impact: MEDIUM
Description: Competitive analysis, positioning relative to alternatives, and market-based pricing strategies.
Supporting file: rules/competitive-pricing-analysis.md
Competitive Pricing Analysis
Impact: MEDIUM
Understanding competitive pricing informs your positioning, but copying competitors is a race to the bottom. Use competitive analysis to differentiate, not duplicate.
Competitive Pricing Matrix
Competitive Analysis Framework
Where to Find Competitive Pricing
Competitive Pricing Positions
Positioning Decision Matrix
Low High
├─────────────────────────┤
┌───┴───┐ ┌─────┴─────┐
High │Premium│ │ Market │
Value │ Price │ │ Leader │
└───┬───┘ └─────┬─────┘
│ │
┌───┴───┐ ┌─────┴─────┐
Low │ Avoid │ │ Value │
Value │ (lose)│ │ Player │
└───────┘ └───────────┘
Low High
Relative Price
Differentiation Over Price Matching
Good Competitive Response
Scenario: Competitor drops price by 30%
✓ Good response:
"We're aware [Competitor] has reduced their prices. We've
decided to maintain our pricing because:
1. Our customers tell us our product saves them 10+ hours/week
2. Our 99.99% uptime SLA is unmatched
3. Our support response time is 2 hours vs their 24+
If price is your primary consideration, [Competitor] may be
a better fit. If value is, we're here."
→ Confident, differentiated, not reactive
Bad Competitive Response
Scenario: Competitor drops price by 30%
✗ Bad response:
"PRICE MATCH SALE! For a limited time, we're matching
[Competitor]'s new lower prices!"
→ Looks desperate, damages brand, trains discounting
✗ Also bad:
"[Competitor]'s cheap pricing is because they cut corners
on security and support."
→ Negative selling rarely works, looks defensive
Competitive Price Justification
Competitive Objection Handling
Good Objection Response
Prospect: "Competitor X is 40% cheaper."
Response: "You're right—Competitor X is less expensive upfront.
Here's what I'd encourage you to factor in:
1. Implementation: We're self-serve in 10 minutes. They require
a 3-week implementation with professional services.
2. Support: We offer 24/7 support at all tiers. Their comparable
support tier is actually more expensive than us.
3. ROI: Our customers report 5 hours/week saved. At $50/hour,
that's $13,000/year per user.
When you factor in total cost and value, we're often the
better investment. Want to walk through the comparison?"
Competitive Monitoring
Competitive Intel Sources
Pricing Page Comparison Best Practices
Good Comparison Page
✓ "How we compare to [Competitor]"
| Feature | Us | [Competitor] |
|---------|-----|--------------|
| Starting price | $29/mo | $49/mo |
| Free trial | 14 days | 7 days |
| Uptime SLA | 99.99% | 99.5% |
| Support response | 2 hours | 24 hours |
| SSO included | Pro tier | Enterprise only |
"Both products solve [problem]. Here's how to decide:
• Choose us if: You value [X, Y, Z]
• Choose [Competitor] if: You need [A, B, C]"
→ Factual, fair, helps buyers decide
Anti-Patterns
- Obsessive monitoring — Spending more time on competitors than customers
- Price matching — Racing to the bottom
- Negative selling — Bashing competitors looks desperate
- Ignoring competitors — Not knowing your market
- Copy-paste pricing — Identical structure without strategy
- Reacting to every move — Chasing instead of leading
- Outdated competitive info — Using stale pricing/features
- Single-competitor focus — Ignoring the broader market
Supporting file: rules/discounts-annual-monthly.md
Discounts and Annual vs Monthly Positioning
Impact: MEDIUM-HIGH
Strategic discounting can accelerate growth; undisciplined discounting destroys margins and trains customers to wait. Annual vs monthly framing significantly impacts LTV and cash flow.
The Discount Spectrum
Annual vs Monthly Economics
Monthly at $99/mo:
├── Year 1 Revenue: $1,188 (if no churn)
├── Typical churn: 5-8% monthly
├── Expected Year 1: ~$900
└── Payment: 12 transactions
Annual at $948/yr ($79/mo equivalent):
├── Year 1 Revenue: $948 (guaranteed)
├── Churn: Annual renewal point only
├── Expected Year 1: $948
└── Payment: 1 transaction, upfront cash
Annual Discount Guidelines
Framing Annual Savings
Good Annual Framing
✓ Toggle Design:
[Monthly $99/mo] [Annual $79/mo — Save $240]
✓ Explicit savings:
"Pay annually and get 2 months free"
✓ Breakdown:
"$948/year = $79/month (billed annually)
You save $240 compared to monthly"
✓ Comparison:
"Monthly: $1,188/year
Annual: $948/year (20% off)"
Bad Annual Framing
✗ Confusing display:
"$79/mo (annual) or $99/mo"
→ Which is which? Confusing.
✗ Hidden billing:
"$79/mo" (small print: billed as $948 annually)
→ Feels deceptive
✗ Discount feels fake:
"Annual: $79/mo (was $199/mo)"
→ Nobody believes the fake anchor
✗ No toggle, only annual:
Hides monthly option entirely
→ Reduces trust
Startup Program Design
Good Startup Program
✓ Startups get 75% off Year 1
Eligibility:
• Less than $2M in funding
• Less than 2 years since founding
• Less than 20 employees
Apply with a 2-minute form.
Most applications approved within 24 hours.
Nonprofit/Education Discounts
Promotional Discount Types
Promotional Discount Guidelines
Good Promotional Example
✓ Launch discount:
"We just launched AI features.
First 500 customers get 25% off annual plans.
Use code AILAUNCH at checkout.
Offer ends Friday at midnight PT."
Clear: reason, limit, timeframe, how to redeem
Bad Promotional Example
✗ Perpetual discount:
"Use code SAVE20 for 20% off! (running for 2 years)"
→ Not a real promotion, just a lower price
✗ Discount without reason:
"Big savings! 40% off this week!"
→ Why? Feels desperate
✗ Complicated redemption:
"Email sales@company.com with code SPECIALOFFER
to schedule a call to discuss discount eligibility"
→ Too much friction
Discount Ladder for Win-Back
Discount Documentation
Discount Approval Matrix
Metrics to Track
Anti-Patterns
- Always-on discounts — Trains customers to never pay full price
- Discount without commitment — Give discount, get nothing in return
- Hidden annual requirement — Price looks monthly but requires annual
- No limit on negotiations — Reps can give any discount
- Ignoring LTV impact — Heavily discounted customers may churn faster
- Promotional addiction — Every month has a "sale"
- Inconsistent policies — Different customers get wildly different deals
- No graduation path — Startup pricing forever
Supporting file: rules/enterprise-pricing-negotiation.md
Enterprise Pricing and Negotiation
Impact: HIGH
Enterprise deals require different pricing psychology, longer sales cycles, and strategic negotiation. The goal is value-based pricing, not cost-plus or competitive matching.
Enterprise vs Self-Serve Differences
Enterprise Feature Gates
Value-Based Pricing Framework
Enterprise Price = Value Delivered × Capture Rate
Value Delivered:
├── Time saved (hours × hourly rate)
├── Risk reduced (cost of incident × probability)
├── Revenue enabled (additional revenue attributable)
└── Costs avoided (vs alternative solutions)
Capture Rate: 10-30% of value (typical)
Calculating Enterprise Value
Enterprise Discount Structure
Good Discount Structure
✓ Multi-Year Pricing:
├── 1 year: $150,000/year (full price)
├── 2 years: $135,000/year (10% off)
└── 3 years: $120,000/year (20% off)
✓ Volume Tiers:
├── 1-50 seats: $50/seat/mo
├── 51-200 seats: $45/seat/mo (10% off)
├── 201-500 seats: $40/seat/mo (20% off)
└── 500+ seats: Custom pricing
Bad Discount Practices
✗ Unlimited negotiation:
"We can do whatever you need on price"
→ No anchor, race to bottom
✗ Discounting without getting something:
"Fine, 30% off, same terms"
→ Leaving money on table
✗ Visible desperation:
"Quarter ends Friday, I can do 50% off today only"
→ Signals weakness, trains future behavior
✗ Inconsistent across customers:
Customer A pays $100K, Customer B pays $50K for same thing
→ Destroys trust when discovered
Negotiation Levers
Negotiation Best Practices
Enterprise Pricing Page Copy
Good Enterprise Page Copy
✓ Tier card:
ENTERPRISE
"For organizations with advanced security needs"
• Everything in Pro, plus:
• SSO with SAML 2.0
• SCIM user provisioning
• 99.99% uptime SLA
• Dedicated success manager
• Custom contract terms
• SOC 2 Type II compliant
[Talk to Sales]
"Get a custom quote for your team"
Bad Enterprise Page Copy
✗ "Enterprise Plan: Contact Us"
→ No value proposition, no feature list
✗ "For big companies with big needs"
→ Vague, not professional
✗ "Price: $$$$$"
→ Looks ridiculous
✗ "[Get Quote]" button only
→ No context on what enterprise includes
Contract Elements
Handling Common Objections
Good Objection Handling
Objection: "Your competitor offers the same thing for 30% less."
Response: "I understand price is important. Let me share what I've
heard from customers who evaluated both:
1. Our implementation takes 2 weeks vs their 2 months
2. Our uptime is 99.99% vs their 99.5%
3. Our SSO supports 15 providers vs their 3
The 30% savings often costs more in the long run. Would it help
if I connected you with a customer who evaluated both?"
Pricing Committee/Approval Tips
Anti-Patterns
- Discounting first — Start high, never start low
- Feature-matching competitors — Compete on value, not features
- Ignoring procurement — They have power, treat them well
- No walk-away point — Willing to lose bad deals
- Price in email — Complex pricing needs conversation
- Same pitch to everyone — Customize to their specific value drivers
- Forgetting expansion — Land price matters less than expand potential
- Rushing the process — Enterprise takes time, respect the cycle
Supporting file: rules/lifecycle-price-increases.md
Price Increases and Lifecycle Communication
Impact: MEDIUM-HIGH
Price increases are necessary for healthy businesses but must be handled carefully. Poor execution causes churn, support burden, and brand damage. Good execution strengthens customer relationships.
When to Raise Prices
Price Increase Magnitude
Grandfathering Strategies
Good Grandfathering Approach
✓ Tiered transition:
"Your current price: $79/mo
New price: $129/mo
Here's your transition:
• Today - Dec 2025: $79/mo (no change)
• Jan 2026 - Dec 2026: $99/mo (25% increase)
• Jan 2027+: $129/mo (new price)
As a thank you for being an early customer, you'll always
get priority support regardless of your plan."
Bad Grandfathering Approach
✗ No warning:
"Starting immediately, your plan is now $129/mo."
→ Shock, anger, support tickets
✗ Hidden in terms:
"As per section 12.4 of our terms, prices may change..."
→ Technically legal, practically damaging
✗ Patronizing:
"We know price increases are hard, but we're confident
you'll find the value worth it!"
→ Dismissive of legitimate concerns
Communication Timeline
Email Structure for Price Increases
Subject: Important update to your [Product] plan
Hi [Name],
[What's happening - lead with facts]
Starting [date], we're updating our pricing. Your [Plan Name]
plan will change from $X/mo to $Y/mo.
[Why - be honest]
Over the past year, we've invested heavily in [specific improvements]:
• [New feature 1]
• [New feature 2]
• [Infrastructure/security improvement]
These investments require us to adjust our pricing to continue
improving [Product] for you.
[What we're doing for you]
As an existing customer, you'll keep your current pricing until
[date], giving you [X months] before the change takes effect.
[Options]
• Stay on your current plan at the new price
• Lock in current pricing with an annual commitment
• Downgrade to [lower tier] if that better fits your needs
• Cancel if [Product] no longer works for you
[How to get help]
Questions? Reply to this email or reach out to support@company.com.
Thank you for being a customer,
[Name/Team]
Good Price Increase Email
✓ Subject: "Your Acme plan pricing is changing on March 1"
Lead:
"Starting March 1, 2025, your Pro plan will increase from
$99/mo to $129/mo."
Why:
"Here's what we've built since you joined:
• AI-powered analytics (launched January)
• 99.99% uptime SLA (up from 99.9%)
• SOC 2 Type II certification
• 24/7 live chat support
To continue investing in these improvements, we're
adjusting our pricing for the first time in 3 years."
Transition:
"Because you've been with us since [date], you'll keep
your current $99/mo pricing through June 1, 2025."
Options:
"If you'd like to lock in $99/mo for another year,
you can switch to annual billing anytime before March 1."
Bad Price Increase Email
✗ Subject: "Exciting news about your account!"
→ Misleading, erodes trust
✗ Lead: "We're thrilled to announce pricing updates!"
→ Tone-deaf, customers aren't thrilled
✗ Why: "Due to market conditions and operational costs..."
→ Vague, no value explanation
✗ No timeline: "Prices will change soon"
→ Creates anxiety, unclear
✗ No options: "Your new price is $X, thanks!"
→ Feels forced, no agency
FAQ for Price Increases
Handling Pushback
Good Pushback Handling
Customer: "30% increase is ridiculous. I'm canceling."
Response: "I hear you—a 30% increase is significant, and I
understand if that changes your calculation.
Before you cancel, I want to make sure you know your options:
1. Lock in current pricing for 12 months with annual billing
2. Downgrade to our Starter plan at $X/mo
3. If neither works, I can offer a 3-month extension at
current pricing while you evaluate alternatives
What matters most to you right now?"
New Price vs Old Price for New Customers
Price Decrease Considerations
Metrics to Track During Price Change
Price Increase Checklist
Anti-Patterns
- Surprise increases — No warning, immediate change
- Vague justification — "Costs are rising" without specifics
- No grandfathering — Forcing everyone to new price immediately
- Celebrating price hikes — "Exciting news!" is tone-deaf
- Hiding behind legal — "Per terms, we can change prices"
- Ignoring feedback — Not responding to customer concerns
- Too frequent — Annual increases erode trust
- No options — Take new price or leave
- Poor timing — During customer's renewal, without notice
Supporting file: rules/metrics-value-models.md
Value Metrics and Pricing Models
Impact: CRITICAL
Your value metric—what customers pay for—is the most fundamental pricing decision. It determines scalability, alignment with customer value, and revenue predictability.
Value Metric Definition
A value metric is the unit of measurement that determines how much customers pay.
Value Metric Selection Criteria
Pricing Model Comparison
Per-Seat Pricing
Structure: $X per user per month
Example:
├── 1-10 users: $15/user/mo
├── 11-50 users: $12/user/mo
└── 51+ users: $10/user/mo (volume discount)
Per-Seat Best Practices
Good Per-Seat Example
✓ Slack-style pricing:
├── Free: Unlimited users, limited history
├── Pro: $8.75/user/mo (billed annually)
└── Business+: $15/user/mo
Clear seat definition + tiered pricing + free tier for adoption
Usage-Based Pricing
Structure: $X per unit of usage
Example (API):
├── First 100K calls/mo: Free
├── 100K - 1M calls: $0.001/call
├── 1M - 10M calls: $0.0005/call
└── 10M+: $0.0002/call
Usage-Based Design Patterns
Good Usage-Based Examples
✓ Stripe's pricing:
├── 2.9% + $0.30 per transaction
└── No monthly fees, no setup
Scales perfectly with customer revenue.
✓ Twilio's pricing:
├── $0.0075/SMS sent (US)
└── Volume discounts available
Clear unit pricing, easy to forecast.
Bad Usage-Based Examples
✗ Unpredictable units:
"$0.001 per compute cycle"
→ Customer can't forecast usage
✗ Too many metrics:
"$X per API call + $Y per GB + $Z per user"
→ Impossible to understand total cost
✗ No usage visibility:
Surprise $10K bill with no dashboard
→ Destroys trust
Flat-Rate Pricing
Structure: Single price for everything
Example:
└── $99/month: All features, unlimited users
When Flat-Rate Works
Hybrid Pricing Models
Structure: Base + Variable
Example 1: Platform fee + usage
├── $99/mo base platform fee
└── + $0.10 per transaction processed
Example 2: Per-seat + usage
├── $25/user/mo base
└── + $0.001/API call above 10K
Hybrid Model Patterns
Choosing the Right Model
Value Metric by Product Type
Pricing Model Transition
Good Value Metric Example
✓ Intercom's pricing:
├── Metric: "People reached"
└── Why it works:
→ Aligns with customer success (more reach = more value)
→ Scales with customer growth
→ Easy to understand and predict
→ Encourages product usage
Bad Value Metric Example
✗ "Per active project"
→ Customers close projects to save money
→ Creates friction, not alignment
✗ "Per database row"
→ Technical metric customers don't understand
→ Penalizes data retention
✗ "Per workflow run"
→ Discourages automation
→ Opposite of value alignment
Anti-Patterns
- Misaligned metric — Customer pays more when they get less value
- Complex composite — 5+ factors in pricing calculation
- Gaming potential — Metric can be manipulated to reduce cost
- Invisible usage — Customer can't track their consumption
- Cliff pricing — Massive price jump at tier boundaries
- Metric switch — Changing value metric breaks customer trust
- Internal metric — Pricing on what's easy to track, not what aligns with value
Supporting file: rules/packaging-bundles-addons.md
Bundles and Add-ons Strategy
Impact: HIGH
Strategic bundling increases perceived value and average deal size. Add-ons create expansion revenue without tier redesign. Both require careful design to avoid complexity.
Bundle Psychology
Individual Products:
├── Product A: $100/mo (worth $100)
├── Product B: $80/mo (worth $80)
└── Product C: $60/mo (worth $60)
Total separate: $240/mo
Bundle:
└── All three: $180/mo (25% discount)
→ Perceived value: $240
→ Price: $180
→ Perceived savings: $60/mo
→ Customer: "Great deal!"
→ You: Higher ACV, lower churn, stickier
Bundle Types
Bundle Design Framework
Good Bundle Examples
✓ Atlassian Cloud Premium:
"Jira + Confluence + Jira Service Management"
→ Products that work together
→ Clear use case (software team)
→ Discount vs separate purchases
✓ Adobe Creative Cloud All Apps:
"Every creative app for one price"
→ Simplifies decision
→ Encourages exploration
→ Strong lock-in
✓ Microsoft 365 Business:
"Office + Email + Teams + OneDrive"
→ Complete solution
→ Hard to unbundle
→ High switching costs
Bad Bundle Examples
✗ Random products bundled:
"Analytics + Email + Project Management"
→ No logical connection
→ Buyer doesn't need all three
✗ Bundle cheaper than anchor:
Individual total: $150, Bundle: $140
→ Weak discount, not compelling
✗ Hidden required add-on:
"$99/mo + required $50/mo support package"
→ Feels deceptive, not a real bundle
✗ Forced bundling of unwanted features:
"To get SSO, you need the Enterprise suite"
→ Creates resentment, not value
Add-on Strategy
Add-on Pricing Guidelines
Good Add-on Examples
✓ Priority support add-on:
Base plan: $99/mo
+ Priority support: $29/mo (24-hour SLA → 2-hour SLA)
→ Clear value, reasonable price
✓ Additional storage:
Base: 100GB included
+ 100GB block: $10/mo
→ Predictable, scales with need
✓ SSO add-on:
Pro plan: $99/mo
+ SSO: $49/mo (vs Enterprise at $299/mo)
→ Lets Pro customers get one feature without full upgrade
Bad Add-on Examples
✗ Essential feature as add-on:
"Export your data: +$25/mo"
→ Should be included, feels extractive
✗ Add-on more expensive than tier jump:
Pro: $99/mo
Pro + Analytics: $99 + $150 = $249/mo
Business (includes analytics): $199/mo
→ Confusing, punishes add-on buyers
✗ Invisible add-on costs:
"Per-user fee + storage fee + API fee + support fee"
→ Impossible to understand total cost
Add-on Discovery and Adoption
Bundle vs Add-on Decision
Cross-Sell and Upsell Framework
Upsell Path (vertical):
Starter → Pro → Business → Enterprise
Same product, more features/capacity
Cross-Sell Path (horizontal):
Core Product → Add-on A
→ Add-on B
→ Add-on C
Related products, complementary value
Bundle Path (diagonal):
Core + Add-on A + Add-on B = "Complete Package"
Combines cross-sell into simplified offering
Revenue Expansion Metrics
Add-on Cannibalizing Core
Pricing Page Add-on Display
Good Display:
┌──────────────────────────────────────────┐
│ PRO PLAN - $99/mo │
│ Everything you need to grow │
│ • Feature 1 │
│ • Feature 2 │
│ • Feature 3 │
│ │
│ Optional add-ons: │
│ ○ Priority support (+$29/mo) │
│ ○ API access (+$49/mo) │
│ ○ Advanced analytics (+$39/mo) │
│ │
│ [Start Trial] [View all add-ons] │
└──────────────────────────────────────────┘
Partner and Integration Bundles
Anti-Patterns
- Too many add-ons — Decision paralysis, support complexity
- Nickel-and-diming — Every feature is an add-on
- Essential features gated — Core functionality held hostage
- Confusing bundles — Overlap between bundles and tiers
- Forced bundles — No option to buy components separately
- Add-on bloat — Adding add-ons without pruning
- Unclear pricing — Can't calculate total cost
- Bundle that increases churn — Customers paying for unused products
Supporting file: rules/packaging-tier-design.md
Tier Design and Packaging
Impact: CRITICAL
How you package features into tiers determines which customers you attract, how much revenue you capture, and how customers perceive your value.
The Good/Better/Best Framework
Tier Distribution Goals
Revenue Distribution (Healthy):
├── Starter (Good): 10-20% of customers, 5-10% of revenue
├── Pro (Better): 60-70% of customers, 40-50% of revenue
└── Enterprise (Best): 10-20% of customers, 40-50% of revenue
┌────────────┐
Revenue by Tier: │ Enterprise │
┌────────────┐ │ 45% │
│ Pro │ │ │
┌──────┐ │ 40% │ │ │
│Start │ │ │ │ │
│ 15% │ │ │ │ │
└──────┘ └────────────┘ └────────────┘
Feature Allocation Matrix
Feature Fencing Strategies
Good Tier Design Examples
✓ Clear value ladder:
├── Starter ($29): Solo developers
│ → 1 project, 1,000 API calls, community support
├── Pro ($99): Growing teams
│ → 10 projects, 50,000 API calls, email support
└── Enterprise (Custom): Large organizations
→ Unlimited, 24/7 support, SSO, dedicated CSM
✓ Feature progression makes sense:
├── Basic: Create and edit
├── Pro: + Collaborate and share
└── Enterprise: + Control and secure
✓ Each tier has a clear "hero" feature:
├── Starter: "Get started free"
├── Pro: "Team collaboration"
└── Enterprise: "Security & compliance"
Bad Tier Design Examples
✗ Too many tiers:
├── Free
├── Starter ($9)
├── Basic ($19)
├── Pro ($39)
├── Team ($79)
├── Business ($149)
└── Enterprise (Custom)
→ Decision paralysis, unclear differentiation
✗ No logical feature progression:
├── Starter: 5 users, SSO, API access
├── Pro: 10 users, no SSO, no API
└── Enterprise: Unlimited, SSO, API
→ Why does Starter have features Pro doesn't?
✗ Starter is too limited:
├── Starter: 1 project, 100 API calls
→ Impossible to evaluate the product
Bundle Psychology
Bundle Pricing Math
Unbundled:
├── Product A: $100
├── Product B: $80
└── Product C: $60
Total if bought separately: $240
Bundled:
└── All three: $180 (25% discount)
→ Higher perceived value
→ Lower per-product price
→ Higher attachment rate
→ Harder for competitors to unbundle
Naming Conventions
Tier Naming Psychology
✓ Aspirational progression:
Starter → Growth → Scale
→ Implies company trajectory
✓ Descriptive of use case:
Personal → Team → Organization
→ Clear who each tier is for
✓ Value-oriented:
Essentials → Professional → Enterprise
→ Implies increasing capabilities
✗ Confusing hierarchy:
Basic → Standard → Premium → Ultimate → Enterprise
→ Too many levels, unclear differences
Free Tier Strategy
Free Tier Limits
Upgrade Triggers
Plan Comparison Best Practices
Anti-Patterns
- Feature soup — 50 features listed, customer can't process
- False hierarchy — Higher tiers don't have clear additional value
- Missing middle — Jump from $29 to $299 with nothing between
- Punitive limits — Starter so limited it's unusable
- Complex add-ons — Too many optional extras confuse pricing
- Arbitrary gates — Features in higher tiers that don't justify the price
- No recommended tier — Customer has to decide entirely on their own
- Same price, different packaging — Appears like arbitrary segmentation
Supporting file: rules/page-pricing-copy.md
Pricing Page Copy and Design
Impact: HIGH
Your pricing page is where buying decisions are made. Clear copy, strategic design, and reduced friction directly impact conversion.
Pricing Page Anatomy
┌─────────────────────────────────────────────────────────────┐
│ HEADER │
│ Clear headline + who this is for │
├─────────────────────────────────────────────────────────────┤
│ BILLING TOGGLE │
│ [Monthly] [Annual - Save 20%] │
├─────────────────────────────────────────────────────────────┤
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
│ │ STARTER │ │ PRO │ │ ENTERPRISE │ │
│ │ $29/mo │ │ ★ $99/mo │ │ Custom │ │
│ │ │ │ POPULAR │ │ │ │
│ │ • Feature 1 │ │ • Feature 1 │ │ • All in Pro│ │
│ │ • Feature 2 │ │ • Feature 2 │ │ • SSO │ │
│ │ │ │ • Feature 3 │ │ • SLA │ │
│ │ [Start Free]│ │[Start Trial]│ │[Contact Us] │ │
│ └─────────────┘ └─────────────┘ └─────────────┘ │
├─────────────────────────────────────────────────────────────┤
│ FEATURE COMPARISON TABLE │
│ Detailed breakdown of what's included in each plan │
├─────────────────────────────────────────────────────────────┤
│ FAQ │
│ Answer common pricing objections │
├─────────────────────────────────────────────────────────────┤
│ SOCIAL PROOF │
│ Logos, testimonials, case studies │
├─────────────────────────────────────────────────────────────┤
│ FINAL CTA │
│ Still not sure? Talk to sales / Start free │
└─────────────────────────────────────────────────────────────┘
Headline Formulas
Good Headlines
✓ "Pricing that grows with your business"
→ Implies scalability, future-proofing
✓ "Start free. Pay when you're ready."
→ Reduces risk, low commitment
✓ "Simple pricing. Powerful features."
→ Addresses complexity concern
✓ "One plan. Everything included."
→ Radical simplicity (if true)
Bad Headlines
✗ "Our Pricing Plans"
→ Says nothing, wasted opportunity
✗ "Choose Your Perfect Plan!"
→ Empty hype, no value
✗ "Affordable Solutions for Every Budget"
→ Generic, could be anyone
✗ "Flexible Pricing Options Available"
→ Vague, no specifics
Tier Card Copy Structure
┌──────────────────────────────┐
│ TIER NAME │ ← Clear, aspirational
│ $XX/mo │ ← Price prominent
│ "For growing teams" │ ← Who it's for
├──────────────────────────────┤
│ ✓ Core feature benefit │ ← Start with most valuable
│ ✓ Second feature benefit │ ← Benefits, not features
│ ✓ Third feature benefit │
│ ✓ Fourth feature benefit │
├──────────────────────────────┤
│ [CTA Button] │ ← Action-oriented
│ "No credit card required" │ ← Friction reducer
└──────────────────────────────┘
Feature List Best Practices
Good Feature Copy
✓ "Unlimited team members" (not "Multi-user support")
✓ "Priority email support — responses within 4 hours"
✓ "Advanced analytics with custom reports"
✓ "SSO with SAML 2.0" (for enterprise)
✓ "99.9% uptime SLA"
Bad Feature Copy
✗ "Robust infrastructure capabilities"
→ Vague, meaningless
✗ "Premium tier access level"
→ What does this include?
✗ "Advanced features"
→ Which features specifically?
✗ "Enterprise-grade security"
→ Be specific: SOC 2, encryption, etc.
CTA Button Copy
CTA Button Variations
Low commitment:
├── "Start free"
├── "Try for free"
└── "Get started — it's free"
Trial-focused:
├── "Start your free trial"
├── "Try Pro for 14 days"
└── "Start trial — no card required"
Paid:
├── "Choose Starter"
├── "Upgrade to Pro"
└── "Get started with Pro"
Enterprise:
├── "Contact sales"
├── "Talk to an expert"
└── "Request a demo"
Annual vs Monthly Toggle
Display Options:
[Monthly] [Annual - Save 20%] ← Show savings
[Monthly] [Annual - 2 months free] ← Concrete value
Price Display:
├── Monthly: $99/mo
├── Annual: $79/mo (billed annually)
└── Show: "$948/year — save $240"
Toggle Best Practices
Social Proof Placement
FAQ Section (Must-Answer Questions)
Good FAQ Answers
Q: "What happens when I exceed my plan limits?"
A: "We'll notify you at 80% usage. If you exceed limits,
we'll reach out about upgrading — we'll never cut you off
or charge surprise fees."
→ Clear, reassuring, no gotchas
Q: "Can I cancel anytime?"
A: "Yes. No contracts, no cancellation fees. Cancel in one
click from your account settings."
→ Direct, confident, removes fear
Bad FAQ Answers
Q: "What's your refund policy?"
A: "Please refer to our Terms of Service for details on our
refund and cancellation policies."
→ Evasive, creates distrust
Q: "Can I switch plans?"
A: "Contact our support team to discuss plan changes."
→ Friction, suggests difficulty
Comparison Table Design
Mobile Pricing Page
Anti-Patterns
- Hidden pricing — "Contact for pricing" for simple products
- Feature overload — 20+ features per tier card
- Weak CTAs — "Learn more" instead of "Start trial"
- No recommended tier — Buyer has to decide alone
- Price buried — Showing features before price
- Complex calculator — 10 sliders to figure out cost
- Missing FAQ — Unanswered objections kill conversions
- No social proof — Pricing page needs trust signals
- Confusing toggle — Monthly selected but annual prices shown
Supporting file: rules/psychology-anchoring-framing.md
Anchoring and Framing
Impact: CRITICAL
The first price a customer sees becomes their reference point for all other prices. Use anchoring intentionally, or it will work against you.
How Anchoring Works
Customer sees $499 first → $199 feels like a deal
Customer sees $99 first → $199 feels expensive
The anchor reframes everything that follows.
Anchoring Strategies
Framing Techniques
Price Display Hierarchy
┌────────────────────────────────────────────┐
│ RECOMMENDED (Anchor + Push) │
│ ┌────────┐ ┌────────┐ ┌────────┐ │
│ │STARTER │ │ PRO │ │ENTERPRISE│ │
│ │ $49 │ │ $99 │ │ $299 │ │
│ │ │ │ ★ BEST │ │ │ │
│ │ │ │ VALUE │ │ │ │
│ └────────┘ └────────┘ └────────┘ │
└────────────────────────────────────────────┘
Show plans left-to-right, ascending price.
Highlight middle tier. Enterprise anchors high.
Good Anchoring Examples
✓ Pricing page order: Enterprise → Pro → Starter
→ Enterprise price anchors high, Starter feels cheap
✓ "Companies using spreadsheets spend 10+ hours per week on this.
Our tool does it in 10 minutes for $99/mo."
→ Time-value anchor makes price feel small
✓ "Salesforce charges $300/user. We charge $30."
→ Competitor anchor + 10x value perception
✓ "Annual plan: $948/year — that's just $79/mo (2 months free)"
→ Shows savings, monthly feels affordable
✓ "Starting at $29/mo"
→ Low anchor to capture price-sensitive visitors
Bad Anchoring Examples
✗ Showing cheapest plan first with no higher anchor
→ $29 becomes the expectation, $99 feels expensive
✗ "Our enterprise plan is $999/mo" (with no context)
→ Sticker shock, no value anchor
✗ Hiding prices entirely "Contact for pricing"
→ Creates anxiety, filters out good leads
✗ Showing crossed-out prices that aren't credible
→ ~~$999~~ $49 looks like a scam
✗ Using anchors that dwarf your price too much
→ "Competitors charge $10,000" for a $20 product seems absurd
The Decoy Effect (Asymmetric Dominance)
Add a third option that makes your target option look better:
Without Decoy:
├── Basic: $99 (10 users)
└── Pro: $249 (unlimited users)
Many choose Basic (cheaper)
With Decoy:
├── Basic: $99 (10 users)
├── Plus: $199 (15 users) ← Decoy
└── Pro: $249 (unlimited users)
Pro now looks like much better value
Decoy Construction Rules
Framing by Customer Segment
Context-Dependent Anchors
Psychological Price Points
Anti-Patterns
- No anchor at all — Customer uses their own (usually lower)
- Anchor too extreme — $10,000 anchor for $100 product lacks credibility
- Inconsistent anchoring — Different anchors across pages confuse
- Negative framing overuse — Too much "don't lose" feels manipulative
- Ignoring segment context — Enterprise doesn't care about "coffee per day"
- Static anchoring — Not testing different anchor strategies
- Forgetting the baseline — What are they comparing you to?
Supporting file: rules/psychology-decoy-charm.md
Decoy Pricing and Charm Numbers
Impact: HIGH
Strategic use of decoy options and number psychology can significantly shift buyer behavior without changing your actual product offering.
The Decoy Effect Explained
A decoy is an option designed to make another option more attractive, not to be chosen itself.
The Economist Example (Famous Study):
Option A: Web-only $59
Option B: Print-only $125 ← Decoy
Option C: Web + Print $125
Without B: 68% chose A, 32% chose C
With B: 16% chose A, 84% chose C
The decoy shifted preference dramatically.
Decoy Construction Framework
Building Effective Decoys
Good Decoy Examples
✓ Storage Plans:
├── 5GB: $4.99/mo
├── 15GB: $9.99/mo ← Decoy (3x storage for 2x price)
└── 50GB: $12.99/mo ← Target (10x storage for ~2.6x price)
→ 50GB looks like incredible value
✓ Consulting Packages:
├── 2 hours: $500
├── 5 hours: $1,000 ← Decoy ($200/hr)
└── 10 hours: $1,500 ← Target ($150/hr)
→ 10-hour package is obviously best deal
✓ Subscription Tiers:
├── Basic: $29 (5 users)
├── Team: $79 (10 users) ← Decoy ($7.90/user)
└── Pro: $99 (25 users) ← Target ($3.96/user)
→ Pro offers 2x value for 25% more
Bad Decoy Examples
✗ Decoy too similar to target:
├── $49: 10 features
├── $54: 11 features ← Too close, not useful
└── $59: 15 features
→ Difference isn't stark enough
✗ Decoy is actually better value:
├── $29: 5GB
├── $49: 25GB ← Oops, this is best value
└── $99: 40GB
→ Decoy became the preferred choice
✗ Decoy is too obviously fake:
├── $10: Full product
├── $500: Same product but blue ← Absurd
└── $15: Full product + support
→ Customers see manipulation, lose trust
Charm Pricing (9-Ending Prices)
Research shows prices ending in 9 are perceived as significantly cheaper:
When to Use Charm Pricing
Price Ending Psychology
Good Charm Pricing Examples
✓ $29/mo for Starter plan
→ Under $30 threshold, accessible
✓ $99/mo for Pro plan
→ Under $100, "two-digit" pricing
✓ $299/mo for Business plan
→ Under $300, still feels "hundreds"
✓ "From $9.99/month"
→ Single-digit anchor, consumer-friendly
✓ Enterprise at $1,000/mo (round)
→ Premium feel, serious business
Bad Charm Pricing Examples
✗ Enterprise plan at $4,999/mo
→ Looks cheap/gimmicky for enterprise
✗ $49.99/mo for a B2B SaaS
→ The .99 feels consumer, not business
✗ Using $X9 for all tiers
→ $29, $59, $99 lacks differentiation
✗ $199.97/mo
→ Overly specific, looks calculated
✗ Mixing patterns randomly
→ $29, $55, $100 creates confusion
Threshold Psychology
Combining Decoys and Charm Pricing
Optimal Tier Structure:
├── Starter: $29/mo (charm, entry)
│ → 5 users, basic features
│
├── Growth: $69/mo (decoy position)
│ → 10 users, more features
│ → $6.90/user
│
└── Pro: $99/mo ★ BEST VALUE
→ 25 users, all features
→ $3.96/user
→ Below $100 threshold
Price Perception by Format
Testing Price Points
Anti-Patterns
- Decoy that cannibalizes — Accidentally making decoy too attractive
- Obvious manipulation — Decoys that insult intelligence
- Charm pricing for enterprise — $9,999/mo looks cheap, not serious
- Inconsistent endings — $29, $47, $85, $110 creates noise
- Ignoring thresholds — $105/mo when $99/mo is possible
- Over-optimizing — $97 vs $99 rarely matters, test bigger changes
- Static pricing — Never testing these psychological levers
Supporting file: rules/psychology-willingness-to-pay.md
Willingness to Pay Research
Impact: HIGH
Most companies guess at pricing. Systematic willingness-to-pay (WTP) research reveals what customers will actually pay, reducing risk and capturing more value.
Why Research WTP
WTP Research Methods
Van Westendorp Price Sensitivity Meter
Four questions reveal price range:
1. "At what price would you consider this product to be so
expensive that you would not consider buying it?"
→ Too expensive
2. "At what price would you consider this product to be priced
so low that you would question its quality?"
→ Too cheap
3. "At what price would you consider this product to be starting
to get expensive, so that it's not out of the question, but
you'd have to give some thought to buying it?"
→ Expensive (high side of OK)
4. "At what price would you consider this product to be a
bargain—a great buy for the money?"
→ Cheap (low side of OK)
Van Westendorp Analysis
% of respondents
100% ─┼───────────────────────────────────
│ Too ╲ ╱ Too
│ Cheap ╲ ╱ Expensive
│ ╲ ╲╱
│ ╲ ╱╲
│ ╲ ╱ ╲
│ ╲ ╱ ╲
│ Cheap ╲╱ ╲ Expensive
│ ╱╲ ╲
50% ─┼────────────╱──╲───────╲───────────
│ ╱ ╲ ╲
│ ╱ ╲ ╲
│ ╱ ╲ ╲
│ ╱ ╲ ╲
0% ─┼───────╱────────────╲───────╲──────
└───────┴─────────────┴───────┴──────→
PMC IDP OPP PME Price
PMC = Point of Marginal Cheapness
IDP = Indifference Price Point (optimal)
OPP = Optimal Price Point
PME = Point of Marginal Expensiveness
Acceptable Price Range: PMC to PME
Gabor-Granger Method
Test specific price points:
"Would you buy this product at $X?"
├── If Yes: "Would you buy at $X+20%?"
│ ├── If Yes: Continue raising
│ └── If No: Record max WTP
└── If No: "Would you buy at $X-20%?"
├── If Yes: Record as price-sensitive buyer
└── If No: Continue lowering or eliminate
Result: Demand curve at tested price points
Customer Interview Questions
Good Interview Approach
✓ "Tell me about the last time you had [problem]."
→ Establishes real pain
✓ "How much time did that cost you?"
→ Quantifies value
✓ "If you could make that never happen again,
what would that be worth to you?"
→ Direct value question
✓ "Some people pay $99/mo for this, others pay $299/mo.
What makes the difference in your mind?"
→ Reveals value perception
✓ "If this were $149/mo, would you sign up today?"
→ Tests specific price point
Bad Interview Approach
✗ "What would you pay for this?"
→ Customers always low-ball
✗ "Is $99/mo too expensive?"
→ Leading question
✗ "Our competitor charges $200, we're only $99."
→ Anchors to competitor, not value
✗ "What features would justify a higher price?"
→ Focus on features, not outcomes
A/B Testing Pricing
Pricing A/B Test Ethics
Segmented WTP Analysis
WTP by Customer Characteristic
Value-Based Pricing Calculation
Step 1: Quantify the value delivered
├── Time saved: 5 hours/week × $75/hour = $375/week = $1,625/mo
├── Revenue impact: 2% conversion lift × $100K/mo = $2,000/mo
└── Risk avoided: $10K breach × 5% risk = $500/mo
Step 2: Total value = $4,125/mo
Step 3: Price at 10-30% of value
├── Conservative (10%): $412/mo
├── Standard (20%): $825/mo
└── Aggressive (30%): $1,237/mo
Step 4: Validate with research
Sample Size Guidelines
Research to Action
Common WTP Research Mistakes
Anti-Patterns
- Skipping research — Guessing leaves money on table
- Asking "What would you pay?" — Customers lie low
- Single method only — Triangulate with multiple methods
- Research on existing customers only — Selection bias
- Ignoring qualitative — Numbers without context
- Over-engineering — Simple research beats no research
- Analysis paralysis — Research to inform, not to avoid decision
- Set it and forget it — WTP changes over time