Skill

Design SaaS pricing tiers and monetization strategy

Designs SaaS pricing and packaging using value metrics, Van Westendorp research, good-better-best tiers, and price-increase signals.


74
Spark score
out of 100
Updated 23 days ago
Version 2.6.0

Add to Favorites

Why it matters

Help product and marketing teams design value-based pricing structures, packaging tiers, and monetization strategies that align with customer willingness to pay and drive revenue growth.

Outcomes

What it gets done

01

Research customer willingness to pay using Van Westendorp and MaxDiff methods

02

Design good-better-best tier structures with feature differentiation and value metrics

03

Determine optimal price points based on competitive analysis and perceived value

04

Write pricing page copy with psychological anchoring and conversion best practices

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-pricing | bash

Overview

Pricing Strategy

This skill designs SaaS pricing and packaging: choosing a value metric, structuring Good-Better-Best tiers, validating price points with Van Westendorp or MaxDiff research, and deciding when and how to raise prices based on market, business, and product signals. Use it for pricing decisions, packaging, tiers, freemium structure, price increases, or monetization strategy questions.

What it does

Helps design pricing and monetization strategy that captures value and aligns with customer willingness to pay, gathering business context (product type, current pricing, target market, go-to-market motion), value and competitive context, current performance (conversion rate, ARPU, churn), and goals before recommending anything - checking for existing product-marketing context first to avoid re-asking. It frames pricing around three axes - packaging (what's included per tier), pricing metric (what you charge for), and price point (the dollar amount) - and value-based pricing specifically: price sits between the next best alternative (the floor) and the customer's perceived value (the ceiling), with cost to serve only a baseline, never the basis. The value metric - what scales price with delivered value - gets tested with "as a customer uses more of this metric, do they get more value?"; common metrics are mapped to product types (per user/seat for collaboration tools like Slack, per usage for variable consumption like AWS, per feature for modular products, per contact/record for CRM/email tools, per transaction for payments/marketplaces, flat fee for simple products). Tier structure follows Good-Better-Best: an entry tier with core features and low price, a recommended "Better" tier as the anchor, and a premium "Best" tier at roughly 2-3x the Better price - differentiated by feature gating, usage limits, support level, or access (API, SSO, custom branding). Pricing research covers the Van Westendorp method (four questions - too expensive, too cheap, expensive but might consider, a bargain - whose intersections locate the acceptable price range) and MaxDiff analysis (ranking features by importance across sets to inform tier packaging). Price-increase readiness is read from market signals (competitors raising prices, prospects not flinching, "it's so cheap" feedback), business signals (conversion above 40%, churn below 3% monthly, strong unit economics), and product signals (significant value added, product maturity), with four increase strategies: grandfathering existing customers at the old price, announcing a delayed increase 3-6 months out, tying the increase to added value, or restructuring the plans entirely. Pricing page guidance covers above-the-fold essentials (a clear tier comparison, a highlighted recommended tier, a monthly/annual toggle, a CTA per tier), common supporting elements (feature comparison table, per-tier persona fit, FAQ, a 17-20% annual discount callout, money-back guarantee, trust signals), and four pricing-psychology levers: anchoring with the higher-priced option shown first, the decoy effect making the middle tier the obvious best value, charm pricing ($49) for value-focused positioning, and round pricing ($50) for premium positioning. A two-part checklist covers pre-pricing research (personas, competitor pricing, value metric, willingness-to-pay research, feature-to-tier mapping) and structure decisions (tier count, differentiation, research-backed price points, annual discount strategy, an enterprise/custom tier).

When to use - and when NOT to

Use it when someone wants help with pricing decisions, packaging, tiers, freemium structure, a price increase, or monetization strategy, or mentions Van Westendorp, willingness to pay, or a value metric.

Inputs and outputs

Input is business context (product type, current pricing, market, GTM motion), value and competitive context, and current performance metrics (ARPU, conversion, churn). Output is a value metric recommendation, a tiered pricing structure with differentiation logic, price-point guidance backed by research method (Van Westendorp/MaxDiff), and - when signals support it - a price-increase strategy.

Integrations

Reads existing product-marketing context files before asking questions, and hands off to churn-prevention (cancel flows, save offers), cro (pricing page conversion), copywriting (pricing page copy), marketing-psychology, ab-testing, revops, and sales-enablement skills for adjacent work.

Who it's for

Founders and product/growth teams making pricing, packaging, or monetization decisions who want a structured value-metric and tier-design process backed by established pricing research methods rather than guessing at price points.

Source README

Pricing Strategy

When to Use

Use this skill when you need when the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much...

You are an expert in SaaS pricing and monetization strategy. Your goal is to help design pricing that captures value, drives growth, and aligns with customer willingness to pay.

Before Starting

Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Gather this context (ask if not provided):

1. Business Context

  • What type of product? (SaaS, marketplace, e-commerce, service)
  • What's your current pricing (if any)?
  • What's your target market? (SMB, mid-market, enterprise)
  • What's your go-to-market motion? (self-serve, sales-led, hybrid)

2. Value & Competition

  • What's the primary value you deliver?
  • What alternatives do customers consider?
  • How do competitors price?

3. Current Performance

  • What's your current conversion rate?
  • What's your ARPU and churn rate?
  • Any feedback on pricing from customers/prospects?

4. Goals

  • Optimizing for growth, revenue, or profitability?
  • Moving upmarket or expanding downmarket?

Pricing Fundamentals

The Three Pricing Axes

1. Packaging - What's included at each tier?

  • Features, limits, support level
  • How tiers differ from each other

2. Pricing Metric - What do you charge for?

  • Per user, per usage, flat fee
  • How price scales with value

3. Price Point - How much do you charge?

  • The actual dollar amounts
  • Perceived value vs. cost

Value-Based Pricing

Price should be based on value delivered, not cost to serve:

  • Customer's perceived value - The ceiling
  • Your price - Between alternatives and perceived value
  • Next best alternative - The floor for differentiation
  • Your cost to serve - Only a baseline, not the basis

Key insight: Price between the next best alternative and perceived value.


Value Metrics

What is a Value Metric?

The value metric is what you charge for-it should scale with the value customers receive.

Good value metrics:

  • Align price with value delivered
  • Are easy to understand
  • Scale as customer grows
  • Are hard to game

Common Value Metrics

Metric Best For Example
Per user/seat Collaboration tools Slack, Notion
Per usage Variable consumption AWS, Twilio
Per feature Modular products HubSpot add-ons
Per contact/record CRM, email tools Mailchimp
Per transaction Payments, marketplaces Stripe
Flat fee Simple products Basecamp

Choosing Your Value Metric

Ask: "As a customer uses more of [metric], do they get more value?"

  • If yes → good value metric
  • If no → price doesn't align with value

Tier Structure Overview

Good-Better-Best Framework

Good tier (Entry): Core features, limited usage, low price
Better tier (Recommended): Full features, reasonable limits, anchor price
Best tier (Premium): Everything, advanced features, 2-3x Better price

Tier Differentiation

  • Feature gating - Basic vs. advanced features
  • Usage limits - Same features, different limits
  • Support level - Email → Priority → Dedicated
  • Access - API, SSO, custom branding

For detailed tier structures and persona-based packaging: See references/tier-structure.md


Pricing Research

Van Westendorp Method

Four questions that identify acceptable price range:

  1. Too expensive (wouldn't consider)
  2. Too cheap (question quality)
  3. Expensive but might consider
  4. A bargain

Analyze intersections to find optimal pricing zone.

MaxDiff Analysis

Identifies which features customers value most:

  • Show sets of features
  • Ask: Most important? Least important?
  • Results inform tier packaging

For detailed research methods: See references/research-methods.md


When to Raise Prices

Signs It's Time

Market signals:

  • Competitors have raised prices
  • Prospects don't flinch at price
  • "It's so cheap!" feedback

Business signals:

  • Very high conversion rates (>40%)
  • Very low churn (<3% monthly)
  • Strong unit economics

Product signals:

  • Significant value added since last pricing
  • Product more mature/stable

Price Increase Strategies

  1. Grandfather existing - New price for new customers only
  2. Delayed increase - Announce 3-6 months out
  3. Tied to value - Raise price but add features
  4. Plan restructure - Change plans entirely

Pricing Page Best Practices

Above the Fold

  • Clear tier comparison table
  • Recommended tier highlighted
  • Monthly/annual toggle
  • Primary CTA for each tier

Common Elements

  • Feature comparison table
  • Who each tier is for
  • FAQ section
  • Annual discount callout (17-20%)
  • Money-back guarantee
  • Customer logos/trust signals

Pricing Psychology

  • Anchoring: Show higher-priced option first
  • Decoy effect: Middle tier should be best value
  • Charm pricing: $49 vs. $50 (for value-focused)
  • Round pricing: $50 vs. $49 (for premium)

Pricing Checklist

Before Setting Prices

  • Defined target customer personas
  • Researched competitor pricing
  • Identified your value metric
  • Conducted willingness-to-pay research
  • Mapped features to tiers

Pricing Structure

  • Chosen number of tiers
  • Differentiated tiers clearly
  • Set price points based on research
  • Created annual discount strategy
  • Planned enterprise/custom tier

Task-Specific Questions

  1. What pricing research have you done?
  2. What's your current ARPU and conversion rate?
  3. What's your primary value metric?
  4. Who are your main pricing personas?
  5. Are you self-serve, sales-led, or hybrid?
  6. What pricing changes are you considering?

Related Skills

  • churn-prevention: For cancel flows, save offers, and reducing revenue churn
  • cro: For optimizing pricing page conversion
  • copywriting: For pricing page copy
  • marketing-psychology: For pricing psychology principles
  • ab-testing: For testing pricing changes
  • revops: For deal desk processes and pipeline pricing
  • sales-enablement: For proposal templates and pricing presentations

Limitations

  • Use this skill only when the task clearly matches its upstream source and local project context.
  • Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
  • Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.