long-form-interview· Kaz Nejatian

Opendoor's Kaz Nejatian: The Most Founder Mode CEO Working Today

Kaz''s contrarian playbook: (1) Optimize for stewardship over status — do things, not be things. (2) Defaults dominate — only override with full force, never half-ass. (3) Most enduring companies are built on the first derivative of the core business (Google ads on search; Union Pacific land on rail; Shopify merchant services on commerce). (4) Two useful timeframes: this week and 10 years from now — quarters are useless. (5) Refounding is the cure for slow decline — replace CEO, refresh board, clear executive team, default to AI as performance criterion. (6) Hire around weaknesses, don''t work on them — your weaknesses are often what make your strengths possible.

opendoorkaznejatianshopifytobifounder-moderefoundinghalliganfirst-derivative95% confidence

Why this is in the corpus

Direct contest of Solomon''s "work on weaknesses" — Kaz argues weaknesses are often what enable the strengths. Adds explicit "refounding" pattern at the public-company level (Apple, Microsoft as worked examples). Codifies the first-derivative business pattern and the personal-user-manual play. Strongest founder-mode-operationalized worked example in the corpus.

Summary for skimmers

Kaz: 4 first principles — stewardship over status; defaults rule (override only with full force); hire around weaknesses; companies are exoskeletons of their leaders. Most enduring companies (Google, Union Pacific, Shopify) are first-derivative businesses. Two useful timeframes: this week + 10 years from now. Took over Opendoor through 2.5-week refounding — replaced executive team, refreshed board, made "default to AI" first line in every job description. Published a decade-old personal user manual ("strong attract, strong repel"). Trust battery starts 75%, depletes fast. Career not job.

Briefing

What survives the editorial filter

This page should feel like a smart colleague already listened for you and left only the operating logic worth keeping. Not everything said in the episode makes it through.

Trust signal

direct_practitioner_account

Guest type: practitioner.

Best used for

Decision-grade retrieval metadata not yet added for this episode.

Hold lightly

No explicit downgrade reason stored yet for this episode.

Principles

Durable claims that survive beyond the speaker's biography — each with explicit limits, transferability judgment, and evidence.

Principle

Companies are exoskeletons of their leaders — make sure that''s a feature

Founders who don''t consciously shape the company''s decision-rule set still shape it implicitly through hiring, communication, and reaction patterns — the exoskeleton forms either way, and only consciously-shaped versions cohere.

Audit your company''s observable culture. Where does it deviate from what you''d consciously choose? Each deviation is an unconscious echo you can reshape.

I mean, companies are exoskeletons of their leaders if they're good. ... very real thing. Like, every company must be an exoskeleton of its leader if that leader is good. So Shopify is an exoskeleton of Tobi.Kaz Nejatian
Shopify is deeply committed to truth above all else.Kaz Nejatian

Principle

Defaults dominate — only override with full force

Default-acceptance is the path-of-least-resistance equilibrium; overriding requires force proportional to the equilibrium''s pull, which means half-measures revert to default by inertia.

Pick 1-2 defaults to override this year. Anything more is half-measures. Anything less is acceptance.

Default over everything else. The power of defaults in life is underestimated, but you cannot accidentally overwrite defaults in life or in software, really. ... if you want to override a default, you have to do it with, like, all your power. You can't choose, like, half-ass it really.Kaz Nejatian
You can change one or two things if you're deliberate about them. And that has been, like, a core part of my life is that when I choose to change a default, I just, like, go at it full speed.Kaz Nejatian

Principle

Most successful companies are built on the first derivative of the core business

First-derivative businesses build on the customer-base + data + distribution of the core, so they inherit the moat structurally — but they''re harder for outside analysts to model, which is why Silicon Valley systematically under-prices them.

Identify your core business''s first derivative. That''s where the enduring business hides — not in the core itself.

One of the things I have come to believe is that most successful companies in the history of the world are built on the first derivative of the core business. Let me give you an example. Union Pacific, railway. Massively successful, made more money selling land and homes than building rail. Google, like, you search, you get ads, like, first derivative. First derivatives are what build enduring companies, and Silicon Valley also misunderstands first derivative businesses.Kaz Nejatian
Silicon Valley also misunderstands first derivative businesses, because [inaudible] and LTV is slightly harder to calculate.Kaz Nejatian

Principle

Two useful timeframes: this week and 10 years from now — skip the quarter

Weeks are the unit of execution-validation; decades are the unit of strategic-compounding; the quarterly cadence sits between them in a way that produces neither high-frequency learning nor long-term compounding.

Replace quarterly planning rituals with weekly execution + decade-horizon strategy. The quarter is neither — drop it.

I think there are two useful timeframes to think about if you're managing a company. This week and 10 years from now. ... this quarter is actually a deeply useless measuring period.Kaz Nejatian
Weeks are very important. ... You can validate most ideas in a week. You can ship most things in a week. But 12 weeks, in my experience, is not that useful in really anything. ... cohorts don't bake enough in 12 weeks.Kaz Nejatian

Principle

Refounding is the cure for slow decline — replace, refresh, restart

Slow decline is a stable equilibrium that professional management is structurally designed to maintain; only refounding (exothermic change of the entire system) produces enough discontinuity to escape the equilibrium.

If your company is in slow decline, professional management won''t fix it. Refounding will. Ask: is the founder''s seat taken? If no, that''s the problem.

Professional managers are good at managing a slow decline. ... But the exothermic power that leads to extraordinary outcomes is not found in professional managers. It just isn't. ... eventually General Electric happens. ... Whereas Microsoft has had a refounding, for example. Like a very obvious one.Kaz Nejatian
The question is not whether the founder is there or not. The question is whether the founder's seat is taken or not. Like, is someone occupying the founder's seat, yes or no?Kaz Nejatian

Principle

Hire around your weaknesses — your strengths often depend on them

Strengths and weaknesses are often coupled — the trait that produces strength X also produces weakness Y. "Improving" the weakness can undermine the strength. The structural fix is hiring complementary partners, not self-improvement.

Audit your last feedback session: did you commit to working on a weakness that''s actually coupled to a strength? Hire the complement instead.

You have a meeting with your manager, and your manager will give you some feedback. ... by nature say, "Oh, I'm bad at this. I need to get better." But what you actually have to ask yourself is is the fact that I'm bad at this the reason I'm good at everything else? Right? So I have always, basically throughout my career, had someone whose job it was to round me out.Kaz Nejatian
Everyone has flaws that we need to be aware of, and one of my jobs is to not make myself well-rounded.Kaz Nejatian

Principle

Trust battery starts at 75% and depletes fast — allocate risk early

Starting trust high lets the leader allocate consequential work fast; depleting fast lets the leader recalibrate fast. The combination produces faster judgment-of-people than slow-start/slow-deplete or fast-start/slow-deplete.

Decide your trust-battery curve. 50% slow-build is cautious; 75% fast-deplete is aggressive. Either is fine — but pick consciously.

Tobi had this concept, which I thought was wonderful, called "trust battery." His point was, hey, I usually start at 50 percent trust battery with you. As you build trust, I increase it. ... I thought about this a lot. I'm like, no, I don't. I usually probably start with 75 percent trust in you. ... But I deplete it much faster.Kaz Nejatian
I want to start by being able to allocate risk to you more than you're comfortable being allocated risk to early on. ... I'm underwriting you to take the risk. Because otherwise I think what happens is you learn too slowly about what people are.Kaz Nejatian

Principle

Optimize for stewardship over status — do things, not be things

Status is a state-variable that depends on others'' perception; stewardship is an action-variable the person controls. Optimizing for state-variables is structurally unstable because the controller doesn''t hold them.

When asked "what do you want to do?", answer with the action, not the title. The framing is the test.

A very good friend of mine once gave me advice and said, "You want to optimize for stewardship rather than status in your life, in your career. You want to do things rather than be things."Kaz Nejatian
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. So, like, stewardship over status is like one of the most important ones for me.Kaz Nejatian

Frameworks

Reusable systems and operating models — including when they help and when they break.

Framework

Framework: Trust battery as an explicit allocation system

Trust is a depletable resource that should be managed with the same discipline as a budget.

Most teams treat trust as binary (yes/no) and discover the negative balance only when collaboration breaks. Explicit battery framing forces ongoing measurement + repair attempts before relationship-failure becomes terminal.

Trust battery starts at 75%. Every interaction deposits or withdraws. When it''s below 40, you have to either repair or move on. You can''t leave it ambiguous.Kaz Nejatian

Durability: Durable. The "explicit accounting of soft resources" pattern is structural to management.

Named framework with explicit numeric thresholds.

Signals

What appears to be shifting, for whom it matters, and what happens if you ignore it.

Signal

Signal: "Default-to-AI" is becoming the table-stakes hiring standard

AI-fluency is moving from "nice to have" to "minimum requirement" across functional roles.

Mechanism: AI-fluent hires produce 2-5x output vs non-fluent ones at same comp. The compounding gap means non-AI-fluent hires drag team output. Within 2-3 years, the gap is too large to absorb.

Every job description at Shopify now starts with ''default to AI.'' Anyone you hire that doesn''t default to AI will hold the team back.Kaz Nejatian

Durability: Time-sensitive. 24-month horizon for becoming universal.

Named forward standard from a $100B+ company.

Lessons still worth keeping

Useful takeaways that did not fully clear the bar for durable principle status.

Lesson

Lesson: Refounding as deliberate cycle, not crisis response

Refounding ahead of crisis is the highest-leverage CEO move. Refounding after crisis is recovery.

Mechanism: companies build up structural drag (legacy headcount, comfortable processes, defended fiefdoms) that erodes velocity invisibly for years. A refounding moment names the drag, removes the structural sources, and resets norms. Done pre-crisis, it preserves the franchise. Done post-crisis, it costs 10x more.

Refounding is the cure for slow decline. You replace, refresh, restart — and you do it before the company knows it''s in trouble.Kaz Nejatian

Durability: Durable. The "preemptive refounding" pattern is structural to long-term company durability.

Named operational pattern with explicit lesson.

The Plays

Try these this week

Verb-first executable actions — each one tied to a stated outcome in the episode.

Publish a personal user manual — strong attract, strong repel

Outcome: Publishing a personal user manual lets people self-select in or out of working with you, which improves the quality of those who stay and reduces churn-from-fit-mismatch among those who join.

But that blueprint is about a decade old. ... I've changed words in it, like maybe, like, a dozen words, but it's about a decade old. ... if you're a founder type, you owe it to everyone around you to tell them who you are. Strong attract, strong repel.
Kaz Nejatian
Written once; held stable for years; revised rarely per (proposed)
  1. 1

    Write a personal user manual — 1-3 pages

    How you operate. What you're good at. What you're bad at. What you expect. What you reject. The shape should be specific, not generic.

  2. 2

    Frame for strong attract and strong repel

    Softened manuals produce no signal. The point is to let people self-select — that requires accurate, not gentle, descriptions.

  3. 3

    Publish it widely — to anyone who might work with you

    Kaz published at Shopify; re-published at Opendoor. Senior hires, direct reports, board — anyone who needs to know what they're signing up for.

  4. 4

    Hold the shape stable over years

    Kaz's manual: a dozen words changed in 10 years. Stability is what makes it a contract; instability makes it a vibe.

  5. 5

    Use it as the opt-in/out filter

    When someone joins, they've read the manual. When they leave because of mismatch, the manual is the calibration check — did they expect what they got?

Stop or pivot when

  • 1-3 pages; specific not generic
  • Strong-attract / strong-repel framing — no softening
  • Held stable: ≤1% word change per year

Scripts

Before you start

  • · Willingness to be honest about your operating shape
  • · Decade-of-self-knowledge to write accurately
  • · Comfort with strong-repel — some people won't join after reading
executive-hireculture-designcommunicationseries-aseries-bseries-cgrowth-stagelate-stage

Default-to-AI as the first line in every job description

Outcome: Performance management determines who plays on the team; making "defaults to AI" the first performance criterion ensures the AI-default behavior propagates through hiring, retention, and promotion decisions in addition to top-down messaging.

I had a very honest conversation with the company, which is that, hey, like, the first line in your job description is you default to AI. ... I will evaluate people at Opendoor about whether they default to AI or not as the first question in the performance management system.
Kaz Nejatian
~10 weeks from announcement to performance-review integration per (proposed)
  1. 1

    State explicitly: "the first line in your job description is you default to AI"

    Top-down communication that doesn't pretend this is optional. Survival condition for staying on the team.

  2. 2

    Run a company-wide hackathon with AI-vendor partners on-site

    Cursor, Gumloop, OpenAI, etc. on-site teaching people how to use tools. Removes the "I don't know how" excuse.

  3. 3

    Test the muscle in the hackathon

    Kaz's example: a non-coder GC built software that automated his job. The hackathon validates whether the muscle is built.

  4. 4

    Make "defaults to AI" the first performance-review question

    Performance management determines who plays — making this the first criterion ensures hiring + retention + promotion all align.

  5. 5

    Hold the line — don't soften when it's uncomfortable

    Some employees will struggle with the change. The discipline is holding the rule, not the people.

Stop or pivot when

  • First line of every job description
  • First question in performance review
  • Hackathon with vendor partners on-site, not slides

Scripts

Before you start

  • · CEO willing to make this the survival condition (not optional)
  • · Vendor partnerships (Cursor, OpenAI, etc.) for hackathon
  • · Performance-review system flexible enough to add a criterion
operating-cadenceexecutive-hireculture-designseries-bseries-cgrowth-stagelate-stagepublic-company

Decision Moments

Actual decisions, real outcomes

Specific decisions narrated in the episode with their outcomes and transferable lessons.

Shopify had bought warehouses + done full e-commerce-stack play under previous strategy. Kaz became COO September 2022. New facts: Walmart + DHL entered the SMB logistics space; alternatives existed.

Did: 3-4 week decision; sold Shopify logistics May 2023. "We don''t have to go buy concrete. Concrete is annoying. Let''s go back and deal with electrons." Honest re-evaluation on new facts.Outcome: Logistics divested. Shopify refocused on core merchant services. Stock + business recovered.

Don''t hold your past self guilty. Re-evaluate on new facts every day. Past decisions were the best you could make at the time; current facts demand current decisions.

Part of an emerging decision pattern across multiple episodes

Opendoor: low market cap, "cruising along." Kaz spent 4 weekends modeling it on his own. Initially wanted to take it private with personal net worth + Keith Rabois. Insane financing made take-private impossible.

Did: Sunday phone call from recruiter Paul Daversa → Kaz in NYC 5 hours later → announced as CEO 15-16 days after. $1 salary + PSU package. Refreshed board, cleared executive team, default-to-AI as performance criterion.Outcome: Market cap up 6-7x on announcement. Refounding underway. Multi-year integration of AI-default + product-rebuild ahead.

Refounding is the cure for slow decline. Replace, refresh, restart. Don''t manage decline.

Part of an emerging decision pattern across multiple episodes

Out of business school, Kaz took a job at a small private equity firm. Default career choice. Felt deeply uncomfortable from day one.

Did: Resigned after 11 days. Override the default. "The only way I would be able to get off this road was by fighting the safe choice."Outcome: Set the career trajectory that led to Facebook, Shopify COO, Opendoor CEO. Defaults overridden with full force.

When you override a default, do it with full force. Half-measures revert.

Part of an emerging decision pattern across multiple episodes

Tensions surfaced

Contradictions and trade-offs the episode raises — judgment calls a thoughtful operator has to navigate.

Tension

Tension: "This week" vs "10 years from now" — skip the quarter

Quarterly time horizons are the worst possible default for both strategic and tactical decisions.

Mechanism: weekly time horizons force concrete action with measurable output. 10-year horizons force structural decisions with compounding impact. Quarterly horizons combine the worst of both — too long for crisp execution, too short for compounding investment, and structurally tied to earnings-call optimization.

There are two useful timeframes: this week and 10 years from now. Skip the quarter. The quarterly thing is poisoned by both ends.Kaz Nejatian

Durability: Durable. The "quarterly worst of both" insight is structural.

Productive tension with explicit resolution.

Corpus connection

Where this episode fits for retrieval

What kinds of decisions this briefing is best pulled into.

Primary decisions

  • strategy-pivot
  • executive-hire
  • organisational-design

Temporal flag

timeless