On this page12
- What's the actual difference between the two pitches?
- Why does the deck story confuse users?
- Why does the user story bore investors?
- How do you keep both pitches consistent?
- The three-surface test
- What does a good translation look like in practice?
- When the two pitches should diverge on purpose
- FAQ
- Should my website ever use investor language?
- Do I need a separate pitch for partners and exchanges?
- How do I pitch journalists when I have both stories?
- What if my investors and my users are the same people?
The difference between an investor pitch and a customer pitch is what each audience is buying. Investors buy a market, a team and a reason the timing is right, so the pitch is about size, momentum and why you win. Customers buy an outcome, so the pitch is about what changes for them, what it costs and whether they can trust you. The two should share one core sentence, then diverge in everything that follows it.
Web3 founders tend to get this backwards. They put the deck on the homepage, then wonder why users bounce, or they bring a user-friendly demo to a partner meeting and get asked about the market size twice.
What's the actual difference between the two pitches?
Each audience walks in with different questions. Write them down and the difference becomes obvious.
| Investor pitch | Customer pitch | |
|---|---|---|
| Core question | Can this become very large, and is this team the one to do it? | Will this solve my problem without hassle or risk? |
| Unit of value | Market, growth, defensibility | Time saved, money saved, a thing made possible |
| Proof they trust | Traction curves, retention, notable backers, team history | Reviews, people like them using it, a clear demo |
| Language | Category, TAM, moat, flywheel | Plain words about their day |
| What kills interest | No clear path to scale | Not understanding it in the first ten seconds |
| Typical length | 10 to 15 slides and a 30-minute call | One sentence, then one screen |
Neither column is better. They answer different questions. The trouble starts when one column leaks into the other.
Why does the deck story confuse users?
Because it's written for someone deciding whether to own a slice of your company, not someone deciding whether to use it.
A typical Web3 deck opens with the market: trillions in real-world assets, billions of unbanked people, a fragmented multichain world. Then it moves to the protocol, the token, the moat. Every slide is sensible in a partner meeting. Paste it onto a website and a normal visitor reads that you're "the coordination layer for a multi-trillion-dollar tokenization market" and has no idea whether they can do anything with you today.
I've watched plenty of teams win the investor room and lose the user room:
silent claps for web3 projects that raised millions of dollars and are yet looking for users Shilika Jain on X, 30 Oct 2022
That gap usually isn't about product. It's about which story the team kept telling after the round closed. If the homepage, the launch thread and the press boilerplate are all still speaking investor, users never get a version written for them. My piece on the explanation problem in crypto goes into why that's so common.
Why does the user story bore investors?
Because "you can send money home in two minutes" answers the user's question and none of the investor's.
An investor hears a clear user benefit and immediately asks the next three things: how many people want this, how fast it's growing, and why someone else can't copy it. A pitch that only has the user story leaves those blank. And investors are also assessing something no user cares about:
VC's don't bet on products, they bet on people! Shilika Jain on X, 29 Sep 2022
The team slide, the founder's history and the way the founder answers hard questions all carry weight in an investor meeting that they'd never carry on a product page. A demo-led pitch can feel lightweight to a partner even when the product is excellent.
How do you keep both pitches consistent?
Use one spine and two faces. The spine is a single sentence both audiences could hear without confusion. The faces are what you build on top of it for each room.
I build it in this order:
- Write the spine. One sentence: who it's for, what changes for them, and the noun that describes what you are. It must be plain enough for a user and specific enough for an investor.
- Build the user face. Add the immediate outcome, the cost, the trust signal and the first action. Nothing about markets.
- Build the investor face. Add market size, traction, defensibility, team and why now. Keep the spine sentence word for word as the opening or the second slide.
- Check the overlap. The same core noun and the same core outcome should appear in both. If the deck says "settlement layer" and the site says "payments app", you've got two companies.
- Write the press version last. Journalists sit in between, so the boilerplate is the spine plus one proof point each audience would respect.
The press version matters more than founders expect. A funding announcement is the moment the investor story becomes public, and if it doesn't connect to the user story, the coverage confuses everyone who reads it. I covered the media side of rounds in the crypto fundraising PR playbook.
The three-surface test
A quick consistency check you can run in ten minutes. Put these three things side by side:
- Slide 1 or 2 of your current deck
- Your homepage headline and subhead
- The first sentence of your press boilerplate
Then check two things in each: the noun used for what you are, and the outcome it names. If all three agree on both, you're consistent and the differences between them are just emphasis. If any two disagree, decide which one is true and fix the others before your next announcement.
I'd add a fourth surface for most Web3 teams: the founder's X bio. It's often the first thing a reporter or investor reads, and it tends to drift fastest.
What does a good translation look like in practice?
This is how the same company might talk in each room. The company is a fictional stablecoin remittance app, invented to show the pattern.
| Deck line (investor) | Homepage line (user) |
|---|---|
| "Cross-border remittances are a massive, high-fee market ripe for stablecoin rails." | "Send money home in minutes, with the fee shown up front." |
| "We've grown monthly active senders every month since launch." | "Thousands of families already use it every month." (only if true) |
| "Our compliance stack and local cash-out partners are hard to replicate." | "Cash out at local partners near your family." |
| "Experienced payments and crypto team." | (Not needed on the homepage. Put it on the about page.) |
The same fact shows up in both columns, translated for the person listening. Nothing contradicts. That's the whole goal.
Real campaigns follow the same logic. When MANTRA Chain announced its $11M raise, the coverage carried a category word investors and reporters were already tracking, real-world asset tokenization, alongside a regional angle in the Middle East. That gave the funding story something to attach to beyond the number. You can see how it ran on the MANTRA Chain case study.
When the two pitches should diverge on purpose
Consistency doesn't mean identical. Some things belong in only one room.
- Token details. Valuation, allocation and vesting belong with investors and in disclosure materials, not in your user pitch. Mixing them into user copy reads as a sales pitch for the token.
- Risks. Investors expect a frank conversation about competition and regulatory risk. Users need honesty about risks to their funds. Different risks, both honest.
- Ambition. "We'll be the default settlement layer for the region" is a fine investor line. To a user it sounds like a promise you haven't kept yet.
There's also a sequencing trade-off. Early on, investors often want to hear real usage before they'll take the market story seriously:
easiest way to raise funds in a web2/web3 market: - build a solid product in a saturated niche - provide 2x value by building coolest features, intuitive experience, low fees etc - show adoption in the first 6 months of initial launch Shilika Jain on X, 19 Nov 2024
Which means the user pitch often has to work first. If users don't understand the product, you won't have the adoption the investor pitch needs. Founders who spend months polishing the deck before fixing the homepage are working in the wrong order.
When a founder is the face of both pitches, interviews and podcasts become the place they get tested in public. That's a big part of why founder profiling sits alongside messaging work in most campaigns I run.
FAQ
Should my website ever use investor language?
On an investors or about page, yes. On the homepage and product pages, keep it out. If you're raising and want investors to find the investment story, link to it rather than putting it in the hero.
Do I need a separate pitch for partners and exchanges?
Usually a third face on the same spine. Partners want to know what's in it for their users and what integration costs them. Write it from the same core sentence so it doesn't drift away from the other two.
How do I pitch journalists when I have both stories?
Lead with whichever one is news. A funding round leads with the investor story but should explain the user outcome in the first two paragraphs. A product launch leads with the user story and can add traction as proof.
What if my investors and my users are the same people?
That happens with some token communities. Even then, separate the moments: when they're deciding whether to use the product, speak to the outcome, and when they're deciding whether to hold the token, give them the investor detail in the right, compliant channel.
If your deck and your homepage sound like two different companies, book 30 minutes with me and we'll find the sentence they should share.
