The Pricing Page Objection Pre-Empter: Turn Pricing-Tier Copy Into Pre-Answered Buyer Doubts
Why this prompt matters
Pricing pages are usually the last page a buyer reads before deciding to self-serve, book a call, or close the tab — and most of their hesitation never reaches sales because it happens silently, before any form gets filled out. Teams that treat pricing-page bounce as a design or headline problem keep rewriting the page's tone while a buyer is actually stuck on an unanswered 'does this tier include X' question that a single sentence could resolve. This prompt forces that distinction up front, so copy gets fixed where copy is the actual problem, instead of burning a sprint trying to write around a real packaging gap.
What we use it for
You just shipped a new pricing page, or haven't touched the current one in eight months, and you suspect buyers are bouncing at the pricing step — but your analytics only show that they left, never why. You run this before the next pricing review meeting, pasting in the live tier copy and whatever competitor pricing your sales team has gathered from call notes.
Prompt
Act as a senior conversion copywriter who has rewritten pricing pages for over 50 B2B SaaS companies and has reviewed post-purchase survey data on why buyers hesitate at the pricing stage.
Context:
- Our product: [ONE-SENTENCE PRODUCT DESCRIPTION]
- Our ideal customer profile: [ICP — ROLE, COMPANY SIZE, BUDGET AUTHORITY]
- Our current pricing page copy (all tiers): [PASTE FULL PRICING PAGE COPY, TIER NAMES, PRICES, AND FEATURE LISTS]
- Known competitor pricing pages for comparison (optional): [PASTE COMPETITOR TIER NAMES + PRICES + KEY FEATURES, OR WRITE 'NONE AVAILABLE']
- Average deal size and sales cycle length: [E.G., '$8,400 ACV, 34-DAY CYCLE']
Task:
For each pricing tier on our page, do the following in order:
1. Name the single most likely objection or doubt a buyer evaluating THAT SPECIFIC TIER will have before clicking 'Buy' or 'Talk to Sales' — be specific to the tier, not generic ('too expensive' is not specific enough; 'unclear if the included seats cover read-only viewers or only active editors' is specific).
2. State whether that objection can be resolved with better COPY (clarify, reframe, add proof) or whether it is actually a PACKAGING problem that copy cannot fix (the tier genuinely lacks something buyers at that price point need).
3. If it's a copy problem, write a short addition or edit to the tier's copy that pre-empts the objection before the buyer has to ask sales or churn silently.
4. If it's a packaging problem, do not attempt to paper over it with copy — flag it plainly so we know to escalate to product/pricing strategy instead.
Constraints:
- Do not invent features, limits, or pricing we did not provide.
- Do not use hype language ('revolutionary', 'game-changing') in any copy addition.
- Each copy addition must be under 40 words and must sound like it was written by the same team that wrote the rest of the page (match tone).
- If a tier has no real objection worth addressing, say so explicitly rather than inventing one.
- Do not address more than one objection per tier — pick the single highest-leverage one.
Output Format:
A table with one row per tier:
| Tier Name | Likely Buyer Objection | Copy or Packaging Problem? | Copy Addition (if applicable) | Escalate to Product? (Yes/No) |
After the table, add a 2-3 sentence summary flagging which tier is most at risk of silent drop-off and why.Result
| Tier Name | Likely Buyer Objection | Copy or Packaging Problem? | Copy Addition (if applicable) | Escalate to Product? |
|---|---|---|---|---|
| Starter ($49/mo) | Buyer can't tell if “3 sending domains” means 3 total, ever, or 3 active at once — they're mid-migration and may temporarily need a fourth. | Copy | Add: “Swap domains anytime at no cost — the limit is concurrent, not lifetime.” | No |
| Growth ($149/mo) | Buyer assumes “unlimited alerts” also means unlimited recipients, but alert routing is capped at 5 team members — a limit the page never discloses. | Packaging — the cap itself needs disclosure, and 5 seats may be too low for this ICP's typical marketing-plus-IT split | — | Yes — flag the seat cap for this ICP band before next pricing review |
| Scale (custom) | “Custom pricing” with no anchor number reads as deliberately high, so qualified buyers self-select out before ever requesting a quote. | Copy | Add a visible anchor: “Most teams land between $650–$900/mo.” | No |
Summary: Growth is the highest-risk tier for this ICP — the 5-person alert-routing cap is likely to surface mid-trial for a 50–200 person company with separate marketing and IT teams, and no amount of rewording fixes a hard seat limit. Starter and Scale are purely copy problems: Starter needs one line clarifying that the domain limit is concurrent, and Scale needs a price anchor so qualified buyers don't vanish before anyone on the sales team ever hears from them.
Most pricing-page reviews ask one blunt question: does this convert? That's the wrong first question. A pricing page can read beautifully and still lose buyers silently, one tier at a time, because each tier carries its own unstated doubt — and no amount of general copy polish fixes a doubt the page never addresses.
This prompt forces a tier-by-tier pass instead of a page-wide one. Lumping every tier into a single “improve this pricing page” request produces generic output: vaguer headlines, more social proof, a bigger call-to-action button. None of that touches the actual reason a specific buyer closed the tab on a specific tier.
Why the structure works
The Role is deliberately narrow: a conversion copywriter who has reviewed post-purchase objection data, not a generic marketing assistant. That framing pulls the model toward specificity — “unclear if seats are per-editor or per-viewer” instead of “pricing is confusing.”
The Context block requires the actual tier copy, not a summary of it. Summarized pricing loses exactly the ambiguous wording that creates buyer doubt in the first place.
The Task does the real work by forcing a classification most teams skip: is this a copy problem or a packaging problem? Teams default to rewriting copy because that's the cheap, immediate lever — even when the real issue is that a tier is missing a feature buyers at that price point actually need. Separating the two stops a marketing team from quietly papering over a product gap with better adjectives.
The Constraints block does two jobs: it stops the model from inventing features that don't exist (a common failure mode when a prompt asks an LLM to “improve” something), and it caps each copy addition at 40 words so the output stays usable as a drop-in edit rather than a rewrite of the whole page.
What makes the output format effective
The table format forces one objection per tier instead of a scattershot list of five vague concerns. One sharp objection per tier is more actionable than five soft ones — it tells you exactly where to spend the next twenty minutes, and the “Escalate to Product?” column means a packaging problem gets routed to the team that can actually fix it, instead of sitting in a copy doc forever.
Run this after any pricing change, and again anytime a tier's conversion rate drops without an obvious cause — the page didn't change, but the market's read of your packaging may have.