A pitch deck should show where the evidence stops
A useful pitch deck marks the boundary between current evidence and the next experiment.
A pitch deck should show where the evidence stops.
I noticed this while revising a seven slide Demo Day deck for Insuveo, the insurance product I am exploring. The deck described a problem I have been studying: work fragmented across email, calls, WhatsApp, PDFs, and spreadsheets, with slower decisions and fragile handoffs. It then moved through the product idea, early evidence, a first commercial milestone, and the team. The sequence looked coherent even though the underlying work remained less settled.
I have active conversations in the insurance industry. Converting those conversations into a design partner pilot has been difficult. I am also exploring cofounder fit and whether senior advisors in India could help open the right doors. Each item belongs in the story, but each carries a different amount of proof.
A clean story can hide the seam
A pitch deck compresses a complicated company into a few slides. Compression is useful because it forces a founder to decide what matters.
It can also remove the seams between what happened and what is expected to happen.
A conversation can become “market validation.” A proposed pilot can look like traction. A person who may help can appear to be part of the team. None of these changes require an explicit lie. The structure and visual confidence of the deck can do the work quietly.
AI makes this easier. I can generate alternatives, tighten language, improve the layout, and produce a polished narrative quickly. The quality of the artifact may rise faster than the quality of the evidence behind it, which makes the gap part of the communication problem.
Future tense deserves a place
An early company has to speak about the future. The product and distribution path are still being discovered. Removing every unproven statement would leave very little to explain, so the boundary has to remain visible.
The deck can say that conversations suggest a recurring coordination problem. It should also make clear that those conversations have not yet produced a running pilot. A short design partner engagement can be shown as the next commercial milestone while remaining a hypothesis. An advisor strategy can be presented as a route I am exploring, without implying that the advisors already exist.
The tense matters because it tells the reader how to evaluate the claim. “We observed” asks whether the evidence is representative. “We plan to test” asks whether the experiment is well designed. Blending the two lets ambition borrow certainty from the past.
I want the deck to carry both. The company needs a direction, and the audience needs an honest view of the distance.
Every slide should create a question
A useful slide does more than state a belief. It points toward the evidence that would change it.
The problem slide raises a practical question: can operators show repeated cases where fragmented communication causes avoidable work? The solution slide raises another: can the proposed workflow run beside existing systems with human approval and produce a measurable improvement? If I cannot describe the next test, the claim may still be too broad.
This turns the deck into a work queue. The missing evidence becomes visible enough to guide the next conversation, product decision, or pilot. A vague ambition such as “transform insurance operations” becomes less useful than a narrow claim that can meet a real case.
The same principle applies to AI product design. A generated answer should preserve the boundary between source material and inference. A founder's narrative should preserve the boundary between evidence and projection. In both situations, fluency can make uncertainty disappear unless the system deliberately keeps it present.
Output is not the same as movement
I have been thinking about why AI assisted work can feel busy without creating a corresponding sense of progress. More research, drafts, messages, and slides are visible. The outside world may remain unchanged.
A pitch deck can sharpen this distinction. An active conversation is movement, but it is in a different state from an agreed pilot. A prototype exists in a different state from a workflow someone has used. These differences should survive the compression of the story.
That does not make preparation meaningless. Better communication can produce a better decision. It becomes valuable when it helps me see which decision or commitment is still missing.
I have not established traction or proved the Insuveo workflow. The deck contains a product thesis and a path I intend to test. Revising it made the remaining distance easier to see, which is useful evidence in itself as long as I do not confuse clarity about the work with completion of the work.