What to Say When an Investor Asks "Why Won't Google Just Build This?"
Thirty minutes in, the pitch is going fine. Then a partner leans back and asks the question every founder of a startup in a big market eventually gets: "What happens when Google builds this?" You have about eight seconds before your silence starts answering for you.
The moment
Drew Houston heard this question constantly while raising for Dropbox. On Sequoia's Crucible Moments podcast, he told Roelof Botha that investors routinely dismissed the company on exactly these grounds — that the business looked competitively doomed because Google, Microsoft, and Yahoo would inevitably do the same thing.
His response wasn't to argue the premise. He agreed with it. Yes, the giants would probably build storage products. Then he turned the question around on the people asking it: plenty of tools already claimed to solve this problem — did anyone in the room actually use any of them? They didn't. Neither did he, which was the whole reason Dropbox existed. He'd tried the existing options as a frustrated user and found them unreliable and badly designed.
The same move shows up in accounts of his Y Combinator interview. Asked why the world needed yet another storage service, Houston answered with a question — whether the partners used any of the existing ones — and got a row of no's.
Note what happened structurally: the investor's question assumed the battlefield was resources. Houston's answer moved the battlefield to craft and focus — territory where a two-person startup credibly beats a behemoth's side project. Google Drive did eventually launch, years later. Dropbox went public anyway.
Why this question gets asked
The partner usually isn't asking for a competitive analysis. They're testing three things at once: whether you've thought past your demo, whether you panic under a premise you can't control, and whether your conviction is grounded in something real or just enthusiasm. "Google will build this" is unfalsifiable in the moment — they know that. How you carry the question matters as much as the content of your answer.
The worst answers share one trait: they fight the premise. "Google doesn't care about this space" reads as naive. "We'll have too much of a head start" reads as arrogant. Both sound like a founder who hasn't sat with the uncomfortable version of the question.
How to answer it live
Three approaches that work in the room, with the actual words.
1. Concede and reframe (the Houston). "Honestly? They might. They've had every chance to — and the existing options are why our users came to us. Have you used any of them?" Use when: the incumbents' products genuinely are mediocre and the room likely knows it. Failure mode: if the incumbent's product is actually good, this collapses. Don't bluff it.
2. The side-project asymmetry. "For them it's a feature on a roadmap. For us it's the company. Features built by committee lose to products built by obsessives — that's most of startup history." Use when: your wedge is depth in a workflow the giant treats as a checkbox. Failure mode: sounds like a poster slogan if you can't immediately follow with one concrete example of depth they can't match.
3. The distribution-isn't-destiny answer. "They'll get distribution for free. They won't get our [specific asset — data, trust posture, workflow lock-in] without making trade-offs their core business won't allow." Use when: you have a real structural conflict to point at — privacy positioning a data-harvesting incumbent can't copy, channel conflict, margin cannibalization. Failure mode: vague "they're too slow" hand-waving. Name the specific trade-off or skip this one.
Whichever you choose, the delivery rule is the same: take the question slowly. A beat of calm before answering signals you've been living with this question for months. Rushing signals you hoped it wouldn't come up.
What Houston got right
He never defended. He redirected the room's attention from a hypothetical (Google's roadmap) to an observable (nobody in the room used the existing products). You can't win an argument about the future in a partner meeting, but you can win one about the present. Find the observable fact that makes your conviction legible, and route every version of this question back to it.
Reading this is preparation. The problem is the moment itself — when the question lands and the room goes quiet. WithControl puts a live assist card in front of you during the call: the reframe, the observable fact, the next move. No recording, no transcription, nothing leaves the room. withcontrol.app
FAQ
Should I admit a big tech company could copy my startup?
Yes, if it's plausibly true — denying an obvious risk costs more credibility than conceding it. Concede the premise, then move the conversation to the asymmetry that favors you: focus, craft, or a structural trade-off the incumbent can't make.
What's the worst way to answer "why won't Google build this"?
Fighting the premise. Claiming the incumbent doesn't care, is too slow, or will never notice you signals you haven't seriously stress-tested your own thesis.
What is an investor really testing with this question?
Composure under an unfalsifiable premise, depth of competitive thinking, and whether your conviction rests on something observable rather than optimism.
Related
Story via Dropbox: How the Cloud Pioneer Reinvented Itself — Crucible Moments, Sequoia Capital. Watch the full conversation; it's worth it.