Principles
Durable claims that survive beyond the speaker's biography — each with explicit limits, transferability judgment, and evidence.
Principle
Technical founders are not always well-suited to hyper-scaling operations
Hyper-scaling requires operational discipline, accountability culture, and go-to-market sophistication — skills uncorrelated with the technical-vision skill that creates the initial product. Founders who try to do both compromise both.
If your founder''s strength is technical and the company needs hyper-scaling operations, the split-role configuration is structurally better than asking the founder to develop ops skills.
“Yeah, it was badly missing plan. The leadership team was somewhat dysfunctional. The go-to market efforts were not very effective. ... if this company is doing well with, essentially, not a very good team, a lot of dysfunction in how decisions are being made, imagine what this company could do with an A-team in place.”Dev Ittycheria
“From day one, my background... I was a CS major in college. I loved programming and when I was CEO at MongoDB, I was spending some fraction of my time, like one third to one half, coding. Or designing things. ... So, I very much wanted to get someone else to be CEO quite early on.”Dwight Merriman
Principle
Open source licensing is a strategic choice — pick the right scheme early
Open source licensing schemes carry different strategic implications (contribution model vs freemium adoption vs hyperscaler defense); choosing the wrong scheme early constrains the business model years later.
If you''re building an open source commercial company, pick the license scheme strategically. AGPL/SSPL for freemium-with-defense; GPL/Apache for contribution-driven. Re-licensing later is hard.
“The founders here made a brilliant, absolutely brilliant decision that we called out in our investment memo on page one, in that they picked the AGPL license, so-called Affero GPL license, which was a more restrictive license that enabled customers to download the software and use it, but it limited the ability for other people to make changes and then offer that software commercially.”Roelof Botha
“Given the experience that I've had with MongoDB, both in the original choice of AGPL and then the choice of SSPL is that, when I meet young companies that are open source, one of the first questions I ask them is "what is the open source licensing approach that they've adopted?" Because you can make changes early on much more easily than you can later.”Roelof Botha
Principle
Address existential threats proactively — don''t wait for the disruption to play out
Disruptions that are obvious in retrospect look ambiguous in real-time; companies that wait until disruption is unambiguous have lost the option to lead it.
For the existential threats you can see coming, ask: am I waiting for the signal to be unambiguous? If yes, you''ve already lost the lead-time.
“In December of 2015, my first Board meeting, the essence of the debate was not do or don't do, but do now or do later. That was the biggest danger that sort of wait and see, versus, let's charge into this and make it happen. ... You have to seize the opportunity of a lifetime during the lifetime of the opportunity. You can be too early, you can be too late, but when you see that the timing is right, you really have to move with very significant urgency.”Tom Killalea
“I thought if the company didn't pursue Atlas, that would be a giant mistake, kind of borderline disaster.”Dwight Merriman
Principle
Pivot proactively, not reactively — even when current direction is "working"
Proactive pivots preserve the option to choose the new direction with current resources; reactive pivots happen when resources are depleted and external pressure forces the decision. Speed of letting-go is the structural predictor of survival.
For your current direction, ask: am I sticking because it''s working or because I''m committed? Speed of letting-go is the predictor of survival.
“Was this stressful, emotional? Was it scary? I would say the answer is yes. I think it's even more scary because we're doing this very proactively. We may be killing something that would have worked.”Dwight Merriman
“I also think the founders that end up building truly successful companies are able to get through these difficult, crucible decisions of letting go sometimes of a wrong idea, sometimes letting go of the wrong hire. And as we've reflected on success across our experience at Sequoia, the speed with which founders are willing to make these difficult decisions is one of the best predictors of ultimate success.”Roelof Botha
Principle
Disagree and commit — when stakeholders are skeptical but the call is yours
Commitment without agreement is the operating mode for big bets — requiring agreement before action filters out high-variance decisions that the team can''t fully evaluate upfront.
For big bets where the team is reasonably split, separate agreement from commitment. The CEO''s job is securing commitment; agreement is optional.
“Are all your stakeholders aligned? Are they all incentivized to make sure that this project is successful? Do you have the right single-threaded leader, what we call our Directly Responsible Individual? Do you need to get people to disagree and commit? Because some people may be skeptical, but you need everyone's commitment to make it happen.”Dev Ittycheria