A demo day pitch should make the right person want a second conversation. Explain the company clearly, show the evidence you actually have, and give interested listeners an easy way to follow up.
Use the working outline, rehearsal sheet, and follow-up checklist below to prepare. The timing example is an editorial exercise, not a rule for any accelerator. Confirm your event's actual format before building the presentation.
Start with the event, not the slides
Ask the organizer about the time limit, audience, presentation setup, permitted materials, and how people can contact founders afterward. Also confirm whether questions are part of the presentation or happen separately.
Then write the job of your pitch in one sentence:
After hearing us, a relevant [investor, customer, or partner] should understand [specific company idea] and want to discuss [next step].
That is different from trying to explain the entire company. Keep the longer pitch deck for the next conversation.
Y Combinator's Demo Day presentation guide frames a short pitch as an invitation to learn more. Its guidance on clarity and practice is useful beyond YC. Event rules, however, come from your actual organizer, not from an older article.
Copy this demo day pitch outline
This six-part outline is a starting point. Combine or remove sections when your time limit requires it.
| Part | What the listener needs | Working sentence |
|---|---|---|
| Company | A plain-language explanation | We help [customer] do [job] with [product]. |
| Problem | A recognizable difficulty | Today, [customer] handles this by [approach], which creates [specific problem]. |
| Product | What someone actually uses | With our product, the customer [concrete action]. |
| Evidence | Current, supportable progress | We have tested or observed [result] during [period]. |
| Team and opportunity | Why this team and why this problem | Our relevant experience is [fact]; the opportunity we are investigating is [specific reasoning]. |
| Next conversation | A clear ask | We would like to meet [person or role] to discuss [topic]. |
Write these sentences before designing slides. If one cannot be explained plainly, a visual may hide the confusion rather than solve it.
A three-minute practice allocation
For an event that allows three minutes, try this initial rehearsal allocation:
| Segment | Practice allowance | What to keep |
|---|---|---|
| Company and customer | 20 seconds | Who it serves and what it does |
| Problem and product | 50 seconds | One customer situation and the product's response |
| Evidence | 45 seconds | The strongest substantiated progress |
| Team and opportunity | 35 seconds | Relevant experience and focused opportunity |
| Ask and closing | 20 seconds | The next conversation and contact route |
| Buffer | 10 seconds | Pauses and transitions |
This totals 180 seconds. It is not a recommended length for every event. If your slot is shorter, reduce the number of points rather than rushing through all six.
The first rehearsal may reveal that your best evidence belongs earlier. Use the outline as an editing tool, not a rigid script.
Worked example: a pre-launch company
The following is fictional and is not a Finta customer story.
We are building DispatchNote for small field-service teams that need to keep customer approvals connected to a job.
Today, an approval can sit in one person's inbox while the technician is waiting for the next step. Our prototype brings the email and the job's approval status into one working view.
We are testing that handoff with service managers. The product is not commercially launched yet, and we are using their feedback to decide which approval steps to support first.
Our founder has coordinated service operations and has experienced this problem directly. We would like to meet operators who can review the prototype and help us understand their approval process.
This version does not invent revenue or turn interviews into customers. It still gives an interested listener a specific reason to talk.
Rehearse for understanding, not memorization
Run the pitch aloud and ask a listener to answer four questions afterward: What do we do? For whom? What evidence did you hear? What do we want next?
Use this rehearsal log:
| Run | Actual duration | What the listener remembered | Confusing point | One change |
|---|---|---|---|---|
| 1 | Time | Their own words | A sentence, claim, or transition | The most useful edit |
| 2 | Time | Their own words | Remaining issue | Next edit |
| 3 | Time | Their own words | Remaining issue | Final check |
Check slides at the size and distance the audience will see them. Keep source details available in the follow-up materials, and make sure every displayed number has a period and supporting record.
Prepare a fallback if a demo or connection fails. You should still be able to explain the customer action and product scope without a working screen.
Prepare the follow-up before demo day
Have an approved one-pager, relevant materials, and a clear contact route ready. Decide who will respond to incoming interest and how you will record the context.
| Item | Ready means |
|---|---|
| Company introduction | Plain-language description and current contact details |
| Supporting materials | Correct version, appropriate access, accurate claims |
| Conversation capture | Name, organization, reason for interest, and agreed next step |
| Follow-up owner | One responsible person, not an unassigned team inbox |
| Next meeting | A useful topic, not just a generic request to reconnect |
In Finta, keep interested people, approved materials, notes, and next steps together. Ask Aurora to turn your own rehearsal notes into a revision checklist or draft a conversation-specific follow-up for review. You choose what to share and send.
Use the meeting-preparation workflow for the next conversation. The best outcome of a short pitch is not more slides. It is a relevant person who knows why they want to learn more.