Stats
Actions
Tags
From saas-pricing-engine
This skill should be used when the user says "write pricing page copy", "create a pricing page", "pricing page design", "write tier descriptions", "pricing FAQ", "how should I present my pricing", "pricing page conversion", "pricing comparison table", "feature comparison copy", "pricing CTA copy", "upgrade prompt copy", "downgrade prevention copy", "annual vs monthly copy", "pricing announcement email", "price increase communication", or any request to write the customer-facing copy, page structure, or communication materials for a pricing page or pricing change. This skill turns a pricing model into persuasive, conversion-optimized customer-facing content. Use this after pricing-modeler has produced the tier definitions and price points.
How this skill is triggered — by the user, by Claude, or both
Slash command
/saas-pricing-engine:pricing-copywriterThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Transform a pricing model into conversion-optimized, customer-facing pricing content — page copy, comparison tables, FAQs, upgrade prompts, and pricing change communications.
Transform a pricing model into conversion-optimized, customer-facing pricing content — page copy, comparison tables, FAQs, upgrade prompts, and pricing change communications.
This skill works best with output from pricing-modeler (tier definitions, price points, feature gates). If none exists, gather the basics: what tiers exist, what each costs, and what's in each.
Build the pricing page in this order:
The headline should answer "why should I pay?" not "how much does it cost?"
Good: "Compliance confidence at every scale" Bad: "Our pricing plans"
The subheadline addresses the primary pricing objection for your audience.
Good: "Start free. Upgrade when your team grows. No surprises." Bad: "Choose the plan that's right for you."
Annual vs. monthly toggle. Always default to annual (it's what you want them to pick).
Copy for annual savings badge:
Never show just the annual price without context. Show the monthly equivalent.
Each tier card follows this structure:
[TIER NAME]
[One-line description of who this tier is for]
[$XX/mo] billed annually (or $XX/mo billed monthly)
[Primary CTA button]
[3-5 key features with benefit framing]
- [Feature] — [why it matters]
- [Feature] — [why it matters]
- Everything in [Previous Tier], plus:
- [Differentiating feature]
The middle/primary tier should be visually differentiated:
Below the tier cards, a detailed comparison for evaluators who need specifics.
Design principles:
Positioned between pricing and FAQ:
Address the top objections and questions. Typical sections:
Read references/pricing-faq-templates.md for a library of proven FAQ copy.
Repeat the primary CTA after the FAQ. For B2B SaaS:
Lead with the buyer, not the feature.
Use specifics, not superlatives.
Frame limits as capability, not restriction.
The upgrade trigger should be implicit in the tier description.
| Tier | Primary CTA | Alternative |
|---|---|---|
| Free | "Get started free" | "Create free account" |
| Starter | "Start free trial" | "Try Starter free" |
| Pro | "Start free trial" | "Upgrade to Pro" |
| Enterprise | "Contact sales" | "Request a demo" |
Avoid:
When raising prices, communicate with transparency and respect:
Subject: Changes to [Product] pricing — effective [date]
[Name],
We're writing to let you know about upcoming changes to [Product] pricing,
effective [date].
[What's changing]
Your [Tier] plan will move from $X/mo to $Y/mo (a [Z]% increase).
[Why]
Over the past [period], we've [invested in / shipped / improved]:
- [Concrete improvement 1]
- [Concrete improvement 2]
- [Concrete improvement 3]
This investment allows us to [outcome that matters to them].
[What's NOT changing]
- Your current features and limits remain the same
- [Any grandfathering or grace period]
- [Lock-in option if available: "Lock in your current rate for 12 months by switching to annual billing before [date]"]
[Support]
If you have questions, reply to this email or [reach out to support].
We're committed to making [Product] worth every dollar.
[Name]
[Title]
When a major feature launch accompanies a price change:
Subject: [Feature] is here — and [Plan] just got better
[Name],
Big news: [Feature] is now live in [Product].
[What it does — one sentence, benefit-framed]
[Feature] is included in your [Tier] plan at no additional cost.
Starting [date], [Tier] pricing moves to $X/mo (from $Y/mo) to reflect
the expanded capabilities. As a current customer, you'll keep your
current rate until [date].
[CTA to try the feature]
When a user hits a tier limit:
You've reached your plan's [limit type] limit.
Upgrade to [Next Tier] to:
- [Primary benefit of upgrading]
- [Secondary benefit]
- [Quantified improvement: "Manage up to X assets"]
[Upgrade now] [View plans]
When a user initiates a downgrade:
Before you switch to [Lower Tier], here's what you'll lose:
- [Feature they actively use] (used X times this month)
- [Feature they actively use] (X team members rely on this)
- [Limit change] (your current usage: X, [Lower Tier] limit: Y)
[Keep current plan] [Continue downgrade]
Use actual usage data when available — "You used API access 47 times this month" is more persuasive than "You'll lose API access."
For STIGViewer and defense-adjacent products:
Tone adjustments:
Trust signals that matter in this vertical:
Pricing page additions for gov/defense:
Read references/compliance-copy-patterns.md for defense-vertical-specific language patterns.
npx claudepluginhub moxywolfllc/moxywolf-plugins --plugin saas-pricing-engineProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Searches MemPalace before answering questions about past work, people, projects, or prior decisions. Returns verbatim stored content instead of guessing from model memory.