How to Pitch Anything: What Investors, Spouses, and Skeptical Colleagues All Have in Common
Here is a thing nobody tells you when you are preparing for your first investor meeting: the skills you need have nothing to do with finance.
They are the same skills you used to convince your partner to go to Tuscany instead of the beach. The same ones you deployed when you talked your team into a complete architecture rewrite. The same ones your ten-year-old uses when they want a later bedtime.
Every pitch is the same at its core. Someone has a resource — money, time, attention, credibility — and you are asking them to bet some of it on you.
Your spouse is an investor. Act accordingly.
Think about the last time you pitched a vacation.
Maybe you wanted Portugal. Your partner was leaning toward staying local. You had a finite amount of goodwill to spend, a finite window in which to make your case, and a partner who had been on the receiving end of your enthusiasm before and had a calibrated skepticism about how "easy" and "affordable" your ideas tend to be.
So what did you do? You probably did not walk them through a 47-slide deck with market research on European tourism trends. You led with the thing they actually cared about. Maybe it was the food. Maybe it was finally getting to see a specific place they had mentioned years ago. You made it concrete, personal, and short — and then you let them ask questions.
That is a great pitch.
Now think about what would have happened if you had led with the logistics. Flight times, visa requirements, the exchange rate, the packing list. By the time you got to the part about the wine and the cliffs at sunset, they were already exhausted.
That is most startup pitches.
What investors are actually doing when they listen to you
Investors — whether they are writing a check, joining as a co-founder, or just agreeing to take a second meeting — are not passively receiving information. They are actively filtering for reasons to say no.
This is not cynicism. It is the correct behavior for someone managing risk with limited time. The question they are asking, constantly, is: is there something here that makes me think this is a bad bet?
Your job is not to overwhelm that filter with volume. Your job is to reduce the things that trigger it.
That means answering four questions before they have to ask:
- Is this a real problem that real people have?
- Is this team capable of solving it?
- Is the opportunity large enough to justify the risk?
- Is there any evidence — anything at all — that this is working?
Notice that "have you built the entire product" is not on the list. At the pre-seed and seed stage, investors are not expecting a finished product. They are expecting a team that has thought clearly, tested their assumptions, and built enough to demonstrate they can execute.
Two working screens will do more for that last point than a hundred-page product spec.
The demo is not a presentation. It is proof.
There is a methodology for this, and it is worth knowing.
Peter Cohan's Great Demo! makes an argument that seems obvious in retrospect: most demos are structured backwards. They build up context, explain the background, walk through the setup — and save the interesting part for the end. By that point, the audience has already checked out.
The better approach is to start with the thing the audience cares about most. Show the result first. Then, if they want to understand how you got there, walk them back through it.
For an investor, that means opening with the output your product produces — the thing that makes a customer's problem go away — before you explain how it works or how you built it. Make the payoff the first thing they see.
Then, and this is the part founders get wrong: stop.
You do not need to show everything. You do not need to walk through every feature, every configuration option, every edge case you have handled. The goal is not to demonstrate completeness. The goal is to leave the investor wanting to ask questions — because a question is engagement, and engagement is what turns a first meeting into a second one.
The functional-plus-mockup approach: the most underrated pitch move
Here is something that feels counterintuitive until you have been in enough of these rooms: a demo with one or two live, working screens plus several mockup screens is often more impressive than a demo of a fully-built product.
Why?
Because the combination communicates two things at once. The live screens say: this team can build, and the hard part works. The mockups say: this team has thought clearly about the full product and knows where they are going.
A fully-built product at the pre-seed stage often raises a different question: why did you spend your runway building everything before you had validated anything?
The functional-plus-mockup approach is not a shortcut. It is a deliberate signal that you understand what stage you are at, what you need to prove, and how to use your resources accordingly. That judgment is exactly what a pre-seed investor is betting on.
The rule is simple: whatever you show must work when you show it. The two live screens should be flawless. The mockups can be explicit about being mockups — investors respect the honesty. What they do not respect is a fragile, half-working system that breaks in the room while you apologize for it.
The thing about getting a "yes"
The goal of an investor pitch is not to close the round in the room. It is to generate enough interest that they want to keep going.
The same is true of the vacation pitch. You are not trying to get your partner to pack their bags on the spot. You are trying to get them to say "okay, send me the link."
That is the bar. Make it concrete. Make it short. Lead with the part they care about. Show the thing that works. Be honest about what is not yet built. And stop before you have answered every question — because an investor who has no questions left has no reason to take the next meeting.
For a detailed breakdown of what different investor types evaluate and how to structure your pitch around their specific criteria, see What Investors Want to See When You Pitch.
For the full methodology on structuring a demo — including how to use the functional-plus-mockup approach in practice — see What Makes a Great Demo.
Ready to build the prototype that makes your pitch land? Apply to work with RamenAtA.