Demo vs analogy in a pitch: if you need a metaphor to explain your product, you have a riddle
If you can show it, show it. A 30-second demo beats any analogy, because a demo proves the product exists and works while an analogy asks the listener to imagine it for you. Use an analogy only when there's nothing to show yet, and even then keep it to one line. If your pitch leans on a metaphor to explain what you do, you don't have a pitch yet. You have a riddle.
I watched an investor make that point to a founder in about fifteen words, and it applied to almost everyone who pitched that night.
The first pitch night
March 24 was the first edition of Spark Tank, our weekly Tuesday pitch show. Founders pitch live, a panel of investors gives feedback live, and everybody in the room learns from everybody else's mistakes. Four founders pitched that first night.
One of them had the kind of results most founders would kill for. A training platform with 250,000 active users across six countries, and big-brand clients. Real traction, real logos.
And he spent his time on an analogy about tailoring.
The tailor analogy, and the investor who killed it
The idea was that his platform tailors training to each person, like a tailor fits a suit. It's a nice image. It's also the wrong job for an image. The panel had to translate the metaphor back into a product, guess what the product actually did, and then compare it to what already exists. That's three steps of work you're asking a stranger to do while you talk.
An investor on the panel went further than Charles and I had:
"I think you should drop the whole tailoring thing entirely."
His reasoning was simple: the founder was using an analogy to show people what he does. So he gave him three words.
"30 second demo."
Why a demo wins
A demo does what an analogy only promises. In half a minute an investor sees what the user sees, what happens when they click, and what they get at the end. No translation, no imagination required. The question "what does this actually do?" is answered before anyone can ask it.
A demo also proves something an analogy never can: that the thing exists and works. Every founder can describe a beautiful product. Not every founder can open a laptop and show one. When you can, do it first.
And it frees up your time. If thirty seconds of screen explains the product, the rest of the pitch can go to what investors actually decide on: who's paying, how much, and why it grows.
How to build a 30-second demo
Thirty seconds is shorter than founders think. It's three beats:
- First ten seconds: the screen the user starts on, and the problem they have on it.
- Next fifteen: the one action that matters. Not a tour of features. One action.
- Last five: what they get. The result on screen, ideally with a number.
Record it, play it back, and cut anything you had to narrate twice. If you can't do it in thirty seconds, the product might be fine, but you haven't found the one action that sells it. That's worth knowing before an investor finds it for you.
Results beat metaphors
The bigger miss was burying the traction. A founder with 250,000 active users and big-brand clients doesn't need a metaphor. Those numbers are the story. Lead with them, show the product for thirty seconds, and the investor fills in the rest themselves.
Founders reach for analogies when they're worried the product is hard to understand. But the fix for "hard to understand" isn't a cleverer comparison. It's showing it. And if you have results, you don't even need the investor to fully understand the product to be interested. Big logos and a big user number are their own explanation.
A few days before the show I'd saved a post making the case that the worst thing in sales is pitching the solution too early. The flip side is just as true in a pitch: the worst thing is explaining the solution too much. Show it, prove it, stop.
The panel's common themes
Across all four founders that night, the panel kept circling the same three things:
- Clarify the value against what already exists. "What do people do today, and why is this better?" should be answered in one breath.
- Name the hurdle. For B2B products that need certification before they can be sold widely, say where you are in that process. Investors will ask anyway.
- Make the revenue model obvious. Who pays, how much, how often. If the panel has to guess, they assume the worst.
None of those are solved by an analogy. All of them get easier when the product is already on screen.
When an analogy is fine
I'm not anti-analogy. If you're pre-product and there's nothing to show, a single comparison can help someone get the shape of what you're building in one sentence. Keep it to one line, then move to evidence: who you've talked to, what they said, what you're building first.
The test is simple. If you deleted the analogy, would the listener still know what you do? If yes, delete it. If no, the problem isn't the analogy. It's that the pitch hasn't found its demo yet.
The fastest way to fix a pitch is to say it out loud in front of investors who'll tell you the truth. If you want rooms like that, see how founders use a show to meet investors.
Frequently asked questions
Should I use an analogy in my pitch?
Only if there's nothing to show yet, and keep it to one line. If you can demo the product, a short demo beats any metaphor.
How long should a pitch demo be?
About 30 seconds is enough to show what the user sees and what they get. That was the exact advice an investor gave a founder at our first pitch night.
What do investors want in the first 30 seconds?
What the product does and proof it works. A founder with 250,000 active users should lead with that number and a short demo, not a metaphor.
Are pitch competitions worth it for raising?
They're a fast way to hear what investors think of your pitch in public. On our first night, the panel's notes on value, certification hurdles and revenue models applied to every founder.