Customer Discovery Presentation Template

Customer discovery findings are only useful if they drive decisions. Most discovery research ends up in a Google Doc that is referenced once and forgotten, or in a presentation that describes what people said without translating it into what the team should build, prioritize, or change.

A customer discovery presentation that drives product and strategy decisions does four things: shows where the evidence came from (so the audience can evaluate its quality), synthesizes patterns from individual interviews into actionable insights (not just quotes), ranks the opportunities by size and urgency, and recommends a specific direction with a clear rationale.

This template covers each of those steps.

Slide 1: Research Objectives

State what questions this discovery effort was designed to answer.

Include:

• The strategic question or decision this research supports: "We are deciding whether to build a mobile app, a Slack integration, or a reporting module next. This discovery was designed to help us prioritize."
• The specific sub-questions the interviews explored: What is the current workflow? Where does it break down? What tools are involved? How is the problem currently worked around? What would a better solution need to do?
• What was explicitly out of scope for this research

The research objectives slide prevents the most common discovery failure: presenting findings that answer questions nobody asked. If the research was designed to answer a specific decision, say so at the start.

Slide 2: Methodology

Describe how the research was conducted so the audience can evaluate the quality of the evidence.

Include:

• Number of interviews conducted (and how many were completed vs. scheduled)
• How participants were selected: existing customers, churned customers, prospective buyers, specific segments
• Interview format: structured, semi-structured, or exploratory
• Duration of each interview
• Who conducted the interviews (external researcher, product manager, founder)
• Whether interviews were recorded and transcribed
• The date range of the research (findings from research done 18 months ago may be outdated)

A finding from 20 interviews with a defined customer segment is different evidence than a finding from 4 informal conversations the founder had at a conference. The methodology slide makes that distinction explicit.

Slide 3: Who We Talked To

Show the distribution of participants across the dimensions that matter for your product.

Typical segmentation dimensions:

• Company size (employee count or revenue band)
• Industry or vertical
• Role and seniority of the interviewee
• Current tool or workflow (what they are using today to address the problem)
• Customer status: current customer (which tier?), churned customer, prospect, never evaluated

This slide tells the audience whether the sample is representative of the target market or biased toward a particular segment. If all 20 interviews were with enterprise customers and the product is being evaluated for an SMB expansion, that needs to be surfaced.

Slide 4: Key Themes

Synthesize the patterns that emerged across interviews, ranked by frequency and intensity.

For each theme:

• Theme name and one-sentence description
• How many participants expressed it (absolute number and percentage)
• Representative quotes — two or three verbatim quotes that illustrate the theme with specificity and emotional weight
• Whether the theme was consistent across segments or concentrated in a particular type of customer

The difference between reporting and synthesis: Reporting: "Several customers mentioned that onboarding takes too long." Synthesis: "Onboarding friction was the most frequently cited source of churn risk. 14 of 18 customers mentioned onboarding unprompted. The specific pain was the requirement to manually configure integrations before the product could deliver any value — a step that took customers an average of 3 days and required IT involvement they had not anticipated. Three customers had considered canceling during this period."

The synthesized version is actionable. The reported version is a data point that requires the audience to do the work the researcher should have done.

Slide 5: Pain Point Ranking

Rank the problems discovered by their size and urgency.

Rating framework:

• Frequency: What percentage of participants mentioned this problem?
• Severity: How much does this problem cost the customer in time, money, or strategic opportunity?
• Urgency: Are customers actively looking for a solution, or is this a latent problem they have adapted to?
• Tractability: Is this a problem the product can actually solve, or is it outside the product's domain?

| Pain Point | Frequency | Severity | Urgency | Tractability | Priority | |---|---|---|---|---|---| | Manual integration setup | 78% | High | High | High | 1 | | No mobile access for field teams | 61% | High | Medium | High | 2 | | Reporting requires Excel export | 56% | Medium | Medium | High | 3 | | Inability to bulk upload data | 44% | Medium | Low | High | 4 |

This framework converts qualitative research into a structured prioritization input. It does not make the prioritization decision — that requires weighing customer needs against engineering cost, strategic positioning, and competitive dynamics — but it provides the customer-side evidence that should inform that decision.

Slide 6: Jobs to Be Done

Summarize what customers are trying to accomplish — the underlying goal behind the feature requests and pain points.

Jobs-to-be-done (JTBD) framing is more durable than feature requests because it captures the intent rather than the proposed solution. "Customers want a mobile app" is a feature request. "Customers need to capture field observations at the point of occurrence without returning to a desktop environment" is a job to be done — and it might be solved by a mobile app, or by SMS input, or by integration with an existing field tool, depending on the customer context.

For each distinct job identified in the research:

• State the job: "When [situation], I want to [action], so I can [outcome]."
• Note which customer segment this job belongs to most
• Indicate whether the current product does this job, does it poorly, or does not do it at all

Slide 7: Opportunity Sizing

Estimate the market opportunity for each high-priority pain point.

This does not need to be a financial model — it needs to be enough quantification that the team can compare opportunities.

For each opportunity:

• How many customers or prospects have this problem (total addressable count)
• What is the current cost of the problem (time, money, workaround investment)
• What could a solution charge (incremental ACV, new tier, or retention value from reducing churn risk)
• What is the rough revenue opportunity if this problem is solved for the target segment

Opportunity sizing moves the discovery output from "things customers want" to "things worth building." Not all customer problems are worth solving — the question is which ones represent sufficient commercial opportunity to justify the investment.

Slide 8: Recommended Direction

State a clear recommendation with a rationale and the evidence that supports it.

Format: "Based on this research, we recommend [specific action] because [evidence from the research]. The primary risk in this recommendation is [risk], which we would mitigate by [approach]."

Include:

• The recommended product or strategy direction
• The three strongest evidence points that support it
• What this recommendation would require (roughly) to execute
• The key assumption that, if wrong, would change the recommendation
• What additional validation is needed before committing to this direction

A discovery presentation that ends with "here are all the things we heard" has not done its job. The job is to reduce uncertainty about a decision. End with a recommendation that makes the decision easier — even if the audience ultimately decides differently.

---

Common Discovery Presentation Mistakes

Too many quotes, not enough synthesis. Quotes are evidence. Synthesis is the finding. A deck of 30 quotes with no pattern analysis is raw data, not a usable research output.

Skipping the methodology. An audience that cannot evaluate the quality of the evidence cannot evaluate the quality of the findings. The methodology slide is not optional.

No recommendation. A discovery presentation that describes findings without recommending a direction puts the synthesis burden on the audience — which defeats the purpose of the research.

Confusing frequency with importance. A pain mentioned by 80% of customers may be less important to solve than a pain mentioned by 20% of customers if the 20% are the largest customers or the highest-urgency buyers. Frequency is one input to prioritization, not the only input.

---

slide-deck.io generates customer discovery presentation templates with research methodology slides, persona synthesis frameworks, pain point ranking matrices, jobs-to-be-done layouts, and opportunity sizing tables — structured for product and strategy team decision-making. Export to PowerPoint or share as a link with cross-functional stakeholders.

Create your customer discovery presentation