Back
3 min read

The One Thing I Learned About Speaking Under Pressure

The One Thing I Learned About Speaking Under Pressure


The One Thing I Learned About Speaking Under Pressure

I’ve sat through hundreds of pitch meetings. Some went great. Others… I still cringe thinking about.

The difference wasn’t preparation. I prepared for all of them.

The difference was how I handled the unexpected question. The one that derailed my mental script. The one where my brain went blank.

Matt Abrahams calls this “spontaneous speaking.” I call it the thing that separates good founders from stressed ones.

Key Takeaways

  • Anxiety spikes when you lose your train of thought — the fix isn’t memorising more, it’s having a structure to land on
  • A simple “What I’m hearing is…” buys you three seconds of processing time without looking lost
  • The best answers in my experience come from admitting “I need to think about that” — customers respect honesty more than a fumbled guess

Why Your Brain Freezes (And What Actually Helps)

When someone asks you something you didn’t expect, your brain treats it like a threat. Cortisol spikes. Blood leaves the prefrontal cortex. Suddenly you can’t remember your own product’s pricing.

Most advice tells you to “breathe” and “stay calm.” That’s like telling someone in a burning building to “relax.”

What actually works: a fallback structure.

Abrahams teaches a simple one: problem → solution → benefit. I’ve been using a variant for years in demos and investor calls. When I get a curveball, I say:

“That’s a great question. The short answer is X. The longer context is Y. Does that cover what you needed?”

It’s not clever. It’s reliable. And reliability under pressure is worth more than eloquence.

The Real Insight (Not in the Video)

Abrahams focuses on technique. But the deeper issue for founders is ego.

We want to sound smart. We want an answer immediately. So we rush, fumble, and dig ourselves into a hole.

I’ve started telling my team: “If you don’t know, say you don’t know. Then ask a clarifying question.”

On a recent customer call, someone asked about a compliance feature we haven’t built yet. Old me would have danced around it. New me said: “We don’t support that today. But tell me what you’re trying to solve — might be something we can build or work around.”

They appreciated the honesty. We found a workaround. They’re still a customer.

Practical Takeaway

You can’t script every conversation. But you can script your recovery.

Write down three fallback structures that feel natural to you. Something like:

  1. Acknowledge (“Good question.”)
  2. Frame (“The main thing to know is…”)
  3. Check (“Does that help?”)

Practice them in low-stakes situations — team standups, casual chats. By the time a VC or a big customer throws a curveball, your response won’t be a scramble. It’ll be muscle memory.

That’s the only preparation that matters for the moments you can’t prepare for.