← All skills
pricing-strategy
Use when designing, auditing, or optimizing SaaS pricing tiers, value metric, or packaging, or when planning a price increase.
About this skill
Use when designing, auditing, or optimizing SaaS pricing tiers, value metric, or packaging, or when planning a price increase.
SKILL.md
pricing-strategy.SKILL.mdPlace it in your Syntic skills folder. For Syntic Code, install in your local skills directory, review the contents and run it in a controlled environment first.
---
name: pricing-strategy
description: Use when designing, auditing, or optimizing SaaS pricing tiers, value metric, or packaging, or when planning a price increase.
category: Marketing
version: 1.0.0
tools: []
---
# Pricing Strategy
Design SaaS pricing that captures the value delivered, converts at a healthy rate, and scales with customers.
Pricing is not math — it's positioning. The right price isn't the one that covers costs plus margin; it's the one that sits between what the next-best alternative costs and what customers believe they get in return. Most SaaS products are underpriced; this is about fixing that clearly and defensibly.
Check the Knowledge Base for existing product-marketing context first, and use it instead of re-asking questions already covered there. Otherwise gather: current state (existing plans/price points/billing model, trial-to-paid conversion rate, ARPC, monthly churn), business context (B2B/B2C, self-serve/sales-assisted, best vs. casual customer segments, competitors and their prices, cost to serve one customer per month), and goal (designing, optimizing, or planning an increase, plus any constraints like grandfathered customers).
## Three Modes
**Design from scratch** — work through value-metric selection, tier structure, price-point research, and pricing-page design. **Optimize existing pricing** — audit what's there, benchmark, and identify specific improvements when conversion is low or expansion is flat. **Plan a price increase** — design a strategy that raises revenue without burning the customer base.
## The Three Pricing Axes
Every pricing decision spans three axes, in this order: **packaging** (what's in each tier) sits on top of **value metric** (what you charge for) sits on top of **price point** (the actual number). Most teams skip straight to price point — that's backwards. Lock the metric first, then packaging, then test the number.
## Value Metric Selection
| 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 the above | Most mature SaaS |
Choose by asking: what makes a customer willing to pay more (that's the metric); does it scale with their success; is it easy to understand (complexity kills conversion); is it hard to game? Red flags: per-seat pricing where one power user does all the work (seats don't scale with value); flat fee where usage varies 10x across customers (subsidizing heavy users); per-API-call pricing with wildly variable weekly volume (unpredictable bills drive churn).
## Good-Better-Best Tier Structure
Three tiers is standard because it anchors perception, not tradition. **Entry (Good):** captures the segment that would churn at a higher price; limited by feature, usage, or support; not free (free is a separate freemium strategy); should cover costs at minimum. **Middle (Better), the default:** priced 2–3x the entry tier, has everything a growing company needs, called out visually as recommended. **Top (Best):** for enterprise needs, often "Contact us" custom pricing; unlocks SSO, audit logs, SLA, dedicated support, custom contracts — build this tier once enterprise deals exceed $1k MRR.
Feature ladder across tiers typically covers: core product (limited → full → full), usage limits (low → medium → high/unlimited), seats (1–3 → 5-unlimited → unlimited), integrations (basic → full → full+custom), reporting (basic → advanced → custom), support (email → priority → dedicated CSM), and admin/SLA features reserved for the top tier only.
## Value-Based Pricing
Price between the next-best alternative and perceived value delivered: `[cost of doing nothing] ... [next-best alternative] ... [YOUR PRICE] ... [perceived value delivered]`.
1. Define the next-best alternative — competitor, spreadsheet, manual process, hiring someone — and what it costs the customer.
2. Estimate value delivered — time saved × hourly rate, revenue generated/protected, cost of error avoided; ask best customers what they'd lose if they stopped using the product tomorrow.
3. Price in the middle — a rough heuristic is 10–20% of documented value delivered; don't price at 50% of value (feels like overpaying) or below the next-best alternative (signals lack of confidence).
**Conversion rate as a signal:** >40% trial-to-paid likely means underpriced — test an increase. 15–30% is healthy for most SaaS. <10% means pricing may be too high, or the trial-to-paid funnel has friction.
## Pricing Research Methods
**Van Westendorp Price Sensitivity Meter** — ask four questions: at what price is this so cheap you'd question quality; at what price is it a bargain; at what price does it start to feel expensive but still acceptable; at what price is it too expensive to consider? Plot the four curves — the intersection of "too cheap" and "too expensive" gives the acceptable range, and "bargain" vs. "expensive" gives the optimal point. Use with B2B SaaS, n≥30 existing customers or qualified prospects.
**MaxDiff analysis** — show respondents feature/price sets and ask which they value most and least; reveals relative feature value, informing packaging more than price point.
**Competitor benchmarking** — list direct competitors and alternatives customers actually compare against; record published pricing (plan names, prices, value metrics) and what's included; identify where the product over- or under-delivers vs. each; price relative to positioning (premium = 20–40% above market, value = at or below). Don't copy competitor prices directly — their pricing reflects their cost structure and positioning, not yours.
## Price Increase Strategy
Raising prices is one of the highest-ROI moves available to SaaS companies, and most wait too long.
| Strategy | Use when | Risk |
|---|---|---|
| New customers only | Significant pushback expected | Low |
| Grandfather + delayed | Loyal base, contract risk | Medium |
| Tied to value delivery | Clear new features/improvement | Low |
| Plan restructure | Significant packaging change | Medium |
| Uniform increase | Confident in value, clearly below market | Medium-high |
**Execution checklist:** quantify the move by modeling new MRR at 100%/80%/70% retention of existing customers; segment by risk (annual contracts, champions vs. detractors, usage-based at-risk accounts); give 60–90 days notice, 30 days minimum; communicate a specific reason (new features, rising costs, investment); offer a path (lock in current price for annual commitment, or a 3-month window); arm CS with FAQ, talking points, and approved offer authority; monitor churn/downgrade/support-ticket volume for 60 days. Expected churn from a 20–30% price increase is 5–15% — if net revenue impact is positive, proceed.
## Pricing Page Design
**Above the fold:** plan names, price with monthly/annual toggle (annual shows savings), 3–5 bullet differentiators per plan, a CTA button per plan, a "most popular" badge on the recommended tier.
**Below the fold:** a full feature-comparison table using ✅/❌ rather than walls of text; an FAQ addressing "can I cancel anytime," "what happens at limits," "do you offer refunds," "is my data secure," "what if I need to upgrade/downgrade"; social proof relevant to each tier; security badges (SOC2, ISO 27001, GDPR) for B2B enterprise.
**Annual vs. monthly toggle:** show or highlight annual pricing by default since it improves LTV, show savings explicitly ("Save 20%" or "2 months free"), and never hide the monthly price — hiding it builds distrust.
## Proactive Triggers
- Conversion rate >40% trial-to-paid → strong underpricing signal; flag testing a 20–30% increase.
- All customers on the middle tier → no upsell path; flag that an enterprise tier or feature lock-in is missing.
- Customers asking for features outside their tier → expansion revenue is being left on the table; flag a gatekeeping review.
- Monthly churn >5% → fix churn before raising prices, since increases accelerate churners.
- Price unchanged for 2+ years → inflation alone justifies a 10–15% increase.
- Only one pricing option → no anchoring, no upsell; flag adding a third tier even if rarely purchased.
## Communication
Bottom line first, before justification. Every recommendation states What + Why + How. Actions get owners and deadlines — no vague "consider." Tag confidence 🟢 verified benchmark, 🟡 estimated, 🔴 assumed.
## Coordinate With
@mention a product strategist for roadmap and broader monetization strategy (not pricing-page or increase execution), a copywriter for pricing-page copy polish, a churn-prevention specialist when retention is the underlying issue, an experimentation specialist to A/B test price points or layouts, and a customer-success specialist for expansion revenue through upselling.
Install
Syntic App
- 1Create a dedicated folder for this skill in your local skills library.
- 2Place SKILL.md into that folder.
- 3Restart Syntic and invoke this skill on matching tasks.
Syntic Code (CLI)
- 1Save SKILL.md in your local Syntic Code skills directory.
- 2Keep related files in the same skill folder.
- 3Run in a safe environment and validate outputs.