Write pricing page copy that preempts sticker shock
Writes a full pricing page — headline, per-plan copy with honest 'built for' descriptors, anchoring, a cost-context block, pricing FAQs, and a reassurance strip — engineered to give the number context before it lands. It also flags when the pricing structure itself, not the copy, is what's generating the shock.
You are a pricing page specialist, and you know the pricing page is where trust either compounds or collapses. Buyers arrive braced for tricks — hidden fees, 'contact us' walls, plans engineered to force upgrades. Sticker shock isn't caused by the number; it's caused by the number arriving without context. Your job is to build the context before the number lands. Write complete pricing page copy: 1. Page headline and subhead — frame value or outcome, not 'Simple, transparent pricing' (everyone says it; nobody believes it). 2. Per-plan copy: plan name, a one-line 'built for' descriptor naming who it fits, the price with billing terms stated plainly, and 5-7 capability bullets phrased as outcomes where honest. 3. An anchoring element — order and framing that makes the recommended plan feel like the sane middle, without fake-crippling the cheap one. 4. A cost-context block — two or three sentences placing the price against the cost of the problem or the alternative (hiring, tools it replaces, hours saved). 5. Three to five pricing-specific FAQs: what happens at the usage limit, cancellation terms, implementation costs, price changes at renewal. 6. A below-the-fold reassurance strip: guarantee or trial terms, a security note if relevant, and one testimonial slot recommendation with the ideal quote theme. Rules: never hide a fee that appears later — surface it here. No asterisks doing dirty work. If a plan is genuinely 'contact us', say what drives custom pricing so the label isn't a wall. State renewal behavior honestly. Before you write anything, interview me. Ask me these questions ONE AT A TIME, waiting for my answer each time: 1. What are your plans and prices, including anything customers discover later — implementation, overages, add-ons? 2. Who is each plan actually for? 3. What does your product replace or reduce — tools, headcount, hours, risk? 4. What pricing objections do you hear most, verbatim if possible? 5. What guarantee, trial, or cancellation terms exist? Once you have my answers, write the page. If my pricing structure itself creates the shock (a 4x jump between tiers, a fee that surprises everyone), flag it — copy can frame a number, but it can't fix a broken ladder.
How to use it
- 1
Copy the prompt into Claude, ChatGPT, or any LLM.
- 2
Disclose everything in question 1, including the fees buyers currently discover late — hiding them from the model reproduces the problem.
- 3
Take question 4's objections from real calls and email threads, not guesses.
- 4
Implement the copy including the FAQ block near the plans, not buried at the page bottom.
- 5
If the model flags a structural pricing problem, take it to a pricing discussion before shipping new copy over it.
Best practices
The cost-context block does the anti-shock work — 'less than one mis-hire' or 'replaces three tools you're paying for now' recalibrates before the eye hits the number.
Write 'built for' lines that genuinely sort ('for teams sending under 10K emails/month'), because self-selection reduces both shock and churn.
Answer the renewal-price question on the page; it's the top unspoken fear of anyone burned by a SaaS renewal before.
Keep one plan honestly small instead of fake-crippled — buyers notice manipulative tiering and it poisons the whole page.
Example: what this looks like in practice
A founder of a $12K-30K/year contract-review platform watches demos go well and pricing page visits go nowhere. She discloses everything: three tiers, a $2,500 onboarding fee currently revealed on the sales call, and the most common objection — 'that's more than our paralegal costs for this'. The model writes the page with onboarding surfaced next to each price, a cost-context block comparing against 11 hours of attorney review per week, 'built for' lines that sort by contract volume, and an FAQ answering the paralegal comparison head-on with a speed-and-liability framing. It also flags the 3.5x jump between tiers one and two. Pricing-page-to-demo conversion improves within the month, and the onboarding fee stops appearing in lost-deal notes.
Best fit
This prompt is one gear in a bigger machine. We orchestrate 20+ tools into outbound systems our clients own — and guarantee the results.
Apply for a Pilot Spot → →Frequently asked questions
Build context before the number lands: a cost block comparing your price against the problem's cost or what it replaces, 'built for' descriptors so buyers self-select the right tier, and FAQs answering the fears people won't ask aloud — renewal increases, hidden fees, cancellation. Shock comes from a number without context, not from the number itself.
More sales copywriting & assets prompts
Generate an outcome-first value proposition buyers can repeat
Builds a complete value proposition system — primary line, three angle variations, a disqualifier, and channel-ready versions — instead of one throwaway tagline. The interview forces buyer, outcome, mechanism, and proof out of your head first, so the output is positioning you can defend, not word salad you'll rewrite next quarter.
Write a case study from a raw customer interview transcript
Turns a raw, rambling customer interview into a publish-ready case study — result-led headline, snapshot metrics box, four-part story, and verbatim pull quotes — while refusing to invent quotes or numbers. If the transcript is missing a strong metric, it tells you exactly what to ask the customer instead of papering over the gap.
Align your cold email and landing page so the click doesn't break the story
Audits your cold email and landing page side by side, finds where the story breaks between click and page, and fixes the cheaper side with minimum edits. The 'message spine' it outputs becomes a five-line contract both assets obey, so the next person who edits either one doesn't silently reintroduce the mismatch.