Most pricing pages are an afterthought. The founder spends weeks on the landing page, then slaps three columns together with "Basic / Pro / Enterprise," lists some features, and calls it done. That's a problem — because the pricing page often has the highest purchase intent of any page on your site. Visitors who land here are already considering buying. The copy just needs to not get in the way.
These prompts target the five areas where pricing page copy matters most: what you name your tiers, how you describe features, how you handle objections in the FAQ, how you frame annual vs monthly, and how you write the enterprise section. Each one is designed to produce copy you can actually ship — not marketing fluff you'll need to rewrite.
Name your pricing tiers so they mean something
"Basic / Pro / Enterprise" tells your visitor nothing about who each plan is for or what they'll get. Good tier names do half the selling before someone reads a single feature. This prompt generates names that signal value and audience fit.
I need to name the pricing tiers for [product name], a [one sentence description].
Here are the tiers:
- Tier 1: [who it's for + key limitations — e.g., "solo users, up to 3 projects, no team features"]
- Tier 2: [who it's for + key capabilities — e.g., "small teams, unlimited projects, basic analytics"]
- Tier 3: [who it's for + key capabilities — e.g., "scaling companies, advanced analytics, priority support"]
My audience segments: [list 2-3 audience types — e.g., "freelancers, startups, mid-market SaaS"]
My brand tone: [e.g., "professional but approachable" or "bold and technical"]
Generate 4 naming options for the full set of tiers. Rules:
- Each name set must have a clear progression (the upgrade path should feel natural)
- Names should hint at who the plan is for OR what it unlocks — not just size/rank
- Avoid: Basic/Pro/Enterprise, Starter/Growth/Scale, Free/Plus/Premium (these are the defaults everyone uses)
- Avoid metaphors that don't relate to the product (no "Rocket / Spaceship / Galaxy" for an accounting tool)
- For each option, write a one-line tagline per tier (e.g., "For teams shipping fast" or "When spreadsheets stop cutting it")
- Explain in one sentence why the name set works for this specific productTier names matter more than people think. When we analyze pricing pages, the ones with descriptive tier names consistently outperform generic ones — visitors spend less time confused about which plan fits them.
Write feature descriptions that sell, not just list
A pricing table full of checkmarks and feature names like "Advanced Analytics" or "Custom Integrations" forces the visitor to guess what those features actually mean for them. This prompt turns feature lists into benefit-oriented descriptions.
Here's my current pricing table feature list:
[Paste your full feature list — include which tiers each feature appears in]
Product: [what you sell]
Audience for each tier:
- Tier 1 ([tier name]): [who buys this]
- Tier 2 ([tier name]): [who buys this]
- Tier 3 ([tier name]): [who buys this]
For each feature, rewrite it in two parts:
1. FEATURE NAME: Short, clear label (3-5 words max)
2. HOVER/TOOLTIP DESCRIPTION: One sentence explaining why this feature matters to the person on that tier (not what it does — why they'd care)
Rules:
- Feature names should be understandable by a non-technical buyer
- Descriptions should reference a real use case or outcome, not restate the feature name
- For features that differentiate tiers (e.g., "10 users" vs "unlimited users"), write the limit in a way that feels generous, not restrictive
- Flag any features that are confusing or redundant — suggest cutting or combining them
- If a feature only matters to power users, say so — it might belong in a details page, not the pricing tableThe best pricing pages we see pair clean tables with descriptive tooltips. If your features are just checkmarks, visitors can't tell why the more expensive plan is worth it. That's a pricing psychology failure, not a design one.
Write pricing FAQ copy that handles real objections
The FAQ section on a pricing page isn't really a FAQ. It's an objection-handling section disguised as helpful answers. Most pricing FAQs waste space on questions nobody actually asks ("What payment methods do you accept?"). This prompt generates FAQs that address the real reasons people don't buy.
I need to write the FAQ section for my pricing page.
Product: [name + one sentence description]
Price range: [e.g., "$29/mo to $199/mo"]
Common sales objections we hear:
1. [e.g., "Is it worth it when we already use spreadsheets?"]
2. [e.g., "What if we outgrow the plan?"]
3. [e.g., "Can we get a refund if it doesn't work?"]
4. [e.g., "Why is it more expensive than [competitor]?"]
Our actual answers to those objections: [paste real answers your sales team gives, even if they're rough]
Free trial or money-back guarantee details: [what you offer]
Billing details: [annual/monthly, when charged, etc.]
Write 6 FAQ items. Rules:
- First 3-4 should address real buying objections disguised as questions (e.g., "What happens if I need more than 10 users?" not "How do I add users?")
- Last 2 should cover logistics (billing, cancellation, switching plans) — keep these short
- Answers should be 2-3 sentences max — direct, not defensive
- Never start an answer with "Great question!" or "Absolutely!" — just answer
- If the answer involves a comparison to competitors, be specific without being aggressive
- Include one FAQ that proactively addresses the most common reason people DON'T buy
- Tone: confident, transparent, slightly casualA strong pricing FAQ does more conversion work than most people realize. It catches visitors who are 80% convinced but have one lingering doubt. If you're not sure what objections to address, run your page through roast.page — the analysis will flag gaps in your objection handling.
Frame annual vs monthly pricing without being manipulative
Every SaaS wants visitors to pick annual billing. The question is how to present it without the dark-pattern energy of fake "savings" badges and crossed-out prices. This prompt generates framing copy that nudges annual plans through honest value communication.
I need copy for the annual vs monthly toggle on my pricing page.
Monthly price: $[X]/mo
Annual price: $[Y]/mo (billed annually at $[Y*12])
The actual savings: [calculate the percentage or dollar amount]
Product: [what you sell]
Audience: [who buys it — e.g., "startup founders, marketing teams"]
Generate copy for these elements:
1. TOGGLE LABELS: What the two options say (not just "Monthly / Annual" — something that communicates the value difference)
2. SAVINGS BADGE: A short label next to the annual option (not just "Save 20%" — something more specific or compelling)
3. NUDGE TEXT: One sentence below the toggle explaining why annual makes sense (without pressuring)
4. MONTHLY REASSURANCE: One sentence for visitors who choose monthly, so they don't feel like they're making a bad choice
Rules:
- Do NOT use fake urgency ("Limited time offer!")
- Do NOT use manipulative anchoring (showing an inflated "original price" that was never real)
- The annual nudge should reference a real benefit: commitment to the workflow, budget predictability, or the actual dollar amount saved over the year
- The monthly option should still feel like a valid choice — some visitors need monthly, and shaming them loses trust
- If the savings are small (under 15%), acknowledge that — don't oversell a minor discount
- Write 3 variations of each element so I can mix and matchWrite the enterprise / custom pricing section
The "Contact Sales" tier is where most pricing pages go to die. A vague box with "Custom pricing" and a form link tells enterprise buyers nothing — and they're the highest-value visitors on the page. This prompt generates enterprise sections that qualify and convert.
I need to write the enterprise / custom pricing section of my pricing page.
Product: [name + what it does]
What "enterprise" means for us: [what enterprise customers actually need — e.g., "SSO, audit logs, dedicated support, custom contracts"]
Typical enterprise deal size: [rough range, so the AI understands the audience]
Enterprise buyer persona: [who makes the decision — e.g., "VP of Engineering who needs SOC 2 compliance"]
Current enterprise CTA: [what you have now — e.g., "Contact Sales"]
Write:
1. SECTION HEADLINE: Something better than "Enterprise" (reference what enterprise customers get, not just their company size)
2. SUBHEADLINE: One sentence that speaks to the enterprise buyer's specific needs
3. FEATURE LIST: 4-6 enterprise-specific features, each with a one-line description that explains why it matters (not just "SSO" but what SSO means for their team)
4. SOCIAL PROOF LINE: A template for displaying enterprise logos or stats (e.g., "Trusted by X teams at companies like ___")
5. CTA BUTTON + SUPPORTING TEXT: A CTA that's more specific than "Contact Sales" and a line underneath that sets expectations (e.g., "30-minute call, no commitment")
Rules:
- Speak to the enterprise buyer's concerns: security, compliance, support SLAs, team management
- Don't make enterprise feel like "the expensive option" — make it feel like "the option built for your requirements"
- The CTA should tell them what the next step actually looks like
- If you offer a free pilot or POC, mention it — enterprise buyers want to try before committing six figures
- Avoid vague phrases like "tailored solutions" or "bespoke offerings" — be specific about what they getEnterprise sections that spell out exactly what's included convert better than mystery boxes. If you're unsure how your current pricing page stacks up, analyze it with our pricing page tool to see where enterprise visitors might be dropping off.