The Boomerang CEO(s): With MongoDB’s Dev Ittycheria

Dev Ittycheria ran MongoDB for 11 years, took it from about $35 million in revenue to more than $2.3 billion, and retired. Ten months later his successor left, and within a week Dev was back in the chair. Since we recorded this, I’ve announced that I’m returning as HubSpot CEO in addition to my work at Sequoia, so I’ve been replaying his advice with a lot more at stake.
The center of this conversation is Dev’s framing that a CEO has 3 jobs: set the strategy, get the right people on the bus to execute it, and create an environment where they’re set up to win. A CEO can do a thousand things, and if they do 997 of them well and those three poorly, they fail. Dev says distance let him see which issues really mattered and where he’d wasted time on little stuff. Good CEOs constantly recalibrate to the main things.
Watch Now
Transcript
Chapters
Cold open
Dev Ittycheria: The CEO is in charge of strategy. What is the company’s strategy? Where are we going? What do we aspire to be? The second job is, do you have the right people on the bus to go execute on that strategy? And that’s really the core leadership team. And then the third job is, are you creating an environment where people are set up for success? That could be the right capital allocation decisions, the culture you create. You’ve talked a lot about culture as a product that can attract and retain great people. I can do a thousand things. I can do this podcast, I can go visit customers. But if I do 997 things well and these three things poorly, I’ve failed as a CEO.
Intro
Brian Halligan: Hey, everybody. Dev Ittycheria on the call today. It’s a fascinating call for me personally, because Dev boomeranged back into the CEO job at MongoDB recently, and I boomeranged back into HubSpot as CEO, refounding the company. He’s a gem, full of wisdom. I learned a lot. Hope you like it.
Main Interview
Brian Halligan: Welcome to the pod, my friend.
Dev Ittycheria: Hey, Brian. Good to be here.
Brian Halligan: Okay. You tried to retire.
Dev Ittycheria: I did.
Brian Halligan: Ten months, and you got a call from someone from MongoDB that the CEO had resigned. Where were you? Take us inside your head at that moment.
Dev Ittycheria: So, actually, I was in Tuscany, Italy. I got an email from the board chair saying, “Hey, can you talk?” And I said, “Yeah, let’s talk tomorrow.” We ended up catching up that morning, and he told me that the then-current CEO was thinking about leaving. I was obviously shocked. And then he asked me, “If that were to happen, would you consider coming back?” I said, “Let me think about it.”
Brian Halligan: I’m sure your wife was involved in your decision to retire in the first place. So you got the call. Your wife’s probably in the room. What was that conversation?
Dev Ittycheria: Well, philosophically, both my wife and I felt like we wanted to spend time together. We were empty nesters. We obviously were very fortunate. And both of us had lost our parents—in fact, my dad had passed away in February. So it kind of put things in perspective: I don’t want to work till I’m 80 and then fall over and die. So we said, let’s enjoy time and do things. And I’d obviously made a decision to join Sequoia, which is part of doing interesting things. But when she heard this, her first reaction was, “What?” And her second reaction was, “Yeah, you should do this.”
Brian Halligan: Oh, okay.
Dev Ittycheria: I mean, obviously MongoDB has been very good to us, and there are a lot of people we worked with who we’re very grateful for. So fast forward: the chair called me to give me an update, saying, “Yeah, he’s leaving. Can you do this?” And I said yes. Candidly, I didn’t want to leave 6,000 employees in the lurch. I didn’t want to leave thousands of customers wondering what’s going on. And obviously there’s a large investor base that had believed in the company. So I felt it was important to do that. We actually had an investor day on Tuesday to give our long-term guidance, and then Wednesday we had our largest user conference in New York.
Brian Halligan: You had ten months to think big thoughts. What were some of the things you reflected on, and some of the learnings coming back?
Dev Ittycheria: I think as a leader, you always should introspect on what happened. I was introspecting on my 11 years at MongoDB—what I think went well and what I could have done better. And there are always things you could have done better. It gives you perspective. You can see the forest for the trees better and really understand what the big issues were that really mattered, and where I wasted time focusing on little stuff that didn’t matter as much. So when I came back, the first thing to me was team. No matter what era you’re in, it’s all about having the right team. And unfortunately, I had to make some hard decisions.
Brian Halligan: I just remember, as CEO of HubSpot, at any given time one of the senior executive slots was open and I was managing their team—and oftentimes two. So I assume you’ve got a giant number of direct reports, because all of their direct reports work for you? Or do you have another plan?
Dev Ittycheria: I brought in an interim person as well, someone I’d worked with, to cover one role. And my predecessor had split product into two groups, which I consolidated. I thought there was a lack of clarity on who did what and when. So we kind of simplified. The whole thesis was: let’s simplify our organization so that we can make good decisions quickly.
Brian Halligan: Okay. And why do you think making decisions quickly is so important?
Dev Ittycheria: I think any business is the output of decisions that result in the products you build, the customers you have and the revenue you generate. If you think about companies, they’re the sum of all their decisions. And to me, the best companies can make good decisions quickly over a long period of time.
We can go into this in a lot of detail, but one of the things about making good decisions is being able to have hard conversations and being able to speak the truth. And frankly, most people are not wired to tell you what they feel. There’s a big gap between what they say and what they feel. So as a leader, you have to make it comfortable for people to really bare their soul and say what’s going on—whether they’re unhappy with their counterpart in another part of the business, whether they’re going to admit mistakes about what they’ve done in their business, what the issues are. Because if you can’t talk about the truth, you’re basically wasting a lot of time.
If you map the time between a problem and solving the problem, the bulk of that time is actually recognizing there’s a problem. Once you all collectively recognize the problem, actually solving it—unless it’s something super structural—is usually not that traumatic. But so much time is wasted debating, on ego, on cherry-picking data, et cetera, and that just makes the process much more painful. So as a leader, you’ve got to cut the BS.
Brian Halligan: I don’t know if this is a compliment or not, but my last guest was Ali Ghodsi from Databricks.
Dev Ittycheria: Who’s done a phenomenal job.
Brian Halligan: Phenomenal job. You remind me a lot of him. Your talk track right there is almost identical to his, where conflict aversion is a real bug and people have to be able to tell you the truth.
Dev Ittycheria: Yes.
Brian Halligan: Can I say something that you may not like?
Dev Ittycheria: Sure.
Brian Halligan: Both you and Ali also rhyme in my head because I find you both a bit intimidating. There are very few people walking around in tech who make me nervous. You two kind of make me nervous. So I don’t naturally think of you as a guy I would want to open up to, and tell you my problems and be vulnerable with.
Dev Ittycheria: Yeah, I’ve been given that feedback before. A co-founder at one of my first companies says my superpower is creating a sense of urgency. That’s a diplomatic way of saying I really raise the temperature to get people to move quickly.
But I think the way to get people to be more open with you is to also exhibit vulnerability. In fact, I think one of the hidden management secrets is being vulnerable. Let me ask you a question: have you ever trusted a person who never admitted a mistake?
Brian Halligan: No. Probably not.
Dev Ittycheria: Right. And as a leader, you’re not perfect. There’s no leader out there who’s perfect. Everyone’s made mistakes. So to me, it matters if I admit either that I made a mistake or that I don’t know something. And I learned this the hard way. In one of my first companies, I used to have massive imposter syndrome, and I felt I had to have my imprint on every decision. Over time, I started realizing I was suffocating my organization. My team was getting fatigued by me. The place was getting dysfunctional, and they were actually trying to work around me versus work with me. And I had this epiphany—I don’t know why I had it—saying, you know what? I don’t need to have all the answers. I need to have good people around me, I need to ask good questions, and then I need to make sure we focus on solving the right problems.
Brian Halligan: Do you remember where or what it was that clicked, that you needed to change that?
Dev Ittycheria: Yes. Actually, it was my co-founder. I had a really tough conversation with him, and he basically said that after that conversation, he was dysfunctional for like two weeks. And I was shocked. The way I delivered it was, in his mind, not constructive—which is probably true. The feedback was directionally right. It was just the way it was delivered, the intensity, that got him dysfunctional. And I realized that in some ways my frustration was not just with him, it was with me, and why we had not seen this issue. I realized I have to be open to the fact that I can make mistakes, and not take it out on other people. And if I admit my mistakes, people will basically mimic the leader and start being much more vulnerable.
And you know what vulnerability does? One, it gets people to feel safe, because now they say, “Okay, this person admits his or her mistakes.” Two, you get to the truth faster, because now you say, “Hey, I don’t think this product thing is going well,” or “I don’t think this team is great,” or “We have this issue with the customer that’s a real, serious issue—let’s not try and hide it.” When you get to the truth, you can solve problems more quickly. And when you solve problems more quickly, that increases the speed at which you can make decisions. And speed compounds. So it’s this whole chain, starting from vulnerability, to driving a business more quickly.
Brian Halligan: Okay, let’s just say I’m one of many Sequoia founders who are quite introverted and conflict averse. Just grew up that way. What coaching would you give me?
Dev Ittycheria: My advice would be that you have to work on that, whether it’s through your own introspection or you get a coach. The job of a CEO is, in some ways, to be confrontational—not in a nasty or unconstructive way, but you have to confront issues. You have to confront why a person is not delivering on their commitments. You have to confront why this product is not having the success it should in the field. You have to confront the go-to-market team on why certain people are not meeting expectations. That’s your job.
And if you don’t do that and you avoid issues, those issues just fester. It’s not like the issue is going to disappear. And then it takes way too long. What I’ve noticed is that when people know there’s an issue and you don’t do anything about it, then you become the problem. That issue or that person or that thing is no longer the problem. You’re the problem, because you’re basically saying there’s a new standard, and that standard is a lot lower than what they thought it was.
Brian Halligan: The conflict aversion thing is interesting inside of my co-founder’s and my dynamic. My co-founder is the world’s most conflict-averse Homo sapiens, and I’m actually a little conflict averse. So it sort of forces me into a box of, I need to be the one who isn’t afraid to create conflict and have those hard conversations. I felt like I was always the person talking about the elephant sitting right in the middle of the table that everyone’s ignoring.
Dev Ittycheria: But you obviously trained yourself to do that, right? Otherwise you wouldn’t have been able to build the business you did.
Brian Halligan: I think I improved on it over time. It certainly wasn’t natural.
Dev Ittycheria: Well, in some ways, we humans are wired to be social animals. Three thousand years ago, if you didn’t get along with people in the village, they’d take you out back and club you to death, right? So by definition, it is very antithetical to who you are. And I think there’s also a deep desire by people to be liked.
Brian Halligan: It’s one of my bugs, actually. As a human, I think it’s good. As a CEO, I think it’s a huge bug.
Dev Ittycheria: Yes. Being liked is okay, but if it stops you from being able to have hard conversations, then you’re not doing that person any service. You’re basically conflating being polite with being kind. To be kind, you actually have to give that person good feedback on where they’re not measuring up.
I just had a conversation over Slack with one of my execs where I was very disappointed. They didn’t take ownership of an issue that we discussed yesterday. And I made the point: “If I care more about this issue than you do, then we have a problem, because this is in your domain and you should be all over this issue.” And the person admitted it—“Yes, you’re absolutely right, I’m going to fix it”—which was great to hear. But I needed to have that discussion with that person.
Brian Halligan: Okay. Related to this: I was CEO of HubSpot starting in 2006. You get criticism as a CEO through certain channels. For a CEO of a public company today, like Mongo or HubSpot, the criticism just comes through everywhere. You see it on Glassdoor, you see it on Blind, you see it on X for sure. You see it from Wall Street in the analyst reports. You see it on LinkedIn, people complaining about your product. Were you born thick-skinned to deal with all that, or is that hard for you?
Dev Ittycheria: Oh, it’s definitely hard, right? You just have to learn to develop thick skin over time. Especially if you have imposter syndrome—and all of us in some way, shape or form do—when someone says your product sucks, or you’re making the wrong—
Brian Halligan: You’ve heard it all.
Dev Ittycheria: I’ve heard it all. Now, what’s interesting is that outside the company, people are very comfortable badmouthing. In fact, I think there’s an asymmetry of bad news to good news. Like on Blind or Glassdoor, anyone who’s upset about something is going to post, whereas someone who’s happy is not really going to do anything. Whereas inside a company, I think leaders have an asymmetry of good information. Because what happens is that good news will find me anywhere: “We closed that deal.” “We hired that rock-star engineer.” “The product launched with great success.” But bad news, you have to go searching for. And the key as a leader is not only do you have to go searching for it, but you have to make it comfortable for people to tell you bad news. Because again, humans are wired not to tell the truth. So you’ve got to minimize the gap between what people feel and what they say.
Brian Halligan: I want to talk about evaluating CEOs for a second. You’re looking for a new you. You found a CEO—
Dev Ittycheria: Yes.
Brian Halligan: —so I’m curious about your reflections on what you got right, maybe wrong, on that. You’re looking for a new one. And you’re evaluating all these Sequoia founders at this point—CEOs. What are you looking for?
Dev Ittycheria: Well, I think it varies. Obviously, with these younger founders, a lot of them may be researchers who came up from an AI research background, and they have never hired a finance person or a go-to-market person. This is the first business they’ve ever been part of—or if they were part of a business, they were very junior in the organization. They don’t] really understand how the sausage was made. So a lot of that is just giving them some perspective and some wisdom on what it takes to build a business.
And in most tech businesses, it usually comes down to two things. Have you built the right product and do you have product-market fit? And do you have a go-to-market organization that can acquire customers cost-effectively and efficiently, in a scalable way? And then what does that mean—do you have the right team around you? One of the things a lot of people ask me is, what does the CEO actually do?
Brian Halligan: Okay, what does the CEO do?
Dev Ittycheria: In my mind—and actually, I have to give Mark McLaughlin, the old Palo Alto CEO, credit for this, because he really crystallized it for me. I kind of knew it, but the way he said it really framed it well. One, the CEO is in charge of strategy. What is the company’s strategy? Where are we going? What do we aspire to be? The second job is, do you have the right people on the bus to go execute on that strategy? And that’s really the core leadership team. And then the third job is, are you creating an environment where people are set up for success? That could be the right capital allocation decisions, the culture you create—you’ve talked a lot about culture as a product that can attract and retain great people—an environment where people really want to stay for the long term.
I can do a thousand things. I can do this podcast, I can go visit customers. But if I do 997 things well and these three things poorly, I’ve failed as a CEO. At least that’s my definition. So those three things are the linchpins for the success of a CEO.
And people think—so, you don’t change strategy that often, but you’re constantly assessing your team, in a world that’s moving so fast. When I left, I had gone through 23 C-levels. And just to be clear, some of them left because they had made a lot of money and said, “You know, I’m done,” and retired. But a lot of them were very effective at a certain stage of the company and just couldn’t scale to the next stage. And the tell for me was a couple of things. One, they weren’t very self-aware. They couldn’t see where they were being ineffective. Two, they were losing their team. That’s another tell, because you can always fool the people above you. You can sometimes fool the people around you. You can never fool the people below you.
Brian Halligan: I love that, by the way.
Dev Ittycheria: They were losing their team, and the quality of the people they were hiring was also not as good as before.
This is where a lot of people think that to be CEO, you need to be this amazingly brilliant person. I think the toughest decisions I faced were not the ones that tested my intelligence. They tested my courage. I’ll give you an example. Someone’s worked with you from the early days. Maybe you know the spouse or partner. You’ve had dinner with them. You’ve bonded over crucible moments, baptism by fire. But at some point you realize that person’s not scaling. And now the decision is: do you put this person ahead of the company, or the company ahead of the person? And the job of the CEO or the founder is that the company always comes first. That’s where a lot of people, when they have to make that hard decision, double-clutch and don’t. And they introduce hope into the process.
Brian Halligan: Yes. You’re looking for a new CEO. What are you looking for?
Dev Ittycheria: So obviously, the first job description that was sent to me—the board has taken the lead, since I’ve been pretty busy coming back—was kind of all the classic things: strategic thinker, has experience with scale, understands how to manage different stakeholders, has a good track record. But what I pushed back on was, yes, that’s all nice, but I really want to focus on certain behaviors.
One, do they want to leave the business in better shape than they found it? Do they really have an ownership mindset? Warren Buffett has this great line that says, I want someone to think about the business as if it’s 100% of their net worth, they’re going to own it for 100 years, and they own 100% of the company.
The second part, I would say, is someone who can balance the short term with the long term, and who’s really thinking about making decisions that they may not even get credit for, because they’re really about the long-term health of the company.
Someone who’s in the details. I’m pretty detail oriented, and sometimes I would get questions like, “Why are you into this detail?” I said, the reason I’m into those details is because it gives me the right to have an opinion about this part of the business, or your part of the business.
And someone who’s not transaction oriented.
Brian Halligan: And what do you mean by that?
Dev Ittycheria: Someone who’s not optimizing for the short term. I think there are some people who are just very myopically focused on where the stock price is in six months or 12 months. And sometimes the comp plan is tied to it: if the stock price is over this threshold for 90 days, you get more equity. I think that, while it aligns with shareholder interests, creates some second-order effects that are not healthy. So that’s an issue.
Brian Halligan: What else?
Dev Ittycheria: I would say someone who has a track record of developing people. I think a lot of people conflate hiring with development. Development is being able to really give people coaching and constructive feedback, holding people accountable, telling them what they need to do to get better. That is something very few people do.
Brian Halligan: Why?
Dev Ittycheria: Because I think a lot of people just focus on, “I’ve got to hire someone,” and then they let them execute. But to me, the leader has to do three things: recruit the person, develop them, and then get them to execute, and execute consistently. A lot of people forget part two. Because even the best people need some context around what’s going on. And as the founder and CEO, you have all the context.
Brian Halligan: One of the mistakes I made—I’m curious if you made the same mistake. I’m an engineer, but not a real engineer. And with my head of engineering, I just didn’t appreciate some of the issues going on. I was very loose in my management style, and I think it hurt me. Same for you?
Dev Ittycheria: A little bit. I’m an engineer, but I’m not, you know—
Brian Halligan: Similar, I think.
Dev Ittycheria: Yeah. Not as hardcore an engineer as some people would have expected. But I think I’ve trained myself to ask a lot of good questions and also to inspect below—go deeper in the organization. People can bullshit me only for so long before I can quickly sniff out that something is awry. And then the other thing I would say—
Brian Halligan: Is developing people.
Dev Ittycheria: Yeah. How they’ve done during hard times. Everyone looks good in an up market. How do they deal with a crisis, a product failure? Because I think that really shows you the test of people, and what they did when things went awry. I also look at, when they had to cut, where they cut. Were they a harvester or a builder? Some people say, “We’ve got to cut 20% of our costs,” and just kind of blindly do it, whereas some people are much more thoughtful: “Here are the things we need to preserve and invest in while we’re taking our cost structure down.”
Brian Halligan: Harvester versus builder. Got it.
Dev Ittycheria: Yes. And then the other thing I would say is—obviously, for senior-level people, it’s hard to find people who have a lot of experience with AI. But how do they think about AI? How do they think about org structure, org design, capital allocation? How do they think about how they would run the business—where they would use AI to innovate, where they would be a fast follower? I would want to understand how they think, because that would tell me a lot about how much they’ve thought about this before. And yes, we’re still in the very early days of AI, especially for senior people. But having some point of view would be important.
Brian Halligan: One of the things that I think makes you a bit of a unicorn is that you are technical and you’ve got real sales chops. Pretty rare. Usually someone grew up through product, or they grew up through sales. What are you looking for on that?
Dev Ittycheria: I’m not dogmatic that it has to be a product person or a go-to-market person. I think if you are smart and have enough curiosity, you can learn enough to be an effective CEO. The thing I’m looking for is, have they exhibited good judgment over a long period of time? How do they navigate through difficult situations? How do they make tough people decisions? Because that’s the job of a CEO. How did they evolve the company’s strategy? How did they make contrarian bets? Because that’s where you can create a lot of value.
For us at MongoDB, when we launched our cloud service, a lot of people thought we were nuts. When I took the company public, our cloud business was 2% of revenue. People kind of chuckled and said, “It’s kind of cute that you’re going to try and compete with AWS.” And that’s now the driver of all our value.
Brian Halligan: Same with HubSpot, by the way. When we went public, we were at $100 million in revenue, and everyone was like, “Well, you’re a marketing software company”—which was our genesis. But we had started into the CRM business and had $1 million of sales revenue. On the roadshow, we’re waving our hands, all excited about the million. We got zero credit.
Dev Ittycheria: Yes. Same exact thing for us.
Brian Halligan: And now we’re totally valued on the CRM business. Okay. Anything else you’re looking for in that Mongo CEO?
Dev Ittycheria: To me, the CEO job, like I said, is having the courage to confront issues, having the courage to make difficult decisions, having the courage to pivot the company in a different direction when everyone says, “This is the path to glory.” I think that’s a very, very important attribute.
Brian Halligan: Put your Sequoia hat on for a minute. There are all these brilliant founders coming through. We’re selecting very few of them. What are you looking for when you’re in a pitch?
Dev Ittycheria: What I’m looking for is someone who’s deeply technical, because I think you need to be technical to build something credible in this world today.
Brian Halligan: You weren’t that deeply technical when you started your first company. I wasn’t that deeply technical.
Dev Ittycheria: True. So let me rephrase. It could be a combination of people. My CTO was more technical than me. But I think that person needs to not just be deeply technical, but also be able to go into as much rigor about unit economics as they could about the details of the product. To me, that’s the nirvana of a founder.
Brian Halligan: Okay. We’re both at Sequoia now, and once in a while Sequoia has off-sites. We had one, and Shaun Maguire, one of our partners, who I love, got up on a rant: we need to find founders who were chess prodigies or won the Math Olympiad or are of that ilk. And Sequoia funds a lot of those people. And I pushed back. I said, I didn’t win anything remotely close to a Math Olympiad, and I don’t think Marc Benioff did. I don’t think any of the SaaS-era CEOs were of that ilk. And I don’t think Benioff’s co-founder was, for example. What’s your take? I didn’t have an argument with him—we went back and forth on how important that was.
Dev Ittycheria: I think what you’re talking about is, do you want someone with just raw compute power, versus someone who has some wisdom, experience, taste and judgment? The interesting question is, in a world where intelligence will be ubiquitous and essentially almost zero cost, what are you looking for? I actually would argue that you need people who have some wisdom and judgment and taste in a world where intelligence is cheap.
Now, if you’re building a deeply technical product, you obviously need to have the technical chops. But finding people and just screening based on whether they’re a Math Olympian or a chess prodigy—I’m not sure. I think we’re going to miss a lot of good people who have some unique experience and insight. The lesson I’ve learned is that smarts come in different flavors. There are some brilliant people who are just not necessarily book smart, but who have unique taste, a unique vantage point, unique judgment, some ability to do things other people can’t—they’re just outliers in certain functions. And I think your job as an investor is to figure out what makes this person unique, and is it relevant to the business they’re trying to build.
Brian Halligan: I’ll give you my take on it. I might be dead wrong, but I feel like we’re in this AI super cycle, and I still think it’s very early, but the application layer is starting to really come to fruition. You’ve got Sierra, you’ve got Rogo, you’ve got so many of these companies at the app layer. I actually think the Math Olympians are less important as we move up the stack.
Dev Ittycheria: Well, I will tell you one thing I’ve learned about people who are that bright—off the charts. I would argue that you and I are brighter than the average person, but some people are off the charts. What I’ve found with those people is that when they went to school, it was quickly figured out that they were the brightest kid. Maybe they even skipped a couple of grades. They were kind of anointed as the smartest kid in the class.
Brian Halligan: Yeah.
Dev Ittycheria: And that persona persists—in college and everywhere. So the problem comes when they don’t know something. They can’t admit they’re wrong, because it basically destroys their persona of “this person has all the answers.” I see a lot of problems with those kinds of people, because they struggle to admit they’re wrong. And then you get into all this dysfunction—doubling down on things that maybe are not working, ego comes into play, et cetera. I’ve worked with many of those types.
I think the other thing that’s important is, no matter how smart you are, you need to have intellectual humility. When I was a younger CEO, when someone said something crazy, I just dismissed them, saying they don’t know what they’re talking about. But many times it caught me flat-footed. Because obviously, if the source is credible and their argument is somewhat persuasive, you’ve got to ask yourself: what do they see that I don’t see? What do they hear that I don’t hear? As a CEO, you’ve got to ask, why are they saying something that’s so contrary to my beliefs? Sometimes they may have an insight that you just missed. And I’ve trained myself to really listen and examine why they’re saying something that disconfirms my beliefs, because sometimes it could be very true, and we have to make a completely different decision than we thought we would because of some insight this person had. So I think the best founders have strong opinions, but they have the humility to listen well and get different points of view.
Brian Halligan: You are a learner, and you’ve developed yourself over time. I’ve noticed this about you. You said something to me before this about how once you’ve been successful, you think you’ve got it figured out and you kind of stop learning and evolving.
Dev Ittycheria: Yes.
Brian Halligan: How do you learn? What’s your process of getting better? Do you have a coach? Do you read a lot? Do you just go do ayahuasca journeys? How do you get better?
Dev Ittycheria: Well, I think it comes down to what I was trying to say earlier. One, I believe that if you’re not embarrassed by who you were two or three years ago, you’re not growing fast enough. If you’re still the same person you were two or three years ago, that means you’re plateauing. A common friend of ours, John McMahon, has a great line: “I like people who don’t think they’re the master of the game. They think they’re the student of the game,” because they constantly have a learning mindset. I think that’s a very appropriate way to say it. You’re constantly learning.
So how do I learn? I read a lot. I listen to a lot of interesting podcasts. I try to go through them quickly, but if someone’s got an interesting point of view, I have a little notebook that I take notes in. If I learn some unique insight, it’s, “Oh, that was important”—I capture that. That’s how I keep learning and growing. I learn a lot by observation with my own team—what’s working, what people are doing well. That’s really helped me in terms of growing. I always think you either grow or die.
And back to why I had to make changes: a lot of the execs who couldn’t scale just couldn’t introspect on what was going well and what wasn’t, and adapt and change as the business needed them to. As a leader, and especially a young founder, the business you’re running with four or five people is going to be very different from the business you’re running with 40 people, versus 400 or 4,000. If you’re not learning and growing—I’m sure the person you were in 2005 or ’06 was very different from the person you were when you left, right? You would not have been successful if you didn’t adapt and evolve.
Brian Halligan: Yeah. I’m working with a lot of these founders, and they’re going from two to 20 to 200 to 2,000. The companies are AI native. They were born post-ChatGPT. They’re growing much faster than Mongo or HubSpot did—a lot faster. Given all that, are there different ways to think about being a CEO? Are there different plays? There are a lot of people talking about new ways of being a CEO. I had the Kalshi CEO on here. The business is going incredibly well. He and his co-founder have 200 direct reports and no managers, and he called it “management by chaos.” I had Winston on here from Harvey, who’s got some very unique ideas about being a CEO. I had Jack Dorsey on from Square, who’s got very unique ideas about how to be a CEO. We’ve talked a lot about classic things that haven’t changed. What’s changed?
Dev Ittycheria: Before I go there, one of the things I would warn a lot of founders about is the question: are you getting a lot of inbound demand, or are you generating demand? What I mean by that is, our business during COVID—maybe for the first couple of months we weren’t sure what was happening, and then it just accelerated, because everyone went digital. And growth hides a lot of mistakes. Growth covers for a lot of flaws. But when the water goes out, all of a sudden those flaws are staring you in the face.
Brian Halligan: What’s the Buffett line? Who’s got their pants on when the tide goes out?
Dev Ittycheria: Who’s swimming naked when the tide goes out. Right. And we made the classic mistake. We overhired in functions. We created too many layers and added so much cost with little value. So my advice to these founders would be: one, make sure you’re not ignoring the issues and challenges in your business. Two, make sure the growth is durable.
I was asked to speak in front of 40 CROs of AI companies. They were saying, “The traditional quota doesn’t make sense anymore. Our salespeople are killing it. I’m getting pressure from the CEO and the CFO to raise quotas,” and so on and so forth—which may make sense. And the question I asked them was, “Okay, your sales productivity is great. But if all your inbound demand disappeared tomorrow, what would the quota be? How much would your salespeople really be driving?” You could hear a pin drop.
So I think people really need to understand how much is inbound versus how much they themselves are generating and then fulfilling. The muscle you have to build is: can I go generate demand, and then fulfill that demand?
Brian Halligan: And what do you do? Okay, you’re a CRO. You’ve got leads coming in the bathroom window—they’re coming in all over the place. Do you start cold calling?
Dev Ittycheria: Well, one, obviously you want to service that demand, because if that’s money staring you in the face, you should take it off the table. But you need to build muscles. In markets where there’s maybe not as much inbound demand, are you building muscles to figure out how you go outbound prospecting and generate demand? And then you should also think about, when you build your comp plan, are you building it for repeatable behavior? Because sometimes a blue whale may come in that’s not repeatable. So you’ve got to think about, what am I incentivizing? What behaviors am I incentivizing that I want to repeat over and over again?
Brian Halligan: So many companies are looking for CROs, and it seems like the supply is far less than the demand.
Dev Ittycheria: Yes.
Brian Halligan: You’re a founder of a 200-person Sequoia-backed—anybody-backed—company. You’re ripping. What are you looking for?
Dev Ittycheria: To me, the big difference between a CRO and, say, a regional VP of sales is that the CRO has to write the playbook for how salespeople go out and prospect, qualify, forecast and close business, and then obviously drive that business to revenue. And every business has its own playbook. The challenge I’ve seen with a lot of salespeople is they cut and paste the playbook from the last company to the company they’ve gone to.
A really thoughtful CRO will try to understand: okay, who’s our ideal customer profile, our ICP? How do we get to that person? What messages are going to resonate? You obviously know the three whys. The first why is, why will this person do anything? What problems or pain or opportunities can you showcase for this person to take action? Fighting inertia is the biggest battle in sales. Once you’ve created that energy, then you have to convince them: why is your product better than any alternatives and substitutes out there? So you have to have a mechanism or process to set the criteria for how they make a decision—and obviously do it in a very authentic way. And then the third thing is, can you get that deal done in a time frame that is acceptable to you, that the business needs?
Those three steps have to be in your playbook, and a good CRO will customize the playbook for that specific business. Obviously, they have to work with the leadership team and the founder to make sure they get the right inputs. But that’s the role of a CRO. Then, once you’ve set the playbook, it’s: who do I need to hire, and how quickly, relative to how the business is growing? That’s the gap I find between a really great CRO and someone who’s just coming in and running the same playbook over and over again.
Brian Halligan: Can I push back a little on that?
Dev Ittycheria: Sure.
Brian Halligan: You and I know each other because I grew up at PTC, and you hired a lot of PTC people into your sales org. I’ve recently been on the interview committee with a whole bunch of Sequoia-backed CEOs looking for CROs. And it has surprised me how many ex-PTC people are actually in the market, interviewing and qualified for some of these.
Dev Ittycheria: MongoDB people are in huge demand.
Brian Halligan: Huge demand. Mongo’s the new PTC, in my head. The second thing that has surprised me is how many of the people who come in who didn’t work for PTC—you ask, “How are you going to run the sales org?” and they say, “MEDDIC.” They basically repeat the PTC sales book. So I kind of push back. I feel like a lot of people are like, let’s just bring in the Mongo/PTC playbook and not overthink the goddamn thing.
Dev Ittycheria: Well, the question is, are they reading from a book, or do they really know what to do?
Brian Halligan: Let’s just say they grew up in an org that ran MEDDIC and ran all the PTC stuff.
Dev Ittycheria: To me, it comes down to philosophy. I philosophically believe that the essence of sales is qualification. Why does the customer want to do something? What pain do they have? What problem are they trying to solve? Who’s going to be involved in the process? How much budget is available? Do I need to go find budget? What is the time frame in which they’re going to make a decision? Who’s my competition? You’re constantly qualifying, qualifying, qualifying. Whether you call it MEDDIC or whatever, that is a qualification methodology to say: have I uncovered answers to all the key questions that I need in order to forecast a deal? Whatever acronym you use, I don’t care. But you’ve got to have a very robust qualification methodology.
Brian Halligan: Fine. But I’m sort of pushing back on you. You’re saying you’ve got to get down to the three whys, and the person you’re hiring—let’s say at some infra company—should rethink things from scratch a little bit and build a custom playbook for that company. When it certainly seems like enterprise sales is almost a solved equation, a little bit. There’s a playbook and a set of people running that playbook. Shouldn’t you just be looking for one of them?
Dev Ittycheria: Here’s where I disagree with you. Selling infra software is difficult, and different from selling application software. With infra software, you have to get the end user to buy in. You may have to get the operational people to buy in, and the security people to buy in, and then the economic buyer to buy in. And the value proposition for each of those personas is very different. The end user cares about one thing. The security people care about another. The ops people care about something else. And the economic buyer says, “Where’s my ROI?” Whereas when you’re selling an app, typically the ROI is kind of consistent all the way down, across all those personas.
And also, infrastructure is a much more technical sale. Obviously things are changing, but the app layer is all about the business logic—can you encapsulate the business logic in a way that’s usable and deployable in a scalable way? With infrastructure—selling databases is not exactly for the faint-hearted. You’ve got to get developers to buy in. They have the right to say no, but they don’t have the right to say yes. They can kill your deal and say, “I’m never going to use MongoDB.” But if they say, “I want to use MongoDB,” it doesn’t mean you’re going to get a PO before the end of the quarter. You’ve got to get buy-in from the security people. Whether it’s an on-prem deployment or a cloud deployment, the ops people still need to be involved. The stakeholders building that application have to say, “Yes, this is the right architecture.” And then someone from procurement has got to say, “Explain to me the economics for why I should pay this much.” That is a pretty complicated sales process.
And then obviously ASP matters a lot. Are you a big-ticket item versus a small-ticket item? Are you a top-down sale versus a bottoms-up sale? For example, at MongoDB, when I got there, the previous regime had brought in a bunch of SuccessFactors salespeople, and all they did was sell top down. You’ve got to do a mix of bottoms up and top down, but the key is you’ve got to first get the end user to want your technology. So that’s where I would push back. Yes, at a high level, enterprise sales is all the same. But when you peel back the onion, there are lots of differences in how you have to sell based on the product and the market you’re going after.
Brian Halligan: The biggest mistake CEOs are making when they’re hiring these CROs?
Dev Ittycheria: One, they conflate the success of the person’s past company with how successful that person is. When you’re hiring an engineer, you want someone who’s come from the best engineering teams, because they quickly weed each other out. If you’re not a good engineer, you can’t hold your mustard with everyone else. You’re going to get thrown out. So if you’re hiring someone who came from a really robust engineering organization, great. That’s a pretty good signal. Whereas if you’re hiring someone from a great company that’s had great success, sometimes those salespeople underestimate the value of their business card and the fact that they got a lot of inbound demand. What I look for is someone who was maybe selling the second- or third-tier product in the market, and they were still successful. That tells me they had to deal with a very powerful incumbent, they had an inferior product, and they still could sell. That tells me they can sell.
Brian Halligan: Love that. Anything else? Failure conditions?
Dev Ittycheria: How should I say this? Senior executives are the best bullshitters around.
Brian Halligan: Yes, they are.
Dev Ittycheria: Because they know a good story. They have a good rap. They sound very credible. They dazzle you with all this charisma and charm and polish. And what you’ve got to do is reference checking. I did a tweet on reference checking. I had a senior, very successful founder call me on two senior execs who had worked for me a while ago. And after he called me, I reflected on that call and said, that happens to me so infrequently.
Brian Halligan: Yes.
Dev Ittycheria: Not many people do it. For a founder, the most consequential decision you can make is assembling your leadership team. Why would you not call and reference check? And not the references they give you, because no one’s going to give you the person who thought they were a bozo—the people they worked with, who you can find. It’s so easy to find these people between the internet, LinkedIn and all these other angles. It’s criminal to not do blind references.
Brian Halligan: I’m in violent agreement. Okay, back to the question I had. You’ve been a CEO from two to 20 to 200 to 2,000. We work with some of these CEOs going through this. My goodness, is it happening faster—so much faster than you and I had seen. And my goodness, has AI changed the playbook, or hasn’t it? You’ve talked a lot about some of the timeless things. What is new or different about being a CEO today? Or is it just, no, it’s the same old shit?
Dev Ittycheria: I think the differences are: one, the speed—the half-life of decisions is much shorter. The world is changing so quickly. In the old days, you could kind of deliberate or basically punt on a decision for a while. I think now you’ve got to act quickly. Otherwise the world’s just going to go by you.
Two, in the old software world, software margins were pretty well understood. Now, with the cost of compute and GPUs, you really need to understand not just your costs, but also your gross margins and how you price. To me, your long-term gross margin is a function of how much value you’re providing on those tokens. At the end of the day, everyone’s consuming tokens. It’s how much value you’re providing on top of the tokens being consumed. So you really need to understand the economics of your business well, especially as these models get better and better.
Brian Halligan: Because you’re building things—if you build something and it didn’t work, it’s like, oh, no big deal, let’s kill it and rebuild it. You can build stuff so much faster, right?
Dev Ittycheria: Right. And you’ve got to constantly monitor whether what you’re building is working. Sometimes it’s not working. Look at what happened with the frontier models. Eighteen months ago, everyone thought OpenAI was crushing it and Anthropic was number two. Now the reverse is true. So the speed at which the world is moving is very different.
I would say the third thing is talent. Now you can do a lot more with fewer people, so there’s a premium on talent—on having the right people. You mentioned Winston. I had Winston come and talk to my team, and one of the things he told me afterwards was, “One of the things I’m doubling down on is people.” The right person is worth their weight in gold. The wrong person could crush a team or even a company. So being very, very judgmental on the team and the people you have, especially in senior roles, is super, super important.
And the last thing I would say—this was important in the old days, but it’s even more important now—is that a good founder needs to modulate the euphorias and the panic modes. You could have a euphoric moment when things look really good, and a good founder needs to keep everyone’s ego in check, saying, “You’re not as good as you think you are. There’s a lot of inbound demand.” And then there are times when a new model drops and you’re like, “Oh my God.” And you’ve got to make sure people know, “No, this is all good. We’re going to work through this,” and remind them of the long-term opportunity. If a founder can do those four things well, I think they’re okay.
Brian Halligan: Those are great. Just a couple of tactical things that come up from founders all the time. In my life, we did 12-month planning cycles. We did a big off-site. We had a whole cycle, and we kind of ran heavy on the tracks. What do you do now? I assume you ran 12-month planning cycles.
Dev Ittycheria: We ran 12-month planning cycles, but every 90 days we recast the plan.
Brian Halligan: And you didn’t do that before?
Dev Ittycheria: No, we did that before. But I think now there’s even more of a premium on redoing that and putting a lot more rigor on what’s happening. Database decisions still tend to be a little bit longer term than other decisions, so I don’t think that showed up in our business as much as in other people’s businesses. But you still want to recast the plan, because your revenue plan is also your proxy for your expense plan. As you’re recasting the plan, what you want to ask is: is my revenue ideally going up faster than I expected? And am I investing appropriately to go service that demand, and making sure I can take advantage by investing in all the things I maybe couldn’t do before? And now I think it’s so much more important to be disciplined about cutting things that are just not working—ruthlessly.
Brian Halligan: Because you start an initiative and it’s just going, and you almost forget about the things you’ve got going. I feel like CEOs need to be the editors-in-chief. But it’s hard to cut that stuff. Any advice on that?
Dev Ittycheria: Back to: CEOs need to be confrontational. They need to challenge the leadership team and those teams: “Why should we keep investing in this?” And again, you can use a nice question: “If you owned 100% of this company, would you still be investing in this project?”
Brian Halligan: Yeah. In the early days of HubSpot, I was not focused, and I got a lot of feedback that I wasn’t focused. And then I got into the mode of being very focused: there are three things we’re going to do a year, here are the projects, we’re going to grind and report on them. I was very good at that. I feel like these days focus is less important, and that you can do more things at the same time. For example, so many of these companies I work with and you work with are, in year two or three, really expanding in Europe, which is something you wouldn’t dare do unless you were seven or eight years into a pretty stable business. Your thoughts on focus?
Dev Ittycheria: It’s less about focus than clarity on your strategy. What is your strategy? Where are you going? And your strategy can evolve. Your actions are obviously a function of what your strategy is. And are you bringing people along in terms of where you’re going? The job of a CEO or founder is to say, “Hey, we’re seeing a ton of success in North America. We’re seeing some signs that Europe is going to be big. We should go.” And then you should understand, okay, what are the trade-offs? That means I don’t invest as much in North America. Or maybe I don’t expand to Asia for another couple of years; I go to Europe. And then the question is, where in Europe? The irony is that right now, Europe is not exactly a great economy. Even at the best-run public companies, their European teams are not doing that great.
Brian Halligan: The problem for Europe is the Legora story with Harvey. Harvey’s crushing them, but everyone’s worried that a startup will grow in Europe and take a lot of market share that’ll be hard to win back.
Dev Ittycheria: Yeah, but I’m less worried about that. I think you’re either a global champion or not.
Brian Halligan: It just slows you down when you go to Europe.
Dev Ittycheria: Yes, but I think it’s not existential.
Brian Halligan: You grew from two to 20 to 200 to 2,000. A whole bunch of my CEOs are in that, call it, 200 to 2,000 range. What changed in there—about your job, about you, about the work?
Dev Ittycheria: One, obviously, when it comes to team, the question you have to ask yourself is: is this the right team for the next two to three years? Maybe now it’s just two years, or 18 months. I think a lot of people—you know, what got you here will not get you there. You have to be, again, very judgmental about whether you have the right team to get you where you want to go. So that’s point number one.
Two, as the business scales, you can’t be in every decision. So you need to start having a mechanism for spot-checking things. Like you said, maybe you have a vacancy, so you go run that division or that team and really know what’s going on. Or you’ve just recruited a new executive, and without micromanaging, you want to still be very involved and understand what they’re doing, and make sure they have the right context and they’re making good decisions, because that’s a very fragile part of the organization. Or you could have someone you start to have reservations about, because they got you here, but you’re not convinced they’re going to get you there. The joke—in any audience, I always ask, “Has anyone here fired anyone too quickly?” No one.
Brian Halligan: Ever.
Dev Ittycheria: Because they introduce hope into the process.
Brian Halligan: Hope is a four-letter word for you.
Dev Ittycheria: Yes. And that’s where I think a CEO—again, what I’ve trained myself on is the asymmetry of information between bad news and good news inside an organization. Whenever I hear something bad, I automatically assume two things. One, I’m the last to know, because bad news always travels very slowly up the organization, but much more quickly down the organization. And two, it’s far worse than what people are telling me, because people sanitize bad news. If you have a customer telling your account team, “We’re throwing you out,” by the time it surfaces to you, in most organizations it surfaces as, “Oh, we have a little problem with Acme Company. We’re on top of it.” Now, we don’t do that at Mongo, but a lot of companies do. And then you find out a month later that the customer churned. And then the question is, why didn’t you act? Again, back to my point: most of the elapsed time between problem identification and problem resolution is acknowledging that it’s actually a problem. When you acknowledge the problem, then you can throw resources at it and say, “We’ve got to go fix this.”
Brian Halligan: Okay. And you think that’s extra important between, call it, 200 and 2,000, where you’re getting bigger and stuff slows down?
Dev Ittycheria: And also, when you’re 40 people, everyone still knows you on a first-name basis. You’re not the grand poobah of the organization. Now you’re 2,000 people: “Oh my God, I saw Dev in the hallway.” So you’ve got to recognize that people are much more intimidated by you as a function of your role and title.
Brian Halligan: The first time you noticed that?
Dev Ittycheria: I could just sense it. I could sense people were very nervous. Or my assistant would come tell me, “Oh my God, they’re so excited to meet you.” And I’m like, really? I’m still the schmuck I was. So you really, really have to operate in a way of saying, “I’m always looking for bad news,” because it’s so hard to find.
Brian Halligan: Okay. When you speak to people, you ask them, “What do you think people say about you when you leave the room?”
Dev Ittycheria: Yes.
Brian Halligan: What do you think people say about you when you leave the room?
Dev Ittycheria: Well, let me answer why I ask that question.
Brian Halligan: I know where it came from. It’s good.
Dev Ittycheria: One of the most effective traits of leaders is how self-aware they are—and actually, how situationally aware they are. How self-aware are they about how they’re coming across? And can they read the room? Are people grokking what they’re trying to say? Are there some people nodding, but you really know they’re not buying in? Are there some people who are checked out, or some people who are very grumpy because this is a decision they’re just not going to buy into? One of the reasons I had to get rid of execs is that they were very self-unaware. They become disconnected from how they’re coming across. The reason we look in the mirror is, “Hey, did I put my shirt on correctly? Are all the buttons buttoned? Have I got a hair sticking out that’s looking weird?” Being self-aware is also having a mechanism to ask, do I really understand how I’m coming across? So a test of how self-aware you are is understanding what people say about you when you leave the room.
Brian Halligan: So this came from PTC—from my supervisor at PTC. At PTC, I ran the Pacific Rim for a long time, and it ripped, and I was overconfident, let’s just put it that way, for a few years in there. I came back and he gave me that line. He said, “What do you think people say about you when you’re not in the room? By the way, you’re never in the room, because you live over in Hong Kong.” I said, “I don’t know.” He said, “People say you think your shit doesn’t stink.” That was 30 years ago, and it still sticks with me. It was a very valuable thing. What do you think people say about you?
Dev Ittycheria: I think it depends. At my best, I think people say: he’s very driven. He can separate the signal from the noise. He holds us accountable, but it’s coming from a place of caring. At my worst, I’m probably someone who can be a bit of a missile, where I won’t go around you, I’ll go through you. I can intimidate people to the point that they get dysfunctional. A lot of the frustration I express at them—I’m really angry with myself, but it’s coming out at them. And I have to check myself. I’ve gotten better at that. But the early Dev—I mean, I probably would have been fired at MongoDB two years in [laughter]. And there are times when I’ve not always been present in meetings, and people can sense that, because there’s something going on that I can’t get out of my head and I’m kind of going through the motions of the meeting. So it really depends situationally on what’s going on.
Brian Halligan: I’ll tell you what I say. I say you’re a wise, seasoned operator, maybe the best in tech. I appreciate you coming on the pod and dropping all the wisdom on us. Thank you very much.
Dev Ittycheria: Thanks, Brian. That’s very nice of you to say.
Brian's Takeaways
Brian Halligan: I hope you guys liked that. Dev is a real operator. I learned a lot from him, and I’m taking a lot of it into my new role as CEO of HubSpot. I really liked the part where he talked about the four things that CEOs need to be very good at.
The first is just high agency: hire high-agency people, and encourage high agency. I’ve been trying to do that at HubSpot. I said in my first company meeting presentation, “Pretend like you own 100% of the shares of HubSpot.” And I got like 50 emails from employees saying, “If I owned 100% of the shares of HubSpot, I would do this.” I find that to be a very useful kind of rubric. And people look at you a little funny. It’s like, okay, that’s a good perspective.
He talked about fast decision making. I’ve been trying to do that at HubSpot, and I think fast is more important than it used to be. It used to be that many of the big decisions CEOs made were kind of one-way doors. You couldn’t go back through that door, and you set sail and it’s just hard to turn that ship around. Most things are two-way doors today. You can build so fast, you can change your mind on most things. So I think speed is a weapon these days. And I’m trying to make a lot of fast decisions here at HubSpot while I still have a beginner’s mind, particularly.
Know your economics. He’s not talking about your P&L and your balance sheet. He’s talking about the underlying economics of the business. I think that’s good advice. Some of the first things I’ve done getting back to HubSpot are to look at usage every way to Sunday, look at NPS every way to Sunday, and then look at unit economics every way to Sunday. Those are the drivers. Those are the leading indicators of what’s going to happen in the future. So I’m pretty zeroed in on that, and you should be too. I like when CEOs talk about leading indicators.
Be the steady person between the high highs and low lows. Historically, in my first run at HubSpot as CEO, this was not me. I would bounce really high and bounce really low, and everyone could kind of feel it. This time I’m going to try to be that steady presence. I took this to heart, and I brought this with me in my first week on the job at HubSpot, and I’m hoping I can keep it up, because there’s going to be a lot of high highs at HubSpot, and there’s going to be a lot of low lows. And I hope to be the steady-as-she-goes.
Just an update on the pod. I’m really enjoying doing it. I’m going to continue to publish episodes. They’re just going to be a little less frequent. If we have a terrific guest, or a friend of mine wants to come on, that’s going to be amazing. We’re going to do it. It may not be every other week like we’ve been doing, but we’ll continue going on, and we’ll have some bangers for you. Thanks a lot.

