One-shot Case Study Blueprint â€” Revenue Copy Template

Deterministic Markdown template that turns ICP, offer, and proof into a paste-ready case study anchored to one hero metric and a single CTA.

What You'll Get

Paste-ready Markdown case study blueprint in the exact output schema (headline, deck, executive summary, client snapshot, problem, constraints, approach, timeline, hero metric, supporting metrics, proof block, quotes, visual callouts, objections handling, lessons, and single CTA).

Built-in input validation: the prompt returns targeted clarifying questions if required inputs (especially the hero metric or proof points) are missing or ambiguous.

Verification flags for every proof item (VERIFIED / UNVERIFIED) and an Assumptions block listing what needs source verification.

Strict single-CTA enforcement and quote-permission markers to avoid unintended CTAs or unauthorized quotes.

Channel-aware copy cues and three exact visual callout captions (metric card, timeline, before/after) ready for designers.

How to Use

1Prepare the required inputs exactly as short paragraphs or bullet lists: Offer; Target ICP; Primary benefit; Hero metric (format: 'metric â€” baseline â†’ result in [timeframe] â€” attribution'); Proof points; Top objections; Primary CTA (exact text); Channel & funnel stage.

2Run the one-shot prompt in ChatGPT with those inputs. If the assistant asks clarifying questions, answer them before expecting the final blueprint.

3Paste the returned Markdown directly into your CMS, landing page builder, sales one-pager, or creative brief. Use the Visual callouts verbatim for design assets.

4If any proof items are marked UNVERIFIED, attach/verifiy source files (analytics export, screenshot, signed quote permission) and rerun to convert flags to VERIFIED.

Normalize the hero metric and attach raw proof

Before running, format the hero metric exactly as 'metric â€” baseline â†’ result in [timeframe] â€” attribution' and provide raw proof (analytics export, screenshot, or signed quote permission). Clear, sourceable proof prevents UNVERIFIED labels and reduces review cycles.

Works Best With

When to use this Revenue Copy Prompt Blueprint

Mid-market to enterprise B2B offers where one measurable outcome can be tracked (conversions, meetings, retention).

Inputs that include one explicit hero metric (metric â€” baseline â†’ result in timeframe â€” attribution) and verifiable proof sources.

Use cases: landing pages, sales one-pagers, MOFU landing copy, case-study PDFs, and sales enablement decks.

Avoid using if metrics or proof are missing â€” the prompt will ask clarifying questions instead of producing unverified claims.

Prompt Template


# Revenue Copy Prompt Blueprint (Conversion & Sales)

## Goal
- Produce a web-ready, conversion-focused case study blueprint that persuades the target reader to take a single next step: **{{primary_cta}}**. The blueprint must make the reader trust the offer by showing a clear problem â†’ mechanism â†’ outcome narrative anchored to one measurable hero metric.

## Inputs
Provide the following inputs (each as a single short paragraph or bullet list). If any required input is missing or vague, the prompt below will ask targeted clarifying questions before generating the case study.

- Offer: {{offer}}
- Target ICP / client profile: {{target_icp}}
- Primary benefit / core outcome promised: {{primary_benefit}}
- Hero metric (one measurable result formatted as "metric â€” change â€” timeframe â€” attribution"): {{hero_metric}}
- Proof points (bullet list of raw assets: metrics, quotes, screenshots, baseline data): {{proof_points}}
- Top objections to address (bullet list): {{objections}}
- Primary CTA (exact text + desired next step): {{primary_cta}}
- Channel & funnel stage (e.g., Landing page / Sales enablement / Email TOFU-MOFU): {{channel_and_funnel}}

## Prompt
You are an expert B2B case-study writer and sales-enablement copywriter. Using the inputs exactly as provided above, produce a deterministic, publication-ready case study blueprint in the Output Format below. Follow these rules:

1. If any required input is missing, ambiguous, or unspecific (e.g., "improved performance" without a metric), do not generate the case study. Instead, return up to 6 precise clarifying questions that will produce the missing data. Wait for answers before continuing.

2. Always anchor the story to **one explicit hero metric** using this phrasing: "Hero metric â€” baseline â†’ result in [timeframe] â€” attribution to action." Use the provided {{hero_metric}} value verbatim unless you ask for clarification.

3. Deliver concrete claims only where proof exists in {{proof_points}}. If a proof point lacks a numeric value, label it as "anecdotal" and flag it for verification.

4. Include a single primary CTA exactly as {{primary_cta}}. Do not add alternate CTAs.

5. For each quote used, include the quote text, the quoted person role/title, and whether permission to publish is confirmed. If permission is unknown, mark "permission: unknown".

6. Produce all sections in the exact order and formats specified in Output Format. Use plain, concise sentences, bulleted lists for quick scan, and one short headline (8-12 words) that captures the outcome.

7. Tone: factual, benefit-driven, credible. Avoid marketing hyperbole and clichÃ©d phrases.

8. Length targets per section (hard guidance):
   - Headline: 8-12 words
   - Subtitle / Deck: 12-18 words
   - Executive summary: 2-3 short sentences
   - Narrative sections (Problem / Constraints / Approach / Results / Lessons): 2-4 bullets or 1-3 short paragraphs each
   - Visual callouts: 3 labeled items (metric card, timeline, before/after visual) with exact copy for captions
   - Quote(s): up to 3 short quotes (10-25 words each)
   - Proof block: 4-6 itemized evidence entries with source and verification status
   - CTA: single line matching {{primary_cta}}

8. Compliance: flag any claim that cannot be sourced to an item in {{proof_points}} as "UNVERIFIED". Do not invent percentages, dollar amounts, or timelines.

Now generate the case study blueprint only after verifying all inputs are present and clear.

## Output Format
Produce the case study blueprint with these headings and in this exact order. Use bold or inline code to highlight field labels where helpful.

1. Headline (8-12 words)
2. Subtitle / Deck (12-18 words)
3. Executive summary (2-3 sentences; include hero metric)
4. Client snapshot
   - Client type: short phrase from {{target_icp}}
   - Engagement length
   - Scope of work (1 line)
5. Problem (3 bullets: root cause, business impact, measurable pain)
6. Constraints & environment (2-4 bullets: tech, timeline, budget, stakeholder limits)
7. Unique mechanism / approach (3 bullets: what was done, why itâ€™s distinctive, how it maps to the hero metric)
8. Implementation timeline (short timeline with 3 milestones and dates/durations)
9. Results â€” Hero metric section (single line in the pattern: Hero metric â€” baseline â†’ result in [timeframe] â€” attribution)
10. Results â€” Supporting metrics (3 bullets with metric, baseline, result, and verification source)
11. Proof block (4-6 items). Each item: short label, numeric claim if available, source, verification status (VERIFIED / UNVERIFIED), and attribution
12. Representative quotes (up to 3): quote text; name/role; permission status
13. Visual callouts (3 items): exact caption text for (a) Metric card, (b) Timeline graphic, (c) Before / After snapshot
14. Objection handling (map each {{objections}} entry to a 1-2 sentence rebuttal grounded in proof)
15. Lessons & next steps (3 bullets: what worked, what to monitor, recommended follow-up offer motion)
16. Single CTA (exact text as {{primary_cta}} and the clear next action the reader should take)
17. Assumptions (ONLY include this short block if any input was missing or any proof item was marked UNVERIFIED; list what was assumed and why)

Strict output requirements:
- Use Markdown headings for each numbered section above.
- Do not include marketing fluff or extra CTAs.
- Do not invent or approximate numeric results; mark any missing numbers UNVERIFIED and ask for sources.
- Keep the entire blueprint under ~700 words if all metrics are present; otherwise allow up to 1,000 words but prioritize scan-friendly bullets.

## Guardrails
- Ban: generic hype, superlatives without proof, "industry-leading", "best-in-class", and similar clichÃ©d phrases.
- Claim hygiene: never fabricate metrics, dates, or attribution. If evidence is missing, mark as UNVERIFIED and provide an explicit next-step to verify.
- Single-CTA rule: one primary CTA only. No embedded registration links, no multiple CTAs across the document.
- Quote protocol: include role/title and permission status. Do not display personal contact info.
- Attribution: every metric must cite a source from {{proof_points}} or be labeled UNVERIFIED.
- Tone and compliance: factual, third-person narrator for narrative sections; first-person quotes preserved verbatim.
- Reuse-safe: write copy suitable for website publication and for use in a sales one-pager without rewriting.

## Examples
Headline (style example): Transforming retention through a single measurable outcome

Proof block (style example):
- Hero metric: "Churn rate â€” 8.2% â†’ 5.1% in 90 days â€” attributed to targeted onboarding redesign" (source: internal analytics export; verification: VERIFIED)

Variables

Usage Notes

Not for

â€¢ Not for producing legally or medically regulated claims or compliance sign-off â€” consult legal/compliance for regulated statements.

â€¢ Not for final ad creatives that require channel-specific policy review (e.g., Facebook/TikTok ad compliance) without an additional compliance pass.

â€¢ Not for replacing original analyticsâ€”this template requires user-supplied metrics and proof sources.

Do not include

â€¢ Do not include invented or approximated numbers, multiple CTAs, marketing superlatives (e.g., 'industry-leading'), or personal contact details.

â€¢ Do not include claims that are not present in provided proof points; any such claims will be marked UNVERIFIED.

One-shot Case Study Blueprint â€” Revenue Copy Template

Generate a deterministic, publication-ready Markdown case study blueprint (headline, deck, exec summary, problem, constraints, approach, timeline, hero metric line, supporting metrics, proof block, quotes, visual callouts, objection map, lessons, single CTA) from constrained inputs.

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

Not for producing legally or medically regulated claims or compliance sign-off â€” consult legal/compliance for regulated statements.

Made for

What to fill in

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

Primary Cta