Verified against ChatGPT · 2026-08-13
Structure a stakeholder presentation around the one objection that'll actually sink it
Builds a presentation outline that surfaces and addresses the single most likely objection early, instead of hoping it doesn't come up until Q&A.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Structure a presentation outline for a specific stakeholder audience, built around defusing the one objection most likely to actually derail it — not a generic problem-solution-ask template. PRESENTATION GOAL Get budget approval for a 6-month pilot of a new customer support ticketing platform. AUDIENCE AND WHAT'S AT STAKE FOR THEM The CFO, who's wary after the last tooling migration went over budget and disrupted support coverage for a month. MOST LIKELY OBJECTION That this is just another tool migration that will repeat last year's budget overrun and disruption. SUPPORTING EVIDENCE AVAILABLE A fixed-price vendor quote and a parallel-run plan that keeps the old system live during transition, but no case study from a company our exact size. TIME LIMIT 15 minutes, including Q&A. First, decide where in the presentation the likely objection should be addressed: if it's fundamental enough that the audience will be silently skeptical of everything said before it's answered, address it early, even before the main pitch; if it's more of a detail that would come up near the end, place it there instead — do not default to 'address objections at the end' as a rule, decide based on how load-bearing this specific objection actually is to the audience's stated stake. Build the rest of the outline so that every section either sets up evidence needed to counter the objection or moves the goal forward — cut anything that does neither, especially given the stated time limit forces real prioritization. Where the supporting evidence available is genuinely insufficient to fully answer the objection, do not paper over that gap with confident language — say directly that the evidence doesn't fully settle it, and outline how the presentation should acknowledge that honestly while still making the case, since a stakeholder audience that catches a bluffed answer to their real objection will trust nothing else in the deck afterward. WHAT NOT TO DO Do not use a generic outline shape (situation-complication-resolution, or problem-solution-benefits) applied mechanically — build the shape around this specific objection and audience. Do not exceed a section count that fits the stated time limit; a 10-minute slot does not get a 12-section outline. OUTPUT FORMAT 1. One line stating where the objection is placed in the outline and why. 2. Section-by-section outline with a one-line purpose per section, sized to the time limit. 3. If the evidence is insufficient to fully answer the objection, one paragraph on how the outline handles that honestly.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Generic presentation templates place objection-handling at the end because that's the conventional structure in business-writing training data, but a load-bearing objection left until the final slides means the audience spends the entire presentation in silent skepticism, discounting every earlier claim — forcing the model to explicitly decide where the objection belongs based on how fundamental it is to the audience's stated stake, rather than defaulting to end-placement, produces a structure that actually matches how a skeptical stakeholder processes information in real time. The instruction against papering over insufficient evidence targets a specific and costly failure mode: language models asked to 'address an objection' will often generate confident-sounding language that implies the evidence fully settles the concern even when it doesn't, because a hedged answer reads as weaker prose — but a stakeholder audience that later discovers the confident answer was thinner than it sounded stops trusting every other claim in the deck, which is a worse outcome than an honest acknowledgment up front. Sizing the section count to the actual time limit matters because outlines generated without a hard constraint tend toward comprehensive coverage of the topic rather than a version cut down to what fits, and a presenter who walks in with more content than time available either rushes past the objection-handling section (defeating the whole point of this structure) or runs over and loses the room before the ask lands. Anchoring every section to either 'sets up the objection rebuttal' or 'advances the goal' as a binary filter is what prevents scope creep back toward a generic comprehensive-overview structure.
What you get back
Objection placement: address it second, right after stating the goal, since the CFO's skepticism about repeat budget overruns will color every subsequent slide if left unaddressed. Section 2 — Why This Isn't Last Year: the fixed-price quote and parallel-run plan, stated plainly, with an honest note that we don't have a same-size case study yet, followed by what would trigger an early stop if the pilot underperforms.
Verified against
ChatGPT GPT-5.1 · 2026-08-13
Changelog
- 2026-08-13 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — custom software, built and maintained for you — that's Scult's day job.
EXPLORE CUSTOM SOFTWARE
