Situation First

pitch

The Five-Line Idea Brief

Published · 6 min read

Most ideas die not because they’re bad, but because they’re communicated in a way that makes the listener feel like they’re being talked at. They hear a paragraph of context, a few qualifiers, and then somewhere in the middle, buried under three hedging phrases, there’s actually a pretty good idea. But by that point, the listener has checked out.

The Five-Line Idea Brief is a discipline for stripping an idea down to what the other person actually needs to make a decision. Not to fully understand it. Not to feel the weight of the effort you put in. Just enough to say yes to the next conversation.

Who it’s for

Anyone who needs a peer, sponsor, or customer to react to an idea rather than receive it. This is for the person who keeps getting “interesting, let’s discuss more” as a polite way of saying nothing. It works for internal pitches, vendor conversations, job interviews, and investor calls equally — the format doesn’t know the audience. Only the content does.

When to use it

Why short briefs outperform long ones

A five-line brief forces you to answer a question most pitches never explicitly ask: what decision am I trying to earn here?

Not the final approval. Not the funding. Not the signed contract. What is the very next concrete step that, if it happened, would move this forward? That answer tells you which five lines matter.

Most long pitches fail because the presenter is trying to make the listener fully informed rather than appropriately confident. Those are different jobs. Full information requires a long document. Appropriate confidence requires precision.

Core framework

  1. Fact — One verifiable observation about the world right now. Not a prediction, not a vision, not a goal. A thing that is currently true that you can both point to. The more specific, the better: a number, a date, a name, a pattern.

  2. Insight — What that fact means for this conversation specifically. This is where most briefs fall apart — they state the fact and let the listener draw their own conclusion. Don’t. Tell them what it means for them: their team, their numbers, their credibility, their risk.

  3. Move — Your recommended action in one sentence. Even if you want to say “we should explore options,” commit to a recommendation. “Run an experiment” is a recommendation. “Do a two-week spike” is a recommendation. “Hire the consultant we met last week” is a recommendation. Optionality is for the appendix, not the brief.

  4. Proof — One credible signal. Not a deck. Not a report. One thing: a metric, a customer quote, a prototype screenshot, a competitive reference. The question to ask yourself: does this proof match their definition of credibility, or mine? A metric that impresses engineers may mean nothing to a CFO.

  5. Ask — The next step you want, stated explicitly, with a timebox. “Can we get approval?” is not an ask. “Can we schedule 45 minutes next week to review the business case?” is an ask. “Can I get two hours of engineering time to validate the approach before we commit?” is an ask.

Worked example

The bad version: “We should probably look at modernizing the data stack at some point. I know there have been some performance issues lately and the team is frustrated. It might be worth getting together to talk through options and understand what it would take.”

Nobody is going to do anything after reading that.

The five-line brief:

“Our checkout query latency doubled in the three weeks after Black Friday — we’re now averaging 4.2 seconds per request. (Fact.) At that speed, we lose approximately 15% of mobile users before the page loads — roughly $340k in abandoned revenue per quarter based on last year’s conversion data. (Insight.) I recommend we dedicate two engineers for one sprint to fix the hot path before we ship any new checkout features. (Move.) I’ve already traced the bottleneck to a single unindexed join — the fix is scoped, not a rewrite. (Proof.) Can you give me ten minutes Thursday to walk through the trace and get a go/no-go? (Ask.)”

That second version takes about 40 seconds to read. The listener knows exactly what the problem costs, what the fix is, why you’re confident it’s scoped, and what saying yes to the meeting commits them to. That’s a brief that earns the next conversation.

Common mistakes

Burying the ask. Putting the ask at the end of four paragraphs of context means the listener has already formed an opinion — usually “this is going to be a long meeting.” Put the ask first if you’re writing it in message form, or land it clearly as line five if you’re saying it live.

Hedging the move. “We might want to consider possibly exploring…” is not a recommendation. It’s noise. Pick a default. If you’re wrong, the conversation will tell you. If you’re right, you’ve just saved twenty minutes of hypothetical debate.

Using your proof, not theirs. Engineers find architecture diagrams credible. Finance finds P&L impact credible. Executives find a competitor already doing it credible. Know who you’re talking to before you choose your one proof artifact.

Going for the big ask when you need the small one. If you need someone’s approval and you haven’t established trust yet, the ask isn’t “fund this.” The ask is “give me thirty minutes to walk you through the business case.” Earn each step.

Practice prompt

Write a five-line brief for the next idea, request, or proposal you need to move forward — at work, with a client, or internally. Read it aloud. It should take under 45 seconds. If you’re gasping for breath, cut adjectives. If it sounds like a bullet list, add one connecting sentence to the Insight. If you find yourself explaining the background first, you haven’t found the Fact yet.

← All pitch guides · Guide builder · Resources & checklists