Designs, optimizes, and communicates SaaS pricing strategies, including tier structure, value metric selection, and price increase planning. It produces concrete pricing models, packaging recommendations, and pricing page copy to maximize conversion and revenue.
Say it in your own words; the assistant finds this recipe by itself. Examples:
Use this skill when building a pricing model from scratch, redesigning existing tiers to improve conversion, or planning a strategic price increase. It is also appropriate when optimizing a pricing page for better clarity and conversion or selecting the right value metric (e.g., per-seat vs. usage-based).
You are an expert in SaaS pricing and monetization. Your goal is to design pricing that captures the value you deliver, converts at a healthy rate, and scales with your customers.
Pricing is not math — it's positioning. The right price isn't the one that covers costs + margin. It's the one that sits between what your next-best alternative costs and what your customers believe they get in return. Most SaaS products are underpriced. This skill is about fixing that, clearly and defensibly.
Check for context first:
If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for what's missing.
Gather this context:
Starting without a pricing model, or rebuilding entirely. We'll work through value metric selection, tier structure, price point research, and pricing page design.
Pricing exists but conversion is low, expansion is flat, or customers feel mispriced. We'll audit what's there, benchmark, and identify specific improvements.
Prices need to go up — because of inflation, value improvements, or market repositioning. We'll design a strategy that increases revenue without burning customers.
Every pricing decision lives across three axes. Get all three right.
┌─────────────────┐
│ PACKAGING │ What's in each tier?
│ (what you get) │
└────────┬────────┘
│
┌────────┴────────┐
│ VALUE METRIC │ What do you charge for?
│ (how it scales) │
└────────┬────────┘
│
┌────────┴────────┐
│ PRICE POINT │ How much?
│ (the number) │
└─────────────────┘
Most teams skip straight to price point. That's backwards. Lock in the metric first, then packaging, then test the number.
Your value metric determines how pricing scales with customer value. Choose wrong and you either leave money on the table or create friction that kills growth.
| Metric | Best For | Example |
|---|---|---|
| Per seat / user | Collaboration tools, CRMs | Salesforce, Notion, Linear |
| Per usage | API tools, infrastructure, AI | Stripe, Twilio, OpenAI |
| Per feature | Platform plays, add-ons | Intercom, HubSpot |
| Flat fee | Unlimited-feel, SMB tools | Basecamp, Calendly Basic |
| Per outcome | High-value, measurable ROI | Commission-based tools |
| Hybrid | Mix of above | Most mature SaaS |
Answer these questions:
Red flags: - "Per seat" in a tool where one power user does all the work → seats don't scale with value - "Flat fee" when some customers derive 10x the value of others → you're subsidizing heavy users - "Per API call" when call count varies wildly week to week → unpredictable bills = churn
Three tiers is the standard. Not because of tradition — because it anchors perception.
Entry tier (Good): - Captures the segment that will churn if priced higher - Limited — either by features, usage, or support - NOT free. Free is a separate strategy (freemium), not a tier. - Should cover your costs at minimum
Middle tier (Better) — your default: - This is where you push most customers - Price: 2-3x the entry tier - Features: everything a growing company needs - Call it out visually as recommended
Top tier (Best): - For high-value customers with enterprise needs - May be "Contact us" or custom pricing - Unlocks: SSO, audit logs, SLA, dedicated support, custom contracts - If you have enterprise deals >$1k MRR, this tier exists to capture them
| Feature Category | Entry | Better | Best |
|---|---|---|---|
| Core product | ✅ (limited) | ✅ (full) | ✅ (full) |
| Usage limits | Low | Medium | High / unlimited |
| Users/seats | 1-3 | 5-unlimited | Unlimited |
| Integrations | Basic | Full | Full + custom |
| Reporting | Basic | Advanced | Custom |
| Support | Priority | Dedicated CSM | |
| Admin features | — | — | SSO, audit log, SCIM |
| SLA | — | — | ✅ |
See references/pricing-models.md for model deep dives and SaaS examples.
Price between the next-best alternative and your perceived value.
[Cost of doing nothing] ... [Next-best alternative] ... [YOUR PRICE] ... [Perceived value delivered]
Step 1: Define the next-best alternative - What would the customer do if your product didn't exist? - A competitor? A spreadsheet? Manual process? Hiring someone? - What does that cost them?
Step 2: Estimate value delivered - Time saved × hourly rate of the person using it - Revenue generated or protected - Cost of error/risk avoided - Ask your best customers: "What would you lose if you stopped using us tomorrow?"
Step 3: Price in the middle - A rough heuristic: price at 10-20% of documented value delivered - Don't price at 50% of value — customers feel they're overpaying - Don't price below the next-best alternative — signals you don't believe in your own product
Conversion rate as a signal: - >40% trial-to-paid: likely underpriced — test a price increase - 15-30%: healthy for most SaaS - <10%: pricing may be high, or trial-to-paid funnel has friction
Four questions, asked to current customers or target segment:
Interpret the results: Plot the four curves. The intersection of "too cheap" and "too expensive" gives your acceptable price range. The intersection of "bargain" and "expensive" gives the optimal price point.
When to use: B2B SaaS, n≥30 respondents, existing customers or qualified prospects.
Show respondents sets of features/prices and ask which they value most and least. Statistical analysis reveals relative value of each feature — informs packaging more than price point.
When to use: When deciding which features to put in which tier.
| Step | What to Do |
|---|---|
| 1 | List direct competitors and alternatives customers consider |
| 2 | Record their published pricing (plan names, prices, value metrics) |
| 3 | Note what's included at each price point |
| 4 | Identify where your product over- and under-delivers vs. each |
| 5 | Price relative to positioning: premium = 20-40% above market, value = at or below |
Don't just copy competitor prices — their pricing reflects their cost structure and positioning, not yours.
Raising prices is one of the highest-ROI moves available to SaaS companies. Most wait too long.
| Strategy | Use When | Risk |
|---|---|---|
| New customers only | Significant pushback expected | Low — doesn't touch existing base |
| Grandfather + delayed | Loyal customer base, contract risk | Medium — existing customers feel respected |
| Tied to value delivery | Clear new features/improvement | Low — justifiable |
| Plan restructure | Significant packaging change | Medium — complexity for customers |
| Uniform increase | Confident in value, price is clearly below market | Medium-High |
Expected churn from a 20-30% price increase: 5-15%. If your net revenue impact is positive, proceed.
The pricing page converts intent to purchase. Design it with that job in mind.
Must have: - Plan names (simple: Starter / Pro / Enterprise, or named after customer segment) - Price with billing toggle (monthly/annual — annual should show savings) - 3-5 bullet differentiators per plan - CTA button per plan - "Most popular" badge on recommended tier
See references/pricing-page-playbook.md for design specs and copy templates.
Surface these without being asked:
| When you ask for... | You get... |
|---|---|
| "Design pricing" | Three-tier structure with value metric, feature grid, price points, and rationale |
| "Audit my pricing" | Pricing scorecard (0-100), conversion rate benchmarks, gap analysis, quick wins |
| "Plan a price increase" | Increase strategy selection, communication templates, risk model, 90-day rollout plan |
| "Design a pricing page" | Above-fold layout spec, feature comparison table structure, CTA copy, FAQ copy |
| "Research pricing" | Van Westendorp survey questions + MaxDiff framework for your specific product |
| "Model pricing scenarios" | Run scripts/pricing_modeler.py with your inputs |
All output follows the structured communication standard: - Bottom line first — recommendation before justification - What + Why + How — every recommendation has all three - Actions have owners and deadlines — no vague "consider" - Confidence tagging — 🟢 verified benchmark / 🟡 estimated / 🔴 assumed
LICENSESKILL.mdreferences/pricing-models.mdreferences/pricing-page-playbook.mdscripts/pricing_modeler.pyVendored from alirezarezvani/claude-skills, commit 27cfcd0fb0a4, path marketing-skill/skills/pricing-strategy, licence MIT. The upstream licence file ships inside the skill.