One-shot Pricing Page Prompt â€” Paste-ready Template

Deterministic one-shot prompt that returns a production-ready pricing page in Markdown: hero, 2-4 tiers, anchor math, risk reversal, FAQs, micro-CTAs, and an A/B test plan for r...

What You'll Get

Complete Markdown pricing page: hero, pricing overview, tiers, anchor rationale, risk reversal, objection responses, FAQs, micro-CTAs, measurable test plan, and content export notes.

2-4 pricing tiers with monthly and annual prices, % savings math, six outcome-focused bullets per tier, 'Best for' fit, caveats, and clear upgrade triggers.

Anchor tier recommendation with defensible pricing rationale and a savings math line.

One compliant guarantee or trial with precise terms (duration and refund conditions).

Three objection micro-responses that reference supplied proof points where available.

Six FAQs covering pricing, billing, scale, ROI timeline, cancellation, and support.

Three micro-CTAs tied to the single primary CTA with placement tags (hero, tier column, FAQ end).

Two A/B test ideas with expected KPI direction and sample-size guidance for practical implementation.

CMS-ready copy snippets (meta title, meta description, H1, CTA text) and UX notes for each block.

How to Use

1Provide all required inputs: offer_description, icp_and_problem, proof_points (bulleted with source tags), objections, funnel_stage, channel, and cta.

2Run the template in ChatGPT and paste your inputs into the prompt blueprint; the prompt returns an Assumptions block if any input is missingâ€”choose an option before continuing.

3Review generated prices, legal language, and proof references; swap in exact numeric pricing if you prefer specific numbers.

4Copy the Markdown output directly into your CMS; use the UX notes to map visual treatments and CTAs.

5Run the recommended A/B tests and track the primary KPI for the funnel stage stated in your inputs.

Provide concise, source-tagged proof and one clear CTA

Supply 3-5 short proof points with exact source tags (e.g., [Customer case], [Survey]), a single primary CTA label and action, and a crisp ICP statement. The cleaner and more specific your inputs, the more paste-ready and conversion-focused the output will be, and the fewer review cycles you'll need.

Works Best With

Works best with concrete, constrained inputs:

Clear ICP and single primary problem statement (who and what breaks today)

Exact CTA label and funnel stage so copy never introduces competing CTAs

Offer description that includes primary mechanism (how value is delivered)

Bulletized proof points with source tags (e.g., [Customer case], [Survey])

A short list of main objections to address directly

A target channel to tune length, tone, and visual UX notes

Prompt Template


# Revenue Copy Prompt Blueprint (Conversion & Sales) (use EXACT section order)

## Goal
- Drive visitors at the {{funnel_stage}} to complete the single primary action: **click the CTA {{cta}}** (e.g., purchase, start trial, book demo). Output must be optimized to increase that action rate and provide 1 clear A/B test suggestion tied to a measurable KPI.

## Inputs
- Offer + primary benefit: {{offer_description}}
- Ideal customer profile and core problem: {{icp_and_problem}}
- Primary proof assets (bulleted list of verified proof): {{proof_points}}
- Main buyer objections to address (bulleted): {{objections}}
- Target channel and placement constraints: {{channel}}
- Primary CTA label and action: {{cta}}

If any of the above inputs are missing or ambiguous, first return an "Assumptions" block naming exactly which inputs are absent and propose 2 concise options for each missing input; wait for selection before continuing.

## Prompt
You are a senior conversion copywriter and pricing strategist. Using the inputs above, produce a complete, production-ready pricing page structure and copy. Follow these rules exactly and output sections in the strict order requested in "Output Format."

Instructions (apply precisely):
1. Tone and channel: write copy optimized for {{channel}}. Use a confident, clear, non-technical tone targeted at {{icp_and_problem}}. Keep each content block scannable (short lines, 10-18 words per line equivalent).
2. Single primary CTA: use exactly one CTA label and action: {{cta}}. Show it prominently in the hero and at the end; do not add competing CTAs.
3. Pricing tiers: produce 2-4 tiers. For every tier follow this template verbatim:
   - Tier name
   - Price anchor and billing cadence (show monthly and annual with % savings)
   - 6 concise bullets (benefit-first, outcome-focused; avoid feature dumping)
   - "Best for" one-line audience fit
   - Transparent caveats (one sentence: who should not pick this tier)
   - Clear upgrade triggers (what event or usage should prompt upgrade)
4. Anchor & discounts: include an anchor tier recommendation and a clear savings math line (e.g., "Save 20% = $X/month"). Make the anchor psychologically defensible.
5. Risk reversal: include one compliant guarantee or trial with precise terms (duration, refund conditions). Do not promise unrealistic results or fabricate case data.
6. Objection handling: synthesize {{objections}} into 3 concise objection-response micro-copies (one-line objection + 1-sentence factual response referencing {{proof_points}}).
7. FAQs: write 6 FAQs that preempt pricing, billing, scale, ROI timeline, cancellation, and support. Answers must be specific, conservative, and verifiable.
8. Micro-CTAs: produce 3 micro-CTAs (single-line) that lead to the primary CTA (not alternative outcomes); label each with intended placement (hero, tier column, FAQ end).
9. Compliance & claim hygiene: cite no fabricated metrics. If you reference a metric from {{proof_points}} mirror the exact phrasing given. If no numeric proof exists, use "customer-reported" or "client-reported" prefacing.
10. Measurable outcomes & test plan: recommend 2 testable changes (e.g., price anchor, CTA text) with expected KPI lift and a simple A/B test setup (sample size guidance relative to conversion goal).
11. Format rules: use headings and subheadings; keep the final copy paste-ready for a CMS. For every block include a one-line UX note (how it should appear visually or interact).

Embed these inputs where relevant: {{offer_description}}, {{icp_and_problem}}, {{proof_points}}, {{objections}}, {{funnel_stage}}, {{channel}}, {{cta}}.

## Output Format
Produce the following sections in this exact order. Use Markdown headings and bold the most important lines. Do not add any sections beyond these.

1. Page Title / Hero
   - Headline (1 strong sentence)
   - Subhead (1-2 lines)
   - Single CTA (button text = {{cta}}) and UX note
   - 2 supporting proof lines (pull from {{proof_points}})

2. Pricing Overview (1-paragraph summary tying price to outcome)

3. Tiers (repeat block per tier following the exact sub-structure)
   - Tier name
   - Price (monthly / annual + savings math)
   - 6 bullets (benefit-first)
   - Best for
   - Caveats
   - Upgrade triggers
   - UX note

4. Anchor & Savings rationale
   - Explain anchor choice and how it drives conversion (one paragraph)
   - Savings math line

5. Risk Reversal
   - Guarantee/trial text with precise terms
   - UX note

6. Objection Micro-Responses (3 items)
   - Objection + 1-sentence response (reference proof where possible)

7. FAQs (6 Q&A pairs)

8. Micro-CTAs (3 lines with placement tags)

9. Measurable Outcomes & Test Plan
   - Primary KPI for {{funnel_stage}} (name and numeric target format)
   - Two A/B test ideas with expected KPI lift and sample-size guidance
   - Quick implementation notes

10. Content Export Notes
   - Short copy snippets for CMS fields (meta title, meta description, H1, CTA alt text)
   - Character limits for ads/headers if used on {{channel}}

11. Assumptions (ONLY include this section if any required input was missing; list assumptions made and invite corrections)

Extra formatting rules:
- Bold only key lines (headline, CTA, tier names).
- Bullets must be succinct; no paragraphs longer than 3 sentences.
- Where you use a proof claim, prefix with source tag in brackets exactly as provided in {{proof_points}} (e.g., [Customer survey]).

## Guardrails
- No hypey generic phrases (ban: "best-in-class", "industry-leading", "game-changing").
- No fabricated results or guarantees. If a metric is unknown, use conservative language: "client-reported", "typical customers see", or "early testers reported".
- One primary CTA only: {{cta}} â€” place in hero and the final CTA area only; micro-CTAs must direct to that CTA.
- Tier bullets must focus on outcomes, not internal features.
- Avoid more than four pricing tiers.
- Do not use more than 2 numeric claims per tier unless supplied in {{proof_points}}.
- Respect channel constraints for length and compliance as per {{channel}}.

## Examples
Headline example (style):
- **Save 10 hours/week managing payroll without hiring extra staff**

Proof block example (style):
- [Customer case] "Acme Co reduced month-end payroll time by 40% in 6 weeks" â€” used as a trust line under the hero; include exact source tag from inputs

Use the prompt above to generate a production-ready pricing page copy file ready for deployment.

Variables

Usage Notes

Not for

â€¢ Enterprise RFPs or multi-line contract negotiations requiring custom quotes and legal terms

â€¢ Regulated claims in medical, legal, or financial verticals without compliance sign-off

â€¢ Products requiring highly complex usage-based billing with dozens of metering dimensions

Do not include

â€¢ Multiple primary CTAs or competing conversion goals

â€¢ Fabricated case studies, invented metrics, or unverifiable percentages

â€¢ Long feature-dump lists instead of outcome-first bullets

â€¢ More than four pricing tiers or non-actionable upgrade triggers

One-shot Pricing Page Prompt â€” Paste-ready Template

Generate a conversion-optimized, paste-ready pricing page structure and copy that enforces a single CTA, clear mechanism, defensible anchor, and measurable A/B tests.

Turn this into a working asset in minutes.

Import into Workspace to auto-fill variables, adapt output style, and iterate with OctiAI's prompt editor.

Auto-fill & personalize from your inputs

AI-assisted edits: tone, structure, constraints

Attach context so outputs stay consistent

Iterate and save versions

What you'll get

Output format

Markdown

Best used when

When working on template or detailed.

Avoid when

Enterprise RFPs or multi-line contract negotiations requiring custom quotes and legal terms

Made for

What to fill in

Use the guidance below to complete each placeholder with the right level of detail.

Funnel Stage