
How to Craft a 30-Second Founder Intro That Sticks
How to craft a 30-second founder intro that sticks. Templates, examples, and the mistakes that make people tune out.
You have about 30 seconds before someone at a startup event decides whether to keep talking to you or politely excuse themselves. That window is your 30-second founder intro — and most founders blow it by either freezing up or dumping their entire company history into a stranger's ear.
A strong founder intro does three things: it tells people what you do, why it matters, and gives them a reason to ask a follow-up question. That's it. Everything else is noise.
What is a 30-second founder intro?
A 30-second founder intro is a short verbal pitch you deliver at networking events, conferences, and casual meetups. Unlike a formal pitch competition, it's conversational — designed to open a dialogue, not close a deal. The goal is to be memorable enough that the other person asks, "Oh, how does that work?" or "Who's using it?"
Think of it as a trailer, not the full movie. You're giving someone just enough to want to see more.
The 3-part formula for a founder intro that works
Every effective 30-second intro follows the same structure: problem, solution, proof. Here's how to build each piece.
1. The problem (one sentence)
Start with the pain point your company solves. Keep it specific and relatable. "Finding good startup events is hard" is weak. "Founders spend 6 hours a week just trying to figure out which events are worth attending" is strong — it has a number, a person, and a real frustration.
2. The solution (one sentence)
Describe what you do without jargon. If your intro includes the words "AI-powered," "synergy," or "disrupt," start over. Say what your product actually does in plain English. "We built a curated event platform that sends founders a weekly list of events in their city, filtered by stage and industry."
3. The proof point (one sentence)
Give one concrete detail that makes people lean in. This could be traction ("we have 5,000 subscribers across 20 cities"), a notable customer, a recent milestone, or a surprising data point. Avoid vague claims like "growing fast" or "great traction." Numbers beat adjectives every time.
30-second founder intro examples
Here are three real-world templates you can adapt. Replace the bracketed sections with your own details.
Template A: The data opener
"Most [target audience] waste [X hours/dollars] on [specific pain]. We built [product] that [specific action] so they can [outcome]. We've got [proof point] already using it."
Example: "Most early-stage founders waste 6 hours a week scanning Eventbrite and LinkedIn for relevant events. We built 47Hz — a curated platform that sends founders a Monday morning digest of startup events in their city. We're live in 20 cities with 5,000 subscribers."
Template B: The question opener
"Have you ever [relatable frustration]? That's the problem we solve at [company]. We [what you do], and right now [proof point]."
Example: "Have you ever shown up to a 'startup event' and it's just a sales pitch for a cloud provider? That's the problem we solve at 47Hz. We curate real founder events — meetups, demo days, pitch nights — and filter out the vendor stuff. We're in 20 cities now."
Template C: The contrast opener
"I used to [old behavior]. Now I [new behavior with your product]. Turns out [insight], so we built [product] for [audience]."
Example: "I used to Google 'startup events near me' every Monday and end up at random happy hours full of recruiters. Now I just check 47Hz — it's a curated weekly digest of real founder events in 20 cities. Turns out the hard part isn't showing up, it's knowing where to go."
Mistakes that make people tune out
After watching hundreds of founder intros at tech events for first-time founders, these are the patterns that lose people:
- Starting with your title. "I'm the CEO and co-founder of..." Nobody cares yet. Start with the problem, not your LinkedIn headline.
- Explaining the technology. "We use a proprietary ML pipeline built on transformer architecture..." You're at a networking event, not a technical interview. Describe the outcome, not the implementation.
- Being too vague. "We help businesses grow." What businesses? Grow how? Specificity is what makes an intro memorable.
- Talking too long. If your intro takes more than 30 seconds, you've lost them. Practice with a timer — most people are surprised how fast 30 seconds goes.
- No call to action. End your intro with something that invites a response. "We're looking for design partners in fintech" or "Have you tried finding events in your city?" gives the other person a way to engage.
How to practice your 30-second intro
A polished intro doesn't happen by accident. Here's how to build the muscle:
- Write it down first. Draft three versions using the templates above. Read them out loud. Cut anything that sounds awkward spoken.
- Record yourself. Use your phone's voice memo app. Play it back. You'll immediately hear the filler words ("um," "like," "basically") and the places where you ramble.
- Test it on a friend. Say your intro to someone outside your industry. If they can't repeat the gist back to you, simplify.
- Iterate after every event. After each networking event, ask yourself: did my intro spark a real conversation? If not, tweak one piece and try again. The two-problem technique can help you test different angles quickly.
When to use your intro (and when to skip it)
Your 30-second intro isn't a one-size-fits-all tool. Context matters.
Use it at: structured networking events, demo days and pitch competitions (the informal parts), conference happy hours, and any event where "What do you do?" is the first question.
Skip it at: casual social hangs where nobody's talking about work, deep 1-on-1 conversations that have already moved past introductions, and introvert-friendly networking events where the format is more relaxed and less transactional.
After the intro: what comes next
A great intro opens the door. What you do next determines whether that conversation leads anywhere.
The best founders flip the script immediately after their intro. Instead of waiting for compliments, they ask a question: "What are you working on?" or "What brought you to this event?" People remember conversations where they felt heard — not ones where they were pitched at.
And when the conversation ends, follow up within 48 hours. A quick message referencing something specific from your conversation beats a generic "great meeting you" LinkedIn request. The intro gets you in the door. The follow-up builds the relationship.
If you're building your pitch skills more broadly, check out our full guide on how to pitch at a startup event — it covers formal pitches, demo day prep, and the psychology of why some founders get funded from casual conversations.
Explore more from 47Hz
Level up your networking game with these guides:
Networking
- How to Pitch at a Startup Event
- The Two-Problem Technique for Networking
- How to Follow Up After a Conference Without Being Salesy
- Networking for Technical Founders