How many tiers should I show?

Limit to 3-4 tiers and name them by who they serve (e.g., For teams, For enterprises) to reduce decision paralysis.

Should I show monthly and annual pricing?

Yes. Display both with a clear savings callout and ensure currency is visible to avoid confusion.

How do I encourage upgrading without dark patterns?

Make the upgrade path obvious in-product, use a clear CTA (e.g., Start free trial), and anchor with the highest-priced tier to set expectations.

pricing-page

Scanned

npx machina-cli add skill Dragoon0x/Product-Skills/pricing-page --openclaw

Files (1)

SKILL.md

1.7 KB

Pricing Page

Present pricing in ways that reduce friction and increase clarity.

How to use

/pricing-page Apply pricing page constraints to this conversation.

Constraints

Structure

MUST lead with the recommended plan (visual emphasis, "Most Popular" badge)
MUST limit to 3-4 tiers. More creates decision paralysis.
MUST name tiers by who they serve, not by size ("For teams" not "Business")
MUST show monthly and annual pricing with clear savings callout
NEVER hide pricing behind "Contact us" unless average deal size exceeds $10k/year

Feature Comparison

MUST group features by category, not random list
MUST bold the differentiating features between tiers
SHOULD use checkmarks sparingly. Specific values beat yes/no.
NEVER list features the user doesn't understand without explanation
MUST highlight what the user loses by choosing a lower tier, not just what they gain

Psychology

Anchor with the highest-priced tier first (right to left reading)
SHOULD include a free or low-cost entry point to reduce commitment anxiety
MUST make the upgrade path obvious from within the product
NEVER use dark patterns (hidden fees, pre-checked add-ons, confusing renewals)

Copy

Plan descriptions: one sentence explaining who this tier is for
CTA button text should reflect the action ("Start free trial" not "Submit")
Price should be the largest text element in each tier card
MUST show what currency the price is in

Source

git clone https://github.com/Dragoon0x/Product-Skills/blob/main/skills/conversion/pricing-page/SKILL.mdView on GitHub

Overview

Pricing Page defines practical patterns to present pricing clearly and reduce friction. It prescribes 3-4 tiers named for who they serve, anchor pricing with the highest-priced tier, and a visible upgrade path. It emphasizes category-grouped features, bold differentiators, and transparent currency and savings to empower confident decisions.

How This Skill Works

Pricing pages are organized to lead with the recommended plan (often with a Most Popular badge) and present 3-4 tiers with both monthly and annual prices. Features are grouped by category, differentiators are bolded, and the currency is clearly shown; losses on lower tiers are highlighted to influence choice. The design includes an obvious upgrade path and a CTA like Start free trial, while avoiding dark patterns.

When to Use It

Designing a new pricing page for a SaaS product.
Adding plan selectors or upgrade prompts within the product experience.
Redesigning monthly vs annual pricing with clear savings callouts.
Creating an upgrade flow that guides users to higher-value tiers.
A/B testing tier names, feature groupings, and pricing layouts.

Quick Start

Step 1: Define 3-4 tiers named by who they serve (e.g., For individuals, For teams, For enterprises) and ensure one is clearly recommended.
Step 2: Design price cards with the highest-priced tier on the right, include a Most Popular badge on the recommended plan, and show currency and both monthly and annual prices with savings.
Step 3: Build a grouped feature comparison by category, bold differentiators, keep checks minimal, and add an obvious upgrade path and a CTA like Start free trial.

Best Practices

Lead with the recommended plan and badge it as Most Popular to guide attention.
Limit to 3-4 tiers and name them by who they serve (e.g., For teams, For enterprises).
Show both monthly and annual prices with a clear savings callout.
Group features by category and bold the differentiating items between tiers.
Highlight what users lose by downgrading and ensure an obvious upgrade path with clear CTAs.

Example Use Cases

Example 1: A pricing page for a collaboration tool uses 3 tiers named For individuals, For teams, For enterprises, anchors the highest price on the right, and marks the middle tier with a Most Popular badge.
Example 2: Features are categorized (Analytics, Integrations, Security) with bolded differentiators like 'Unlimited projects' and 'SSO' while checkmarks are sparing and the currency is shown (USD).
Example 3: A free entry point (Free Starter) reduces commitment anxiety and demonstrates a tangible upgrade path to paid tiers.
Example 4: In-product upgrade prompts appear with a prominent 'Start free trial' CTA and a visible upgrade path from within workflows.
Example 5: The pricing card set displays monthly and annual prices side by side with a clear savings note and currency symbol, enabling quick comparison.

Frequently Asked Questions

Add this skill to your agents