What Your Elevator Pitch Needs: Every Component Annotated
An elevator pitch is not a short version of your deck. It is a different thing entirely. The deck proves your business. The pitch earns the next conversation.
Most founders write their elevator pitch the same way they write a deck slide: they lead with the company name, describe what it does, mention the market size, and hope the investor gets it. That does not work. Investors hear thirty pitches a week. What they are listening for is a specific sequence — and if the sequence is wrong, the rest does not matter.
Here is every component a pitch needs, in the order it should appear, with a real example annotated.
The complete pitch, annotated
Every highlight below is a component. If you can say your pitch and point to each one, the pitch is structurally sound.
Seven components. Sixty seconds. This is the template most funded founders use — not always in these exact words, but always with these seven pieces present.
Now let’s look at each one.
1. What you build
The first thing an investor needs to understand is the category. Not your company name. Not your backstory. The thing.
What it sounds like: “We build scheduling software” or “We run a marketplace for…” or “We make a device that…”
One sentence, no adjectives. “AI-powered next-generation” tells them nothing. “Scheduling software” tells them everything they need to place you.
The common mistake is leading with the company name. “Hi, I’m Sarah from BuildSync” is not an opening — it is a missed opportunity. Lead with what you built, then tell them who you are if they ask.
What to cut: origin stories, founding history, and mission statements. None of that belongs in the first line. The investor will ask if they care.
2. Who you serve
Immediately after saying what you built, name the customer. This is not “businesses” or “enterprises” — it is a specific person in a specific role with a specific problem.
What it sounds like: “for construction managers” or “for first-time home buyers” or “for solo accountants”
The narrower the customer definition, the more credible the pitch. Investors know that broad customers mean unclear product decisions. Saying “construction managers who oversee projects between $2M and $20M” is better than “construction companies.” Specificity signals that you have talked to real customers.
The common mistake: making the customer too broad to cover more of the market. This always backfires. An investor who funds construction software knows the space — vague customer definitions register as “they have not done the work yet.”
3. The problem
This is the most important part of the pitch, and the most consistently underwritten. Founders rush it because they want to get to the solution. Investors stay because the problem pulled them in.
What it sounds like: “who are losing $50K per project to avoidable delays”
Notice the specificity. Not “who struggle with project delays.” Not “who have inefficient workflows.” “$50K per project” is a number. It tells the investor the scale of pain, which tells them the ceiling for what someone would pay to fix it.
Three things a good problem statement has:
- A specific customer action or situation (losing money, spending time, missing deadlines)
- A number, if you have one
- The reason it is avoidable or unacceptable — not just that it happens
If you cannot put a number on the problem, put a scale on it. “Delays that get projects cancelled” is worse than “$50K” but better than “delays.”
The mistake: defining the problem in terms of your solution (“the problem is there is no good scheduling software”). The problem exists independently of you. Name it that way.
4. How it works
This is the shortest component. One sentence. The mechanism, not the feature list.
What it sounds like: “Our AI auto-adjusts timelines the moment anything slips”
What to include: the core action your product takes. What changes because your product exists.
What to exclude: the technology stack, the integrations, the roadmap, the API. None of it belongs here. The investor is not buying a product — they are buying a business hypothesis. They need to understand what happens, not how it happens.
The test: can someone repeat your mechanism sentence back to you after one hearing? If not, it is too complex. Cut it until it fits in one breath.
5. Proven impact
This is where most pitches go from plausible to believable. You have described a problem and a solution. Now you show that the solution works.
What it sounds like: “cutting project delays by 40%”
A percentage. A before-and-after. A result a real customer told you. The specificity of the number matters more than its size — “40%” is more credible than “dramatically” and “significantly” combined.
If you have no customer results yet, use a proxy: time spent in your beta, improvement in a controlled test, feedback from pilots. If you have truly nothing, move this component to after the traction component and lead with customers instead of results.
The mistake: softening the number. “Up to 40% faster” and “some customers report 40% fewer delays” both register as weaker than “40%.” State the number plainly.
6. Traction
Traction is proof that the problem is real and the market exists. It is not a brag — it is evidence for the investor’s thesis.
What it sounds like: “12 paying construction firms after 6 months in market”
Include: number of customers, whether they are paying, and how long you have been live. These three facts together tell the investor your velocity. “12 customers in 6 months” is a different signal than “12 customers in 3 years.”
If you have no paying customers, use engagement: active users, pilots, waitlist signups with context. If you have none of those, mention the closest validation you have — a strong LOI, a paid pilot, a notable design partner.
What not to say: “we are talking to several companies” or “we have a lot of interest.” These are not traction. They are intention. Only count it if money or commitment has changed hands.
7. The ask
End with the number. Not “we are looking for investment” — the number.
What it sounds like: “We’re raising $750K to double our sales team.”
Two parts: the amount and what it pays for. The amount anchors the conversation. What it pays for shows you have done the math and know what the money will do.
Keep it to one use of funds. Not “to hire engineers, expand sales, and run marketing.” One thing. The thing that matters most. Everything else is secondary and belongs in the follow-up meeting.
The mistake: no ask. Many founders end on traction and hope the investor offers. They will not. You asked for the meeting — ask for what you want in the meeting.
What YC asks in the full investor meeting
This anatomy covers your 60-second opener. Once it lands, you get the meeting.
Michael Seibel at Y Combinator wrote a seven-question framework for that meeting. His questions: what does your company do, how big is the market, what is your progress, what is your unique insight, what is your business model, who is on your team, and what do you want.
Three of those live directly in this pitch anatomy — the what-you-do (components 1 through 4 compressed), traction, and the ask. Market size, business model, and team belong in the meeting, once the investor is already engaged. The 60-second pitch is not the place to prove the business. It is the place to make them want to hear about it.
One question is worth pausing on: the unique insight. Seibel defines it as what you know about the problem that everyone else does not. For the elevator pitch, your problem number (“$50K per project”) is the shorthand version of that insight. In the meeting, you explain why you know it. The number gets the meeting. The insight earns the term sheet.
Michael Seibel’s full pitch framework at Y Combinator →
The sequence matters as much as the components
These seven components work in this order because each one sets up the next.
What you build → sets the category Who you serve → sharpens the category The problem → makes the category urgent How it works → proposes a solution to the urgent problem Proven impact → shows the solution works Traction → shows the market agrees The ask → tells the investor exactly what to do next
Change the order and the logic breaks. Putting the ask before the traction feels presumptuous. Putting the problem after the solution makes the pitch feel academic. The sequence is not a stylistic choice — it matches the investor’s mental model.
What to do with this
Write your pitch using this structure. Then say it out loud.
Most founders discover at this point that the written version and the spoken version are different things. On paper, the pitch reads cleanly. Out loud, the transitions are awkward, the numbers feel rushed, the problem statement takes twice as long as it should.
The only fix for this is repetition. Say it, record it, listen back. Hear what the investor hears. Tighten the one thing that sounds weakest. Record again.
That loop — script, record, listen, revise — is what separates a pitch that lands from a pitch that only makes sense to the founder.