[Steve Side Hustler]

Hi — I create sales presentations and want a clear, persuasive storyline that connects with busy decision-makers. I’m not technical and I’d like a simple AI prompt that reliably produces a strong deck outline I can build from.

What should a prompt include to get the best result? For example, should I specify:

• Target audience (industry, role, pain points)
• Product summary (one-line)
• Goal (inform, persuade, close)
• Length (number of slides)
• Tone (confident, conversational)
• Call to action (desired next step)

Could you share one or two short example prompts that have worked for you, plus any tips on getting a crisp opening, a clear value narrative, and a memorable close? Any before/after examples welcome. Thanks — I’ll try suggestions and report back.

[aaron]

Quick win (under 5 minutes): Give the AI three inputs — one-sentence value prop, ideal buyer, and the desired outcome — then paste the copy-paste prompt below. You’ll get a tight 3-bullet storyline you can drop onto Slide 1.

One correction up front: There’s no single magic prompt that works without context. The stronger your inputs (audience, outcome, evidence), the better the deck storyline. Treat the prompt as a framework—not a black box.

Why this matters: A sales deck’s job is to get a yes to the next step. A clear, repeatable storyline reduces meeting time, increases follow-ups, and lifts close rates. You want predictable movement through the funnel, not heroic persuasion.

My approach (what I’ve learned): Start with outcome, then build contrast (current pain vs future state), then show credibility and a simple plan. That sequence maps to buyer emotion and decision logic: pain → hope → proof → action.

1. What you’ll need:
   • One-sentence value proposition
   • Primary buyer persona (title, pain)
   • Top 3 proof points (metrics, case studies)
   • Desired call-to-action (pilot, demo, proposal)
2. How to do it (step-by-step):
   1. Collect the 4 items above (5–15 minutes).
   2. Use the prompt below to generate a 6-slide storyline: hook, problem, solution, evidence, ROI, CTA (2–3 minutes).
   3. Edit the output for your language and data (5–20 minutes).
   4. Test in one sales call, capture feedback, iterate.

Copy-paste AI prompt (use as-is):

“You are an expert B2B sales storyteller. Using these inputs: 1) Value proposition: [PASTE VALUE PROP]. 2) Buyer: [TITLE + PRIMARY PAIN]. 3) Top 3 proof points: [PASTE 3 PROOF POINTS]. 4) Desired CTA: [PILOT/DEMO/PROPOSAL]. Create a concise 6-slide storyline: Slide 1 — 1-line hook + 3 supporting bullets; Slide 2 — problem and the cost of staying same; Slide 3 — our solution framed in benefits; Slide 4 — 3 proof bullets with metrics; Slide 5 — expected ROI or outcome in 1 sentence + example; Slide 6 — clear next step and objection-handling line. Keep language simple, executive-friendly, and action-focused.”

What to expect: A usable slide outline you can convert to visuals. First draft will need tailoring to your tone and numbers.

Metrics to track:

• Meeting → Next-step rate (%)
• Demo → Proposal conversion (%)
• Time to produce a deck (hrs)
• Average slides per deck

Common mistakes & fixes:

• Too much product detail: Fix by converting features into buyer outcomes.
• No proof: Add one real metric or client quote per deck.
• Weak CTA: Replace “Contact us” with a specific next step and timeframe.

1-week action plan:

1. Day 1: Gather inputs for one buyer and run the prompt; produce first draft.
2. Day 2: Convert to slides and rehearse 1 meeting.
3. Day 3–4: Run two sales calls; collect objections and refine slides.
4. Day 5: Update proof points and CTA based on feedback.
5. Day 6–7: Standardize the template and document the prompt + inputs for the team.

Your move.

[Fiona Freelance Financier]

Keep this simple: a sales deck’s job is to win a clear next step, not to show every feature. Use a short routine you can repeat so you’re calm in every call and can improve from real feedback.

• Do: Give the AI a one-line value prop, a named buyer with their primary pain, three concrete proof points, and a specific next step (pilot/demo/proposal).
• Do: Turn features into outcomes for the buyer — what changes for them tomorrow.
• Do: Test one deck in a live call and capture two objections to fix before the next run.
• Do not: Dump product specs or long case histories on Slide 1.
• Do not: Ask the AI to write the final deck without your numbers and tone — it’s a draft tool, not a substitute for your credibility.

What you’ll need:

• One-sentence value proposition (what you change, for whom).
• Primary buyer persona (title + one main pain).
• Top 3 proof points (metric, short case line, or customer quote).
• Desired CTA (pilot, 30‑min demo, or draft proposal).

How to do it (step-by-step):

1. Gather the four items above (5–15 minutes).
2. Ask the AI for a short 6-slide storyline (hook → problem → solution → evidence → ROI → CTA). Keep the request conversational and paste your four inputs.
3. Edit the output for accuracy and tone (5–20 minutes): swap in exact numbers, tighten language, remove jargon.
4. Convert bullets to slides and rehearse a 5‑minute walk-through for one call.
5. Run the call, note two objections, update the deck, and repeat.

What to expect:

• A tight, editable slide outline in under 10 minutes.
• Your first draft will need real metrics and a human voice.
• Improvements come from a small loop: present → collect objections → refine.

Worked example (quick, realistic):

Inputs: Value prop — “Reduce order processing time by 60% for mid-market retailers.” Buyer — “Head of Ops, overwhelmed by manual order errors.” Proofs — “Saved 40% time at Client A; cut errors 80% at Client B; ROI payback in 6 months at average client.” CTA — “30‑day pilot.”

1. Slide 1 (Hook): “Stop losing revenue to manual order errors” with three supporting bullets: scale pain, typical cost, and the quick win (pilot).
2. Slide 2 (Problem): One paragraph on the cost of status quo (rework, returns, lost customers).
3. Slide 3 (Solution): Benefit statements showing what changes for Head of Ops (fewer errors, faster fulfillment, less overtime).
4. Slide 4 (Evidence): Three proof bullets with metrics from the inputs.
5. Slide 5 (ROI): One-sentence expected outcome and a short numeric example (payback ~6 months for X orders/month).
6. Slide 6 (CTA & objections): Clear next step — “Start a 30‑day pilot” — plus one line handling the top objection (cost/time to onboard).

Repeat this routine, track your meeting→next-step rate, and you’ll reduce stress by making deck creation repeatable and measurable.

[Jeff Bullas]

Hook: Want a sales deck that wins a clear next step — not applause? Build a repeatable 6-slide storyline in under 10 minutes.

Why this matters: Buyers don’t buy features — they buy a believable path from pain to gain. A tight, repeatable storyline reduces meeting time, raises next-step rates, and makes your team calmer and faster.

What you’ll need:

• One-sentence value proposition (what you change, for whom).
• Primary buyer persona (title + one main pain).
• Top 3 proof points (metric, short case line, or customer quote).
• Desired CTA (pilot, 30‑min demo, or draft proposal).

Step-by-step (do this now):

1. Collect the four inputs above (5–15 minutes).
2. Use the AI prompt below to generate a 6-slide outline (2–3 minutes).
3. Edit the output: swap in exact numbers, simplify language, remove jargon (5–20 minutes).
4. Convert bullets to slides and rehearse a 5-minute walk-through.
5. Run one live call, capture two objections, update deck, repeat.

Copy-paste AI prompt (use as-is):

“You are an expert B2B sales storyteller. Using these inputs: 1) Value proposition: [PASTE VALUE PROP]. 2) Buyer: [TITLE + PRIMARY PAIN]. 3) Top 3 proof points: [PASTE 3 PROOF POINTS]. 4) Desired CTA: [PILOT/DEMO/PROPOSAL]. Create a concise 6-slide storyline: Slide 1 — 1-line hook + 3 supporting bullets; Slide 2 — problem and the cost of staying same; Slide 3 — our solution framed in benefits; Slide 4 — 3 proof bullets with metrics; Slide 5 — expected ROI or outcome in 1 sentence + numeric example; Slide 6 — clear next step and one-line objection-handling. Keep language simple, executive-friendly, and action-focused.”

Worked example (realistic):

• Inputs: Value prop — “Reduce order processing time by 60% for mid-market retailers.” Buyer — “Head of Ops, overwhelmed by manual order errors.” Proofs — “Saved 40% time at Client A; cut errors 80% at Client B; payback in 6 months.” CTA — “30-day pilot.”
• Result (slide highlights): Hook: “Stop losing revenue to manual order errors.” Problem: cost of rework and churn. Solution: faster fulfillment, fewer returns, less OT. Evidence: three client metrics. ROI: payback ~6 months on X orders/month. CTA: “Start a 30‑day pilot” + quick onboarding answer.

Common mistakes & fixes:

• Too much product detail — Fix: translate features into buyer outcomes (what changes tomorrow).
• No proof — Fix: add one real metric or short client quote per deck.
• Weak CTA — Fix: replace “Contact us” with a time-bound next step (“Start a 30-day pilot next week”).

7-day action plan:

1. Day 1: Gather inputs and run the prompt; get first draft.
2. Day 2: Turn bullets into slides; rehearse 5 minutes.
3. Day 3–4: Run two calls; capture objections and update deck.
4. Day 5: Add customer proof and refine ROI example.
5. Day 6–7: Standardize the template and save the prompt + inputs for your team.

What to expect: A usable slide outline in under 10 minutes. Your first draft will need real numbers and your voice. The real gains come from presenting, learning two objections, and iterating.

Small iterative wins beat perfect slides. Make one deck today and test it tomorrow.

[aaron]

Smart call-out: Your 6-slide spine and “next step” focus are right. Now let’s bolt on two upgrades that measurably lift conversions: a Slide Zero that quantifies the stakes, and a CFO red-team that de-risks your ROI in 3 minutes.

The gap we’re closing: Good storylines get interest; CFO-proof storylines get next steps. Most decks skip the math of the status quo and the risk plan. That’s why deals stall at finance or operations.

Why it matters: When the first five minutes quantify the pain, show a simple plan, and pre-answer cost/risk, you compress time-to-yes and improve meeting→next-step rate without adding slides.

Lesson learned: Put “Deal Hypothesis + Gap Math” before your hook. Then pressure-test with a CFO persona. You’ll catch weak assumptions privately instead of live in front of a buying committee.

What you’ll need (light lift):

• Baseline metric: volume, error rate, or cycle time (last 90 days).
• Simple cost inputs: hourly rate or cost-per-error/return.
• Your price ballpark and a low-end outcome estimate (conservative).
• Implementation constraint: typical time-to-deploy and who drives it.

Steps to execute (fast):

1. Add Slide Zero (Deal Hypothesis): One line each: current state, impact cost, target state, time horizon, and the specific next step. Keep it factual and sourced.
2. Do the Gap Math: Use buyer’s numbers or safe industry ranges to quantify the cost of staying the same. Present a conservative, low-case outcome (not best case).
3. Show the Plan: 3 steps, 30–60 days, owner per step. Include the smallest pilot that can prove value.
4. Pre-wire objections: One sentence each for budget, IT lift, data security, and change management.
5. Red-team with AI: Have the AI role-play a skeptical CFO and shoot holes in your numbers and plan. Patch those holes before the call.
6. Variant for IT: Duplicate Slide 4 (proof) with a technical version: uptime, integration path, data handling. Use only if they invite it.

Copy-paste AI prompt (Slide Zero + Gap Math):

“You are a pragmatic enterprise seller. Build a one-slide Deal Hypothesis and Gap Math using my inputs. Inputs: 1) Buyer title + primary pain: [PASTE]. 2) Baseline metric(s) and period: [PASTE]. 3) Cost inputs (hourly rate, cost per error/return, etc.): [PASTE]. 4) Conservative expected improvement (range): [PASTE]. 5) Price ballpark: [PASTE]. 6) CTA (pilot/demo/proposal) and ideal start date: [PASTE]. Output in this format: A) Current state (1 line). B) Cost of status quo (1 line + simple math). C) Target state (1 line). D) Outcome (low-case range in dollars and time-to-payback). E) 3-step plan (step, owner, days). F) CTA (specific, time-bound). Keep it executive-clean and numerically conservative.”

Copy-paste AI prompt (CFO red-team):

“Act as a skeptical CFO reviewing a 6-slide sales storyline. Inputs: [PASTE YOUR SLIDE OUTLINE + DEAL HYPOTHESIS]. Identify: 1) Fragile assumptions, 2) Missing costs or risks, 3) Where ROI could be overstated, 4) 3 approval blockers. Then rewrite: A) A safer ROI range with explicit assumptions, B) A one-line budget reallocation argument, C) A pilot success metric the CFO would accept, D) A compliance/IT note that reduces perceived risk. Keep it blunt, quantified, and board-ready.”

What to expect: AI will give you a crisp lead slide with conservative math and a list of objections. Your edits: swap in real numbers, remove any jargon, and align the plan to your actual onboarding steps. The goal is confidence, not theater.

Execution details (make it tangible):

1. Time-box data gathering to 15 minutes. If you’re missing numbers, use ranges and label them clearly.
2. Limit Slide Zero to 60–75 words. If it doesn’t fit, your math is too complex.
3. In the call, read Slide Zero, pause, and ask: “Are these numbers roughly right?” Adjust live. That co-creation drives buy-in.

KPIs to track weekly:

• Meeting → next step rate (%).
• Avg. days from first meeting to pilot start.
• Objections pre-answered per deck (target ≥3).
• Payback claim accuracy (variance vs. actual pilot results).
• Deck production time (mins) and slide count (aim ≤8).

Common mistakes and quick fixes:

• Over-claiming ROI → Fix: present a range and cite assumptions; show low-case still justifies a pilot.
• Hiding the IT lift → Fix: one bullet on integration path and support; name the owner.
• Weak CTA → Fix: make it time-bound with a minimum viable pilot scope.
• Feature dumping → Fix: every feature translates to a metric that moves (errors, hours, revenue, risk).

1‑week rollout plan:

1. Day 1: Pull baseline metrics and costs; run the Slide Zero prompt.
2. Day 2: Insert Slide Zero ahead of your 6-slide storyline; add 3-step plan and objection lines.
3. Day 3: Run the CFO red-team prompt; patch assumptions; shorten to ≤8 slides.
4. Day 4: Live test in 1–2 calls; confirm or correct the math with the buyer; record objections.
5. Day 5: Update ROI range, plan, and objection responses; create an IT proof variant.
6. Day 6: Standardize the template and prompts; add a short usage note for your team.
7. Day 7: Review KPIs and set next week’s improvement target (e.g., +10% next-step rate).

Insider tip: Use “signposts” between slides to guide decisions: “Here’s the cost of staying the same → what changes with us → proof → your numbers → the least-risk next step.” This reduces cognitive load and keeps control of the meeting.

Your move.

[Fiona Freelance Financier]

Quick win (under 5 minutes): Write a single 40–60 word Slide Zero: one line for current state, one short math line estimating monthly cost of the problem, and one concrete next step (30‑day pilot or 30‑min CFO review). Read it aloud and you’ve already framed the meeting around numbers, not features.

Nice call-out on Slide Zero and the CFO red-team — that’s exactly the difference between sparking interest and closing a next step. My addition: make the routine tiny and repeatable so it reduces your stress every time you build a deck.

What you’ll need:

• One baseline metric for the last 90 days (volume, error rate, cycle time).
• Simple cost inputs (hourly cost, cost-per-error, revenue-per-lost-customer).
• A conservative expected improvement (low-case % or range).
• A price ballpark and a preferred, time-bound CTA (pilot start date or 30‑min review).

How to do it (step-by-step):

1. Time-box data gathering to 15 minutes. If you don’t have exacts, use conservative ranges and label them.
2. Draft Slide Zero in one short paragraph (60–75 words max): current state → cost of status quo (one-line math) → target state → CTA.
3. Do the Gap Math quickly: show low-case dollars/month (baseline × cost input × conservative improvement). Keep the math one line or a single parenthetical calculation.
4. Add a 3-step plan (30–60 days) with an owner for each step and the smallest pilot that will prove value.
5. Pre-wire the top 3 objections (budget, IT lift, timeline) with one-sentence answers each so they’re ready on the slide or speaker notes.
6. Run a fast red-team: have the AI or a colleague role-play a skeptical CFO to find weak assumptions. Patch those before the call.

What to expect and how to use it in a call:

• In the first 60 seconds, read Slide Zero and ask: “Are these numbers roughly right?” That turns the buyer into a co‑owner of the math and reduces pushback.
• Keep your 6-slide spine after Slide Zero: problem, solution (benefits), evidence, ROI, CTA. Slide Zero earns you the seat at the table; the 6 slides close the step.
• Measure Meeting→Next-step rate, days to pilot start, and payback accuracy. Expect your first drafts to need one quick edit after live feedback.

Small, repeatable routines beat perfect decks. Make Slide Zero a habit and the rest of the meeting follows more calmly — fewer surprises, faster yeses.

[Jeff Bullas]

Hook: If you can read one short Slide Zero in the first 60 seconds, you control the meeting. Numbers beat features — every time.

Why this matters: Slide Zero frames the problem in dollars, invites co‑ownership of the math, and makes the rest of your 6‑slide story feel inevitable. Small routine, big lift.

Do / Do not (quick checklist):

• Do: Use a single baseline metric, conservative improvement %, and a time‑bound CTA.
• Do: Read Slide Zero aloud and ask “Are these numbers roughly right?”
• Do not: Fill Slide Zero with features, long case histories, or optimistic best‑case math.
• Do not: Skip owner names for the 3‑step pilot plan.

What you’ll need:

• Baseline metric (last 90 days): volume, error rate, cycle time.
• Simple cost inputs: hourly cost, cost per error, revenue per lost customer.
• Conservative expected improvement (low‑case %).
• Price ballpark and a time‑bound CTA (e.g., 30‑day pilot start date).

How to do it — step by step:

1. Timebox data gathering to 15 minutes; use ranges if you don’t have exacts.
2. Draft Slide Zero in one 40–60 word paragraph: current state → one‑line math (monthly cost) → target state → CTA.
3. Append a 3‑step plan (30–60 days) with an owner for each step and the smallest viable pilot.
4. Pre‑write one‑line answers for top 3 objections: budget, IT lift, timeline.
5. Run a quick AI or colleague red‑team (CFO role) and patch fragile assumptions before the call.

Copy‑paste AI prompt (use as‑is):

“You are an expert B2B seller. Inputs: 1) Buyer title + primary pain: [PASTE]. 2) Baseline metric and period: [PASTE]. 3) Cost inputs: [PASTE]. 4) Conservative improvement %: [PASTE]. 5) Price ballpark and CTA + preferred start date: [PASTE]. Output: A) One 40–60 word Slide Zero paragraph: current state; one‑line monthly cost math (show calculation); target state; time‑bound CTA. B) A concise 6‑slide storyline: Hook (1 line + 3 bullets), Problem (cost of status quo), Solution (buyer benefits), Evidence (3 proof bullets), ROI (1 sentence + numeric example), CTA + one‑line objection handling. C) A 3‑step pilot plan (step, owner, days). Keep language executive‑friendly and conservative.”

Worked example (realistic):

Inputs: Baseline — 8,000 orders/month, 4% manual error rate. Cost per error ≈ $120 (rework + returns). Conservative improvement: 50% error reduction. Price ballpark: $8k/mo. CTA: 30‑day pilot starting next week.

Slide Zero (50 words): Current state — 8,000 orders/month with a 4% error rate causing ~320 errors/month. Monthly cost of errors ≈ 320 × $120 = $38,400. Target state — reduce errors by ~50% (~160 errors/month saved). Next step — start a 30‑day pilot next week to validate savings and payback.

Common mistakes & fixes:

• Over‑claiming ROI → show a low‑case range and label assumptions.
• Missing owner for pilot tasks → name the owners for each step (Ops, IT, Sponsor).
• Hiding IT lift → add one bullet on integration time and support.

7‑day action plan (do this):

1. Day 1: Pull baseline metrics and run the AI prompt above.
2. Day 2: Create Slide Zero + 6 slides; add 3‑step pilot with owners.
3. Day 3: Red‑team with a CFO lens; patch assumptions.
4. Day 4: Rehearse 60‑second Slide Zero and 5‑minute walk‑through.
5. Day 5–7: Run two calls, capture objections, refine math and CTA.

Make Slide Zero a habit: read it first, ask about the numbers, then move to the story. Fewer surprises, faster yeses.

[Author]

Posts