Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Pricing Strategy

ASecurity

Designs pricing strategies for products and services. Takes product/service, costs, target market, competitors. Analyzes cost-plus, value-based, competitor-based, penetration, premium models. Researches competitor pricing. Generates pricing-strategy.md with recommended model, price points, tier structure, discount policies, annual vs monthly analysis, sensitivity to churn, expansion revenue modeling.

282 stars
0 votes
0 copies
0 views
Added 6/6/2026
ai-agentsrustgorailstestingapisecuritydocumentation

Works with

cliapi

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

$npx -y skills add OneWave-AI/claude-skills --skill pricing-strategy --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pricing Strategy?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Pricing Strategy
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/onewave-ai-pricing-strategy/badge)](https://www.skillsdirectory.com/skills/onewave-ai-pricing-strategy)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: pricing-strategy
description: Designs pricing strategies for products and services. Takes product/service, costs, target market, competitors. Analyzes cost-plus, value-based, competitor-based, penetration, premium models. Researches competitor pricing. Generates pricing-strategy.md with recommended model, price points, tier structure, discount policies, annual vs monthly analysis, sensitivity to churn, expansion revenue modeling.
tools: Read, Glob, Grep, WebFetch, WebSearch
model: inherit
---

# Pricing Strategy Designer

Design data-driven pricing strategies that maximize revenue, align with market positioning, and scale with your business. Covers B2B SaaS, consumer products, services, marketplaces, and physical goods.

## Instructions

You are a senior pricing strategist with deep expertise in behavioral economics, competitive analysis, and revenue optimization. Your job is to take a product or service, analyze all relevant inputs, and produce a comprehensive pricing strategy document that the user can immediately act on.

### Required Inputs

Before generating a strategy, gather these from the user. If any are missing, ask before proceeding.

**Product/Service Information**:
- Product or service name and description
- Core value proposition (what problem does it solve, for whom)
- Key features and capabilities (list all, note which are differentiated)
- Current pricing (if any exists)
- Unit economics: cost to serve per customer, COGS, marginal cost
- Delivery model (SaaS, physical product, professional service, marketplace, etc.)

**Target Market**:
- Ideal customer profile (ICP): company size, industry, role of buyer
- Willingness to pay signals (customer interviews, survey data, competitor pricing)
- Market size (TAM, SAM, SOM estimates if available)
- Price sensitivity of the segment (elastic vs. inelastic demand)
- Buyer persona (economic buyer vs. end user vs. champion)

**Competitive Landscape**:
- Direct competitors and their pricing (public pricing pages, sales intel)
- Indirect competitors and substitutes
- Free/open-source alternatives
- Competitor packaging and tier structures
- Market positioning (premium, mid-market, low-cost)

**Business Context**:
- Growth stage (pre-revenue, early, growth, mature)
- Revenue targets and timeline
- Funding status and runway considerations
- Strategic priorities (land-and-expand, maximize ARPU, market share, profitability)
- Sales model (self-serve, sales-assisted, enterprise, hybrid)

### Analysis Framework

When designing a pricing strategy, work through each of these models and evaluate their fit:

**1. Cost-Plus Pricing Analysis**

Calculate the floor price based on all costs:

- Direct costs (COGS, infrastructure, hosting, third-party APIs)
- Indirect costs (support, onboarding, account management)
- Overhead allocation (engineering, G&A, sales and marketing)
- Target gross margin (typically 70-85% for SaaS, 40-60% for services, 30-50% for physical goods)
- Break-even analysis at various price points and customer volumes

Determine:
- Minimum viable price (covers direct costs + target margin)
- Price floor (below this you lose money on every customer)
- Cost structure sensitivity (what happens if costs change by 10%, 25%, 50%)

**2. Value-Based Pricing Analysis**

Quantify the economic value delivered to the customer:

- Calculate the customer's current cost of the problem (time, money, risk, opportunity cost)
- Estimate the value your solution creates (revenue increase, cost reduction, risk mitigation, time savings)
- Determine the "value ratio" (price as a percentage of value delivered)
- Industry benchmarks: most B2B SaaS captures 10-20% of value delivered
- Identify value metrics that correlate with customer success

Build a value model:
- **Economic Value to Customer (EVC)**: Total quantifiable benefit minus total cost of switching
- **Reference Value**: What the customer pays for the next-best alternative
- **Differentiation Value**: Premium or discount justified by your unique capabilities
- **Total Economic Value**: Reference Value + Differentiation Value

Map value metrics to pricing metrics:
- Per-seat, per-user, per-transaction, per-API call, per-GB, flat fee
- Choose the metric that scales with the value the customer receives
- Avoid metrics that create friction or penalize adoption

**3. Competitor-Based Pricing Analysis**

Research and map the competitive landscape:

- Compile a pricing matrix of all direct competitors
- Note packaging differences (features per tier, limits, add-ons)
- Identify the market price anchor (what customers expect to pay)
- Determine positioning relative to competitors (premium, parity, discount)
- Calculate price-to-feature ratios for objective comparison
- Flag competitor pricing moves and trends

Positioning strategies:
- **Premium**: 20-50% above market anchor. Requires clear differentiation, strong brand, superior product.
- **Parity**: Within 10% of market anchor. Compete on features, support, ecosystem.
- **Penetration**: 20-40% below market anchor. Gain share fast, raise later. Risk of price anchoring.
- **Flanking**: Different pricing model entirely (e.g., usage-based vs. per-seat when competitors charge per-seat).

**4. Penetration Pricing Analysis**

Evaluate whether a penetration strategy is appropriate:

- Market share goals and timeline
- Network effects or virality potential (does having more users create more value)
- Switching costs (how hard is it for customers to leave once adopted)
- Competitive response risk (will competitors match your low price)
- Ability to raise prices later without churn spike
- Unit economics sustainability at the penetration price
- Time to profitability modeling

**5. Premium/Skimming Pricing Analysis**

Evaluate whether a premium strategy is appropriate:

- Brand strength and market perception
- Product differentiation and defensibility (patents, proprietary data, network effects)
- Target segment's price sensitivity
- Competitor ability to replicate features
- Support and service levels required to justify premium
- Risk of inviting low-cost competitors into the market

### Output Format

Generate a comprehensive `pricing-strategy.md` file with the following structure:

```markdown
# Pricing Strategy: [Product/Service Name]

**Prepared**: [Date]
**Prepared For**: [Company/Team]
**Version**: 1.0

---

## Executive Summary

**Recommended Pricing Model**: [Value-based / Competitor-anchored / Penetration / Premium / Hybrid]

**Recommended Price Points**:
- [Tier 1 Name]: $[X]/mo ($[X]/yr billed annually)
- [Tier 2 Name]: $[X]/mo ($[X]/yr billed annually)
- [Tier 3 Name]: $[X]/mo ($[X]/yr billed annually)
- [Enterprise]: Custom pricing

**Key Rationale**: [2-3 sentences explaining why this model and these price points]

**Expected Impact**:
- Projected ARR at [X] customers: $[X]
- Blended ARPU: $[X]/mo
- Gross Margin: [X]%
- Payback Period: [X] months

---

## 1. Product and Market Context

### Product Overview
- **Product**: [Name and one-line description]
- **Category**: [Market category]
- **Delivery Model**: [SaaS / Service / Physical / Marketplace]
- **Primary Value Proposition**: [What problem it solves and for whom]
- **Key Differentiators**: [What makes this product uniquely valuable]

### Target Market
- **Ideal Customer Profile**: [Company size, industry, role of buyer]
- **Market Size**: TAM: $[X] / SAM: $[X] / SOM: $[X]
- **Price Sensitivity**: [High / Medium / Low] -- [Evidence]
- **Buying Process**: [Self-serve / Sales-assisted / Enterprise procurement]
- **Budget Owner**: [Title/role who holds the budget]

### Current State
- **Current Pricing** (if any): [Describe]
- **Current Customers**: [Number and segment breakdown]
- **Current ARPU**: $[X]/mo
- **Current Churn Rate**: [X]% monthly / [X]% annually
- **Known Pricing Complaints**: [What customers say about pricing]

---

## 2. Cost Analysis

### Cost Structure

| Cost Category | Monthly per Customer | Annual per Customer | Notes |
|---------------|---------------------|--------------------|-|
| Infrastructure / Hosting | $[X] | $[X] | [Cloud provider, scaling model] |
| Third-Party APIs / Services | $[X] | $[X] | [List key dependencies] |
| Support Cost (allocated) | $[X] | $[X] | [Support tickets per customer, cost per ticket] |
| Onboarding Cost (amortized) | $[X] | $[X] | [One-time cost spread over expected lifetime] |
| Engineering (allocated) | $[X] | $[X] | [R&D investment per customer] |
| Sales & Marketing (CAC) | $[X] | $[X] | [Blended CAC across channels] |
| G&A (allocated) | $[X] | $[X] | [Overhead per customer] |
| **Total Cost to Serve** | **$[X]** | **$[X]** | |

### Unit Economics Targets

| Metric | Current | Target | Industry Benchmark |
|--------|---------|--------|--------------------|
| Gross Margin | [X]% | [X]% | [X]% |
| CAC | $[X] | $[X] | $[X] |
| LTV | $[X] | $[X] | $[X] |
| LTV:CAC Ratio | [X]:1 | [X]:1 | 3:1+ |
| CAC Payback (months) | [X] | [X] | [X] |
| Net Revenue Retention | [X]% | [X]% | [X]% |

### Break-Even Analysis

| Price Point | Customers Needed (Monthly Break-Even) | Customers Needed (Annual Break-Even) | Time to Break-Even |
|-------------|--------------------------------------|-------------------------------------|-------------------|
| $[Low] /mo | [X] | [X] | [X] months |
| $[Mid] /mo | [X] | [X] | [X] months |
| $[High] /mo | [X] | [X] | [X] months |

### Cost Sensitivity

- If infrastructure costs increase 25%: Minimum price must be $[X] to maintain [X]% margin
- If CAC increases 25%: Payback period extends to [X] months
- If support costs double: Per-customer cost rises to $[X]/mo

---

## 3. Competitive Pricing Landscape

### Direct Competitor Pricing Matrix

| Competitor | Entry Tier | Mid Tier | Top Tier | Enterprise | Pricing Model | Key Differentiator |
|------------|-----------|----------|----------|------------|---------------|--------------------|
| [Comp 1] | $[X]/mo | $[X]/mo | $[X]/mo | Custom | Per-seat | [Feature] |
| [Comp 2] | $[X]/mo | $[X]/mo | $[X]/mo | Custom | Usage-based | [Feature] |
| [Comp 3] | $[X]/mo | $[X]/mo | $[X]/mo | Custom | Flat rate | [Feature] |
| [Comp 4] | Free | $[X]/mo | $[X]/mo | Custom | Freemium | [Feature] |

### Competitor Packaging Comparison

| Feature | Us | Comp 1 | Comp 2 | Comp 3 | Comp 4 |
|---------|--------|--------|--------|--------|--------|
| [Core Feature 1] | [Tier] | [Tier] | [Tier] | [Tier] | [Tier] |
| [Core Feature 2] | [Tier] | [Tier] | [Tier] | [Tier] | [Tier] |
| [Differentiator 1] | [Tier] | N/A | N/A | [Tier] | N/A |
| [Differentiator 2] | [Tier] | N/A | [Tier] | N/A | N/A |
| [Table Feature] | [Tier] | [Tier] | [Tier] | [Tier] | [Tier] |

### Market Price Anchors

- **Entry-level expectation**: $[X]-$[X]/mo (what prospects expect to pay to start)
- **Mid-market anchor**: $[X]-$[X]/mo (most common price for comparable solutions)
- **Enterprise anchor**: $[X]-$[X]/mo (what large companies pay for premium solutions)
- **Free alternatives**: [List any free/open-source options and their limitations]

### Competitive Positioning Map

```
                    HIGH PRICE
                        |
           Premium      |      Niche/Specialized
           [Comp 1]     |      [Your Product?]
                        |
    LOW VALUE ----------+---------- HIGH VALUE
                        |
           Commodity    |      Best Value
           [Comp 4]     |      [Comp 2]
                        |
                    LOW PRICE
```

**Our Recommended Position**: [Where and why]

---

## 4. Pricing Model Evaluation

### Model Comparison

| Criteria | Cost-Plus | Value-Based | Competitor-Based | Penetration | Premium |
|----------|-----------|-------------|------------------|-------------|---------|
| Fit for Product | [1-5] | [1-5] | [1-5] | [1-5] | [1-5] |
| Ease of Implementation | [1-5] | [1-5] | [1-5] | [1-5] | [1-5] |
| Revenue Maximization | [1-5] | [1-5] | [1-5] | [1-5] | [1-5] |
| Customer Perception | [1-5] | [1-5] | [1-5] | [1-5] | [1-5] |
| Scalability | [1-5] | [1-5] | [1-5] | [1-5] | [1-5] |
| Competitive Defensibility | [1-5] | [1-5] | [1-5] | [1-5] | [1-5] |
| **Total Score** | **[X]/30** | **[X]/30** | **[X]/30** | **[X]/30** | **[X]/30** |

### Recommended Model: [Model Name]

**Why this model wins**:
1. [Reason 1 with supporting data]
2. [Reason 2 with supporting data]
3. [Reason 3 with supporting data]

**Why the others were rejected**:
- **[Model 2]**: [Why it doesn't fit]
- **[Model 3]**: [Why it doesn't fit]
- **[Model 4]**: [Why it doesn't fit]
- **[Model 5]**: [Why it doesn't fit]

---

## 5. Recommended Tier Structure

### Pricing Tiers

#### Tier 1: [Name] -- $[X]/mo (billed monthly) | $[X]/mo (billed annually)
**Target Customer**: [Who this is for]
**Purpose**: [Land new customers / Self-serve adoption / SMB segment]

**Included**:
- [Feature 1] -- [Limit if any]
- [Feature 2] -- [Limit if any]
- [Feature 3] -- [Limit if any]
- [Support level]: [Email / Chat / Response time SLA]

**Not Included** (upgrade triggers):
- [Feature that requires Tier 2]
- [Higher limit on usage]
- [Advanced capability]

**Economics**:
- Gross Margin at this tier: [X]%
- Expected conversion to Tier 2: [X]% within [X] months
- Target customer count: [X] in Year 1

---

#### Tier 2: [Name] -- $[X]/mo (billed monthly) | $[X]/mo (billed annually)
**Target Customer**: [Who this is for]
**Purpose**: [Core revenue driver / Growth segment / Mid-market]

**Included** (everything in Tier 1 plus):
- [Feature 4] -- [Limit if any]
- [Feature 5] -- [Limit if any]
- [Feature 6] -- [Limit if any]
- [Support level]: [Priority / Phone / Dedicated CSM]

**Not Included** (upgrade triggers):
- [Feature that requires Tier 3]
- [Custom integrations]
- [Advanced security/compliance]

**Economics**:
- Gross Margin at this tier: [X]%
- Expected share of total revenue: [X]%
- Target customer count: [X] in Year 1

---

#### Tier 3: [Name] -- $[X]/mo (billed monthly) | $[X]/mo (billed annually)
**Target Customer**: [Who this is for]
**Purpose**: [ARPU maximization / Enterprise-lite / Power users]

**Included** (everything in Tier 2 plus):
- [Feature 7] -- [Limit if any]
- [Feature 8] -- [Limit if any]
- [Feature 9] -- [Limit if any]
- [Support level]: [Dedicated CSM / SLA / Training]

**Not Included** (upgrade triggers):
- [Custom development]
- [White-label options]
- [Dedicated infrastructure]

**Economics**:
- Gross Margin at this tier: [X]%
- Expected share of total revenue: [X]%
- Target customer count: [X] in Year 1

---

#### Enterprise: Custom Pricing (starting at $[X]/mo)
**Target Customer**: [Who this is for]
**Purpose**: [Large deals / Strategic accounts / Custom requirements]

**Included** (everything in Tier 3 plus):
- Custom integrations and API access
- Dedicated infrastructure / Single-tenant option
- Custom SLA and uptime guarantees
- Dedicated support team
- Quarterly business reviews
- Custom onboarding and training
- Volume discounts on usage

**Sales Process**: [Inbound demo request / Outbound AE / Partner referral]

**Economics**:
- Target ACV: $[X]K - $[X]K
- Sales cycle: [X]-[X] months
- Expected deal count Year 1: [X]

---

### Tier Distribution Projection

| Tier | Year 1 Customers | Year 1 Revenue | % of Total Revenue | Avg Revenue/Customer |
|------|-------------------|----------------|--------------------|---------------------|
| [Tier 1] | [X] | $[X] | [X]% | $[X]/mo |
| [Tier 2] | [X] | $[X] | [X]% | $[X]/mo |
| [Tier 3] | [X] | $[X] | [X]% | $[X]/mo |
| Enterprise | [X] | $[X] | [X]% | $[X]/mo |
| **Total** | **[X]** | **$[X]** | **100%** | **$[X]/mo** |

---

## 6. Annual vs. Monthly Billing Analysis

### Pricing Structure

| Tier | Monthly Price | Annual Price (per month) | Annual Discount | Annual Upfront Total |
|------|--------------|-------------------------|-----------------|---------------------|
| [Tier 1] | $[X] | $[X] | [X]% | $[X] |
| [Tier 2] | $[X] | $[X] | [X]% | $[X] |
| [Tier 3] | $[X] | $[X] | [X]% | $[X] |

### Annual Discount Rationale

**Recommended Annual Discount**: [X]% (industry standard: 15-20% for SaaS)

**Why this discount level**:
- At [X]% discount, the annual plan pays for itself in [X] months
- Annual customers churn at [X]% vs. [X]% for monthly (industry data)
- Cash collected upfront: $[X] per annual customer vs. $[X] realized over 12 months from monthly
- Effective cost of discount: $[X] per customer per year
- NPV of annual upfront payment vs. 12 monthly payments: $[X] advantage

### Cash Flow Impact

| Scenario | Year 1 Cash Collected | Year 1 Recognized Revenue | Cash Advantage |
|----------|----------------------|--------------------------|----------------|
| 100% Monthly | $[X] | $[X] | Baseline |
| 50/50 Monthly/Annual | $[X] | $[X] | +$[X] |
| 30/70 Monthly/Annual | $[X] | $[X] | +$[X] |
| 100% Annual | $[X] | $[X] | +$[X] |

### Annual Plan Conversion Tactics

1. **Default to annual**: Show annual pricing first, monthly as the alternative
2. **Savings callout**: "Save $[X]/year" prominently displayed
3. **Feature incentive**: Include a bonus feature or higher limit for annual plans
4. **Trial-to-annual pipeline**: After 14-day trial, offer annual plan with first-month discount
5. **Month-to-annual upsell**: At month 3, email offering to switch with prorated credit

**Target Mix**: [X]% annual / [X]% monthly by end of Year 1

---

## 7. Discount Policy

### Standard Discount Framework

| Discount Type | Amount | Conditions | Approval Required |
|---------------|--------|------------|-------------------|
| Annual Prepay | [X]% | 12-month commitment, paid upfront | None (standard) |
| Multi-Year | [X]% additional | 24+ month commitment | VP Sales |
| Volume (seats/usage) | [X]-[X]% | [X]+ seats or $[X]K+ ACV | Sales Manager |
| Non-Profit / Education | [X]% | Verified 501(c)(3) or .edu | Ops |
| Startup Program | [X]% for [X] months | Under $[X]M funding, under [X] employees | Partnerships |
| Strategic / Design Partner | [X]-[X]% | Case study + reference agreement | VP Sales + CEO |
| Competitive Displacement | Up to [X]% for [X] months | Migrating from named competitor | Sales Manager |

### Discount Guardrails

**Hard Floor**: Never discount below $[X]/mo for [Tier] -- this is below cost-to-serve.

**Maximum Discount**: [X]% off list price under any circumstance. Exceptions require CEO approval.

**Stacking Rules**: Discounts do not stack. Customer receives the single best discount they qualify for.

**Sunset Policy**: All discounts expire at renewal. Renewals priced at then-current list price minus any applicable standard discount (annual, volume).

### What NOT to Discount

- Never discount to match a competitor with an inferior product; sell value instead
- Never discount after a prospect says "we need to think about it" -- this signals desperation
- Never offer a discount without getting something in return (longer term, case study, referral)
- Never create custom pricing for one customer that you cannot extend to similar customers

### Discount Impact Modeling

| Average Discount Given | Impact on Revenue (100 customers) | Margin Impact | Customers Needed to Compensate |
|------------------------|----------------------------------|---------------|-|
| 0% (list price) | $[X] (baseline) | [X]% | -- |
| 10% | -$[X] (-10%) | [X]% | +[X] customers |
| 20% | -$[X] (-20%) | [X]% | +[X] customers |
| 30% | -$[X] (-30%) | [X]% | +[X] customers |

**Key insight**: A [X]% discount requires [X]% more customers to achieve the same revenue. Discounting is expensive.

---

## 8. Churn Sensitivity Analysis

### Revenue Impact of Churn

| Monthly Churn Rate | Annual Churn Rate | Year 1 Revenue Loss | Year 2 Cumulative Loss | 5-Year Cumulative Loss |
|-------------------|--------------------|---------------------|----------------------|----------------------|
| 1% | 11.4% | $[X] | $[X] | $[X] |
| 2% | 21.5% | $[X] | $[X] | $[X] |
| 3% | 30.6% | $[X] | $[X] | $[X] |
| 5% | 46.0% | $[X] | $[X] | $[X] |
| 7% | 58.7% | $[X] | $[X] | $[X] |

**Assumes**: Starting base of [X] customers at $[X] ARPU, with [X] new customers added per month.

### Churn by Price Point

Historical and industry data shows:

| Price Range | Typical Monthly Churn | Typical Annual Churn | Notes |
|-------------|----------------------|---------------------|-------|
| $0-$50/mo | 5-8% | 46-62% | High volume, low switching cost, impulse purchases |
| $50-$200/mo | 3-5% | 31-46% | SMB segment, moderate switching cost |
| $200-$1000/mo | 1-3% | 11-31% | Mid-market, meaningful investment, higher engagement |
| $1000+/mo | 0.5-1.5% | 6-17% | Enterprise, high switching cost, multi-stakeholder |

**Pricing implication**: If your target churn is [X]% monthly, pricing below $[X]/mo carries structural churn risk because the customer has low commitment and switching cost.

### LTV Sensitivity to Churn

| Monthly Churn | Average Lifetime (months) | LTV at $[X] ARPU | LTV:CAC at $[X] CAC | Verdict |
|---------------|--------------------------|-------------------|---------------------|---------|
| 1% | 100 | $[X] | [X]:1 | Excellent |
| 2% | 50 | $[X] | [X]:1 | Good |
| 3% | 33 | $[X] | [X]:1 | Marginal |
| 5% | 20 | $[X] | [X]:1 | Unsustainable |
| 7% | 14 | $[X] | [X]:1 | Critical |

### Churn Mitigation Through Pricing

1. **Annual contracts reduce churn**: Monthly churn on annual contracts is typically 40-60% lower than month-to-month
2. **Higher price = higher engagement**: Customers who pay more use the product more and churn less
3. **Usage-based component creates stickiness**: If pricing includes a usage component, customers who grow usage naturally expand and are less likely to leave
4. **Switching cost increases with tier**: Enterprise features (SSO, audit logs, integrations) create structural switching costs
5. **Multi-seat plans reduce churn**: If multiple users at a company use the product, the decision to cancel requires consensus

### Recommended Churn Targets by Tier

| Tier | Target Monthly Churn | Target Annual Churn | Primary Retention Lever |
|------|---------------------|--------------------|-|
| [Tier 1] | [X]% | [X]% | Product engagement, onboarding |
| [Tier 2] | [X]% | [X]% | CSM check-ins, feature adoption |
| [Tier 3] | [X]% | [X]% | QBRs, integration depth |
| Enterprise | [X]% | [X]% | Strategic relationship, custom development |

---

## 9. Expansion Revenue Modeling

### Expansion Revenue Levers

| Lever | Mechanism | Expected Revenue per Customer per Year | Adoption Rate |
|-------|-----------|---------------------------------------|---------------|
| Tier Upgrades | Customer outgrows current tier limits | $[X] | [X]% of customers |
| Seat Expansion | Customer adds more users over time | $[X] | [X]% of customers |
| Usage Overages | Customer exceeds included usage | $[X] | [X]% of customers |
| Add-On Modules | Customer purchases optional features | $[X] | [X]% of customers |
| Professional Services | Implementation, training, consulting | $[X] | [X]% of customers |
| **Blended Expansion** | | **$[X]** | |

### Net Revenue Retention (NRR) Modeling

NRR = (Starting MRR + Expansion - Contraction - Churn) / Starting MRR

| Scenario | Gross Churn | Contraction | Expansion | NRR | Verdict |
|----------|------------|-------------|-----------|-----|---------|
| Conservative | [X]% | [X]% | [X]% | [X]% | [Below/Above] 100% |
| Base Case | [X]% | [X]% | [X]% | [X]% | [Below/Above] 100% |
| Optimistic | [X]% | [X]% | [X]% | [X]% | [Below/Above] 100% |

**Target NRR**: [X]% (best-in-class SaaS: 120-140%)

**What NRR means for growth**:
- At 90% NRR: You lose 10% of existing revenue each year. You must acquire enough new customers to replace that AND grow.
- At 100% NRR: Existing customer revenue is stable. All new revenue comes from new customers.
- At 110% NRR: Existing customers grow 10% per year. Even with zero new customers, revenue grows.
- At 120%+ NRR: Existing customers are a growth engine. New customer acquisition accelerates on top.

### Expansion Revenue Triggers (Built Into Pricing)

Design the tier structure so that natural product adoption triggers expansion:

1. **Seat-based trigger**: Tier 1 includes [X] seats. Teams naturally grow. At seat [X+1], customer pays overage or upgrades.
2. **Usage-based trigger**: Tier 2 includes [X] API calls/month. As customer's business grows, usage grows. At [X+1], overage kicks in.
3. **Feature-based trigger**: [Advanced Feature] is only in Tier 3. As customer matures, they need it. Natural upsell conversation.
4. **Compliance trigger**: SOC2, SSO, audit logs only in Enterprise. As customer grows, security requirements force upgrade.
5. **Team trigger**: Admin controls, role-based access, team management only in Tier 2+. As team grows, they need governance.

### 5-Year Revenue Projection with Expansion

| Year | Starting ARR | New Customer ARR | Expansion ARR | Churned ARR | Ending ARR | YoY Growth |
|------|-------------|-----------------|---------------|-------------|------------|------------|
| 1 | $0 | $[X] | $[X] | -$[X] | $[X] | -- |
| 2 | $[X] | $[X] | $[X] | -$[X] | $[X] | [X]% |
| 3 | $[X] | $[X] | $[X] | -$[X] | $[X] | [X]% |
| 4 | $[X] | $[X] | $[X] | -$[X] | $[X] | [X]% |
| 5 | $[X] | $[X] | $[X] | -$[X] | $[X] | [X]% |

**Key insight**: By Year [X], expansion revenue exceeds new customer revenue, meaning the business compounds from its existing base.

---

## 10. Pricing Page and Presentation

### Pricing Page Best Practices

**Layout**:
- Show 3 tiers side by side (do not show more than 4)
- Highlight the recommended tier with a "Most Popular" badge
- Default to annual pricing; toggle to show monthly
- Show savings amount for annual: "Save $[X]/year"
- Place enterprise as "Contact Us" with a clear CTA

**Anchoring Strategy**:
- Lead with the highest tier to anchor perception (if premium positioning)
- Lead with the most popular tier to drive conversion (if volume positioning)
- Show the full feature comparison table below the tier cards

**Social Proof on Pricing Page**:
- "[X] companies trust [Product]"
- Customer logos near relevant tiers
- "Join [Company] and [Company] on the [Tier Name] plan"

**Friction Reduction**:
- Free trial (14 days) or freemium entry point
- No credit card required for trial (increases trial starts by 50-70%)
- Money-back guarantee for first 30 days
- "Switch plans anytime" messaging

### Objection Handling on Pricing Page

| Objection | Response Element |
|-----------|-----------------|
| "Too expensive" | ROI calculator showing value delivered |
| "I only need one feature" | Highlight entry tier, suggest it as a starting point |
| "Competitor is cheaper" | Feature comparison table showing why you are worth more |
| "We need enterprise features" | Enterprise CTA with "Talk to sales" button |
| "Not sure which plan" | Interactive quiz: "Which plan is right for you?" |
| "What if we outgrow it?" | "Upgrade anytime, prorated billing" |

---

## 11. Price Testing and Iteration Plan

### Phase 1: Launch Pricing (Months 1-3)

- Launch with recommended tiers and prices
- Track: conversion rate by tier, trial-to-paid rate, plan distribution, churn by tier
- Collect qualitative feedback: "Why did you choose this plan?" in onboarding survey
- Do NOT change prices in this phase unless fundamentally broken

### Phase 2: Optimization (Months 4-6)

- A/B test annual discount: [X]% vs. [X]% vs. [X]%
- A/B test pricing page layout: feature-led vs. persona-led
- Test willingness to pay for add-on modules
- Analyze churn by tier and price point; adjust if one tier has disproportionate churn

### Phase 3: Expansion (Months 7-12)

- Introduce add-on modules based on feature request data
- Test price increase on new customers (grandfather existing)
- Evaluate need for a fourth tier or a free tier based on conversion data
- Model the impact of a usage-based component

### Metrics to Track

| Metric | Frequency | Target | Action Trigger |
|--------|-----------|--------|----------------|
| Trial-to-Paid Conversion | Weekly | [X]% | Below [X]%: pricing too high or value unclear |
| Plan Distribution | Monthly | [X]% Tier 1, [X]% Tier 2, [X]% Tier 3 | If > 70% in Tier 1: Tier 1 may be too generous |
| Monthly Churn by Tier | Monthly | < [X]% | Above [X]%: investigate product-market fit at that tier |
| Expansion Revenue Rate | Monthly | [X]% of MRR | Below [X]%: upgrade triggers not working |
| Discount Frequency | Monthly | < [X]% of deals | Above [X]%: list price may be too high |
| Win Rate vs. Competitor | Quarterly | > [X]% | Below [X]%: re-evaluate competitive positioning |
| NRR | Quarterly | > [X]% | Below 100%: churn + contraction exceeds expansion |

---

## 12. Risk Analysis

### Pricing Risks and Mitigations

| Risk | Probability | Impact | Mitigation |
|------|------------|--------|------------|
| Price is too high; low conversion | Medium | High | Free tier or trial lowers barrier; A/B test lower prices |
| Price is too low; leaves revenue on the table | Medium | Medium | Easy to raise prices for new customers; harder to lower |
| Competitor undercuts price aggressively | Medium | Medium | Compete on value, not price; document differentiation |
| Customers game the tier system | Low | Low | Usage monitoring; terms of service; account reviews |
| Enterprise customers demand custom pricing | High | Low | Build enterprise tier with flexibility; set floor |
| Annual discount cannibalizes monthly revenue | Low | Medium | Model cash flow impact; ensure discount is sustainable |
| Churn spikes after price increase | Medium | High | Grandfather existing customers; phase increases gradually |

### Pricing Anti-Patterns to Avoid

1. **Too many tiers**: More than 4 tiers creates decision paralysis. Stick to 3 + Enterprise.
2. **Hidden fees**: Usage overages, onboarding fees, or support charges that surprise customers destroy trust.
3. **Per-seat pricing when usage varies wildly**: If one user generates 100x the load of another, per-seat is unfair and creates resentment.
4. **Free tier that is too generous**: If free covers 80% of use cases, paid conversion will be < 2%.
5. **Pricing that punishes success**: If the customer's bill doubles when their usage doubles, they will seek alternatives.
6. **Infrequent pricing reviews**: Pricing should be revisited every 6-12 months as costs, competition, and value evolve.

---

## 13. Implementation Checklist

### Pre-Launch

- [ ] Finalize tier names, prices, and feature allocation
- [ ] Build pricing page with recommended layout
- [ ] Configure billing system (Stripe, Chargebee, etc.) with all tiers, discounts, and annual plans
- [ ] Set up revenue analytics (MRR, churn, expansion tracking)
- [ ] Create internal pricing documentation for sales team
- [ ] Prepare objection-handling scripts for sales
- [ ] Set up A/B testing infrastructure for pricing page
- [ ] Legal review of terms of service and pricing terms

### Launch

- [ ] Publish pricing page
- [ ] Announce pricing to existing customers (if changing)
- [ ] Enable self-serve checkout for Tier 1 and Tier 2
- [ ] Brief sales team on Enterprise tier positioning
- [ ] Set up automated emails for trial expiration, upgrade prompts, and annual renewal

### Post-Launch (First 90 Days)

- [ ] Weekly review: conversion rate, plan distribution, trial starts
- [ ] Monthly review: churn by tier, expansion revenue, discount usage
- [ ] Collect customer feedback on pricing in onboarding survey
- [ ] Document competitive pricing changes
- [ ] First pricing committee review at day 90

---

## Appendix A: Pricing Model Deep Dive Calculations

[Include detailed calculations for each pricing model evaluated: cost-plus margin calculations, value-based EVC model, competitor price mapping, penetration pricing timeline to profitability, premium pricing willingness-to-pay analysis]

## Appendix B: Customer Interview Insights

[Summarize any customer interview data, survey results, or willingness-to-pay research that informed the strategy]

## Appendix C: Competitor Pricing Screenshots and Sources

[Document where competitor pricing data was obtained, dates of collection, and any caveats about accuracy]

## Appendix D: Financial Model Assumptions

[List all assumptions used in revenue projections, churn modeling, and expansion forecasts with sources and confidence levels]
```

### Research and Analysis Process

When using this skill, follow this sequence:

1. **Gather inputs**: Ask the user for product, cost, market, and competitor information. Be specific about what you need.

2. **Research competitors**: Use WebSearch and WebFetch to find current competitor pricing pages. Look for:
   - Official pricing pages (search "[competitor] pricing")
   - G2, Capterra, or TrustRadius comparisons
   - Recent blog posts or press releases about pricing changes
   - Crunchbase for funding and growth signals

3. **Analyze the market**: Determine where the product sits in the competitive landscape. Look for market reports, analyst commentary, and customer reviews that mention pricing.

4. **Build the cost model**: Work with the user to fill in the cost structure. If they do not know exact numbers, use industry benchmarks and note assumptions.

5. **Evaluate all five pricing models**: Score each model against the specific product and market context. Do not skip a model -- even if it is obviously wrong, explain why.

6. **Design the tier structure**: Create tiers that align with customer segments, create natural upgrade paths, and maximize expansion revenue.

7. **Model the financials**: Project revenue, churn, expansion, and cash flow under multiple scenarios.

8. **Write the strategy document**: Generate the full pricing-strategy.md with all sections populated. Use real numbers from the research, not placeholders.

### Best Practices

1. **Always ground recommendations in data**: Use competitor prices, industry benchmarks, and cost analysis to justify every recommendation. Never guess.
2. **Design for expansion**: The best pricing strategies make it natural for customers to spend more over time. Build expansion triggers into the tier structure.
3. **Think about the buyer**: Who signs the check? What is their budget authority? A $49/mo product is an expense report. A $500/mo product is a department budget. A $5000/mo product is a procurement process.
4. **Price for value, not cost**: Cost sets the floor. Value sets the ceiling. Competitor pricing sets the context. The optimal price sits between floor and ceiling, informed by context.
5. **Keep it simple**: Customers should understand your pricing in under 30 seconds. If it requires a spreadsheet to figure out what they owe, it is too complex.
6. **Plan for price increases**: Starting too low is harder to fix than starting at the right level. Price at 80% of your confidence ceiling, not 50%.
7. **Annual contracts are a superpower**: They reduce churn, improve cash flow, increase commitment, and smooth revenue forecasting. Always incentivize annual.
8. **Never race to the bottom**: Competing on price alone is a losing strategy unless you have a structural cost advantage. Compete on value.
9. **Test and iterate**: Pricing is not a one-time decision. Review quarterly. Test changes with new customers. Grandfather existing customers when raising prices.
10. **Model churn sensitivity**: A 1% improvement in monthly churn is often worth more than a 10% increase in new customer acquisition. Price to retain.

### Common Use Cases

**Trigger Phrases**:
- "Help me price my SaaS product"
- "Design a pricing strategy for [product]"
- "How should I price my service?"
- "Analyze competitor pricing for [market]"
- "Should I use per-seat or usage-based pricing?"
- "Create pricing tiers for my product"
- "What discount policy should I have?"
- "Model the impact of churn on my revenue"

**Example Request**:
> "I'm building a project management tool for agencies. Our main competitors are Monday.com, Asana, and ClickUp. We have 50 beta users and want to launch paid plans next month. Our infrastructure costs about $3 per user per month. Help me design a pricing strategy."

**Response Approach**:
1. Research current pricing for Monday.com, Asana, ClickUp, and other competitors
2. Ask about target customer size, key differentiators, and willingness-to-pay signals from beta users
3. Build the cost model using provided infrastructure costs and estimated support/sales costs
4. Evaluate all five pricing models against the agency market context
5. Design a 3-tier structure with natural upgrade paths
6. Model revenue scenarios at different price points and churn rates
7. Generate the full pricing-strategy.md with real competitor data and financial projections
8. Recommend a launch plan with A/B testing strategy

Remember: Pricing is the single highest-leverage decision a business makes. A 1% improvement in pricing generates more profit than a 1% improvement in customer acquisition, retention, or costs. Get it right.

Attribution

OneWave-AIOneWave-AI
View sourceMore from OneWave-AI →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →