How Do I Make a Startup Pitch Deck for a First Meeting?

Read online

Open Note: A first-meeting deck is not a compressed data room. Its job is to make the company understandable, show why the conversation matters now, and give the investor a clear question to evaluate.

Short answer: Build a startup pitch deck for a first meeting around the customer, problem, product, evidence, market, distribution, competition, team, financing plan, and largest risk. Lead with a specific company story, not a slogan. Use the fewest slides that support the decision, define every important metric, and distinguish actual performance from forecasts. The deck should invite a useful conversation; it should not pretend that uncertainty has disappeared.

What the question is really asking

“How do I make a pitch deck?” often means “How do I decide what an investor needs to know first?” Start with the meeting’s job. A first conversation is usually about fit and whether there is enough evidence to continue. It is not full diligence and it is not a promise of funding.

Your deck should answer three questions quickly: what is happening in the company, why it matters, and what this financing would make possible.

Open with the customer and change

The first slide should name the customer, the problem, and the company’s solution in plain language. Avoid a sentence that could describe hundreds of startups. “Software for businesses” is not a company story. Explain what the customer does today and what changes after adopting the product.

Add stage, geography, and business model when they materially affect the interpretation. A healthcare company selling through hospitals needs a different frame from a consumer product with self-serve distribution.

Show the problem and why now

Describe the costly or urgent job the customer is trying to complete. Use customer evidence, workflow detail, or a dated change in the market. A large statistic is not a problem statement by itself.

Explain why the timing matters: a new regulation, technology, behavior, cost structure, or distribution channel. If the timing is a hypothesis, label it as one and name the evidence you are gathering.

Make the product visible

Show the smallest product story that makes the solution concrete. A workflow, screenshot, or before-and-after sequence is often better than a feature list. Connect the product to the customer’s outcome and explain what is already working versus what is planned.

Do not hide implementation complexity. If onboarding, integrations, or regulation constrain growth, name the constraint and how the company is addressing it.

Put the evidence in context

Choose two or three metrics that match the stage: paid customers, usage, retention, revenue, conversion, gross margin, pilots, or a specific customer outcome. Define the period, cohort, and denominator. State the limitation next to the claim.

Separate actuals from forecasts. If you show next year’s revenue, list the assumptions that drive it and identify the one most likely to fail. Investors generally learn more from a transparent model than a precise-looking hockey stick.

Explain market, distribution, and competition

Start the market slide with the company’s reachable wedge and how it expands. Tie the claim to customers, pricing, frequency, or a credible channel. Then explain how customers find, evaluate, and buy the product.

Describe the alternatives customers use, including manual work and doing nothing. State why customers switch and what mechanism creates an advantage. If the advantage is still being tested, make that part of the story.

Team, raise, and risk

Connect the founding team to the customer and problem. Name the capability the company still needs to add. For the raise, state the amount, expected runway, and milestones it funds. The right raise is the amount that can reach the next meaningful proof point, not necessarily the largest available round.

Name the largest risk and the experiment or milestone that will reduce it. A risk slide can increase trust when it shows that the team knows what would change its mind.

Design for the conversation

Keep one idea per slide, use readable type, and remove decorative claims that compete with evidence. Add the date and version. Make sure charts have labels and sources where appropriate. Test the deck with someone who does not know the company and ask what they think the business does, for whom, and what happens next.

Illustrative example

A founder creates a 13-slide deck for a seed meeting. It opens with a workflow problem for independent clinics, shows a product path, reports 18 paid clinics and 72% six-month logo retention, and identifies implementation time as the next constraint. The raise funds a repeatability test across two regions. These figures are illustrative only.

Founder decision

Before sending the deck, write the meeting question it should help answer and remove slides that do not support it. Use the Investor Meeting Question Bank to prepare for the discussion behind the slides.

When not to follow this advice

Do not build a new deck when a current, accurate version answers the investor’s question. If the company is too early for a credible financing story, use a short context memo and focus on the milestone that would make the next conversation more useful.

Related reading

Continue with Should I Send a Pitch Deck Before an Investor Meeting? and What Happens in a First VC Meeting?.

Disclosure: This is general educational information for founders, not legal, tax, accounting, investment, or financial advice. Illustrative numbers are examples only.