The Pricing Paradox: Value-Based vs Cost-Based
Most companies price wrong. They calculate cost, add 40% markup, that's the price. But you're not selling based on cost. You're selling based on the value you create. If you solve a $1M problem, charge $100K. If the solution only costs $10K to build, doesn't matter. Value is still $1M.
Value-based pricing: What is the customer's pain? How much would they save by solving it? Charge 20-30% of the value created. If you save them $500K/year, charge $100-150K/year.
This is why pricing strategy is existential for GTM. If you're underpriced, no amount of marketing fixes it. If you're overpriced, no positioning saves you.
The Five Pricing Models (And Their GTM Implications)
Model 1: Freemium (Free + Paid Upgrades)
How it works: Free tier for basic use. Paid tiers unlock advanced features. Example: Slack (free for small teams, pay per user for large teams).
GTM implications: Product-led growth (PLG). No sales team needed initially. Free users become customers. Massive top-of-funnel volume. Low conversion rate (2-5%), but huge volume.
Pros: Viral growth potential. Users "try before buy." Low friction.
Cons: Many free users never convert. Customer acquisition is product, not sales/marketing. Need very strong product-market fit.
Example: Slack's freemium model: Free forever for small teams (up to 90-day message history). Pro at $12.50/user/month. This created 750M+ total signups, 200M+ MAU, $150M+ ARR.
Model 2: Tiered Pricing (Good / Better / Best)
How it works: Three tiers. Basic features at low price. More features at mid price. All features at premium price. Example: HubSpot (Starter $50/month, Professional $1,200/month, Enterprise custom).
GTM implications: Clear upgrade paths. Start users at low tier, expand to higher tier as needs grow. Sales team focuses on enterprise. Marketing focuses on getting to Starter tier.
Pros: Easy to understand. Appeals to different segments (SMB, mid-market, enterprise). Predictable pricing.
Cons: Can feel arbitrary (what's the real difference between Good and Better?). Customers always want the cheapest option. Might leave money on the table with low tier.
Example: Stripe's pricing: $0 setup for test mode. Then 2.7% + 30¢ per transaction (no monthly fee). This simple, transparent pricing helped Stripe become payments leader. No tiers—same price for everyone.
Model 3: Usage-Based (Pay for What You Use)
How it works: Charge based on consumption. API calls, data transferred, users, events, etc. Example: AWS ($0.12 per GB transferred). Twilio ($0.0075 per SMS sent).
GTM implications: Low barrier to entry. Customers only pay if they use. Scales with customer success. But creates unpredictable costs (customers hate bill shock).
Pros: Fair pricing (pay for value). Aligns incentives (you make more when customer succeeds). Low commitment barrier.
Cons: Unpredictable customer spend. Need to educate on cost optimisation. Potential for bill shock (customer avoids).
Example: Datadog: Metric ingestion at $0.10 per 1M ingested metrics/day. Makes money when customers are successful (more monitoring = more metrics). Customer can start free, scale as needed.
Model 4: Enterprise / Seat-Based (Per-User)
How it works: Charge per authorized user. Example: Salesforce ($165/user/month). Jira ($10/user/month).
GTM implications: Sales team required. Each seat is a conversation. As customer grows, they need more seats, more cost. Creates expansion revenue (customer grows, you grow). But also creates resistance (customers see each new hire as a cost increase).
Pros: Predictable revenue. Built-in expansion motion. Each new user = revenue increase.
Cons: Can feel like a tax on growth. Customers try to game (fewer users = less licensing). Hard to expand to competitive products (if you're expensive per user, they'll find alternative).
Model 5: Custom / Enterprise (Contact Sales)
How it works: No public pricing. Every deal is custom. SaaS for large enterprises. Example: Salesforce (enterprise), SAP, Oracle.
GTM implications: Sales-heavy. Long sales cycles (6-18 months). Deal customisation (features, SLA, support, implementation). Requires dedicated sales team and sales engineering.
Pros: Highest prices (extract maximum value). Can customise to customer needs.
Cons: Slow sales cycle. Expensive to acquire (sales team costs). Low volume. Harder for customers to evaluate (no price transparency).
The Pricing Decision Framework: Which Model Should You Choose?
Start with your ICP:
- SMB (1-100 employees): Freemium or low-cost tiered ($10-100/month). No sales team. Product-led or simple self-serve signup.
- Mid-market (100-1K employees): Tiered pricing ($500-5K/month). Sales team helps with deals. Complex integrations.
- Enterprise (1K+ employees): Custom pricing ($50K-1M+/year). Dedicated sales and sales engineering. Custom contracts, SLA, support.
Then ask:
- How predictable is customer consumption? (Usage-based if very variable. Tiered/seat if predictable.)
- How much value does the product create for them? (Expensive product = high value = can charge more.)
- What do competitors charge? (Don't blindly follow, but understand market expectations.)
- How will this model affect expansion? (Want customers to grow with you? Tiered or usage-based. Want expansion at new customer level? Seat-based.)
Pricing Strategy Examples
Case Study 1: Slack's Pricing Evolution
- 2013 Launch: Freemium model. Free with 10,000-message history limit. $12.50/user/month for unlimited.
- Why it worked: SMBs and startups could use free. Grew virally (free users became advocates). As teams grew, moved to paid. Average customer spent $50K+/year by expansion.
- Pricing psychology: Per-user pricing makes sense for Slack (each person is a user). Freemium meant no sales friction. Expansion automatic (add user = add revenue).
- Result: IPO at $23B valuation (2019). $750M+ ARR by 2020.
Case Study 2: Stripe's Pricing Strategy
- 2010 Launch: 2.7% + $0.30 per transaction. No tiers. No setup fees. Same price for everyone.
- Why it worked: Transparent. Fair. Developer-friendly (build fast, only pay if transactions succeed). Easier than PayPal/Square's model.
- Pricing psychology: Variable cost aligned with success. Developer gets paid (customer transaction succeeds), Stripe gets paid. No upfront cost = low barrier to entry.
- Result: $150B+ valuation (2024). Largest payment processor for developers/platforms.
How to Price Your Product: 7-Step Process
Step 1: Calculate Customer Value
Interview 10 customers. Ask: "What would you pay to solve this problem?" Don't ask directly ("how much would you pay for this?"). Ask indirectly: "What does your current solution (manual process, spreadsheet, competitor) cost in time and resources?"
Step 2: Understand Competitor Pricing
Research 5-10 competitors. What do they charge? How are they packaged? Are there tiers? Usage limits? This gives you market anchors.
Step 3: Define Value Tiers
Create 3 tiers based on customer personas and use cases:
- Basic: Core value. 70% of features. Solo users / small teams.
- Professional: Full value. 95% of features. Growing teams.
- Enterprise: Full value + support + customisation. 100% of features + SLA + integration. Large companies.
Step 4: Test Pricing
Don't overthink. Pick a price. Use it for 30 days. Track: conversion rate, revenue, customer feedback on price. Too many uptiering? Too few? Reprice.
Step 5: Write Transparent Pricing Page
Show what's in each tier. Include features table. Include limits (API calls, users, storage). Make upgrade path obvious.
Step 6: Monitor Metrics
- Conversion rate by tier (too few to mid? Lower the upgrade barrier).
- Churn by tier (losing Enterprise fast? Improve support / feature parity).
- Revenue per customer by segment (paying less than expected? Reprice or improve value perception).
Step 7: Iterate
Every 6 months: Review metrics. Adjust pricing if needed. Add new tiers if market emerges. Remove tiers if unused.
The PMM Role in Pricing: What You Actually Own
Pricing decisions are made by founders, CFOs, and boards. But pricing works — or fails — through product marketing. PMM is accountable for three things that determine whether a pricing model achieves its commercial potential:
1. Value framing
Price is a number. Value is a perception. A £500/month product feels cheap to a buyer who believes it will save 20 hours per week and expensive to a buyer who is not sure what it does. PMM's job is to ensure buyers arrive at the pricing page having already formed an accurate, high-value perception of what the product delivers.
This means: the website, the sales pitch, and the email sequences must establish value before they reach the price. If the buyer's first encounter with the price is on the pricing page without prior context, the price becomes the anchor rather than the value. That is a PMM failure upstream of the pricing decision itself.
2. Tier differentiation clarity
Most pricing tiers fail because the difference between them is not clear enough to drive the buyer toward a specific choice. "More features" is not differentiation. The tier names and descriptions must connect to specific buyer stages, use cases, or outcome levels.
A practical test: cover the price column on your pricing page and read only the tier names and descriptions. Can a buyer in your ICP immediately identify which tier is for them, without reading the feature table? If no, the tier differentiation is unclear and buyers will either default to the cheapest tier or leave without deciding.
3. Objection pre-emption on the pricing page
Every pricing page has a set of predictable objections. PMM should know what they are because they appear in sales calls, in win/loss interviews, and in support tickets. The most common are: "Is this worth the annual commitment?" / "What if we outgrow this tier?" / "Can we integrate this with [tool]?" / "What happens if we cancel?"
PMM's job is to ensure these objections are addressed on the page before the buyer has to ask. A buyer who has to find the answer to an objection on a competitor's site has already left. A buyer whose objection is answered on your page converts.
Run a quarterly pricing page audit: read it as a first-time buyer who is skeptical. List every question that arises. For every question not answered on the page, either add the answer or validate that it is intentionally omitted because the buyer should be asking a sales rep. Every unanswered question that a buyer should self-resolve is leaking conversion.
Price Increase Messaging: How to Tell Customers Without Losing Them
You'll raise prices. Everyone does. Key is transparent communication and proper timing.
- Announce 60+ days before: Give customers time to plan. Last thing they want is surprise bill.
- Grandfather existing customers: Existing customers keep old price for 1-2 years. New customers get new price. Builds goodwill.
- Lead with value: "We've invested in X new feature / improved security / better support. To sustain this, we're raising price to $Y."
- Offer alternative: "If you want to stay at old price, move to lighter-weight plan."
- Example message: "Over the past year, we've added machine learning models, 99.99% uptime SLA, and 24/7 support. To sustain this quality, we're raising Enterprise pricing from $100K to $125K/year on Jan 1. Your existing contract stays at $100K until renewal."
Red Flags: Signs Your Pricing is Broken
- Conversion rate under 2%: Either product isn't compelling, or price is too high relative to perceived value.
- Customers constantly negotiate: Every deal involves a discount. You're overpriced or underpositioned.
- High churn from certain tier: Tier isn't delivering value promised. Either improve tier or re-price.
- No upsell: Customers stay in Basic tier forever. Either improve value of higher tiers, or make upgrade path more obvious.
- Complaints about price: If you're hearing "too expensive" constantly, you're either overpriced or bad at explaining value.
Frequently Asked Questions
How often should we change pricing?
Ideally: every 12-18 months. More often, you confuse customers. Less often, you leave money on the table as market changes. Good schedule: Raise 10-20% annually to account for inflation + value delivery.
Should we offer discounts?
Be careful. Annual discounts (10-20% for annual commitment) make sense. Volume discounts (10+ seats, take 15% off) make sense. Random discounts train customers to never buy at full price. Set clear discount policy so Sales isn't giving away margin.
What if competitors undercut us?
Don't follow. Compete on value, not price. If they're $99 and you're $199, the question is: why is your product worth 2x? If you can't answer that, either improve product or adjust price. But don't engage in price war.
Next Steps
Review your current pricing model. Is it aligned with your GTM (SMB = freemium, Mid-market = tiered, Enterprise = custom)? Test 3 variants. Measure conversion/churn/revenue. Pick winner. Implement for 3-6 months. Iterate.
Related resources: