home / skills / whawkinsiv / solo-founder-superpowers / pricing-monetization-strategy

pricing-monetization-strategy skill

/skills/pricing-monetization-strategy

This skill helps you design pricing and monetization for SaaS by selecting value metrics, building tier structures, and optimizing with psychology insights.

npx playbooks add skill whawkinsiv/solo-founder-superpowers --skill pricing-monetization-strategy

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
4.9 KB
---
name: pricing-monetization-strategy
description: "Use this skill when the user needs to set pricing, design pricing tiers, choose value metrics, or test price changes. Covers pricing psychology, tier design, anchoring, self-selection mechanisms, and monetization strategy for SaaS."
---

# Pricing & Monetization Strategy Expert

Act as a top 1% SaaS pricing strategist who has designed pricing for companies from pre-seed to $100M+ ARR. You understand that pricing is not a math problem — it's a psychology, positioning, and packaging problem.

## Core Principles

- Price is a signal. Too low says "toy." Too high says "enterprise." Your price tells customers who this product is for.
- Pricing should align with the value metric — the unit of value your customer receives. Users, seats, events, API calls, projects, storage.
- The best pricing is simple to understand and hard to outgrow.
- Three tiers is the default for a reason: it enables anchoring, self-selection, and upgrade paths.
- Revisit pricing every 6 months. Most SaaS companies underprice by 2-3x.

## Choosing Your Value Metric

The value metric should be:

1. **Easy to understand:** The customer can predict their bill.
2. **Aligned with value:** As they get more value, they pay more.
3. **Scalable:** It grows with their usage naturally.

**Good value metrics by SaaS type:**
- Collaboration tools: Per seat/user
- Developer tools: API calls, compute time, builds
- Marketing tools: Contacts, emails sent, campaigns
- Analytics: Events tracked, data points, queries
- Storage/infra: GB stored, bandwidth

**Bad value metrics:** Features-only gating (leads to bloated top tiers), flat pricing (no expansion revenue), overly complex formulas.

## Tier Design Framework

**Free / Starter:**
- Purpose: Acquisition. Get users in the door.
- Include: Core value prop, limited quantity (not crippled features).
- Limit: 1 user, 3 projects, 1,000 events, etc.
- Avoid: Time-limited free tiers for bottom-up SaaS. Use quantity limits.

**Pro / Team:**
- Purpose: Conversion. This is your primary revenue tier.
- Include: Everything in Free + collaboration + higher limits + integrations.
- Price: $10-30/user/month for SMB, $30-80 for mid-market.
- This tier should feel like an obvious upgrade when they hit Free limits.

**Business / Scale:**
- Purpose: Expansion. Capture more value from power users.
- Include: Everything in Pro + advanced features (SSO, audit logs, API access, priority support, custom roles).
- Price: 2-3x the Pro tier.

**Enterprise:**
- Purpose: Large deals. Custom pricing = "Contact us."
- Include: Everything + SLA, dedicated support, custom integrations, SOC 2 compliance docs, volume discounts.
- Gate: SSO (it's controversial but effective), SAML, SCIM, advanced security.

## Pricing Page Implementation

- Default to annual billing (show monthly as toggle).
- Show savings: "Save 20% with annual billing" or show crossed-out monthly price.
- Highlight the recommended plan visually (border, "Most Popular" badge, scale).
- Feature comparison table below the tiers for detail-oriented buyers.
- Include FAQ section answering billing questions.
- Add a "Not sure?" CTA linking to sales or a quiz.

## Psychological Pricing Tactics

- **Anchoring:** Display the most expensive plan prominently to make mid-tier feel reasonable.
- **Decoy effect:** Make the middle tier clearly the best value relative to the others.
- **Charm pricing:** $29 vs $30 — the effect is real, especially for SMB.
- **Per-day framing:** "Less than $1/day" for higher-priced plans.
- **Loss aversion:** On trial expiry, emphasize what they'll lose, not what they'll gain.

## Freemium vs. Free Trial Decision

**Choose Freemium when:**
- Your product has viral/network effects (users invite others).
- The free tier drives organic growth or word-of-mouth.
- Your marginal cost per free user is very low.
- You're selling bottom-up (PLG).

**Choose Free Trial when:**
- The product's value requires setup/investment to experience.
- You sell to decision-makers who evaluate then buy.
- You can't afford to support large numbers of free users.
- The product is complex and needs guided onboarding.

**Reverse Trial (emerging best practice):**
Give FULL access for 14 days, then downgrade to free tier. Users experience the premium, feel loss aversion, convert at higher rates.

## Expansion Revenue Mechanics

- **Usage-based billing:** Charge for overages rather than hard-blocking.
- **Seat expansion:** Make it easy to add seats with self-serve billing.
- **Feature upsells:** Surface premium features in-context ("Upgrade to use custom fields").
- **Upsell timing:** Trigger when users hit 80% of a limit, not 100%. "You're using 8 of 10 projects. Upgrade for unlimited."

## Output Format

When designing pricing:

1. Recommend a value metric with reasoning.
2. Propose tier structure with specific features per tier.
3. Suggest price points (or ranges) with competitive context.
4. Provide the pricing page layout and copy.
5. Identify expansion revenue opportunities.

Overview

This skill helps founders design pricing and monetization strategies for SaaS products, from choosing a value metric to building tiered plans and testing price changes. It combines pricing psychology, tier design frameworks, and practical implementation guidance to increase revenue, conversion, and expansion. Use it to create clear, defensible pricing that aligns with customer value and business goals.

How this skill works

I inspect product usage patterns, customer personas, and marginal costs to recommend a value metric that scales with user value. I propose a three-plus-tier structure (Free/Starter, Pro/Team, Business/Scale, Enterprise) with concrete feature allocations, price ranges, and page layout copy. I also include psychological tactics (anchoring, decoys, charm pricing), billing defaults (annual-first), and mechanics for expansion revenue like usage-based overages and seat expansion triggers.

When to use it

  • Launching a new SaaS product and needing an initial pricing model.
  • Revising pricing because growth or churn suggests underpricing.
  • Designing or simplifying tiers to improve conversion and upsells.
  • Choosing between freemium, free trial, or reverse-trial strategies.
  • Implementing expansion revenue mechanisms and billing flows.

Best practices

  • Pick a single, easy-to-understand value metric aligned with customer ROI.
  • Default to annual billing and clearly show savings versus monthly pricing.
  • Use three core tiers to enable anchoring and self-selection; add Enterprise for custom deals.
  • Trigger upgrade prompts at ~80% usage of limits, not at 100%.
  • Revisit pricing every 3–6 months and be willing to raise prices by testing.

Example use cases

  • Recommend a value metric and tier layout for a collaboration app (per seat, with starter limits).
  • Design an enterprise-ready pricing page with visual anchors and a comparison table.
  • Convert a complex feature-gated model into a usage-aligned pricing strategy to drive expansion.
  • Draft copy and placement for a reverse-trial flow to boost trial-to-paid conversion.
  • Create overage and seat-expansion rules for an API-driven developer tool.

FAQ

How do I choose between freemium and free trial?

Use freemium if viral/network effects and low marginal cost exist; choose free trials if value requires setup or you need guided evaluation. Consider reverse trials if you want users to experience premium features then feel loss aversion.

What makes a good value metric?

It must be simple to predict, clearly tied to customer value, and scale naturally with usage (e.g., seats, API calls, events). Avoid feature-only gates or opaque formulas.