pricing-strategy
SaaS pricing design and optimization covering value metric selection, tier architecture, price point research, pricing page design, price increase execution, and competitive pricing analysis.
What this skill does
# Pricing Strategy
Production-grade SaaS pricing framework covering the three pricing axes (value metric, packaging, price point), value-based pricing methodology, tier architecture, pricing research methods, pricing page design, price increase execution, and competitive pricing positioning. Pricing is positioning -- the right price communicates as much about your product as your marketing does.
## Use when
- The user asks to "design pricing", "set prices", or "choose a value metric"
- Pricing tiers need to be restructured (Good-Better-Best, add/remove tiers, repackage features)
- A price increase is planned and needs execution design (strategy, timing, communication, grandfathering)
- Conversion on the pricing page is flat or declining
- Freemium vs free trial decision needs to be made, or the freemium tier is cannibalizing paid
- Competitor pricing shifts require a positioning response
- The user says "our pricing feels off" or asks for a pricing audit
---
## Table of Contents
- [Operating Modes](#operating-modes)
- [The Three Pricing Axes](#the-three-pricing-axes)
- [Value Metric Selection](#value-metric-selection)
- [Tier Architecture](#tier-architecture)
- [Value-Based Pricing](#value-based-pricing)
- [Pricing Research Methods](#pricing-research-methods)
- [Pricing Page Design](#pricing-page-design)
- [Price Increase Playbook](#price-increase-playbook)
- [Freemium vs Free Trial Decision](#freemium-vs-free-trial-decision)
- [Competitive Pricing Analysis](#competitive-pricing-analysis)
- [Pricing Signals and Diagnostics](#pricing-signals-and-diagnostics)
- [Output Artifacts](#output-artifacts)
- [Related Skills](#related-skills)
---
## Operating Modes
### Mode 1: Design From Scratch
No pricing exists or full rebuild needed. Work through value metric, tier structure, price points, and page design.
- *Validate:* value metric chosen before tier design; tier design locked before price points; price points tested against the corridor before page design.
### Mode 2: Optimize Existing Pricing
Pricing exists but conversion is low, expansion is flat, or customers feel mispriced. Audit, benchmark, and identify specific improvements.
- *Validate:* the diagnosis names a specific failure mode (e.g., "middle tier too narrow", "value metric doesn't scale") before any change is proposed.
### Mode 3: Price Increase
Prices need to go up. Design a strategy that increases revenue without burning customer relationships.
- *Validate:* grandfather policy defined, communication window set (90+ days for annual customers), and expected churn modeled before sending the first notice.
---
## The Three Pricing Axes
Every pricing decision lives across three axes. Most teams skip to price point. That is backwards.
```
┌──────────────────┐
│ VALUE METRIC │ What do you charge for?
│ (how it scales) │ (per seat, per usage, per feature)
└────────┬─────────┘
│
┌────────┴─────────┐
│ PACKAGING │ What is in each tier?
│ (what you get) │ (feature bundles, limits, support levels)
└────────┬─────────┘
│
┌────────┴─────────┐
│ PRICE POINT │ How much?
│ (the number) │ (actual dollar amount)
└──────────────────┘
```
Lock in the value metric first, then packaging, then test the price point.
---
## Value Metric Selection
### Common Value Metrics
| Metric | Best For | Examples | Scales With Value? |
|--------|---------|---------|-------------------|
| Per seat / user | Collaboration tools, CRMs | Salesforce, Notion, Linear | Yes if all users are active |
| Per usage | APIs, infrastructure, AI | Stripe, Twilio, OpenAI | Yes |
| Per feature | Platform plays, modular products | HubSpot, Intercom | Somewhat |
| Flat fee | Simple products, SMB market | Basecamp, Calendly | No (subsidizes heavy users) |
| Per outcome | Measurable ROI products | Commission-based tools | Perfectly |
| Hybrid | Most mature SaaS | Base fee + usage, seat + features | Yes |
### Selection Criteria
Answer these 4 questions:
| Question | Answer Points To |
|----------|-----------------|
| What makes a customer willing to pay MORE? | That is your value metric |
| Does the metric scale with their success? | If they grow, you should grow |
| Is it easy to understand? | Complexity kills conversion |
| Is it hard to game? | Customers should not be able to work around it |
### Value Metric Red Flags
| Red Flag | Problem | Fix |
|---------|---------|-----|
| Per-seat in a tool where 1 power user does all the work | Seats do not scale with value | Switch to usage or feature-based |
| Flat fee when some customers get 10x the value of others | Subsidizing heavy users | Add usage tiers or hybrid model |
| Per-API-call when volume varies wildly week to week | Unpredictable bills cause churn | Add usage bands or committed minimums |
| Per-feature when core value requires multiple features | Nickel-and-diming perception | Bundle core features, gate advanced only |
---
## Tier Architecture
### Good-Better-Best (3 Tiers)
Three tiers is the standard because it anchors perception.
| Tier | Role | Pricing Rule | Feature Rule |
|------|------|-------------|-------------|
| Entry (Good) | Captures price-sensitive segment | Covers your costs minimum | Core product, limited usage |
| Middle (Better) | Where you push most customers | 2-3x entry tier | Everything a growing company needs |
| Top (Best) | High-value enterprise customers | 3-5x entry or custom | SSO, audit logs, SLA, dedicated support |
### Feature Allocation Framework
| Feature Category | Entry Tier | Middle Tier | Top Tier |
|-----------------|-----------|------------|---------|
| Core product | Limited | Full | Full |
| Usage limits | Low | Medium | High/Unlimited |
| Users/seats | 1-3 | 5-25 or unlimited | Unlimited |
| Integrations | Basic (3-5) | Full | Full + custom |
| Reporting | Basic | Advanced | Custom |
| Support | Email (48h) | Priority (24h) | Dedicated CSM |
| Admin features | -- | -- | SSO, SCIM, audit logs |
| SLA | -- | -- | 99.9% uptime |
| Data retention | 90 days | 1 year | Unlimited |
| API access | -- | Rate-limited | Full |
### Tier Naming
| Approach | Examples | Best For |
|----------|---------|---------|
| Size-based | Starter, Growth, Enterprise | Universal SaaS |
| Capability-based | Basic, Pro, Enterprise | Feature-differentiated products |
| Audience-based | Individual, Team, Organization | Collaboration tools |
| Persona-based | Freelancer, Agency, Enterprise | Audience-segmented products |
**Naming rules:**
- Names should be instantly understandable
- Avoid jargon or made-up words
- The default/recommended plan should be visually highlighted
---
## Value-Based Pricing
### The Pricing Corridor
```
[Cost floor] ... [Next-best alternative] ... [YOUR PRICE] ... [Perceived value]
```
### Step-by-Step
**Step 1: Define the next-best alternative**
- What would the customer do without your product?
- What does that cost them? (competitor, manual process, hiring)
**Step 2: Estimate value delivered**
- Time saved x hourly rate of the person using it
- Revenue generated or protected
- Cost of errors/risk avoided
- Ask customers: "What would you lose if you stopped using us?"
**Step 3: Price in the corridor**
- Price at 10-20% of documented value delivered
- Above the next-best alternative (signals confidence)
- Below the perceived value ceiling (customer feels good ROI)
### Conversion Rate as a Pricing Signal
| Trial-to-Paid Rate | Signal | Action |
|-------------------|--------|--------|
| > 40% | Likely underpriced | Test a 20-30% price increase |
| 15-30% | Healthy for most SaaS | Optimize packaging, not price |
| < 10% | Possibly overpriced OR trial experience is broken | Investigate whether the issue is price or activation |
---
## Pricing Research Methods
### Van Westendorp Price Sensitivity Meter
Four questions asked to 30+ current customers or qualified prospects:
1. At what price wouldRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.