When you're setting or changing prices, /pricing-strategist models tiers, value metrics, and competitive positioning, so you can capture more revenue. — Claude Skill
A Claude Skill for Claude Code by Nick Jensen — run /pricing-strategist in Claude·Updated
Model SaaS pricing tiers, value metrics, and price change strategies.
- Pricing tier design with feature fencing logic
- Value metric selection and validation framework
- Price increase communication templates
- Annual vs monthly pricing ratio analysis
- Competitive pricing gap and positioning audit
Who this is for
What it does
Run /pricing-strategist with your feature set and target segments to get a 3-tier pricing page with feature fencing, anchor pricing, and upgrade triggers.
Feed /pricing-strategist your current pricing and target increase — it returns a rollout plan with grandfathering rules, communication timeline, and email templates.
Use /pricing-strategist to evaluate 4-5 candidate value metrics against criteria: correlates with value, scales predictably, easy to measure, hard to game.
Paste competitor pricing pages into /pricing-strategist to get a positioning map showing where you sit on price-vs-value and gaps to exploit.
How it works
Describe your product, segments, current pricing (if any), and the pricing decision you're facing.
The skill analyzes the scenario and models pricing options with revenue impact estimates.
It generates tier structures, value metric recommendations, or price change plans with communication templates.
Test the recommendations with customer segments and iterate based on conversion data.
Example
B2B SaaS analytics tool. Currently one plan at $99/mo. Growing from SMB into mid-market. Features: dashboards, custom reports, API access, SSO, audit logs. 500 customers. Need to introduce tiers.
Starter ($79/mo): 5 dashboards, 10 reports, email support. Growth ($199/mo): Unlimited dashboards, custom reports, API access, priority support. Enterprise ($499/mo): SSO, audit logs, SLA, dedicated CSM. Anchor effect: Enterprise makes Growth look reasonable.
Recommended: number of data sources connected. It correlates with value (more sources = more insight), scales naturally, and is easy to meter. Fallback: seat-based with viewer seats free.
Grandfather current customers at $99 on Growth tier for 12 months. After 12 months, move to $149 (25% discount vs new pricing). Communicate 90 days before change. Offer annual lock-in at $99/mo for 2-year commit.
Metrics this improves
Works with
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
| Model | Best For | Pros | Cons |
|---|---|---|---|
| Per-seat | Collaboration tools | Predictable, scales with adoption | Discourages sharing |
| Usage-based | Infrastructure, API | Aligns with value, low entry | Unpredictable revenue |
| Flat-rate | Simple products | Easy to understand | Leaves money on table |
| Tiered | Most SaaS | Captures segments | Can be complex |
| Hybrid | Mature products | Flexible, optimized | Harder to communicate |
Value Metric Selection
Your value metric should be:
| Criteria | Question | Example |
|---|---|---|
| Easy to understand | Can you explain it in 5 words? | "Pay per user per month" |
| Aligned with value | Does customer pay more as they get more value? | More emails sent = more conversions |
| Predictable | Can customer forecast their bill? | Seat count is predictable |
| Scalable | Does it grow with the customer? | API calls scale with usage |
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
| Principle | How It Works | Application |
|---|---|---|
| Anchoring | First price sets expectations | Show enterprise price first |
| Decoy effect | Third option makes one look better | Middle tier becomes attractive |
| Charm pricing | 9-ending feels cheaper | $99 vs $100 |
| Price partitioning | Split price seems smaller | $50/mo + $20 support |
| Round numbers | Feel more premium | $1,000 for enterprise |
Packaging Framework
Good/Better/Best Structure
| Tier | Target | Feature Strategy | Pricing |
|---|---|---|---|
| Good (Starter) | Entry-level, price-sensitive | Core features, limited usage | Low anchor |
| Better (Pro) | Growth, main target | Full features, higher limits | Optimal margin |
| Best (Enterprise) | High-value, complex needs | Unlimited, premium support | Value-based |
Feature Fencing Strategies
| Strategy | Description | Example |
|---|---|---|
| Usage limits | Cap quantity/volume | 1,000 vs 10,000 emails |
| Feature gates | Reserve features for higher tiers | SSO in Enterprise |
| Support tiers | Differentiate service level | Email vs dedicated CSM |
| SLA guarantees | Higher uptime commitments | 99.9% vs 99.99% |
| Integration access | Limit connection types | Basic vs premium integrations |
Annual vs Monthly Framework
| Factor | Monthly | Annual |
|---|---|---|
| Discount | Baseline | 15-20% off (2 months free) |
| Cash flow | Spread out | Upfront capital |
| Churn | Higher (monthly exit) | Lower (commitment) |
| Target | Skeptics, small biz | Confident, enterprise |
| Positioning | "Flexibility" | "Best value" |
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
Reference documents
title: Section Organization
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.
title: Competitive Pricing Analysis impact: MEDIUM tags: competitive, analysis, positioning, market, pricing
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
| Dimension | Your Product | Competitor A | Competitor B |
|---|---|---|---|
| Entry price | $29/mo | $49/mo | Free tier |
| Target tier | $99/mo | $149/mo | $79/mo |
| Enterprise | Custom | $299/mo | Custom |
| Value metric | Per seat | Per seat | Per project |
| Annual discount | 20% | 10% | None |
| Free trial | 14 days | 7 days | Freemium |
Competitive Analysis Framework
| Factor | What to Analyze |
|---|---|
| Price points | Entry, mid, high, enterprise |
| Packaging | Tier structure, feature allocation |
| Value metric | What do they charge for? |
| Discounting | Annual, volume, promotional |
| Positioning | Premium, value, budget |
| Target segment | SMB, mid-market, enterprise |
| Go-to-market | Self-serve, sales-led, hybrid |
Where to Find Competitive Pricing
| Source | Reliability | Access |
|---|---|---|
| Public pricing page | High | Easy |
| G2/Capterra reviews | Medium | Easy |
| Sales conversations | High | Requires outreach |
| Customer interviews | High | Requires relationships |
| Job postings | Low | Inferences only |
| SEC filings | High | Public companies only |
| Industry analysts | Medium-High | Paid research |
Competitive Pricing Positions
| Position | Strategy | When to Use |
|---|---|---|
| Premium | Price above market | Superior product, strong brand |
| Market rate | Price at market | Commodity, feature parity |
| Value | Price below market | Disruption, growth focus |
| Freemium | Free core, paid advanced | High volume, network effects |
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
| Instead of... | Do This |
|---|---|
| Matching lowest price | Differentiate on value |
| Matching highest price | Justify with premium features |
| Matching feature-for-feature | Find unmet needs |
| Copying their tiers | Design for your customers |
| Reacting to changes | Proactive value creation |
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
| If You're More Expensive | Justify With |
|---|---|
| 20-50% higher | Superior features, support, reliability |
| 50-100% higher | Different segment (enterprise vs SMB) |
| 2x+ higher | Different value prop entirely |
| If You're Cheaper | Position As |
|---|---|
| 10-30% lower | Better value, same capabilities |
| 30-50% lower | Modern alternative, less bloat |
| 50%+ lower | Disruptive, focused solution |
Competitive Objection Handling
| Objection | Response Strategy |
|---|---|
| "[Competitor] is cheaper" | Focus on value, TCO, outcomes |
| "[Competitor] has more features" | Focus on relevant features, simplicity |
| "[Competitor] is free" | Free has hidden costs (time, support, limits) |
| "[Competitor] is enterprise-proven" | Faster, more focused, better experience |
| "[Competitor] is market leader" | Innovation often comes from challengers |
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
| What to Monitor | Frequency | Tool |
|---|---|---|
| Pricing page changes | Weekly | Visualping, archive.org |
| Review site mentions | Weekly | G2, Capterra alerts |
| Social mentions | Daily | Brand monitoring tools |
| Job postings | Monthly | LinkedIn, job boards |
| Press/funding | Ongoing | Google alerts, news |
| Product changes | Monthly | Product Hunt, changelogs |
Competitive Intel Sources
| Source | Best For |
|---|---|
| Lost deal analysis | Why customers chose competitor |
| Win analysis | Why customers chose you |
| Customer interviews | Deep competitive perception |
| Sales call recordings | Objections and comparisons |
| Support tickets | Feature comparison requests |
| Trial drop-offs | What made them leave |
Pricing Page Comparison Best Practices
| Do | Don't |
|---|---|
| Compare on your strengths | Compare on their strengths |
| Use factual differences | Make subjective claims |
| Link to third-party validation | Make unsubstantiated claims |
| Update regularly | Let it get stale |
| Be fair (acknowledge their strengths) | Be dismissive |
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
title: Discounts and Annual vs Monthly Positioning impact: MEDIUM-HIGH tags: discounts, promotions, annual, monthly, billing
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
| Type | When Appropriate | Risk Level |
|---|---|---|
| Annual commitment | Always offer | Low |
| Volume/seat | Large teams | Low |
| Startup/nonprofit | Qualified programs | Low-Medium |
| Seasonal/launch | Rare, strategic | Medium |
| Win-back | Churned customers | Medium |
| Competitive match | Proven alternative | Medium-High |
| Ad-hoc negotiation | Enterprise only | High |
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
| Discount | Positioning | Typical Use |
|---|---|---|
| 0% (same price) | "Convenience of annual" | Premium products |
| 10-15% | "Save ~1 month" | Standard SaaS |
| 17-20% | "2 months free" | Most common |
| 25%+ | "3+ months free" | Growth-focused |
Framing Annual Savings
| Frame | Example | Psychology |
|---|---|---|
| Months free | "Get 2 months free" | Concrete gain |
| Percentage off | "Save 20%" | Standard discount |
| Dollar savings | "Save $240/year" | Tangible money |
| Daily cost | "Just $2.60/day" | Minimizes perception |
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
| Element | Recommendation |
|---|---|
| Discount level | 50-90% off for 1-2 years |
| Eligibility | VC-backed, <2 years old, <$5M raised |
| Application | Simple form, quick approval |
| Graduation | Clear path to paid at program end |
| Value | It's marketing—feature prominently |
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
| Segment | Typical Discount | Verification |
|---|---|---|
| Nonprofits | 25-50% off | 501(c)(3), charity status |
| Education | 50-90% off | .edu email, institution |
| Open source | Free or 90% off | Public repo, contributors |
| Government | 10-25% off | .gov domain, contract |
Promotional Discount Types
| Type | Duration | Use Case |
|---|---|---|
| Launch | 1-4 weeks | New product/feature launch |
| Holiday | 1-7 days | Black Friday, end of year |
| Anniversary | 1-2 weeks | Company/product birthday |
| Win-back | Limited | Re-engage churned customers |
| Referral | Ongoing | Reward for referrals |
Promotional Discount Guidelines
| Guideline | Why |
|---|---|
| Rare | Frequency trains waiting |
| Time-bound | Creates urgency |
| Reason-based | Launch, milestone, not desperation |
| Clear end date | No ambiguity |
| New customers only (usually) | Protect existing revenue |
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 [email protected] with code SPECIALOFFER
to schedule a call to discuss discount eligibility"
→ Too much friction
Discount Ladder for Win-Back
| Time Since Churn | Offer |
|---|---|
| 1-3 months | "We miss you" + 20% off first month back |
| 3-6 months | "Things have changed" + 30% off 3 months |
| 6-12 months | "Here's what's new" + 50% off first 3 months |
| 12+ months | Treat as new customer with acquisition offers |
Discount Documentation
| Document | Contents |
|---|---|
| Public pricing | Standard discounts (annual, volume) |
| Internal policy | Approval matrix, discount limits |
| Sales playbook | When/how to offer, escalation |
| Legal/finance | Revenue recognition rules |
Discount Approval Matrix
| Discount Level | Approver |
|---|---|
| 0-10% | Sales rep |
| 11-20% | Sales manager |
| 21-30% | VP Sales |
| 31%+ | C-level |
| Custom terms | Legal + Finance |
Metrics to Track
| Metric | What It Tells You |
|---|---|
| Annual mix | % of new revenue from annual |
| Discount rate | Average discount given |
| Deal velocity | Do discounts speed cycles? |
| LTV by discount | Does discounted revenue retain? |
| Promo conversion | Does promo traffic convert? |
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
title: Enterprise Pricing and Negotiation impact: HIGH tags: enterprise, negotiation, custom-pricing, contracts, sales
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
| Dimension | Self-Serve | Enterprise |
|---|---|---|
| Decision maker | Individual/team | Committee/procurement |
| Sales cycle | Minutes to days | Weeks to months |
| Pricing | Published, fixed | Custom, negotiated |
| Payment | Credit card | Invoice, PO, wire |
| Contract | Click-through | Custom MSA |
| Support | Self-serve/email | Dedicated CSM |
| Discount | None/minimal | Expected, structured |
Enterprise Feature Gates
| Feature | Why Gate It | Enterprise Need |
|---|---|---|
| SSO/SAML | Security requirement | IT compliance |
| SCIM provisioning | User management | Scale |
| Audit logs | Compliance tracking | Security |
| Custom SLA | Uptime guarantees | Risk mitigation |
| Dedicated support | Priority access | Business continuity |
| Custom contracts | Legal requirements | Procurement |
| Data residency | Regulatory compliance | Privacy laws |
| On-prem/VPC | Security requirements | Sensitive industries |
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
| Value Driver | Calculation | Example |
|---|---|---|
| Time savings | Hours saved × fully-loaded cost × users | 5 hrs/wk × $75/hr × 100 users = $1.95M/yr |
| Risk reduction | Breach cost × probability reduction | $4M breach × 5% reduction = $200K |
| Revenue lift | Revenue × attributed improvement | $10M ARR × 2% lift = $200K |
| Alternative cost | Cost of next-best alternative | Build internally: $500K/yr |
Enterprise Discount Structure
| Commitment | Typical Discount | Why It Works |
|---|---|---|
| Multi-year | 10-25% off annual | Predictable revenue |
| Upfront payment | 5-15% additional | Cash flow benefit |
| Volume (seats) | 10-30% tier break | Encourages expansion |
| Bundle | 10-20% for suite | Increases ACV, stickiness |
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
| What You Give | What You Get |
|---|---|
| Multi-year discount | Longer commitment |
| Volume discount | More seats committed |
| Implementation credits | Faster decision |
| Extended trial | More stakeholder buy-in |
| Price lock | Case study/reference rights |
| Payment terms | Larger upfront payment |
Negotiation Best Practices
| Phase | Strategy |
|---|---|
| Discovery | Understand their budget, timeline, alternatives |
| Anchoring | Start with full list price, justify with value |
| Concession | Never give without getting |
| Timing | Create urgency without desperation |
| Walk-away | Know your minimum, be willing to walk |
Enterprise Pricing Page Copy
| Element | Approach |
|---|---|
| Price display | "Custom" or "Contact sales" |
| CTA | "Talk to sales" or "Request a demo" |
| Feature list | Full list with enterprise highlights |
| Social proof | Enterprise logos, case studies |
| SLA/security | Compliance badges, certifications |
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
| Element | Standard | Enterprise Needs |
|---|---|---|
| Term | Month-to-month | Annual or multi-year |
| Payment | Credit card | Invoice, NET 30-60 |
| SLA | Best effort | Defined uptime + credits |
| Support | Standard | Premium with SLAs |
| Security | Standard | Custom security addendum |
| Liability | Limited | Negotiated caps |
| Termination | Anytime | For cause, notice period |
Handling Common Objections
| Objection | Response Strategy |
|---|---|
| "Too expensive" | Reframe to value: ROI, TCO comparison |
| "Competitor is cheaper" | Differentiate on value, not price |
| "We need a discount" | "What commitment can you make for that?" |
| "Budget isn't approved" | "What would make this a priority?" |
| "We need to think about it" | "What specific concerns can I address?" |
| "We want monthly" | Show annual savings, offer shorter initial term |
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
| Strategy | Why |
|---|---|
| Build internal champion | They'll fight for budget internally |
| Arm them with ROI | Give them the talking points |
| Address IT/Security | Proactive on concerns |
| Executive alignment | Ensure top-down buy-in |
| Clear timeline | Creates urgency without pressure |
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
title: Price Increases and Lifecycle Communication impact: MEDIUM-HIGH tags: price-increase, grandfathering, migration, communication, lifecycle
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
| Signal | What It Means |
|---|---|
| Value increased significantly | New features, better product |
| Costs increased | Infrastructure, support, compliance |
| Market shifted | Competitors raised prices |
| Underpriced at launch | Validated higher willingness-to-pay |
| Conversion too high | 80%+ conversion = priced too low |
| No resistance | Prospects never push back on price |
| Margin compression | Growth without profit |
Price Increase Magnitude
| Increase | Perception | Frequency |
|---|---|---|
| 5-10% | Inflation adjustment | Annual OK |
| 10-20% | Moderate increase | Every 2-3 years |
| 20-40% | Significant change | Major product changes |
| 40%+ | Re-pricing | With grandfathering |
Grandfathering Strategies
| Strategy | Description | When to Use |
|---|---|---|
| Forever grandfathered | Old price indefinitely | Loyal, long-term customers |
| Locked for X years | Old price for 1-2 years | Standard approach |
| Graduated increase | Phased to new price | Large increases |
| Feature-based | Old price, old features | Adding new tier |
| No grandfathering | Everyone to new price | Rare, small increases |
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
| Timing | Action |
|---|---|
| 60-90 days before | Announce to existing customers |
| 30 days before | Reminder email |
| 7 days before | Final reminder |
| Day of | Confirmation of change |
| After | Check in, handle issues |
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 [email protected].
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
| Question | Good Answer |
|---|---|
| "Why now?" | Specific improvements + honest cost factors |
| "Can I keep old pricing?" | Clear grandfathering terms |
| "What if I can't afford it?" | Downgrade options, annual lock-in |
| "Will prices increase again?" | Honest answer + commitment period |
| "What's changed?" | Concrete feature list |
Handling Pushback
| Response Type | How to Handle |
|---|---|
| Understanding | Thank them, confirm transition |
| Questions | Answer directly, offer call |
| Frustration | Acknowledge, restate options |
| Threats to churn | Understand needs, offer alternatives |
| Demands | Hear out, but hold boundaries |
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
| Approach | When to Use |
|---|---|
| New price immediately | Standard—new customers get new price |
| Promotional window | "Old price for new signups through [date]" |
| Tiered rollout | New price for new signups, then existing |
Price Decrease Considerations
| Scenario | Approach |
|---|---|
| Simplification | Merge tiers, communicate value |
| Competitive response | Position as permanent, not reactive |
| Market change | Acknowledge market, emphasize value |
| Existing customers | Auto-apply new lower price |
Metrics to Track During Price Change
| Metric | What to Watch |
|---|---|
| Churn rate | Before/during/after comparison |
| Support tickets | Volume and sentiment |
| Downgrade rate | Movement to lower tiers |
| Annual conversion | Lock-in response |
| NPS/CSAT | Customer sentiment |
| New customer conversion | Price sensitivity at new level |
Price Increase Checklist
- Define new pricing and grandfathering
- Update pricing page (effective date)
- Prepare customer communication
- Brief support team
- Prepare FAQ document
- Set up tracking/monitoring
- Schedule communications
- Plan for escalations
- Update billing system
- Document everything
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
title: Value Metrics and Pricing Models impact: CRITICAL tags: metrics, value-metric, per-seat, usage-based, pricing-models
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.
| Metric Type | Examples | Scales With |
|---|---|---|
| Per-seat | /user, /agent, /admin | Team size |
| Usage-based | API calls, GB storage, events | Product usage |
| Flat-rate | /month, /year | Time only |
| Outcome-based | /transaction, /lead, /success | Business results |
| Hybrid | Base + usage, seat + overage | Multiple factors |
Value Metric Selection Criteria
| Criteria | Question | Importance |
|---|---|---|
| Value alignment | Does customer pay more when they get more value? | Critical |
| Understandable | Can you explain it in one sentence? | Critical |
| Predictable | Can customer forecast their bill? | High |
| Trackable | Can you measure it accurately? | High |
| Scalable | Does it grow with customer success? | High |
| Defensible | Is it hard for competitors to undercut? | Medium |
Pricing Model Comparison
| Model | Revenue Predictability | Value Alignment | Adoption Friction | Best For |
|---|---|---|---|---|
| Per-seat | High | Medium | Low | Collaboration tools |
| Usage-based | Low | High | Low | Infrastructure, APIs |
| Flat-rate | High | Low | Very low | Simple products |
| Tiered flat | High | Medium | Low | Feature-based SaaS |
| Hybrid | Medium | High | Medium | Mature products |
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)
| Pros | Cons |
|---|---|
| Predictable revenue | Encourages seat hoarding |
| Easy to understand | Penalizes collaboration |
| Scales with org growth | Friction to add users |
| Industry standard | Heavy users subsidize light |
Per-Seat Best Practices
| Practice | Description |
|---|---|
| Define user types | Active user, admin, viewer, etc. |
| Minimum seats | Team plans start at 3+ seats |
| Volume discounts | Reduce friction for large teams |
| Viewer/free seats | Encourage broader adoption |
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
| Pros | Cons |
|---|---|
| Aligns with value delivered | Unpredictable revenue |
| Low barrier to entry | Bill shock risk |
| Scales with customer success | Harder to budget |
| No artificial limits | Complex to communicate |
Usage-Based Design Patterns
| Pattern | Structure | Example |
|---|---|---|
| Pay-as-you-go | Pure consumption | AWS Lambda |
| Tiered usage | Rate decreases with volume | Twilio |
| Committed use | Discount for commitment | Cloud reserved instances |
| Overage model | Base + overage fees | Email platforms |
| Credit system | Prepaid credits | AI/ML platforms |
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
| Pros | Cons |
|---|---|
| Simplest to understand | Leaves money on table |
| Easy buying decision | No upgrade path |
| Predictable for customer | High-value customers underpay |
| No usage tracking needed | Low-value customers may overpay |
When Flat-Rate Works
| Scenario | Why It Works |
|---|---|
| Simple product | Limited features, clear scope |
| Niche market | Similar customer value across base |
| Early stage | Focus on growth, not optimization |
| Commodity | Competing on simplicity |
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
| Pros | Cons |
|---|---|
| Predictable base revenue | More complex |
| Captures usage upside | Harder to communicate |
| Flexible for segments | Requires good billing system |
Hybrid Model Patterns
| Pattern | Base Component | Variable Component |
|---|---|---|
| Platform + consumption | Access fee | Usage fee |
| Seat + usage | Per user fee | Overage fee |
| Minimum + overage | Minimum commit | Pay for excess |
| Tier + add-ons | Feature tier | Optional extras |
Choosing the Right Model
| If your product... | Consider |
|---|---|
| Value scales with users | Per-seat |
| Value scales with usage | Usage-based |
| Value is same for all | Flat-rate |
| Complex value drivers | Hybrid |
| Measurable outcomes | Outcome-based |
Value Metric by Product Type
| Product Category | Common Value Metrics |
|---|---|
| Collaboration | Per seat |
| Analytics | Per seat or data volume |
| Infrastructure | Usage (compute, storage, bandwidth) |
| Communication | Per message, per minute |
| Marketing | Per contact, per email, per visitor |
| Payments | Per transaction (% or flat) |
| Support | Per agent, per ticket |
| Security | Per endpoint, per user |
Pricing Model Transition
| From | To | Strategy |
|---|---|---|
| Flat → Tiered | Introduce feature tiers | Grandfather existing |
| Per-seat → Hybrid | Add usage component | Cap at current spend initially |
| Free → Paid | Introduce limits | Long grace period |
| Usage → Hybrid | Add base fee | Offset with usage credits |
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
title: Bundles and Add-ons Strategy impact: HIGH tags: bundles, add-ons, packaging, cross-sell, expansion
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
| Type | Structure | Best For |
|---|---|---|
| Pure bundling | Only sold together | Suite products |
| Mixed bundling | Separate or together | Flexibility |
| Leader bundling | Popular item + extras | Cross-sell |
| Joint bundling | Equal partners | Platform plays |
| Customizable | Pick X of Y | Complex needs |
Bundle Design Framework
| Element | Consideration |
|---|---|
| Complementarity | Do products work better together? |
| Value creation | Is bundle worth more than sum? |
| Simplification | Does it reduce decision complexity? |
| Price anchor | Does individual pricing create anchor? |
| Cannibalization | Does it cannibalize higher-margin products? |
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 Type | Description | Pricing Model |
|---|---|---|
| Feature add-on | Additional capability | Flat monthly fee |
| Usage add-on | Extra capacity | Per-unit or block |
| Service add-on | Premium support | Percentage of base |
| Integration add-on | Third-party connectors | Per integration or flat |
| Compliance add-on | Security/compliance | Premium tier or flat |
Add-on Pricing Guidelines
| Principle | Guideline |
|---|---|
| Relative pricing | Add-on should be 10-30% of base |
| Value clarity | Clear ROI for the add-on |
| Optional feel | Core product works without it |
| Expansion path | Leads to tier upgrade eventually |
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
| Touchpoint | Add-on Presentation |
|---|---|
| Pricing page | Show as optional extras |
| Checkout | "Add premium support for $X/mo" |
| In-app | Feature gate with upgrade prompt |
| Usage limit | "You've hit your limit. Add more?" |
| CSM outreach | Personalized recommendation |
Bundle vs Add-on Decision
| Scenario | Use Bundle | Use Add-on |
|---|---|---|
| Products always used together | Yes | No |
| Feature appeals to subset | No | Yes |
| Simplifying product line | Yes | No |
| Expansion revenue goal | Maybe | Yes |
| Competitive response | Yes | No |
| Complex buyer needs | No | Yes |
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
| Metric | Definition | Target |
|---|---|---|
| Attach rate | % of customers with add-on | 20-40% |
| Expansion revenue | Revenue from existing customers | 30%+ of total |
| Net revenue retention | Revenue from cohort after 12mo | 110-130% |
| Add-on ARPU | Average add-on revenue per customer | Track trend |
Add-on Cannibalizing Core
| Risk | Mitigation |
|---|---|
| Add-on replaces tier upgrade | Price add-on close to tier difference |
| Customers feel nickel-and-dimed | Limit total add-on options |
| Complexity increases churn | Bundle popular combinations |
| Support burden | Self-service add-on management |
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
| Type | Structure | Example |
|---|---|---|
| Tech partner bundle | Your product + partner product | "Slack + Zoom + Asana" |
| Service partner | Product + implementation | "Software + consulting package" |
| Reseller bundle | Discounted for reseller margin | White-label partnerships |
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
title: Tier Design and Packaging impact: CRITICAL tags: packaging, tiers, bundles, good-better-best, pricing
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 | Role | Target Customer | Pricing Strategy |
|---|---|---|---|
| Good (Starter) | Entry point, low barrier | Price-sensitive, evaluators | Low anchor, limited margin |
| Better (Pro) | Main revenue driver | Core ICP, growth stage | Optimal margin, best value |
| Best (Enterprise) | Maximum value capture | High-value, complex needs | Value-based, custom |
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 Type | Starter | Pro | Enterprise |
|---|---|---|---|
| Core product | Full | Full | Full |
| Usage limits | Low | Medium | High/Unlimited |
| Collaboration | Limited | Full team | Org-wide |
| Integrations | Basic | Popular | All + custom |
| Security | Standard | SSO | SSO + SCIM + audit |
| Support | Self-serve | Email/chat | Dedicated CSM |
| SLA | None | 99.9% | 99.99% + custom |
| Data/Analytics | Basic | Advanced | Custom + export |
Feature Fencing Strategies
| Strategy | Description | Best For |
|---|---|---|
| Usage-based | Limit quantity, not capability | API calls, storage, seats |
| Feature gates | Reserve specific features | Advanced analytics, SSO |
| Time gates | Limit history/retention | Log retention, data history |
| Speed gates | Limit performance | Priority processing, SLAs |
| Support gates | Differentiate service | Response time, dedicated support |
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 Type | Structure | Psychology |
|---|---|---|
| Pure bundling | Only available together | Simplicity, forced value |
| Mixed bundling | Sold separately or together | Flexibility + bundle discount |
| Add-on model | Core + optional extras | Customization, expansion |
| All-you-can-eat | Everything included | Simplicity for buyer, risk for seller |
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 Level | Good Names | Avoid |
|---|---|---|
| Entry | Starter, Basic, Essentials, Free | Lite, Trial, Cheap |
| Middle | Pro, Growth, Team, Plus | Standard, Normal |
| Top | Enterprise, Business, Scale, Premium | Ultimate, Diamond, VIP |
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
| Strategy | Description | Best For |
|---|---|---|
| Freemium | Forever free with limits | PLG, high volume |
| Free trial | Time-limited full access | High-touch, consideration |
| Reverse trial | Start paid, downgrade option | SaaS, engagement |
| Sandbox | Limited/test environment | Developers, API products |
Free Tier Limits
| Too Generous | Just Right | Too Restrictive |
|---|---|---|
| Full features forever | Core features, usage caps | Can't experience value |
| No incentive to upgrade | Clear upgrade triggers | Churns before converting |
| Supports freeloaders | Filters serious users | Filters good prospects too |
Upgrade Triggers
| Trigger Type | Example | Placement |
|---|---|---|
| Usage limit hit | "You've used 80% of your quota" | In-app notification |
| Feature gate | "SSO is available on Pro" | At feature access point |
| Growth milestone | "You have 5+ team members" | Dashboard, usage page |
| Time trigger | "Your trial ends in 3 days" | Email, modal |
Plan Comparison Best Practices
| Element | Best Practice |
|---|---|
| Columns | 3-4 tiers max (including free) |
| Rows | Highlight differences, not all features |
| Checkmarks | Partial vs full (limited, unlimited) |
| Empty cells | Show what's missing, not just what's included |
| CTA | Unique per tier (Start free, Try Pro, Contact sales) |
| Highlight | Mark recommended tier clearly |
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
title: Pricing Page Copy and Design impact: HIGH tags: pricing-page, copy, design, conversion, cta
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
| Formula | Example | Best For |
|---|---|---|
| Simple + clear | "Simple, transparent pricing" | Most products |
| Benefit-led | "Pricing that scales with you" | Growth products |
| Objection crusher | "No hidden fees. No surprises." | Trust-sensitive |
| Segment-focused | "Plans for teams of every size" | Multi-segment |
| Value-anchored | "Start free, upgrade when ready" | PLG products |
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
| Do | Don't |
|---|---|
| Lead with most valuable feature | List in random order |
| Write benefits, not features | "API access" |
| Use consistent language | Mix technical and simple |
| Show limits clearly | Hide restrictions |
| 4-6 key items per card | 15+ feature items |
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
| Tier | CTA Copy | Why |
|---|---|---|
| Free | "Get started free" | Zero commitment |
| Starter | "Start 14-day trial" | Time-bound, full access |
| Pro | "Start your trial" | Confident action |
| Enterprise | "Talk to sales" | Human conversation |
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
| Practice | Why |
|---|---|
| Default to annual (usually) | Higher LTV, lower churn |
| Show savings prominently | Motivates annual choice |
| Display monthly equivalent | Makes annual feel affordable |
| Show total annual cost | Transparency builds trust |
Social Proof Placement
| Location | Type | Purpose |
|---|---|---|
| Above pricing cards | Customer logos | Trust before commitment |
| Below tier cards | Testimonial quotes | Validation after comparison |
| Near Enterprise CTA | Enterprise logos | "Companies like you use us" |
| Footer | Usage stats | "Join 10,000+ companies" |
FAQ Section (Must-Answer Questions)
| Question | Purpose |
|---|---|
| "Can I switch plans?" | Reduce lock-in fear |
| "What happens if I exceed limits?" | Clarify overages |
| "Is there a free trial?" | Reduce risk |
| "What payment methods do you accept?" | Remove friction |
| "Can I cancel anytime?" | Reduce commitment fear |
| "Do you offer discounts for startups/nonprofits?" | Capture segments |
| "What's included in all plans?" | Clarify base value |
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
| Element | Best Practice |
|---|---|
| Rows | Features grouped by category |
| Sticky header | Plan names + prices always visible |
| Checkmarks | ✓ for included, — for excluded |
| Partial | Show limits: "5 projects" vs just ✓ |
| Highlighting | Recommended plan column stands out |
| Mobile | Collapsible or horizontal scroll |
Mobile Pricing Page
| Element | Mobile Optimization |
|---|---|
| Toggle | Prominent, easy to tap |
| Cards | Stack vertically |
| Comparison | Collapsible accordion |
| CTA | Sticky at bottom |
| Price | Large, unmissable |
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
title: Anchoring and Framing impact: CRITICAL tags: psychology, anchoring, framing, behavioral-economics, pricing
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
| Strategy | How It Works | Example |
|---|---|---|
| High-low anchor | Show premium first, target looks cheap | List Enterprise at $999, Pro looks reasonable at $199 |
| Crossed-out price | Original price as anchor | |
| Competitor anchor | Position against expensive alternative | "Competitors charge $500/mo" |
| Value anchor | Quantify the value delivered | "Saves 10 hours/week ($500 in labor)" |
| Annual anchor | Show annual total, monthly feels small | "$1,188/year = just $99/mo" |
Framing Techniques
| Frame | Example | Psychology |
|---|---|---|
| Gain frame | "Save 20%" | Positive outcome |
| Loss frame | "Don't lose $1,200/year" | Loss aversion |
| Time frame | "$3.25/day" | Smaller perceived cost |
| Value frame | "Less than a coffee per day" | Relatable comparison |
| Investment frame | "ROI in 30 days" | Expected return |
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
| Element | Decoy Strategy |
|---|---|
| Price | Close to target tier |
| Features | Slightly worse than target |
| Value ratio | Poor compared to target |
| Purpose | Make target look superior |
Framing by Customer Segment
| Segment | Best Frame | Example |
|---|---|---|
| Price-sensitive | Savings, value | "Save 40% vs competitors" |
| Time-starved | Time savings | "Get 10 hours back per week" |
| Risk-averse | Security, guarantee | "30-day money-back guarantee" |
| Growth-focused | ROI, scale | "10x your output in 90 days" |
| Enterprise | Total cost of ownership | "Lower TCO than building in-house" |
Context-Dependent Anchors
| Context | Anchor Strategy |
|---|---|
| Homepage | Value proposition, savings |
| Pricing page | Tier comparison, best value |
| Checkout | Annual savings, upgrade benefits |
| Upgrade modal | Current limitation, unlock message |
| Enterprise page | Competitor costs, custom value |
Psychological Price Points
| Price Point | Perception | Best For |
|---|---|---|
| $9 | Impulse, low commitment | Add-ons, trials |
| $29 | Accessible, entry-level | Starter tiers |
| $49-79 | Serious but affordable | Solo/SMB |
| $99 | Threshold, significant | Core product |
| $199-299 | Premium, team-level | Growth stage |
| $499+ | Enterprise-adjacent | Mid-market |
| Custom | True enterprise | High-touch sales |
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?
title: Decoy Pricing and Charm Numbers impact: HIGH tags: psychology, decoy, charm-pricing, behavioral-economics, pricing
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
| Decoy Type | Structure | Effect |
|---|---|---|
| Asymmetric dominance | Similar price, fewer features | Target looks superior |
| Compromise effect | Extreme option on each end | Middle becomes "safe" |
| Attraction effect | Close to target but worse | Target more attractive |
Building Effective Decoys
| Component | Decoy Property | Target Property |
|---|---|---|
| Price | Similar or slightly lower | Same or slightly higher |
| Features | Clearly inferior subset | Complete package |
| Value ratio | Poor $/feature | Strong $/feature |
| Perception | "Why would I choose this?" | "This is obviously better" |
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:
| Price | Perceived As | Research Finding |
|---|---|---|
| $39 vs $40 | ~15-20% cheaper | Left-digit effect |
| $99 vs $100 | Different category | Crossing threshold |
| $199 vs $200 | "One hundred something" | Anchors to lower hundred |
When to Use Charm Pricing
| Context | Use Charm (9s) | Use Round Numbers |
|---|---|---|
| Consumer/SMB | Yes, increases conversion | Less effective |
| Enterprise | Avoid, looks cheap | Yes, signals quality |
| Discounts | Yes, $199 "feels right" | No |
| Premium tiers | Maybe $299 | $300 signals premium |
| Psychological threshold | $99 < $100 | $1,000 sounds prestigious |
Price Ending Psychology
| Ending | Perception | Best For |
|---|---|---|
| X9 | Bargain, value | Mass market, discounts |
| X5 | Balanced, fair | Mid-tier, straightforward |
| X0 | Premium, round | Enterprise, luxury |
| X7 | Specific, calculated | Data-driven feel |
| X.99 | Consumer, retail | Low-cost, impulse |
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
| Threshold | Below | At/Above |
|---|---|---|
| $10 | Impulse buy | Consideration |
| $50 | "Affordable" | "Investment" |
| $100 | Individual decision | May need approval |
| $500 | Manageable | Budget item |
| $1,000 | Serious purchase | Committee/approval |
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
| Format | Perception | Example |
|---|---|---|
| $99 | Cheaper than | $99 |
| $99.00 | More expensive feel | $99.00 |
| $99/mo | Clear commitment | $99/mo |
| $99 per month | More substantial | $99 per month |
Testing Price Points
| Test Type | What to Measure |
|---|---|
| $X9 vs $X0 | Conversion rate difference |
| With/without decoy | Tier selection distribution |
| Threshold crossing | $99 vs $105 conversion |
| Annual display | $99/mo vs $1,188/yr perception |
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
title: Willingness to Pay Research impact: HIGH tags: psychology, research, willingness-to-pay, van-westendorp, pricing
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
| Approach | Accuracy | Risk |
|---|---|---|
| Gut feeling | Low | High—usually underprices |
| Cost-plus | Low | Ignores value, leaves money |
| Competitor copy | Medium | May not fit your value |
| WTP research | High | Data-driven decisions |
WTP Research Methods
| Method | Complexity | Best For |
|---|---|---|
| Van Westendorp | Low | New products, ranges |
| Gabor-Granger | Medium | Testing specific prices |
| Conjoint analysis | High | Feature/price trade-offs |
| A/B testing | Medium | Live price testing |
| Customer interviews | Low | Qualitative understanding |
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
| Question | What It Reveals |
|---|---|
| "How do you currently solve this?" | Alternative costs |
| "What does this problem cost you?" | Value ceiling |
| "What would you pay to make this go away?" | Direct WTP |
| "If this cost $X, would that feel fair?" | Price reaction |
| "What would make $X feel worth it?" | Value drivers |
| "At what price would you walk away?" | Price ceiling |
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
| Test Type | Setup | Considerations |
|---|---|---|
| Price test | Different prices, same product | Need volume, ethics concern |
| Package test | Same price, different packages | Cleaner signal |
| Anchor test | Different display, same price | Low risk |
| Conversion test | Test signup conversion | Doesn't test long-term LTV |
Pricing A/B Test Ethics
| Practice | Guideline |
|---|---|
| Equal access | Don't charge different prices to same audience |
| Time-based | Test different periods, not same period |
| New customers | Test on new customers, not existing |
| Small differences | 10-20% range, not 2x differences |
| Post-test equity | Honor lowest price if discovered |
Segmented WTP Analysis
| Segment | Typical WTP | Research Approach |
|---|---|---|
| Enterprise | Highest | Sales conversations, RFPs |
| Mid-market | High | Mixed interviews + surveys |
| SMB | Medium | Large-scale surveys |
| Prosumer | Low-Medium | Product analytics |
| Consumer | Lowest | A/B testing, surveys |
WTP by Customer Characteristic
| Factor | Higher WTP | Lower WTP |
|---|---|---|
| Company size | Enterprise | SMB |
| Pain severity | Acute problem | Nice-to-have |
| Sophistication | Early adopter | Laggard |
| Budget ownership | Has budget | Needs approval |
| Alternative cost | High | Low/free options |
| Switching cost | Already invested | Fresh evaluation |
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
| Method | Minimum Sample | Ideal Sample |
|---|---|---|
| Van Westendorp | 50 | 200+ |
| Gabor-Granger | 100 | 300+ |
| Conjoint | 200 | 500+ |
| Interviews | 10-15 | 30+ |
| A/B test | Depends on conversion | 95% confidence |
Research to Action
| Finding | Action |
|---|---|
| WTP higher than current | Raise prices |
| WTP lower than current | Add value or find new segment |
| Wide WTP range | Segment with tiers |
| Tight WTP cluster | Flat pricing may work |
| Strong feature preferences | Reconsider packaging |
Common WTP Research Mistakes
| Mistake | Impact |
|---|---|
| Asking hypothetical questions | Get hypothetical answers |
| Leading with price | Anchors and biases responses |
| Wrong audience | Research existing, price for new |
| Too few respondents | Noise, not signal |
| Ignoring segments | Blended data hides segments |
| Research once, never again | Markets change |
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