← All skills

/pricing-breakdown

by Aera · Marketing

Will open Aera to add this skill. Don't have Aera? Download

Analyze a SaaS pricing page and recommend packaging, copy, and conversion fixes.

pricingsaasconversionpackaginglanding pages
SKILL.md
# Pricing Page Teardown

Use this skill to analyze a pricing page and recommend changes that improve clarity, conversion, and packaging.

## Inputs

Use the current page if it is a pricing page. If not, navigate to the pricing page for the company the user names. If pricing is hidden or gated, analyze what is visible and note the limitation.

## Process

1. Identify the product, target buyer, pricing model, and primary conversion action.
2. Extract tiers, prices, billing periods, included features, limits, add-ons, trials, guarantees, and enterprise paths.
3. Evaluate packaging clarity: tier names, feature grouping, buyer fit, upgrade triggers, plan contrast, and default recommended plan.
4. Evaluate conversion quality: CTA labels, objection handling, FAQs, social proof, trust signals, annual discount framing, risk reversal, and mobile readability.
5. Identify confusion, missing information, vague feature labels, and hidden cost risks.
6. Compare against 2 to 3 obvious competitors when useful and quick to verify.
7. Recommend specific copy, layout, and packaging experiments.

## Output Format

## Verdict
A short diagnosis of the pricing page's main strength and main conversion risk.

## What The Page Communicates
Summarize tiers, price points, buyer fit, and conversion path.

## Critical Fixes
List high impact issues with Evidence, Why it matters, and Fix.

## Packaging Experiments
Give 3 to 5 concrete tests, such as tier rename, feature regrouping, limit changes, CTA changes, or plan recommendation changes.

## Copy Rewrites
Provide replacement copy for confusing tier descriptions, CTAs, FAQs, or objection handling.

## Competitive Notes
Only include sourced competitor observations.

## Rules

- Do not invent private pricing.
- Treat pricing psychology as a hypothesis, not certainty.
- Include exact replacement text where helpful.
- Do not use em dashes.