How to Pitch Your Startup

Lecture overview

Hale focuses on making a startup understandable before trying to make it impressive. He recommends conversational language, a direct explanation and descriptions that listeners can picture. His examples show how jargon, vague claims and missing information get in the way. He also discusses when comparisons to familiar businesses are useful and why a concise explanation matters.

The guide below adds original PitchPolar examples, editing techniques and practice exercises. These are applications of the topic, rather than quotations or a transcript of the talk.

01 Start with a picture people can understand

A listener needs something concrete to imagine. Give them a customer, a task and a product before introducing the bigger ambition. Otherwise, they may spend the rest of your pitch trying to work out what the company actually does.

PitchPolar example — fictional business:

A vague opening: “We are transforming operations with an intelligent, integrated platform.”

A clearer opening: “We make scheduling software for independent dental clinics. Receptionists use it to fill appointments when patients cancel.”

The second version gives the listener a starting point. They can imagine a receptionist, an empty appointment and a useful tool. It leaves room for follow-up questions about adoption, pricing and the size of the opportunity.

Try this: underline the words that identify your customer and your product. If you cannot find them, rewrite the opening before adding more detail.

02 Make the problem observable

A broad problem statement can sound important while revealing very little. Describe what happens today, who deals with it and where the friction occurs.

For the fictional scheduling company, “clinics have inefficient workflows” is difficult to evaluate. “When someone cancels, the receptionist calls patients one by one to fill the slot” identifies a process that a listener can understand and question.

Do not invent customer numbers to make the story stronger. If you have interviewed customers, separate what they told you from what you have measured. A plausible explanation is still a hypothesis until you have evidence.

Try this: write one sentence describing the customer's current workaround. If the workaround is unclear, your problem statement may need more customer research.

03 Explain the product through an action

A list of features rarely helps a new listener understand how the product works. Describe what a person does with it and what changes afterward.

For example: “A receptionist adds a cancelled appointment, and the software offers that time to patients on the waiting list.” This gives the audience an action to follow. You can then explain the technology if someone asks how matching or messaging works.

Editing check: replace a sentence about your architecture with a sentence about the user's experience. Keep the technical detail available for the discussion that follows.

04 Use comparisons carefully

A familiar comparison can save time, but it can also send someone in the wrong direction. Before using one, ask what assumptions the listener will bring with it: a marketplace, a subscription product, a delivery operation or something else.

If you describe a business as “a marketplace for laboratory equipment,” be ready to explain who buys, who sells and what your company does between them. A comparison that needs several exceptions may be less useful than a plain description.

Try this: write the pitch with and without the comparison. Ask someone which version gives them a more accurate understanding of the product.

05 Cut words without cutting meaning

Shortening a pitch should make it easier to understand. Deleting the customer, product or essential context can make a sentence shorter but less useful.

Work through three editing passes:

1. Remove claims that do not explain anything, such as “revolutionary” or “next-generation.”
2. Replace abstract phrases with concrete nouns and verbs.
3. Remove background information that the listener does not need yet.

Read the result aloud. If a sentence is difficult to say naturally, it will probably be difficult to follow in a conversation. Aim for an opening that sounds like something you would say to a thoughtful person who has just asked what you are building.

06 Test understanding before polishing delivery

Confidence and presentation style cannot fix an explanation that people misunderstand. Test the content first.

Ask someone outside your company to listen once. Then ask them to describe the customer, the product and the problem in their own words. Avoid correcting them immediately; their first answer tells you what your explanation actually communicated.

If they remember the industry but not the product, the opening may be too broad. If they remember a feature but not the customer, the use case may need to appear earlier. Revise the relevant sentence and test again.

Your next-pitch checklist

• Can someone identify the customer and product after hearing the opening once?
• Have you described a problem or workaround they can picture?
• Does the product explanation include a concrete user action?
• Are any comparisons accurate enough to help?
• Have you removed claims that add no information?
• Have you tested the explanation with someone outside the team?

Use the checklist to prepare a conversation, rather than trying to squeeze the entire company into the opening. Keep evidence, commercial details and technical answers ready for the questions that follow.

Original video

Watch Kevin Hale's lecture on YouTube. The YC Startup Library page provides the original lecture and transcript.