Build a discovery-call deck that guides prospects from problem to solution. Step-by-step structure, slide-by-slide tactics, and AI tools to personalize
The blank slide is the most expensive real estate in a sales conversation. You have done the research, booked the call, and lined up the right stakeholders. Then you open PowerPoint, stare at the default template, and lose an afternoon fighting alignment, tweaking font sizes, and pasting in screenshots that still look like a startup fever dream.
A discovery call is not a demo. It is not a pitch, exactly. It is a structured conversation that uncovers whether the prospect has a problem you can solve, and whether they are willing to pay to solve it. The deck you bring either sharpens that conversation or smothers it. When the slides are generic, text-heavy, and built around your product timeline instead of the prospect’s reality, you lose the room before you finish the agenda slide.
This guide gives you a repeatable, slide-by-slab structure for a discovery-call deck that converts. It works across industries because it leads with the buyer’s problem, earns the right to talk about your solution, and ends with a clear, low-friction next step. You will also see how to build and personalize these decks fast with AI-powered tools like Preso so you are never stuck on the blank slide again.
Before we break down the structure, let’s get the prerequisites out of the way.
A deck is only as strong as the thinking behind it. Before you open any presentation tool, line up these three things:
A clear call objective. Are you qualifying a pain point, establishing technical fit, or warming a cold account for a later pitch? Write down the single outcome you want from this call. If you cannot state it in one sentence, you are not ready to build slides.
Prospect-specific research. Spend 15 minutes inside the company’s website, news, job listings, and LinkedIn. What language does their leadership use? What initiative is this call tied to? A structured discovery call template can help you map likely goals and tailor your questions, but the deck needs to reflect that same intel.
Your core narrative. Not a script, but a logical flow: the world before your product, the moment of tension, and the new reality your product enables. That narrative becomes the spine of every slide.
With those in place, you can build a deck that feels tailored and sharp, not generic and forgettable. If you want an even faster starting point, Preso’s discovery and demo decks built from a single brief template turns a plain-English description of your call objective into a complete, on-brand deck.
The shape of your deck should change depending on what you need to learn. A call with a VP of Sales who is evaluating pipeline tools will demand different proof points than a call with an IT leader concerned about security. That sounds obvious, but too many teams grab the same company overview deck for every first call.
Instead, open a fresh document and title it with the call objective. Examples:
When the objective is that concrete, you can cut anything that does not serve it. A Zendesk guide on discovery calls makes the point plainly: avoid yes/no questions and validate pain points. The deck should do the same. If a slide does not help you either surface a problem, frame a better way, or earn trust, it does not belong in a discovery deck.
The most common mistake in a discovery deck is leading with your company story. A timeline slide, the founder origin, the four product pillars. Buyers tune out because they have not yet agreed that the problem you solve matters to them.
A converting discovery deck uses a problem-first structure. The narrative arc follows this shape:
Preso’s deck templates are built around this kind of narrative logic. When you select a template for a sales conversation, you are not picking a color scheme, you are picking a structural bet on what will move the buyer. The same is true when you generate decks from your stack programmatically: the system arranges content around a defined narrative, not a generic chronology.
Now the actual deck. The structure below keeps you under 10 slides, which is enough for a 30-minute call with room for conversation. Every slide earns its place.
Swap a generic title like “Acme Corp Discovery Call” for something that shows you did the homework. Use the prospect’s own language when you can. Examples:
The subhead should name the date, your name, and the prospect’s name. If the company has a recognizable brand color or mark, place it subtly. Not a logo collage, just a visual nod. Preso’s many designs for one deck feature lets you try a few visual directions without rebuilding anything, so you can land on the one that feels most aligned to the prospect’s aesthetic.
Do not show a list of topics. Show a journey. Three steps, each phrased as a shared goal:
This frame tells the prospect you are not about to monologue. It also gives you permission later to ask hard questions, because you already set the expectation that step one is about them, not you.
Pro Tip: Put a one-line call timer on this slide visually, something like “30 minutes total; we will spend the first 15 on your world.” It signals respect for their time and sets the conversational rhythm.
This slide is the engine of the deck. It should describe a single, recognizable problem in the prospect’s terms. Do not genericize it. If you know the prospect deals with slow data retrieval, write “When a customer asks for a status update, your team pulls data from three separate dashboards and an email thread.”
Use research you gathered beforehand. A Gong analysis of discovery call questions found that top performers anchor their questioning in specific observable behaviors, not abstract pain areas. Your problem slide should mirror that specificity.
The layout matters: left side, a visual of the broken process (a fuzzy screenshot or a simple diagram). Right side, three bullets describing the cost: time lost, revenue delayed, team frustration. No more.
Now, describe the solution in the prospect’s world, not yours. Instead of “Our AI-powered platform ingests data,” say “When a customer asks for an update, a single dashboard pulls the status from every source and pushes it to their phone.”
This is where you earn the right to talk about your product later. If you jump to a feature tour here, you lose the thread. Instead, stay inside the prospect’s workflow and paint the outcome. An Acquire article on effective discovery calls calls out the power of aligning your solution to the metrics the buyer already cares about. This slide should do exactly that.
Now you can introduce your product, but only through the lens of the problem you just named. Use a tightly scoped screenshot, a short, narrated product clip, or a two-step diagram that shows precisely how the prospect would use your tool in the scenario from slide 3. Limit yourself to three capabilities max. You can always show more if they ask.
If you built the deck with Preso’s plain English to deck engine, you likely already have an AI-generated diagram or chart that visualizes this workflow. Edit it to match the prospect’s terminology. Small language changes signal deep personalization.
Avoid a generic logo slide. Instead, show one or two customer outcomes that are as close as possible to the prospect’s situation. Use a format like:
If you do not have a case study that exactly matches, pick the one that shares the same job title or industry. Pair it with a forward-looking statement: “We believe [Prospect] could see similar results given your [current state].”
A research-backed breakdown by Winning by Design notes that connecting buyer outcomes directly to the call’s problem statement is one of the highest-impact things you can do in a first meeting. This slide makes that tangible.
End with a slide that proposes a single, concrete next action. Not “let’s hop on another call,” but something that requires low effort from the buyer and moves the deal forward. For example:
Include your contact details and a one-click booking link. Do not clutter this slide with logos or disclaimers. Keep it clean and action-oriented.
Preso’s sales and revenue deck solutions make it easy to build this slide with built-in booking integrations and personalized next-step copy that pulls from your CRM.
The biggest friction point for teams is the time it takes to tailor a deck per prospect. You have the research, but translating that into slide-level changes feels slow. This is where AI and templates earn their keep.
Preso lets you describe the prospect and the call context in plain English, and it generates a fully designed, on-brand deck. For example, you can write: “Discovery call deck for a 200-person logistics company struggling with on-time delivery reporting. Objective: validate if they need better real-time dashboards and propose a three-week pilot.” Preso designs the slides around that brief, pulling in relevant layouts, charts, and AI-generated imagery.
If you need to scale this further, account-tailored pitch decks personalized per prospect can be built inside the editor or via the Presentation API. Starting from a target account enriched in Clay or Apollo, Preso weaves in company details, then delivers the deck directly to Salesforce, HubSpot, or your presentation tool. This means your reps walk into calls with a deck that looks designed for that specific prospect, not a recycled template.
Warning: Do not over-personalize to the point of creepiness. A deck that mentions the prospect’s last 10 tweets reads as inauthentic. Personalization should be background context that surfaces the right problem statement, not a party trick.
A discovery deck is not a one-and-done artifact. The way you deliver it and the follow-up you attach can either extend the momentum or stall the deal.
Share the deck before the call. Send a PDF or a link a day in advance with a short note: “Here is what we will walk through tomorrow. I tailored it around [specific challenge]; feel free to add any questions you want covered.” This turns the deck into a collaboration tool, not a performance.
During the call, use the deck as a visual anchor, but do not read from it. The slides should prompt conversation, not dictate it. Pause on the problem slide and ask: “Does this match what you are seeing internally?” That question alone often reveals more than any agenda slide ever could.
After the call, send a self-running recap. Preso’s Sequences feature writes a natural AI voice-over script for each slide, so you can share a narrated walkthrough that the prospect can watch on their own time, in their preferred language. This is especially powerful for a discovery follow-up: the champion can share it internally without you re-explaining everything, and the narrative stays consistent.
For teams managing high volumes, generating decks programmatically becomes essential. The Preso REST Presentation API and MCP server let you hook deck generation into workflows: a new deal moves from SQL to discovery stage, and the system produces a tailored deck automatically, ready for review. This changes the deck from a creative bottleneck into a signal of operational maturity.
The difference between a discovery deck that sits in a downloads folder and one that drives a follow-up meeting often comes down to small, tactical choices.
Pro Tip: Start the design process with the call objective, not a slide count. If you cannot justify why a slide is there in one sentence, delete it. A five-slide deck that hits the core problem and next step outperforms a 20-slide deck that tries to also serve as a product demo.
Warning: Avoid generic slide titles like “About Us,” “Our Technology,” or “Market Landscape.” Every title should contain a verb or a direct benefit. “How We Cut Response Time by 40%” is better than “Product Overview.”
Pro Tip: Use visual hierarchy deliberately. The prospect’s eye should land on the problem statement or the outcome, not your logo. Text size, contrast, and whitespace are free tools. A Mereo article on sales deck insights details a “Power Pitch” structure where discovery questions are woven directly into solution snapshots. Visually, that means side-by-side problem and solution columns on a single slide, so the connection is immediate.
Warning: Do not cram the deck with every feature your product has. A discovery call is not the place to demo your API endpoints. Stick to the capabilities that directly address the validated problem. If the prospect asks for more, you can pull up a separate product deck, but only after you have confirmed need.
Pro Tip: Test your deck on a colleague who knows nothing about the prospect. If they can describe the problem you are solving and the next step after seeing the slides once, the deck is working. If they stumble or ask “what does this company do?” fix the narrative, not the design.
Warning: Do not assume the same deck works for every call because the product is the same. The problem you highlight for a VP of Engineering will differ from the one you highlight for a CMO. HubSpot’s discovery call resource reinforces that matching the deck structure to the buyer persona is a conversion multiplier. Build a few modular slide groups so you can swap problem statements and proof points per persona without rebuilding the full deck each time.
The discovery-call deck is not a presentation. It is a structured conversation partner. When built well, it earns trust, surfaces real problems, and creates a natural path to the next step.
Build your next discovery-call deck with Preso. Describe your prospect and the call objective in plain English, and get a polished, on-brand deck ready to share, present, or export. Start at trypreso.com and spend your time selling, not aligning text boxes.