Build an Investor Presentation Around Evidence, Not Features

An early-stage investor presentation explains why a customer needs your product, why your team can build a durable business around it, and what new capital will prove. The deck supports that argument; it is not a substitute for it.

For technical founders, the hard part is connecting the mechanism to the commercial result. An architecture diagram can explain how a system works without explaining who will buy it. A market-size slide can suggest opportunity without showing how you will reach the first customer.

Build the presentation around that connection. Lunera’s stated focus is foundational software, including developer tools, data infrastructure and applied AI, with an emphasis on founder insight and learning from customers rather than polished scale metrics at the earliest moments.

A practical investor presentation structure

Use the following as a working structure, not a required slide count. Combine sections when the argument is simple; separate them when a consequential claim needs evidence. Y Combinator’s seed-deck guidance similarly prioritizes clarity and concision, covering the problem, solution, traction, insight, business model, market, team and funding request.

Section	Question to answer	What to show
Company	What do you build, and for whom?	A plain-language description naming the customer and outcome.
Customer problem	What fails in the current workflow?	The task, current workaround and cost of leaving it unresolved.
Product	How does your solution change that workflow?	One concrete input-to-outcome example, with a focused demo if useful.
Why now	What changed to make this possible or necessary?	A specific technical, economic or customer change—not simply a growing category.
Evidence	What have you learned from actual use?	Dated usage, retention, paid adoption or customer-discovery findings, with definitions.
Technical edge	Why can you deliver a better result?	The mechanism, relevant comparison and conditions where the advantage holds.
Market and distribution	Who buys first, and how will you reach them?	A narrow initial segment, buyer, acquisition route and credible expansion path.
Alternatives	Why would a customer switch?	Direct competitors, internal builds and doing nothing, compared on meaningful trade-offs.
Business model	How does adoption become a viable business?	Pricing, payer, delivery costs and assumptions still being tested.
Team	Why are you equipped to solve this?	Relevant technical work, customer access and complementary capabilities.
Financials and ask	What does the round enable?	Current cash and burn, the amount sought, spending assumptions and measurable milestones.

Sequoia’s pitching guide explicitly includes current alternatives, why now and whether the solution will endure. Those questions are useful checks against a presentation that is mostly a feature tour.

Make the technical edge testable

Replace “proprietary technology” with an explanation a reader can challenge.

For a hypothetical data-infrastructure product, the argument might be: checking schema compatibility before deployment catches a class of breaking changes that runtime monitoring detects only after release. The commercial benefit to demonstrate is fewer disruptions caused by those changes—not “better data” in the abstract.

Then show the limit. Which changes can the system detect? Which environments does it support? What is the integration burden? If you have benchmark results, state the baseline, workload, hardware, sample size and measurement method. Distinguish a lab result from production evidence.

Keep the core mechanism in the main deck. Put detailed architecture, benchmark methodology and dependency risks in an appendix. The investor should understand both the advantage and what could erode it, including reliance on another platform’s roadmap.

Separate traction from potential

Use evidence that matches the claim:

• Customer pain: describe observed workflows and costly workarounds; distinguish interviews from purchase commitments.
• Adoption: separate sign-ups, activated users and recurring production use.
• Retention: define the cohort, qualifying activity and observation period.
• Revenue: distinguish recurring contracts from pilots and one-off services; separate contracted amounts from cash collected.
• Distribution: show how customers arrived and whether the route can be repeated.

If you are pre-revenue, say so. Present what you have learned and the next experiment rather than disguising an immature business as a scaled one. A customer logo alone does not tell the reader whether the relationship is an interview, trial, pilot or paid deployment.

Connect the funding request to a decision

“Hire engineers and grow sales” describes spending, not progress. Explain which uncertainty each expense helps resolve: production reliability, willingness to pay, repeat usage or a repeatable acquisition route.

Include the cash assumptions behind the plan. For applied AI, for example, model inference, retries, human review and support—not just the model’s headline unit price. Label projections separately from historical results and show how slower customer conversion changes runway.

For a fuller view of what follows the presentation, see the VC process from first pitch to funded capital.

Edit for the way the deck will be used

For a live meeting, use short headlines and one main idea per slide. For a deck sent ahead, add enough context to make it understandable without narration. Keep the underlying claims consistent across both versions. YC’s design guidance emphasizes legibility, simplicity and making the point explicit.

Before sending, ask someone unfamiliar with the product to explain the customer, the advantage and what the round will prove. If they cannot, revise the argument before polishing the slides.