Kaz Nejatian on Refounding Opendoor: The Most Founder Mode CEO Who Isn't the Founder

Kaz Nejatian might be the most intentional CEO in tech right now. A former Shopify CTO who left to refound a struggling public company, he operates from a set of deeply held first principles that inform everything from how he structures his compensation to how he talks about Open Door with his six-year-old at dinner. This isn’t a turnaround story in the traditional sense. It’s a case study in what happens when someone who genuinely doesn’t care about managing decline takes the founder’s seat.

The Episode

Brian Halligan (HubSpot co-founder, now at Sequoia) sits down with Kaz Nejatian for an unusually personal conversation that covers his immigrant roots, his faith, his approach to marriage and family, and the mechanics of taking over a public company in two and a half weeks. Kaz is disarmingly honest about his weaknesses as a manager, his deliberate overriding of life’s defaults, and why he believes most professional CEOs are incentivized to delay death rather than build something.

The conversation has a different texture from most founder interviews. Kaz doesn’t perform confidence or vision. He talks about bursting into tears after a day of layoff conversations at Shopify, about reading the Bible every day as a tech CEO, about structuring his entire family life around his mission. It’s less a playbook and more a philosophy of how to live while building.

Stewardship Over Status, Defaults Over Everything

Kaz’s operating system runs on two core principles. The first: optimize for stewardship rather than status. Do things rather than be things. When people asked him early in his career what he wanted to do, he’d name a job title. His mentors pushed back: what does that actually mean?

“People who optimize for happiness end up not being happy because happiness is a state. People who optimize for service end up actually being usually deeply happy.”

The second principle is about defaults. In software and in life, people accept almost every default they’re given. You can’t accidentally override a default; you have to do it with full force. Kaz lasted 11 days at a private equity firm after business school before quitting because it was the “default choice” and he knew the only way off that path was to fight it.

The product design insight that flows from this: if you set defaults that require users to think constantly, they’ll fire your software. The same applies to life. You can change one or two defaults if you’re deliberate, but you have to go all the way.

On the personal side, Kaz reads the Bible every day and goes to church every Sunday as a tech CEO. He grew up Muslim in the Middle East, moved to Canada at 12, and arrived at faith through a deliberate process of considering what makes him better as a human being. He frames prayer as a form of meditation: sitting down, acknowledging you don’t control everything, reflecting on the day. The difference, he says, is that he meditates “with someone else present.”

The Immigrant Edge: No Safety Net

When Brian suggests immigrants succeed because they get to “reset their defaults,” Kaz pushes back. That’s the romantic version. The real answer is simpler: there’s no safety net.

“Toby couldn’t get a job. He had to start Shopify. My parents didn’t know anyone. I had to pay for college so I had to start working and no one would hire me.”

This reframes entrepreneurial risk. Human beings structurally misprice risk, which is the one structural advantage entrepreneurs have. The pain of failure isn’t as bad as you think, but there will be far more painful moments than you expect.

“Each pain is not as bad as you think it is, but everything is more painful than you think it is.”

His default advice to aspiring entrepreneurs: probably don’t. If you have to decide to be one, you probably aren’t one. The real entrepreneurs already started their paper route at seven.

Founder Mode: Outcomes, Not Processes

Since Paul Graham’s founder mode essay, Kaz has become the poster child for the concept, though he’s uncomfortable with it. For him, founder mode boils down to one thing: the CEO takes responsibility for outcomes, not processes.

He has a chief operating officer (Jung, who followed him from Shopify) whose job is process design. His job is outcome delivery. The difference between professional managers and founders, he says, is that professional managers care more about process than truth. Their source of power comes from management. His doesn’t.

“No one thinks I’m a good manager. I’ve managed thousands of people and I don’t think any of them would say Kaz is a great manager.”

But many would say they’d work for him again. Many would say he’s a good leader. The distinction matters. He doesn’t try to become well-rounded. Instead, he’s always had someone whose job it was to round him out. When your manager gives you feedback about a weakness, the real question is: is the fact that I’m bad at this the reason I’m good at everything else?

He published a “blueprint” (a user manual for working with him) that’s about a decade old. The logic: if you’re a founder type, you owe it to everyone to tell them who you are. Strong attract, strong repel. “If you go to an Italian restaurant and complain the sushi is bad, that’s your fault.”

The Trust Battery, Modified

He borrows Tobi Lutke’s trust battery concept but runs it differently. Where Toby starts at 50% and builds up, Kaz starts at 75% but depletes much faster. The logic: he wants to allocate risk to people early. If you join a hockey team, it’s a bad idea to assume the center is a bad player; you’re better off assuming they’re good and doing your job well. But when trust depletes, he acts fast. Two quarters after he joined Opendoor, only one member of the previous executive team remained.

First Derivative Businesses

One of Kaz’s most striking frameworks: the most successful companies in history are built on first derivatives of their core business, not the obvious thing everyone focuses on.

Union Pacific Railway made more money selling land and homes than carrying freight. Google’s core product is search; its business is ads. Shopify started as SaaS but became a merchant services company (payments, tax, billing, ads). This is what Silicon Valley consistently misunderstands, he argues, because first derivative businesses have cohorts that bake differently and customer acquisition cost calculations that are harder.

This connects to why Silicon Valley loves enterprise sales (simple to model) and struggles with SMB and consumer. Both HubSpot and Shopify, he notes, were founded outside the Valley partly because Silicon Valley is “allergic to SMB.” Neither company would have survived the Valley’s bias.

The Shopify Logistics Reversal

At Shopify, Kaz ran the logistics division when the company made its big bet on warehouses and inventory. The decision to divest took about four weeks, and the sale happened within months.

The reasoning wasn’t that the business failed. When Shopify entered logistics, there was no good option for small businesses besides Amazon. Four years later, Walmart, DHL, and several startups had filled the gap. The customers they were trying to serve didn’t need them anymore. “We were not jealous of anyone else’s margin. The people we need to serve didn’t need us anymore.”

What impressed him about the process: Shopify is “incredibly good at successfully discovering things that don’t work and being honest with itself.” There was no table-pounding argument. Companies, he says, are exoskeletons of their leaders, and Shopify’s commitment to truth above all else comes directly from Tobi.

Lessons from Tobi Lutke

Kaz identifies Tobi’s superpower as applying a near-zero discount rate to the future. Where most corporate leaders value a 5-year outcome at 20% of its current value, Tobi cares about what happens in 10 years as much as what happens today.

From this comes a provocative claim about time horizons: there are only two useful timeframes for managing a company. This week, and 10 years. Quarterly thinking is “a deeply useless measuring period.” A week is powerful because you can validate most ideas and ship most things in a week. But 12 weeks isn’t long enough for cohorts to bake or for most meaningful outcomes to reveal themselves.

The 16-Day Opendoor Takeover

The origin story reads like a thriller. Flying home from a Shopify event in Dallas, Kaz picked Opendoor to study “for no reason at all.” He spent every weekend for four weeks modeling the company, thinking through the product, using it. His wife endured weeks of dinner conversation about nothing else.

His first move was to text Keith Rabois: “My wife and I are going to spend our entire net worth to take Opendoor private.” Sell everything, leverage as much as possible. But then the company did a financing that made acquisition impossible, and Kaz assumed it was over.

Then a Sunday phone call from recruiter Paul DeVarsa about a public company CEO job. Kaz said he wasn’t interested. “Unless it’s Opendoor.” It was. He was in New York in 5 hours. From that call to the CEO announcement: 15-16 days.

The night before the announcement, his wife was sleeping in the hotel room, so at 3:30 AM he was pacing Central Park West on calls about the deal, unable to talk in the room and unable to let anyone overhear public company discussions.

His conditions to the board: the new board members he wanted, and a promise not to care about appearances for a while. “I’m not a caretaker type. I intend to build product for a living.”

Why Turnarounds Fail (And How Refounding Differs)

Tech turnarounds are rare because most are attempted by professional managers. The most successful turnaround is Apple, which was in worse shape than Opendoor. Microsoft had an effective refounding under Satya Nadella. GE never had its refounding moment.

The key insight: the question isn’t whether the founder is present. It’s whether the founder’s seat is occupied, whether someone is bringing that exothermic energy to the system. When companies go sideways, it’s usually not one thing going wrong; it’s a death spiral where everything needs to change.

Kaz is particularly pointed about compensation structures. RSUs incentivize professional managers to delay the inevitable. He asked for a $1 salary and options. The final structure uses PSUs with zero value below certain stock prices, aligning his compensation directly with shareholder value creation. His critique: “Wall Street is full of Harvard MBA types who have driven companies to zero while getting rich.”

Making Opendoor AI-Native

A recent company-wide hackathon revealed how far Opendoor has come. A home property manager, someone who had never written code, used Cursor and Gumloop to build software that automated his entire job. He’s now managing a portfolio of AI tools instead.

The mechanism: the first line of every job description at Opendoor now reads “you default to AI.” The performance management system evaluates whether employees default to AI as its first question. Kaz frames this bluntly: “We’re a professional sports team. The job of the performance management system is to tell you whether you get to play on the team or not.”

Career vs. Job

Kaz draws a sharp line between having a career and having a job. A job is something you do for someone else to get paid. A career is something you work on every day for yourself. Most people have jobs, and that’s fine. But Kaz optimizes his entire life for his career, and so does his family.

His wife optimizes her life for his career. His kids know Opendoor’s mission. Dinner conversations involve building products with his six-year-old. “Our job as a family, we’re all in as a family.”

His advice to young people: work all the hours. When your manager lets you work, work. You need to discover your breaking points, and the only way to find them is by working hard. “Tom Brady threw a lot of passes before he got good.”

On following your passion: think instead about how you can be of service. If you think about what you can get, things work out poorly. If you think about how you can serve, they usually work out.

Afterthoughts

This episode stands out for its unapologetic intensity. Kaz doesn’t hedge or moderate. He reads the Bible every day, works relentlessly, structures his entire family around his company’s mission, and asked for a dollar salary. It’s a coherent worldview, not a collection of hot takes.

A few threads worth sitting with:

• The first derivative framework is genuinely useful for evaluating businesses. Most commentary focuses on what a company does; the real question is what adjacent value the core activity creates.
• His modification of the trust battery (start high, deplete fast) is a practical framework for new leaders entering an organization. High initial trust accelerates learning about people, even if the turnover cost is real.
• The claim that there are only two useful timeframes (this week and 10 years) is provocative but has real implications for how companies plan. Quarterly cycles may be necessary for public reporting, but they’re poor units for strategy.
• His view that professional managers are structurally incentivized to delay death rather than build is a critique not just of CEOs but of compensation design. RSUs vs. options is an underexplored lever for aligning management with genuine value creation.
• The idea that you should ask “is the fact that I’m bad at this the reason I’m good at everything else?” before working on a weakness is a useful reframe that most career advice ignores.