8â€‘Slide Sales Deck Talkâ€‘Track Generator (Oneâ€‘Shot Template)

One-shot prompt template that produces a ready-to-present, 8-slide sales deck narrative with 20-30s speaker notes, two headline variants, ROI lines, pricing summary, and A/B-fri...

What You'll Get

Complete 8-slide deck narrative in the required order: Title + 2 headline variants, Problem, Solution, Value Props (3), Proof/Customer Example, ROI (2 metrics), Pricing, Closing (primary CTA + 1 alternative).

Speaker notes (20-30 seconds / ~40-60 words) for every slide, ready for live delivery.

Two short headline variants (6-12 words) and a one-line tagline for the Title slide.

Expected outcome line per slide (the measurable prospect action the slide aims to trigger).

A/B-ready outputs: variant wording and branching reply prompts for follow-ups and testing.

Enforced input validation: the prompt requests up to 3 clarifying questions if required inputs (offer, ICP, core_problem, primary_benefit, proof_points, pricing_model, objections, ctas) are missing/ambiguous.

Assumptions block included only when numeric claims are estimated; every estimate is explicitly labeled and has a one-line assumption.

Single primary CTA enforced across the deck and one alternative CTA on the Closing slide.

How to Use

1Provide the required inputs exactly: offer, ICP, core_problem, primary_benefit, proof_points, pricing_model, objections, ctas.

2Run the one-shot prompt in ChatGPT. If clarifying questions are returned, answer up to 3 to avoid fabricated estimates.

3Copy the generated narrative into your slide tool (PowerPoint/Google Slides) and paste speaker notes into the notes field for each slide.

4Run 2-4 variants (change 1 input at a timeâ€”CTA wording, headline variant, or a value-prop metric) and A/B test subject lines and opening slides in outreach sequences.

5Before sending externally, replace any 'estimate' numbers with customer-provided metrics where possible and route pricing/contract language through procurement/legal if required.

Maximize conversion: swap in real customer metrics

Replace any estimated metrics with client-specific numbers before sending. Use one clear primary CTA and test the secondary CTA only in a separate variant. Keep personalization tokens (company name, competitor trigger, ARR band, headcount) visible so sellers can fill them quickly.

Works Best With

Works best when you can provide a few concrete baseline metrics

Average tickets per week or average proposal authoring hours

Typical first-response time or sales cycle length

Two sample proof points or at least one anonymized case/example

Prompt Template


# Revenue Copy Prompt Blueprint (Conversion & Sales)

## Goal
- Produce an 8-slide sales deck narrative that converts {{icp}} prospects at the {{funnel_stage}} stage into the next meeting or trial by clearly demonstrating the problem, solution, specific value, proof, ROI, and a single primary CTA.

## Inputs
- Required inputs embedded in the prompt below: {{offer}}, {{icp}}, {{core_problem}}, {{primary_benefit}}, {{proof_points}}, {{pricing_model}}, {{objections}}, {{ctas}}.  
- If any of these inputs are missing or ambiguous, the prompt must ask up to 3 targeted clarifying questions before generating the deck.

## Prompt
Generate an 8-slide sales deck narrative and speaker notes that is ready for a salesperson to present. Use the inputs exactly as provided: {{offer}}, {{icp}}, {{core_problem}}, {{primary_benefit}}, {{proof_points}}, {{pricing_model}}, {{objections}}, {{ctas}}.

Produce the assets in this strict order and format. Be specific, concise, and measurable. Do not invent customer results; if you must estimate, label the number as an "estimate" and state the assumption.

1) Title slide (One-liner + 2 headline variants)
- Provide two headline variants (short, bold, 6-12 words) that present the core promise of {{offer}} for {{icp}}.
- One-line tagline (max 12 words) that summarizes the outcome.
- Speaker note (20-30 seconds).

2) Problem slide
- Headline (1 line).
- 3 concise bullets that quantify the pain for {{icp}} and tie to {{core_problem}} (use numbers if available).
- 20-30s speaker note that frames urgency and cost of inaction.

3) Solution slide
- Headline (1 line) that positions {{offer}} as the specific fix.
- 3 short bullets explaining how {{offer}} addresses each element of {{core_problem}}.
- 20-30s speaker note highlighting fit for {{icp}} and differentiation vs generic alternatives.

4) Value props slide (3 bullets)
- Slide headline.
- Three value-prop bullets; each must include (a) feature, (b) direct benefit, and (c) measurable outcome or time-to-value (real metric or "estimate" with assumption).
- 20-30s speaker note summarizing the three props and suggested proof cue.

5) Proof / Customer example slide
- Headline.
- One customer example or case study framed: context â†’ action â†’ result. Use items from {{proof_points}}. For each numeric result, show source or label "estimate" if not provided.
- 20-30s speaker note that anticipates the key credibility question.

6) ROI / Impact slide (2 metrics)
- Headline.
- Two clear metric lines (e.g., "X% reduction in Y" or "$Z annual savings") with baseline, result, and timeframe. Use provided {{proof_points}} where possible; otherwise provide conservative estimates and mark them as estimates with assumptions.
- Short calculation or logic sentence showing how metrics were derived.
- 20-30s speaker note that connects metrics to buyer priorities.

7) Pricing summary slide
- Headline.
- Pricing snapshot using {{pricing_model}}: list packages or a single price, deliverables per price, billing cadence, and any common discounts or pilot terms.
- One brief objection-prep line tying price to value (use {{primary_benefit}}).
- 20-30s speaker note explaining next-step options for procurement.

8) Closing slide (Primary CTA + 1 alternative CTA)
- Headline.
- One primary CTA (must be a single actionable next step chosen from {{ctas}}) and one alternative CTA (e.g., pilot, ROI review).
- One sentence on expected commitment/time from the prospect (e.g., "30-minute technical review").
- 20-30s speaker note with suggested closing language and how to handle the most likely objections from {{objections}} (provide 2 short rebuttal lines).

Formatting and additional requirements
- For every slide include: Slide number, Slide title, 2-4 content bullets (no long paragraphs), and a Speaker note (20-30s; ~40-60 words).
- Maintain one primary CTA across the deck (the Closing slide may show one primary CTA and one secondary option).
- Mark any numerical claims that are not present in {{proof_points}} as "estimate" and add a one-line assumption.
- Provide a one-line "Expected outcome" under each slide describing the measurable prospect action the slide aims to trigger (e.g., "Agree to pilot", "Schedule technical call").

If any required input above is missing or ambiguous, ask up to 3 clear clarifying questions before generating the deck. After clarifications are answered, produce the full deck in one pass.

## Output Format
Return the deck exactly in this sequence and headings. Use bold for slide headlines and italic for speaker notes. Include an "Assumptions" block only if you had to create estimates due to missing inputsâ€”list assumptions as short bullet lines.

The deck must contain:
- Title slide with two headline variants and one-line tagline
- Slides 2-8 as specified, each with content bullets, speaker note (20-30s), and "Expected outcome"
- A short "Next steps" line under the closing slide that repeats the single primary CTA
- If any numeric values are estimates, an "Assumptions" block at the end (only present if used)

## Guardrails
- No cliches or hype phrases (ban: "game-changer", "disruptive", "best-in-class"); use concrete language.
- Claim hygiene: do not fabricate case study results. If a number is not provided in {{proof_points}}, label it as "estimate" and state the assumption.
- One primary CTA onlyâ€”do not scatter multiple CTAs across slides. The closing slide may include one alternative CTA.
- Keep each slide body to 2-4 bullets and each speaker note to 20-30 seconds (~40-60 words).
- Avoid technical jargon unless {{icp}} is a technical role; if used, include one-line plain-language translation.
- When addressing objections from {{objections}}, provide succinct rebuttals (max 2 lines each) tied to evidence or process.

## Examples
Headline variants (deck Title slide) â€” example style
- Variant A: "Cut support costs 30% by automating Tier-1 requests"  
- Variant B: "Automate Tierâ€‘1 support and reclaim engineering time"

Proof block â€” example style
- Customer: Acme Corp â€” Context: 200-seat SaaS provider. Action: Rolled out {{offer}} across support team. Result: 28% reduction in ticket volume and $120K annual savings (source: customer report). If a number had been estimated, show it as: "Estimate: 25% reduction (assumes 20% automation rate)."

-----

Variables

Usage Notes

Not for

â€¢ Producing legally binding contract language or final SOWs without legal review

â€¢ Making regulated medical, legal, or financial claims that require certification or compliance review

â€¢ Deep technical architecture proposals that require engineering diagrams or security artifacts

Do not include

â€¢ Multiple primary CTAs scattered across slides â€” one primary CTA only

â€¢ Fabricated customer results (label any non-provided numbers as 'estimate' with assumptions)

â€¢ Sensitive PII (names, emails, proprietary figures) in shared templates

â€¢ ClichÃ©s and unsubstantiated superlatives (e.g., 'game-changer', 'best-in-class')

8â€‘Slide Sales Deck Talkâ€‘Track Generator (Oneâ€‘Shot Template)

Produce a concise, seller-ready 8-slide deck narrative (one-liner, problem, solution, 3 value props, proof, 2-metric ROI, pricing, closing) with 20-30s speaker notes, two headline variants, and enforced personalization fields so outputs are production-ready and A/B-friendly.

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

Producing legally binding contract language or final SOWs without legal review

Made for

What to fill in

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

Icp