Sequoia CEO coach: Why it’s never been easier to start a company, and never been harder to scale one | Brian Halligan (co-founder, HubSpot)

The thing about being a founder, CEO is there's no one there to rescue you. Your parents aren't gonna rescue you, your BC's not gonna rescue you. That kinda hits you when you hit your first crisis. Starting a company has never been easier, scaling one into a durable high impact organization has never been harder. The number of companies formed is going to mushroom over the next 10 years relative to the last 10 years. It's just gonna be hard to stand out and Really accelerate what's most different about what it was like to be a CEO maybe 10, 20 years ago versus today. There's a massive tax and optionality when you can move this fast and try a lot of things. It puts pressure on the CEOs to be faster and better decision makers. A lot of people in the world want to be founders. They want to be CEOs. I don't think anyone can do it. People talk about nine. It's way more than that. It's full contact. Do you feel like there are specific profiles or traits to be successful? I look for four things. I call it my lock algorithm. Today my guest is Brian Halligan, co-founder and longtime CEO of Hubspot.

I asked Brian to come on this podcast because he is more than anyone I've met. A student of the job of a CEO. After leaving Hubspot last year, he became the in-house CEO coach at Sequoia, where he brings together dozens of top CEOs to learn from each other. He does one on one coaching with some of the world's top CEOs. He also hosts a popular podcast called Long Strange Trip. Where he interviews some of the world's most successful CEOs.

In this conversation, we unpack what it takes to be a successful CEO in today's era. Let's get into it after a short word from our wonderful sponsors. Applications break in all kinds of ways, crashes, slowdowns, regressions, and the stuff that you only see once real users show up. Sentry catches it all. See what happened, where, and why. Down to the commit that introduced the error, the developer who shipped it, and the exact line of code all in one connected view. I've definitely tried the five tabs and slack thread approach to debugging. This is better. Sentry shows you how the request moved, what ran, what slowed down, and what users saw.

We already have this episode, so unlocking it is cheap and permanent: the full transcript, segment and word-level timestamps, and .txt, .srt, .vtt and word-level JSON downloads, as many times as you like, forever.

10 free credits is 10 episodes like this one a month. Episodes nobody has transcribed yet cost their length in hours, because we have to actually transcribe them.