pricing-strategy

When this skill is activated, always start your first response with the 🧢 emoji.

Pricing Strategy

A practical framework for designing, packaging, and testing software pricing. Pricing is the highest-leverage growth lever most teams ignore - a 1% improvement in pricing yields 2-4x the revenue impact of a 1% improvement in acquisition. This skill covers the full pricing lifecycle: choosing a model (freemium, usage-based, seat-based, flat), packaging features into tiers, building enterprise plans that close six-figure deals, and running price tests without torching customer trust. Agents can use this to draft pricing pages, evaluate model trade-offs, design packaging, and structure experiments.

When to use this skill

Trigger this skill when the user:

• Is designing or redesigning a pricing page or pricing model
• Needs to decide between freemium, free trial, usage-based, or seat-based pricing
• Wants to package features into tiers (good/better/best)
• Is building an enterprise tier and needs to structure negotiation levers
• Wants to run a price test or willingness-to-pay survey
• Needs to set or change prices for a SaaS product
• Is evaluating free-to-paid conversion rates or upgrade triggers
• Asks about price anchoring, decoy pricing, or price discrimination strategies

Do NOT trigger this skill for:

• Billing system implementation details (use a payments or Stripe skill)
• General business strategy or go-to-market planning unrelated to pricing

Key principles

1. Value before price - Price is a function of perceived value, not cost. Before

setting any number, articulate the measurable outcome customers get. If you cannot name the outcome, you cannot defend the price.

1. Packaging is strategy, pricing is tactics - Which features go in which tier

matters more than the dollar amount on each tier. Get packaging wrong and no price point saves you. Get packaging right and you have room to adjust prices later.

1. One metric to rule them all - The best pricing models charge on a single value

metric that scales with the customer's success. Seats work when every user gets equal value. API calls work when consumption correlates with revenue. Pick the metric where "more usage = more value for the customer."

1. Segment by willingness to pay, not by cost to serve - Tiers should separate

customers who get different amounts of value, not customers who cost you different amounts. A startup and an enterprise both use the same servers, but the enterprise extracts 100x more value - price accordingly.

1. Test prices, not just features - Most teams A/B test buttons and headlines but

never test prices. Price sensitivity data is the highest-signal input to pricing decisions and can be gathered safely with the right methodology.

Core concepts

Value metric is the unit you charge on - seats, API calls, messages sent, revenue processed, GB stored. The ideal value metric is easy to understand, scales with customer value, and is predictable enough for customers to budget. Slack charges per seat. Twilio charges per message. Stripe charges per transaction. Each aligns price with the value the customer receives.

Packaging is the act of grouping features into tiers. The standard model is good/better/best (three tiers). The middle tier should be the target - it is where 60-70% of customers should land. The top tier exists to make the middle tier look reasonable (anchoring) and to capture high-willingness-to-pay customers.

Price fences are the criteria that separate tiers. They must be objective and hard to game. Good fences: number of seats, API volume, data retention period, SLA level. Bad fences: company size (self-reported), "startup" vs "enterprise" (subjective).

Willingness to pay (WTP) is the maximum price a customer segment will accept. It varies dramatically by segment. You discover WTP through Van Westendorp surveys, Gabor-Granger analysis, or conjoint studies - never by asking "what would you pay?" directly.

Common tasks

Design a three-tier SaaS pricing page

Framework: Good / Better / Best

1. Name tiers by persona, not size - "Starter / Team / Business" beats

"Small / Medium / Large." Names signal who the tier is for.

1. Anchor with the top tier - Show the most expensive tier first (left or top).

It reframes the middle tier as reasonable.

1. Highlight the target tier - Use a "Most Popular" badge on the middle tier.

60-70% of signups should land here.

1. Limit to 3-4 tiers - More tiers create decision paralysis. If you need a

fourth, make it "Enterprise - Contact Sales."

1. Feature differentiation checklist:
2. Free/Starter: core value proposition, hard usage cap, no integrations
3. Team/Pro: collaboration features, higher limits, basic integrations
4. Business/Enterprise: SSO, audit logs, SLA, dedicated support, custom contracts

Pricing page copy pattern:

[Tier name]
[One sentence: who this is for]
[$X / mo per seat]
[3-5 feature bullets, starting with the most differentiating]
[CTA button]

Choose between freemium and free trial

| Factor | Freemium | Free Trial | |---|---|---| | Best when | Product has viral/network effects, low marginal cost | Product value is obvious but needs time to discover | | Conversion rate | 2-5% free to paid (typical) | 15-25% trial to paid (typical) | | Risk | Freeloaders consume resources without converting | Short trial may not show full value | | Examples | Slack, Dropbox, Figma | Salesforce, HubSpot, Netflix |

Decision rule: Use freemium when free users create value for paid users (network effects, content creation, referrals). Use free trial when the product's value requires sustained use to appreciate but does not benefit from a large free base.

Hybrid option: Free trial of the paid tier, then downgrade to a limited free tier. This shows users the full value, then lets them keep a foothold. Zoom does this well.

Implement usage-based pricing

When to use: The customer's value scales linearly with consumption, and usage is measurable and predictable. Good fits: API platforms, cloud infrastructure, messaging services, data pipelines.

Structure options:

• Pure pay-as-you-go - No commitment, pay per unit. Low barrier, but revenue is

unpredictable. Best for developer tools (Twilio, AWS Lambda).

• Committed use + overage - Base commitment at a discount, then per-unit overage.

Gives revenue predictability. Best for mid-market and enterprise (Snowflake).

• Tiered volume - Price per unit drops as volume increases. Incentivizes growth.

Best when you want customers to consolidate spend (Stripe's volume discounts).

Implementation checklist:

1. Pick one value metric (not two or three)
2. Set a minimum monthly commitment (even $0 with a credit card on file)
3. Provide a usage dashboard and spend alerts
4. Offer committed-use discounts for annual contracts
5. Bill in arrears with a clear invoice breakdown

Gotcha: Usage-based pricing makes revenue forecasting harder. Pair it with annual

commitments or minimum spend agreements for enterprise customers.

Structure an enterprise tier

Enterprise pricing is not a number on a webpage - it is a negotiation framework.

Must-have enterprise features (price fences):

• SSO / SAML integration
• Audit logs and compliance certifications (SOC 2, HIPAA)
• Dedicated support (named CSM, SLA with uptime guarantee)
• Custom contracts and invoicing (NET 30/60/90)
• Data residency and security controls
• Admin controls, role-based access, and user provisioning (SCIM)

Pricing levers for negotiation:

1. Seat count - volume discount at 100+, 500+, 1000+ thresholds
2. Contract length - 10-20% discount for multi-year commits
3. Payment terms - annual upfront is default; quarterly or monthly at a premium
4. Usage tiers - committed volume at lower per-u