You have sixty seconds. Maybe less.

The investor leans back. The prospect glances at their phone. The senior leader checks the time. Your window is closing before you've said anything that matters.

Most people respond by speeding up. They cram features, credentials, and context into a verbal fire hose. The listener zones out by second twelve.

The Real Problem With Short Pitches

The issue is not that sixty seconds is too short. The issue is that you are treating your pitch like a data dump instead of a story.

Stories have structure. They create forward motion. They make the listener lean in because they want to know what happens next. A good sixty-second story does not feel rushed. It feels inevitable.

But most people skip the structure entirely. They open with background. They bury the problem. They explain the solution before anyone cares. By the time they get to the part that matters, the listener has already moved on.

Why the Classic Advice Falls Short

You have been told to "start with why" or "lead with the problem." That is not wrong. But it is incomplete.

Leading with a problem is not the same as building narrative tension. Saying "companies waste millions on bad hires" is a fact. It does not pull the listener forward. It does not make them feel the stakes. And without stakes, there is no story. Just information they can ignore.

The Hook-Tension-Resolution-Point Framework

This is the structure that turns a pitch into a sixty-second story. Four parts. Each one has a job. Miss one and the story collapses.

Part One: The Hook

Your first sentence is not context. It is not a warm-up. It is a disruption.

The hook creates a gap between what the listener expects and what you just said. It raises a question in their mind before you answer it. Examples: "We turned down our biggest client last month." "Three years ago, this company did not exist. Today we're in eleven countries." "Most sales teams are training the wrong skill."

Notice what these do not do. They do not explain. They do not justify. They create a micro-mystery. The listener wants to know why you turned down that client. What changed in three years. Which skill is wrong.

Vocal delivery for the hook: Moderate pace. Firm but not loud. Let the sentence land before you continue. Pause for one full breath after the hook. That pause is where the question forms in their mind.

Part Two: Tension

Tension is where you build the stakes. This is not "here is the problem." This is "here is what happens if the problem is not solved."

Tension makes the listener feel something. It connects the abstract problem to a concrete cost. If you are pitching a hiring tool, tension is not "bad hires cost money." Tension is "your best engineer just spent six weeks onboarding someone who quit. Now she is job hunting too."

Good tension is specific. It uses real numbers or real scenarios. It paints a picture the listener recognizes from their own experience. The goal is for them to nod internally and think "yes, I have lived this."

Vocal delivery for tension: Slow down slightly. Drop your pitch on the key cost or consequence. This is where you let the weight of the problem settle. Do not rush past this part. If you skip the emotional beat, the resolution will not land.

Part Three: Resolution

Now you deliver the shift. This is the "what we do" or "here is how it works" moment. But it is not a feature list. It is a mechanism.

The resolution explains how your solution eliminates the tension you just built. If the tension was "your engineer is wasting weeks on bad hires," the resolution is "we screen for actual on-the-job behavior in the first interview, so you know in twenty minutes instead of six weeks."

One mechanism. One sentence. Do not explain every feature. Do not list benefits. Just name the thing that solves the problem you made them feel.

Vocal delivery for resolution: Lift your energy. Not louder, but brighter. This is the turn in the story. Your tone should signal relief, possibility, momentum. If your voice stays flat here, the resolution will feel like another problem.

Part Four: The Point

This is your close. The point is not a call to action in the traditional sense. It is the so what that ties the story to the listener's world.

Good points reframe what just happened. They give the listener a lens to carry forward. Examples: "That's why we only work with teams ready to move fast." "If you're still hiring the old way, you're selecting for the wrong signal." "The companies winning right now are the ones who figured this out six months ago."

The point creates a fork. It implies a decision. It positions your listener on one side or the other. And it does this without being pushy.

Vocal delivery for the point: Return to your baseline tone. Grounded. Certain. No up-talk. No question mark in your inflection. This is a period, not a comma. The story is complete.

A Worked Example

Let's say you are pitching a leadership coaching program to a VP of Sales. Here is how the framework plays out.

Hook: "Your top rep just accepted a manager role. In six months, half her team will quit."

Pause. Let that land.

Tension: "She was great at closing deals. But managing people is a different skill set. She has no coaching training. No framework for hard conversations. So she either micromanages or disappears. Either way, her best people leave. And you lose the rep and the team."

Slow down on "micromanages or disappears." Drop pitch on "best people leave."

Resolution: "We train new managers in the eight conversations they will have in the first ninety days. Real scenarios. Real language. By week two, they are running one-on-ones that actually retain people."

Lift energy. Confident, clear.

Point: "If you are promoting people without training them to lead, you are creating the turnover problem you are trying to solve."

Firm close. Let it sit.

Total time: fifty-two seconds. And the VP is leaning in, not checking their phone.

The hook creates a gap between what the listener expects and what you just said. It raises a question in their mind before you answer it.

Common Mistakes to Avoid

Even when you know the framework, execution can break down. Here are the traps that kill sixty-second stories.

• Opening with context instead of a hook. "So, a little background on our company…" is not a hook. It is a sleep trigger. Start with disruption, not setup.
• Skipping the pause after the hook. The pause is not dead air. It is the moment the question forms. Without it, the hook has no power.
• Making tension abstract. "This is a big problem for companies" does not create stakes. "Your best people are leaving and you do not know why" does.
• Listing features in the resolution. The resolution is not a feature tour. It is one clear mechanism that solves the tension you built.
• Ending with a weak call to action. "So, yeah, let me know if you want to chat" is not a point. A strong point reframes the decision and lets the listener choose.
• Rushing the whole thing. Sixty seconds does not mean talking fast. It means choosing fewer, better words and giving each one room to breathe.

Your Next Step

You now have the framework. Hook, tension, resolution, point. You know what each part does and how to deliver it.

The next move is to write your own sixty-second story. Not in your head. On paper. Then say it out loud. Record it. Listen back. You will hear where you rush, where you bury the hook, where the tension falls flat.

Most people never do this work. They wing it. And they wonder why their pitches do not land. You are not most people.