OctiAI

Categories

One-shot B2B Landing Page Prompt — 6-Section Markdown Template

Deterministic prompt that converts ICP + offer + proof into a paste-ready, conversion-focused 6-block landing page with a single CTA and linked proof.

What You'll Get

How to Use

Format proof points for fast mapping

Provide proof as concise bullets in the required 'type — short source' format (e.g., 'case study — ACME Corp, CFO'). Prefer measurable stats when available. If proof is weak, label it 'anecdotal' and add a quick credibility fix (short pilot, audit, or customer quote).

Works Best With

Use when you need single-shot, paste-ready landing pages for high-intent B2B buyers

Prompt Template


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

## Goal
- Produce a high-conversion B2B landing page (deterministic 6-section block map) that makes the reader complete a single primary conversion action defined by the CTA.

## Inputs
Provide the following inputs inside the prompt block below. If any required input is missing or vague, the assistant must ask up to three targeted clarifying questions before producing the landing page.

- Offer: {{offer}}
- ICP (ideal customer profile): {{icp}}
- Funnel stage (choose one: awareness | consideration | decision): {{funnel_stage}}
- Channel (landing page, not an email/DM/ad): {{channel}}
- Primary benefit (single concise outcome the ICP cares about): {{primary_benefit}}
- Proof points (enter as a bullet list; each item is "type — short source"): 
  {{proof_points}}
- Objections (enter as a bullet list of top 3 buyer objections): 
  {{objections}}
- Primary CTA (single action phrase, e.g., "Start trial", "Request demo"): {{cta}}

## Prompt
Using the exact inputs above, produce a single, ready-to-paste Markdown landing page block map with the sections and elements listed in the Output Format. Follow these instructions precisely:

1. Begin by restating the single primary conversion objective in one sentence (e.g., "Goal: Get a {{icp}} to {{cta}}"). Include the funnel_stage and the primary conversion metric to optimize (e.g., sign-ups, demo requests, leads).
2. Output only the landing page content in Markdown with the exact section headings and order required by Output Format. Do not add extra top-level sections.
3. For each block, deliver the exact sub-elements specified in Output Format. Be specific: use concrete claims tied to the provided proof_points and map each claim to a proof source. If proof is weak, mark the claim as "anecdotal" and propose one quick credibility fix (e.g., add a measurable KPI, audit, or quote).
4. Keep copy concise and scannable: headlines ≤ 12 words, subheads ≤ 20 words, benefit bullets 10-14 words each. Provide a single on-page CTA ({{cta}}) and place it only in the Hero and the CTA block.
5. Address each objection from {{objections}} with a short counter (one sentence) and a linked proof point reference.
6. Include suggested microcopy (button text, form label, privacy note), recommended visual type for each block (hero image, demo screenshot, chart, logo strip, customer photo), and recommended primary social proof element (case study, testimonial, stat) prioritized from {{proof_points}}.
7. Produce 6 variant headline/hooks (tone variants: factual, aspirational, contrarian, urgency, pain-led, proof-led). Each variant must include a 5-8 word hook line and a 12-18 word subhead tailored to {{icp}} and {{primary_benefit}}.
8. Make outcomes measurable and aligned to {{funnel_stage}}: for the Hero block state one realistic success metric to track (e.g., "Demo requests/week", "MQL conversion") and a conservative target uplift phrased as a qualitative projection (e.g., "expect measurable lift within X weeks" only if supported by provided proof; otherwise state "requires data").
9. If any input is ambiguous, ask up to three specific clarifying questions before producing the page; do not proceed until clarity is achieved.
10. Follow Guardrails exactly.

Use this exact input block when you run:
Offer: {{offer}}
ICP: {{icp}}
Funnel stage: {{funnel_stage}}
Channel: {{channel}}
Primary benefit: {{primary_benefit}}
Proof points:
{{proof_points}}
Objections:
{{objections}}
Primary CTA: {{cta}}

## Output Format
Produce the landing page as Markdown using the exact headings and order below. Use bold for microcopy labels (e.g., **Button:**). All sections must be present and populated; if any required evidence is missing, include a short "Assumptions" block immediately after Goal listing only when you previously asked clarifying questions or when inputs were incomplete.

- Goal (one sentence)
- HERO
  - Headline (≤12 words)
  - Subhead (≤20 words)
  - One-sentence explain-the-mechanism line (what unique mechanism delivers the benefit)
  - 3 benefit bullets (10-14 words each)
  - Primary CTA button text (**Button:** {{cta}})
  - Suggested visual (one short phrase)
  - Primary conversion metric to track and realistic qualitative target
- BENEFITS (3 blocks)
  - Each block: Title (≤6 words); 3 bullets linking claim → proof point (one-line each)
  - Suggested supporting visual for each block
- PROOF
  - Prioritized proof elements extracted from {{proof_points}} in this order: case study/stat > logo > testimonial > data point > third-party mention
  - For each proof element include: one-line claim, source citation, micro-excerpt to use on page (≤25 words)
- OBJECTIONS
  - List each objection from {{objections}} and provide a one-sentence rebuttal plus the linked proof_point reference
  - Include an optional micro-FAQ (1-2 Qs) addressing the strongest objection
- CTA BLOCK
  - Headline for CTA section (≤10 words)
  - One reinforcing subhead (≤18 words)
  - Primary CTA button (**Button:** {{cta}}) and two microcopy lines: form label and privacy note
  - Conversion friction checklist (3 items to remove friction)
- FAQ
  - 4 concise Q&A pairs addressing product fit, implementation, pricing signal, and guarantee/risk reversal language (no absolute guarantees)
- VARIANT HOOKS
  - 6 headline+subhead pairs as specified in Prompt step 7

Only one primary CTA must appear (the {{cta}}). If any input required earlier was omitted, include an "Assumptions" block immediately after Goal listing stating what was assumed (max 3 bullets).

## Guardrails
- Ban cliches, hype phrases, and vague superlatives (no "best-in-class", "industry-leading", "world-class").
- Claim hygiene: do not invent metrics or outcomes. If a numeric claim is used, it must be traceable to an item in {{proof_points}} or labeled "estimate" and show the assumption behind it.
- No multiple CTAs: only the single {{cta}} allowed on the page.
- Avoid feature dumps: every benefit must tie to a customer outcome and a proof point.
- Tone: professional, decisive, and concise; match vocabulary to {{icp}}.
- Compliance-safe phrasing: no health/legal/financial guarantees unless explicitly supported in {{proof_points}}.
- If proof is insufficient for a promised outcome, flag it under PROOF and propose a low-effort validation step (e.g., short pilot, A/B test, quoted case study interview).

## Examples
Headline example (style):
- Headline: Cut onboarding time in half for enterprise IT teams
- Subhead: Replace manual handoffs with one platform that centralizes workflows and reporting

Proof block example (style):
- Claim: Centralized workflow reduced handoffs for a midsize telco
- Source: Customer interview — Customer Name, Role
- Micro-excerpt: "We reduced handoffs and sped up launches without adding headcount" (use as testimonial line)

Now produce the landing page following the Output Format using the inputs supplied above.

Variables

Usage Notes

Not for

Do not include

One-shot B2B Landing Page Prompt — 6-Section Markdown Template

Turn constrained inputs (ICP, offer, funnel stage, proof points, objections, CTA) into a deterministic 6-section Markdown landing page that enforces a single primary CTA, maps each claim to proof, and supplies microcopy, visuals, and six headline variants.

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.

What you'll get

Output format

Markdown

Best used when

Avoid when

Sign in to save, like, or rate this prompt.

Made for

What to fill in

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

Offer

Provide the key details needed for this variable.

Icp

Provide the key details needed for this variable.

Funnel Stage

Provide the key details needed for this variable.

Channel

Provide the key details needed for this variable.

Primary Benefit

Provide the key details needed for this variable.

Proof Points

Provide the key details needed for this variable.

Objections

Provide the key details needed for this variable.

Cta

Provide the key details needed for this variable.

Rules

Canonical Examples

Input: Offer: 8-week SaaS onboarding audit and playbook; ICP: B2B SaaS Head of Customer Success at Series B; Funnel stage: decision; Channel: landing page; Primary benefit: reduce time-to-value for new enterprise customers; Proof points: - case study — BrightApps (reduced onboarding time by 32% in 8 weeks), - testimonial — Head of CS, BrightApps, - audit report — internal benchmark across 10 customers; Objections: - Too disruptive to current process, - Requires engineering resources, - Unclear ROI for pilots; CTA: Request demo

Loading result...

Failed to load output.


Goal: Get a B2B Saaas Head of Customer Success to Request demo — decision stage, optimize for demo requests.

HERO
- Headline: Cut onboarding time for enterprise customers
- Subhead: Eight-week audits and playbooks that reduce time-to-value for Series B SaaS teams
- One-sentence mechanism: We run a targeted audit, prioritize friction points, and deliver an implementable playbook for ops-led rollouts.
- Benefit bullets: ...

Why it works: This output enforces a single conversion goal, ties each claim directly to provided proof, and yields a deterministic 6-section block map optimized for decision-stage buyers who need quick validation and a clear next step.

Input: Offer: 14-day sales outreach sequence templates + CRO review; ICP: Revenue ops manager at mid-market B2B companies; Funnel stage: consideration; Channel: landing page; Primary benefit: increase qualified demo replies from outbound; Proof points: - stat — tested on 6 clients averaged 18% reply rate increase (internal A/B), - testimonial — VP Sales, SlateTech, - sample script — anonymized sequence; Objections: - Generic templates won't fit our ICP, - Legal/compliance concerns with messaging, - Hard to measure impact quickly; CTA: Request demo

Loading result...

Failed to load output.


Goal: Get a Revenue ops manager to Request demo — consideration stage, optimize for demo requests.

HERO
- Headline: Get higher demo replies from outbound
- Subhead: 14-day tested outreach sequences plus a CRO review to lift reply rates
- One-sentence mechanism: We deliver sequences plus a CRO-synced review that aligns messaging with buyer triggers.
- Benefit bullets: ...

Why it works: Provides a rigid, paste-ready landing page that maps each benefit to supplied proof (stat, testimonial, sample script) and supplies a single CTA for conversion-stage buyers evaluating outbound improvements.

Works Best With

Use when you need single-shot, paste-ready landing pages for high-intent B2B buyers