A client readout should make the recommendation easier to evaluate. The agency’s work is to connect the evidence to the client’s decision, including what remains uncertain and what should happen next.
What should the presentation contain?
Use three levels: a concise decision summary, a working presentation with evidence, and accessible method and source material. The summary should state the proposed action and why it follows from the study. The working slides should make the reasoning inspectable. The supporting material should let a researcher check the sample and source claims.
Do not hide a material limitation in an appendix. If recruitment, small segments, or retrospective recall changes how the client should act, include that limit beside the recommendation.
How should agencies use quotes and counts?
Choose quotations that illustrate the pattern faithfully, including relevant exceptions. Check each quotation against its transcript and maintain the link to the source. A vivid anecdote may be useful without being typical; label it accordingly.
When showing counts, name the denominator and explain what was counted. A chart of coded mentions differs from a chart of participants. If one person can mention several themes, percentages need not sum to 100%. Do not treat a qualitative convenience sample as a population estimate solely because it contains many interviews.
What can you learn from the public sample?
The User Intuition preview contains a 43-participant Walmart shopper example with two playable calls, transcripts, a report, and a 15-slide presentation. Review the path from a participant’s answer to a finding and then to an implication. Inspect the method and limits as carefully as the headline.
Download the sample presentation as a PDF to review it with your delivery team.
Use it with your delivery team: listen to a call, identify the claim it supports, and discuss what additional evidence would be needed before making a client recommendation. This is more useful than evaluating slide polish alone.
Who owns the recommendation?
Agencies, consulting firms, and research teams can preserve their methodology on User Intuition, use their own sample or the 4M participant panel, and review recordings and evidence-linked findings. Researchers still decide whether a theme is meaningful, whether contradictory evidence changes the conclusion, and how the result fits the client’s context.
Before presenting, distinguish the participant evidence, your interpretation, and the proposed action. A client should be able to disagree with an inference without losing access to the observations behind it.
How should delivery work be scoped and priced?
Include evidence review, interpretation, presentation preparation, and revision rounds in the agency fee. Platform interviewing is a separate cost basis. Thirty quality Starter voice interviews cost $900 with your sample or $1,800 with standard panel recruitment, with no monthly fee. Specialist recruiting is quoted separately, and incentives arranged for your own participants are additional.
Use the proposal template to agree outputs and approvals, and the capacity guide to reserve review time. The final readout is ready when its claims are supported and its limits are clear, not merely when all planned interviews have finished.
Build one claim from interview to recommendation
Consider an illustrative shopper who says they could not find an item and asked a member of staff for help. The observation is that this person reported a navigation problem on that trip. A possible interpretation is that wayfinding contributed to friction. A recommendation to redesign all store signage goes further and needs additional support. Keeping these steps separate makes it easier for the client to evaluate the reasoning instead of treating a vivid account as a complete business case.
Look for other accounts that support or challenge the interpretation. Did shoppers in a similar context find the item easily? Did the problem occur after a layout change? Was the item actually unavailable? The relevant distinction may be navigation, inventory, or product recognition. The analysis should preserve those alternatives until the evidence supports narrowing them. A presentation that combines them into one convenient theme can obscure the action the client should take.
Write the slide’s claim at the level the study supports. It may be a recurring problem in the interviewed sample, a hypothesis worth testing, or an isolated event that illustrates a possible failure. Each can be useful when labeled accurately. The recommendation can then specify a next step proportional to that evidence, such as checking an operational record or testing a targeted change.
Select quotations without turning them into decoration
A useful quotation is specific, relevant to the claim, and faithful to its original context. Review the question that prompted it as well as the answer. A participant’s agreement after a leading prompt has a different evidentiary role from an explanation they offered spontaneously. Preserve that distinction when deciding how prominently to feature the quote.
Do not select only the most polished language. A less articulate answer may represent an important perspective, and an exception may reveal the condition under which a recommendation fails. Choose enough source material to explain the pattern and its boundaries. There is no fixed number of quotations that establishes prevalence; use the underlying analysis to support a prevalence claim.
When editing a quotation for readability, keep a trace to the original and avoid changing its meaning. If an excerpt omits material that changes the interpretation, choose a different excerpt or explain the context. The client should be able to inspect the source rather than relying entirely on the agency’s selection.
Design charts for the actual evidence
Use a chart only when it helps explain a comparison the research supports. If the data describes the interviewed sample, label it that way. State whether a number counts people, mentions, coded moments, or completed answers to a particular question. Different denominators can be legitimate, but readers should not have to infer why they differ between slides.
For segment comparisons, show the relevant bases and consider whether the groups were recruited and interviewed comparably. A dramatic percentage difference in two very small groups may be a prompt for further research rather than a stable market pattern. Include that limitation beside the visual. Avoid using a polished chart to imply more precision than the study provides.
Design separate views when the presentation room and the detailed evidence review have different needs. A live readout can use a clear headline and a simple visual, while the supporting document contains coding notes and source detail. The two versions should remain consistent about the claim and its limits. Simplification should remove visual clutter, not the qualification that makes the conclusion accurate.
Prepare the client conversation around decisions
Agree the purpose of the readout before creating slides. Is the client choosing a proposition, deciding what to investigate next, or aligning stakeholders on a problem? Organize the discussion around those decisions. A chronological account of every research activity may demonstrate effort while leaving the client uncertain about what to do.
Allow time for the client to challenge interpretations. A useful question is which part of the evidence or reasoning would need to change for them to reach another conclusion. This keeps the discussion connected to the study instead of turning it into a contest of opinions. Record unresolved questions and distinguish requests for clarification from requests for new research.
End with agreed next steps, owners, and the evidence needed for any remaining decision. If the study did not resolve the original question, say why and explain the most useful follow-up. A clear account of uncertainty can still help the client allocate effort; overstating a conclusion creates a more serious delivery problem than acknowledging the study’s limits.
Use a repeatable editorial review
Have a colleague review the readout against the approved brief. Check whether each major learning goal is addressed, whether the recommendation follows from the evidence, and whether important exceptions are visible. Verify quotation sources and chart bases. Read the executive summary on its own to confirm that it does not make a stronger claim than the detailed analysis.
Use a brief review record rather than an elaborate score. Note the claim, the issue, the source, and the change needed. Once those changes are made, check the affected slides again and confirm that the summary still matches. This creates an inspectable quality process without turning every project into a separate reporting exercise.
After delivery, ask which findings informed action and which required more explanation. Use that feedback to improve the next readout, while recognizing that client adoption also depends on factors outside the presentation. The aim is to improve clarity, traceability, and decision usefulness. It is not to infer research quality solely from whether the client accepted the recommendation.
Inspect the workflow before your next client brief
Hear actual calls and see the sample presentation from a 43-participant Walmart shopper example. The two call recordings, transcripts, and 15-slide readout let you assess probing depth, traceability, and how study limits are communicated. The presentation download is a PDF.
Use the agency research page for client-delivery workflows, the consulting page for engagement research, or the insights-team page for internal research programs. Bring one real brief to the evaluation. Agree the decision, sample requirements, guide, cost basis, and review standard before launching.