Exact Formula Used To Build A $130 Billion Company! I Said No to $3B From Mark Zuckerberg!
- Guest
- —
- Read time
- ~4 min
- Uploaded
- 24 Mar 2025
- Duration
- 2:29:52
- Views
- 894.6K
KEYPOINTS
- 01
Surface complexity often fake — build once, ask what else; agency expands.
Exact formula $130B company episode: design teams need huge idea volume because ~99% ideas bad — process filters. Loved building; built own computer at school; Stanford product design path.
- 02
Get money early / scale / mass adoption then build out business later — one path.
Values/behaviours study tied to performance — clear framework. Fear expressing selves via job-title thinking overcomeable.
- 03
Couch sleep with Christmas blanket — ‘we've had enough’ relationship limit.
Human cost of build obsession. Still love to build stuff.
- 04
99% bad ideas → volume process not genius waiting.
Generate then kill. Design culture.
- 05
Complicated-looking things become simple after one build.
Demystify. Second product easier psychologically.
- 06
Stanford product design as craft school.
Formalise taste + making. Not only theory.
- 07
Behaviour-value frameworks for teams.
Hire/culture clarity. Performance link.
- 08
Scale-first vs polish-first tension named.
Context-dependent. Know which game.
EXAMPLES
- 01
~$130B company formula framing.
Hook.
- 02
~99% ideas bad → volume.
Process.
- 03
Built own computer at school.
Origin.
- 04
Stanford product design.
Path.
- 05
Couch Christmas blanket enough moment.
Cost.
OTHER RELEVANT
- 01
Ship volume of ideas; kill 99% fast.
After first build, ask what else immediately. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip. Hold the guest's named mechanisms and numbers; apply one concrete change this week rather than collecting another abstract tip.
- 02
Demystify complexity by making one real thing.
Set relationship limits before couch-enough crises.
- 03
Write team behaviours tied to values.
Choose scale-vs-polish consciously.