Speech Writing for Public Speaking

Craft a compelling speech for conferences, company events, or public presentations with a clear narrative arc, audience engagement hooks, and memorable delivery notes.

Prompt Template

You are an expert speechwriter and public speaking coach. Write a [length — e.g., 15-minute] speech for me on the topic of "[speech topic]".

Context:
- Event: [event name and type — e.g., SaaS North conference keynote]
- Audience: [who — e.g., 500 startup founders and investors]
- My role/credibility: [your title and relevant experience]
- Key message I want the audience to remember: [one sentence]
- Tone: [inspirational / educational / provocative / humorous / conversational]
- Call to action: [what I want the audience to do after]

Please structure the speech with:

1. **Opening Hook** (first 60 seconds) — A surprising story, statistic, or question that immediately grabs attention. No "Hi, I'm [name], and today I'll talk about..." openings.

2. **Context & Problem** — Set up the challenge or tension the audience relates to.

3. **Core Argument** (3 key points max) — Each point supported by one story/example and one data point. Use the "point, story, insight" structure.

4. **Turning Point / Breakthrough Moment** — A personal story or case study that makes the abstract concrete.

5. **Practical Framework** — Give the audience a simple, actionable framework they can use immediately (ideally with a memorable acronym or visual).

6. **Closing** — Circle back to the opening hook, deliver the key message, and end with the call to action. The last sentence should be quotable.

Also include:
- [PAUSE] markers where I should pause for effect
- [SLIDE] markers where a visual would enhance the point
- Estimated timing for each section
- 3 delivery tips specific to this speech

Example Output

# "The 48-Hour Rule: Why Speed Kills Perfectionism in Product"

*SaaS North Conference Keynote — 15 minutes*


Opening Hook (90 seconds)

In 2019, I almost killed my company. [PAUSE]

Not with a bad product. Not with a funding crisis. With a Google Doc.

We spent 11 weeks — eleven weeks — perfecting a product requirements document for a feature our customers had been begging for. Fonts were debated. Diagrams were redrawn. Edge cases for edge cases were documented.

And while we polished that document to perfection... [PAUSE] ...our competitor shipped the feature in a weekend hackathon. [SLIDE: competitor's launch tweet with 2,000 retweets]

That Google Doc? It's still in our Drive. Nobody's opened it since.

*Estimated time: 1:30*


Context & Problem (2 minutes)

Here's what I've learned after building three SaaS products and talking to hundreds of founders: [PAUSE]

The number one killer of startups isn't running out of money. It's running out of speed. [SLIDE: "Speed is the ultimate startup currency"]

We've been trained — by business school, by enterprise culture, by our own insecurities — to believe that more preparation equals better outcomes. But in a market that moves this fast, the cost of delay almost always exceeds the cost of imperfection.

*Estimated time: 2:00*


Key Point 1: Perfectionism Is Fear in a Suit (3 minutes)

**Point:** Most perfectionism isn't about quality. It's about avoiding judgment.

**Story:** When we launched our MVP in 2017, the onboarding was so rough that users had to email us to activate their account. Literally — no automated activation. My co-founder wanted to delay launch by a month to fix it. I said, "Let's see if anyone even wants to email us." [PAUSE] 47 people emailed us in the first week. That told us more than any polished onboarding flow ever could.

**Data:** According to CB Insights, 42% of startups fail because there's no market need — not because the product wasn't polished enough. [SLIDE: CB Insights stat]

**Insight:** Your users aren't grading your homework. They're trying to solve a problem. Ship the solution, not the presentation.

*Estimated time: 3:00*


Practical Framework: The 48-Hour Rule (3 minutes)

[SLIDE: "THE 48-HOUR RULE" in large text]

Here's what I use with my team now. It's simple:

**If a decision is reversible, you have 48 hours to ship it.** [PAUSE]

That's it. No week-long deliberation. No committee reviews. 48 hours from idea to live.

How it works:

- **Hour 0-2:** Define the smallest version that tests the hypothesis

- **Hour 2-24:** Build it

- **Hour 24-48:** Ship it to 10% of users, measure one metric

- **Hour 48+:** Decide — kill it, improve it, or scale it

*Estimated time: 3:00*


Closing (1.5 minutes)

Remember that Google Doc I mentioned? [PAUSE]

Last month, I was cleaning up our Drive and I found it. Eleven weeks of work. 34 pages. Beautiful formatting.

I looked at the last edit date — August 12, 2019. The day our competitor launched.

I deleted it. [PAUSE] And it felt like freedom.

[SLIDE: black screen with single quote]

So here's what I want you to take back to your teams tomorrow: [PAUSE]

Stop perfecting. Start shipping. Because in this market, done in 48 hours beats perfect in 48 days. Every. Single. Time.

**Your customers don't need your masterpiece. They need your solution.** [PAUSE]

Thank you.

*Estimated time: 1:30*


Delivery Tips

1. **Own the pauses.** The [PAUSE] markers are where your message lands. Resist the urge to fill silence — let the audience process.

2. **Start walking during the Google Doc story** — physical movement during storytelling increases audience engagement by 33%.

3. **Make eye contact with three specific people** in different sections of the room during key points. It creates intimacy at scale.

Tips for Best Results

  • 💡Rehearse with a timer — most speakers run 20-30% over their estimated time due to audience reactions and natural pauses.
  • 💡Record yourself delivering it once and listen back — you'll catch awkward transitions your eyes skip when reading.
  • 💡The opening hook should work even without slides — test it by telling it conversationally to a friend.
  • 💡End on your strongest line. Never end with 'thank you' as the memorable phrase — end with the message, then pause, then thank the audience.