Zigging vs. zagging: How HubSpot built a $30B company | Dharmesh Shah (co-founder/CTO)
Executive Summary
Dharmesh Shah joins Lenny Rachitsky to discuss first principles, contrarian bets, simplicity, problem focus and flashtags. This selected coverage omits humor/public-speaking, going-public, later culture and AI material. HubSpot history and the title's $30B figure are unverified here. Thermodynamics is used as a company-complexity analogy. Untimed topics are editorial, not video chapters.
Key Takeaways
Separate first principles from company beliefs
Shah distinguishes what is collectively known to be true from a founding principle such as transparency. A preference may be central to the company without being a universal rule. Label assumptions and choices honestly before reasoning from them.
Choose a limited number of contrarian bets
He favors high-conviction, low-consensus bets, but says the number should be greater than zero and not too high. Disagreement is not enough: the bet still has to be right. Identify what you believe and what evidence could change that view.
Know the conventional alternative
His zig-versus-zag discussion asks for a conscious choice rather than reflexive opposition. HubSpot's SMB focus is his example of sticking with a low-consensus bet. Those business-history claims are his account, unverified here, not proof that copying the same choice will work.
Expect the company challenge to change
He describes early survival, then avoiding stagnation, then fighting complexity as the company grows. His thermodynamics comparison is an analogy, not a literal business law. Review whether the habits that helped at one stage now make the next stage harder.
Count complexity beyond implementation
Shah says a feature or second product costs more than the initial work and maintenance. It also changes coordination and the choices customers and teams must understand. Evaluate those ongoing costs before deciding an addition is worth it.
Solve the problem with a constraint
He says HubSpot went broad to address the customer's integration problem, while limiting how deeply it would compete in every component. Fall in love with the problem rather than a favorite solution. Broad scope still needs a clear constraint so it does not become a promise to be best at everything.
Signal the strength of your opinion
His flashtags address the megaphone issue: a casual founder opinion can be mistaken for an instruction. He describes labels such as FYI and suggestion to signal that no response is expected. Agree on what the labels mean before assuming others interpret them the same way.
The Conversation Breakdown
Separate first principles from company beliefs
⏱ Untimed topicShah distinguishes what is collectively known to be true from a founding principle such as transparency. A preference may be central to the company without being a universal rule. Label assumptions and choices honestly before reasoning from them.
Choose a limited number of contrarian bets
⏱ Untimed topicHe favors high-conviction, low-consensus bets, but says the number should be greater than zero and not too high. Disagreement is not enough: the bet still has to be right. Identify what you believe and what evidence could change that view.
Know the conventional alternative
⏱ Untimed topicHis zig-versus-zag discussion asks for a conscious choice rather than reflexive opposition. HubSpot's SMB focus is his example of sticking with a low-consensus bet. Those business-history claims are his account, unverified here, not proof that copying the same choice will work.
Expect the company challenge to change
⏱ Untimed topicHe describes early survival, then avoiding stagnation, then fighting complexity as the company grows. His thermodynamics comparison is an analogy, not a literal business law. Review whether the habits that helped at one stage now make the next stage harder.
Count complexity beyond implementation
⏱ Untimed topicShah says a feature or second product costs more than the initial work and maintenance. It also changes coordination and the choices customers and teams must understand. Evaluate those ongoing costs before deciding an addition is worth it.
Solve the problem with a constraint
⏱ Untimed topicHe says HubSpot went broad to address the customer's integration problem, while limiting how deeply it would compete in every component. Fall in love with the problem rather than a favorite solution. Broad scope still needs a clear constraint so it does not become a promise to be best at everything.
Signal the strength of your opinion
⏱ Untimed topicHis flashtags address the megaphone issue: a casual founder opinion can be mistaken for an instruction. He describes labels such as FYI and suggestion to signal that no response is expected. Agree on what the labels mean before assuming others interpret them the same way.
Core Frameworks & Ideas
High-conviction, low-consensus bets
Choose a small number of deliberate bets and explain both the conviction and the conventional alternative.
Fight for simplicity
Count the ongoing coordination and comprehension cost of additions, not only development and maintenance.
Flashtags
Use agreed labels to distinguish information, a tentative suggestion and a stronger view.
Actionable Next Steps
- ✓Label one company belief as a choice rather than a universal first principle.
- ✓List your contrarian bets and the conventional option for each.
- ✓Review the ongoing complexity cost of a planned feature or product.
- ✓Agree on FYI and suggestion labels so casual opinions do not become accidental instructions.
Notable Quotes
“It's not what you believe is true, it's what do we all collectively know to be true to the best of our knowledge?”
“So the number of things that you're a contrarian on has to be greater than zero, but not too high.”
“But then the third stage is you're fighting complexity.”
The One Thing to Remember
Be deliberate about the few bets that make you different, and keep the problem and cost of complexity clear.