0
Pricing page copy that handles objections honestly
⁂auto-checked, 23 hours oldAauraNovice
The prompt
Write pricing page copy for product_name with tiers: tier_names_and_prices.
What makes people hesitate at each tier (be honest, tell me the real objection, not a soft version): real_objections_per_tier
Do this:
1. For each tier, write a one-line description that states who it's actually for (a specific customer profile, not 'perfect for growing teams').
2. Address the real objection for each tier directly in the copy near that tier, don't bury objection-handling in a separate FAQ if it's decision-critical.
3. Write the feature comparison so the differences between tiers are genuinely clear, a prospect should be able to self-select correctly without contacting sales, unless that's actually the intended friction point (tell me if it is).
4. If there's a 'most popular' or recommended tier, justify why in copy terms, not just a badge with no reasoning given.
5. Write one FAQ answer addressing the single most common pricing pushback you'd expect (based on the objections I gave you), answered directly and specifically, not deflected with 'reach out to our team.'
Avoid vague tier names like 'Pro' with no differentiation logic explained anywhere on the page.
Where it has been run
| Model | Version | People | Broke | Auto | Last |
|---|---|---|---|---|---|
| Claude | Haiku 4.5 | 0 | 0 | 1/1 | 23 hours ago |
Example output
Tier descriptions: Starter, 'for solo founders testing if this fits before committing budget'; Team, 'for teams of 5-20 who need shared visibility, not just personal tracking'; Enterprise, 'for orgs needing SSO and dedicated support, priced by conversation.' Objection handling: Team tier's real objection (per your input) is 'seems expensive per seat compared to Starter,' addressed directly with a line showing the per-seat cost drops as team size grows, placed right under the price, not hidden in FAQ. Feature comparison table restructured so the Team tier's unique value (shared dashboards) is the first row, not buried alphabetically. 'Most popular' badge on Team justified with 'because most teams outgrow solo tracking within the first month,' a stated reason, not just a badge. FAQ answer written addressing 'why isn't there a cheaper multi-seat option,' answered directly with the actual tradeoff reasoning rather than deflecting to sales contact.
0 comments
Sign in to comment or report what this prompt did for you.
Sign inNo comments yet. Run the prompt and report what you got.