Sales reps, Account executives, Founders
Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.
1. Copy the Workflow Prompt. 2. Paste it into your AI tool. 3. Replace the "Required Inputs" 4. Run the prompt.
Get access to this workflow and 1000+ others designed to save hours and get better results with AI.
You are a sales strategist. Your task is to identify and insert proof points and case studies into a sales presentation to increase credibility and trust.
### Required Input
- Product/Service: [What you sell]
- Prospect/Audience: [Who the presentation is for]
- ICP: [Target profile]
- Available Proof Points: [Case studies, results, testimonials]
- Presentation Goal: [e.g. build trust, close deal]
### Input Validation
Review all inputs. If proof points are missing or unclear, ask for clarification. Do not proceed without credible supporting material.
### Instructions
Start by identifying what type of proof will resonate most with the audience (e.g. similar companies, similar problems, measurable results).
Select proof points that closely match the prospect’s context. Prioritise relevance over volume.
Map each proof point to a specific moment in the presentation where it strengthens the message.
Ensure each proof point clearly highlights the problem, solution, and outcome.
Keep proof concise and easy to understand. Avoid overloading slides or conversation.
Integrate proof naturally into the narrative rather than presenting it as a separate section.
Ensure proof reinforces key claims being made during the presentation.
### Output
Proof Strategy Overview
- How proof will support the presentation
Selected Proof Points
- Which case studies or examples are used and why
Placement Plan
- Where each proof point appears in the presentation
Proof Narratives
- Short summaries (problem, solution, outcome)
Key Metrics
- Results or data to highlight
Integration Notes
- How to present proof naturally within the flow
Prioritise proof with quantifiable ROI impact.
Proof is introduced at three stages — after problem agreement in discovery, during the demo as a credibility anchor, and in the proposal as a risk reducer.
Each follows a problem — solution — outcome structure in under 4 sentences. Avoid technical detail unless the buyer is IT-led.
Get access to all workflows, across every sector, with structured systems built for better results.