Pricing Page (High‑Conversion) — Web Design Skill
Unverified●30/40Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor◐PartialPlain prose you can paste in — but no Cursor rules file
Codex◐PartialPlain prose you can paste in — but no AGENTS.md
Gemini CLI◐PartialPlain prose you can paste in
Copilot◐PartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add pricing-pageWho is stuck, and on what
People land on your pricing page, get confused, and leave without buying. You never know if it's the price, the plans, or just that nothing on the page answers their doubts.
What it gives you
A complete pricing page plan: your plans laid out with what's included, a recommended pick, clear buttons, and a ready-to-use list of questions and answers that calm buyer worries.
When NOT to use it
It won't build or publish the page for you, and it won't decide what prices to charge.
The whole source
Frontmatter — 2 properties
| name | pricing-page |
|---|---|
| description | Use when designing or rewriting a high-converting SaaS pricing page (structure, plan design, copywriting, SEO/AEO, FAQs, layout patterns, experiments). Includes checklists, templates, and common pitfalls. |
| 1 | --- |
| 2 | name: pricing-page |
| 3 | description: Use when designing or rewriting a high-converting SaaS pricing page (structure, plan design, copywriting, SEO/AEO, FAQs, layout patterns, experiments). Includes checklists, templates, and common pitfalls. |
| 4 | ---A5 — No allowed-tools declared — no way to tell what this skill may touch |
| 5 | |
| 6 | # Pricing Page (High‑Conversion) — Web Design Skill |
| 7 | |
| 8 | Design a pricing page that helps visitors **choose** and feel good about it. |
| 9 | Your job is not to “show prices.” |
| 10 | Your job is to **reduce uncertainty**. |
| 11 | |
| 12 | ## Before you design/write |
| 13 | Gather (ask if missing): |
| 14 | |
| 15 | ### 1) Offer + audience |
| 16 | - What are you selling? (category) |
| 17 | - Who is it for? (ICP + primary use case) |
| 18 | - What’s the main value metric? (seat, usage, project, revenue, etc.) |
| 19 | |
| 20 | ### 2) Plans |
| 21 | - Plan names + prices (monthly/annual) |
| 22 | - Limits per plan (the 3–6 limits that matter) |
| 23 | - What’s the upgrade trigger? (what causes people to move up?) |
| 24 | |
| 25 | ### 3) Objections + risk |
| 26 | - Top 3 reasons people don’t buy today |
| 27 | - Security/compliance needs? (SOC2, GDPR, etc.) |
| 28 | - Can you offer: free trial, free plan, money-back, demo? |
| 29 | |
| 30 | ### 4) Proof |
| 31 | - Testimonials, logos, results, case studies, metrics |
| 32 | |
| 33 | ### 5) Traffic context |
| 34 | - Are visitors coming from: homepage, feature pages, ads, comparison pages? |
| 35 | - What do they already know? |
| 36 | |
| 37 | --- |
| 38 | |
| 39 | ## Core structure (what a pricing page should have) |
| 40 | |
| 41 | ### Above the fold (must) |
| 42 | - **Clear value headline** (what outcome, for who) |
| 43 | - **Monthly/Annual toggle** with annual savings callout |
| 44 | - **3‑plan pricing table** (most common) or 2‑plan (simple product) |
| 45 | - **Primary CTA** per plan (consistent verbs) |
| 46 | |
| 47 | ### Below the fold (high leverage) |
| 48 | - **Plan comparison** (feature matrix or “what you get” bullets) |
| 49 | - **FAQ** (objection handling) |
| 50 | - **Social proof** near decision points |
| 51 | - **Security / compliance / procurement** section (if B2B) |
| 52 | - **Final CTA** + contact sales |
| 53 | |
| 54 | --- |
| 55 | |
| 56 | ## Layout types (pick one) |
| 57 | |
| 58 | ### A) Classic 3‑card |
| 59 | Best when: |
| 60 | - you have 3 natural tiers (Starter / Pro / Business) |
| 61 | - pricing is simple |
| 62 | |
| 63 | Rules: |
| 64 | - 1 plan labeled **Recommended** |
| 65 | - show “most popular” without yelling |
| 66 | |
| 67 | ### B) Value metric slider |
| 68 | Best when: |
| 69 | - pricing scales with usage (seats, events, credits) |
| 70 | |
| 71 | Rules: |
| 72 | - keep math obvious |
| 73 | - keep a safe default (median customer) |
| 74 | |
| 75 | ### C) “Pick your path” (two columns) |
| 76 | Best when: |
| 77 | - different audiences (Individuals vs Teams) |
| 78 | |
| 79 | Rules: |
| 80 | - separate by persona first, then price |
| 81 | |
| 82 | ### D) Enterprise last mile |
| 83 | Best when: |
| 84 | - you have a self-serve path + sales-led path |
| 85 | |
| 86 | Rules: |
| 87 | - Enterprise should read like **procurement reassurance** |
| 88 | |
| 89 | --- |
| 90 | |
| 91 | ## High‑conversion strategies (practical) |
| 92 | |
| 93 | ### 1) Make the decision easy |
| 94 | - 3 plans max (unless you have a strong reason) |
| 95 | - One recommended plan |
| 96 | - Bullets describe **outcomes**, not internal features |
| 97 | |
| 98 | ### 2) Anchor value (without being shady) |
| 99 | - Annual toggle with “Save X%” |
| 100 | - Show “Starting at” only if your pricing is truly variable |
| 101 | - Avoid surprise fees |
| 102 | |
| 103 | ### 3) Reduce risk |
| 104 | Choose at least one: |
| 105 | - Free trial |
| 106 | - Free plan |
| 107 | - Money‑back guarantee |
| 108 | - “Talk to sales” with a clear promise (response time, demo) |
| 109 | |
| 110 | ### 4) Handle objections before they bounce |
| 111 | Most effective FAQ topics: |
| 112 | - “Can I cancel anytime?” |
| 113 | - “What happens if I hit limits?” |
| 114 | - “Do you offer discounts?” |
| 115 | - “Is this for freelancers/teams?” |
| 116 | - “Security / data / compliance” |
| 117 | |
| 118 | ### 5) Provide a comparison that’s readable |
| 119 | - Avoid huge spreadsheets |
| 120 | - Group by: Core, Collaboration, Admin/Security, Support |
| 121 | - Highlight what changes at each tier |
| 122 | |
| 123 | --- |
| 124 | |
| 125 | ## Copywriting (templates) |
| 126 | |
| 127 | ### Headlines (choose a formula) |
| 128 | - “{Outcome} for {audience}—without {pain}” |
| 129 | - “Plans that scale from {small} to {big}” |
| 130 | - “Start small. Upgrade when {trigger}.” |
| 131 | |
| 132 | ### Plan description (2 lines) |
| 133 | - Who it’s for |
| 134 | - What it unlocks |
| 135 | |
| 136 | Example: |
| 137 | - **Pro** — For designers shipping weekly. Better components, faster iteration. |
| 138 | |
| 139 | ### CTA buttons |
| 140 | Rules: |
| 141 | - Use verbs that match the motion: |
| 142 | - “Start free trial” |
| 143 | - “Buy Pro” |
| 144 | - “Contact sales” |
| 145 | - Keep CTAs consistent across plans (don’t mix “Get started” / “Try now” / “Sign up”). |
| 146 | |
| 147 | ### Feature bullets (write like outcomes) |
| 148 | - ❌ “Unlimited projects” |
| 149 | - ✅ “Ship unlimited client sites without extra fees” |
| 150 | |
| 151 | --- |
| 152 | |
| 153 | ## Pricing table checklist (UI) |
| 154 | - Visible monthly/annual toggle |
| 155 | - “Save X%” callout on annual |
| 156 | - Recommended plan styling (subtle) |
| 157 | - Key limits visible (3–6 max) |
| 158 | - Included items visible (3–6 max) |
| 159 | - Clear next step under each plan (trial/buy/contact) |
| 160 | - Link: “Compare plans” (scrolls to matrix) |
| 161 | - Mobile: table becomes stacked cards (not a horizontal scroll nightmare) |
| 162 | |
| 163 | --- |
| 164 | |
| 165 | ## SEO + AEO (AI answers) checklist |
| 166 | |
| 167 | ### SEO basics |
| 168 | - Title: “Pricing — {Product}” + outcome keyword |
| 169 | - Meta description: 1 sentence on value + 1 sentence on pricing starting point |
| 170 | - Clean URL: `/pricing` |
| 171 | - Internal links from: |
| 172 | - homepage CTA |
| 173 | - feature pages |
| 174 | - comparison pages |
| 175 | |
| 176 | ### AEO (answer engines) |
| 177 | - Add an FAQ section that answers: |
| 178 | - refund policy |
| 179 | - trial length |
| 180 | - cancellation |
| 181 | - what counts as a seat/usage |
| 182 | - enterprise procurement |
| 183 | - Write FAQs in **plain Q/A** format. |
| 184 | - Optional: FAQ schema (if your stack supports it). |
| 185 | |
| 186 | --- |
| 187 | |
| 188 | ## Common pitfalls |
| 189 | - Too many plans (analysis paralysis) |
| 190 | - Features listed with no context (why it matters) |
| 191 | - Pricing hidden behind “Contact sales” for everything |
| 192 | - Switching value metric mid-page (confusing) |
| 193 | - Over-designed table that harms readability |
| 194 | |
| 195 | --- |
| 196 | |
| 197 | ## Output format (when generating a pricing page) |
| 198 | Return: |
| 199 | 1) **Page outline** (sections + order) |
| 200 | 2) **Pricing table spec** (plans, bullets, limits, CTA) |
| 201 | 3) **FAQ list** (6–12 Q/A) |
| 202 | 4) **SEO/AEO** (title + meta + FAQ schema suggestion) |
| 203 | 5) **Layout recommendation** (A/B/C/D + why) |
| 204 | |
| 205 | --- |
| 206 | |
| 207 | ## Quick questions (if user gives you only “make a pricing page”) |
| 208 | - Free plan or trial? |
| 209 | - Monthly/annual pricing numbers? |
| 210 | - Value metric? |
| 211 | - Recommended plan (which one and why)? |
| 212 | - Top 3 objections? |
| 213 |
Reviews
Installed this one?Write the first review and take the Trailblazer badge.
Alternatives
Structure Your Invention For A Patent FilingDescribe your invention in plain words and get back a formal write-up that lays out the problem it solves, how it works, and which parts are worth protecting.●····●37/40Claims Drafting: The Core Patent SkillDescribe your invention in plain words and get back a numbered set of formal patent claims — the legal wording that defines exactly what you own.●····●36/40Patent Novelty and Non-Obviousness CheckDescribe your invention in everyday words and get back a clear read on whether it's new and original enough to patent, plus where it might hit trouble.●····●35/40Patent Pipeline: From Invention to FilingDescribe your invention in plain words and get back a complete first-draft patent application — claims, full description, and abstract — ready to hand to a patent attorney.●····●35/40