Let’s start with a fair statement. Venture capital has funded some of the most important companies of the last fifty years. Many investors we know are thoughtful, generous, and genuinely in the corner of the founders they back.

But the system around venture, the incentives, the narratives, the norms that get passed from accelerator to accelerator and podcast to podcast, all of that is hurting a lot of founders. Some parts of it are actively lowering their odds of success.

Three patterns worry us most.

1. Not every company is a rocket ship

Venture math depends on outliers. A fund needs a small number of companies to return the entire fund, which means investors are structurally looking for rocket ships: companies that can go vertical, fast, and become enormous.

That’s a rational strategy for a fund. It’s a dangerous default for a founder.

Most good companies are airplanes. They fly. They carry real customers to real destinations. They can be profitable, durable and life-changing for the people who build them. A $20M or $50M exit can change a founder’s life forever, and plenty of companies that never “exit” become great businesses that pay their founders well for decades.

The problem starts when a founder with a perfectly good airplane gets told the only acceptable outcome is a rocket. So they bolt on rocket engines. They raise more than the business can absorb. They hire ahead of demand. They chase rates the market can’t support. They try to run a marathon at their 5K pace. And the airplane, which was flying just fine, often comes apart in mid-air.

We’ve watched it happen. Companies with real revenue and loyal customers burned through capital chasing a trajectory that was never theirs, and ended up worse off than if they’d never raised the round. More specifically, the problem was they internalized the perspective of their most aggressive investors.

2. 9-9-6 is a burnout machine

There’s a growing glorification of extreme hours in startup culture. 9-9-6, borrowed from parts of the Chinese tech industry, means working 9am to 9pm, six days a week. We’ve even heard founders brag about 7-10-7: 7am to 10pm, seven days a week.

Founders work hard. That’s part of the job, and there are seasons when the hours have to stretch. But treating 72-plus hour weeks as a permanent operating standard is a bet against how humans actually work biologically.

Decision quality drops when people are exhausted. Judgment gets cloudy. Relationships at home erode. Teams copy the founder’s pace and burn out right behind them. And the costs compound quietly, until a founder hits a wall they didn’t see coming.

The founders we see build lasting companies treat their energy like a strategic resource. They protect sleep. They protect relationships. They build rhythms that let them perform for ten years, not ten months. A startup is a marathon run at an uncomfortable pace. Sprinting the whole way just means you don’t finish.

3. The coaching blind spot

Here’s the one that makes the least sense to us.

Investors routinely expect founders to spend money on lawyers, accountants, recruiters, and software. Those are treated as necessary infrastructure. But spending on coaching or advisory support for the founder, especially early, is often treated as optional, indulgent, or something to consider after a problem shows up.

Think about where the risk actually lives in an early-stage company. It’s concentrated in one or two people. The founders’ judgment drives hiring, strategy, fundraising, culture, and every major decision. When that judgment is sharp, the company moves well. When it’s clouded by pressure, isolation, or inexperience, the company drifts, and nobody else in the building is positioned to catch it.

That makes the founder the single biggest point of failure in the business. And the earlier the stage, the more true that is.

Yes, we’re a coaching company, so take our bias into account. But the logic stands on its own. If you want to insure the most important asset in a company, you’ll start with the person making the big decisions. Supporting founders early, when habits are forming and mistakes are cheapest to correct, is one of the highest-leverage investments an investor can make. Instead, it’s usually one of the last.

What founders can do about it

You can’t change the venture industry on your own. You can decide which of its norms you accept.

Know what you’re building. Be honest about whether your company is a rocket or an airplane, and raise accordingly. Choose investors whose expectations match your actual business.

Build at a pace you can sustain. Hard work is required. Self-destruction is optional.

Invest in your own judgment early. Find people who have been where you’re going and can tell you the truth. Whether that’s a coach, a peer group, or seasoned advisors, don’t wait until something breaks.

The goal was never to look like a startup from the headlines. The goal is to build something real, and to still be standing when it works.

Subscribe now

The biggest threat to your bottom line isn’t the market or your strategy - it’s your relationships.

Why traditional leadership development doesn’t stick, and what secure leadership infrastructure actually looks like.

Editor’s note from Wisdom Partners: We work with founders on the systems, decisions, and culture that make their companies scalable. But the relationships in a founder’s life — with a partner, with a co-founder, with the leadership team — shape every one of those outcomes. Katarina Polonska works with high-performing professionals on exactly that layer, and she has a sharper lens on it than almost anyone we’ve read. We’re publishing three guest posts from her in the next few weeks. Here’s the first.

-

Leadership teams inside high-growth, fast-paced companies - especially the ones who look strong on paper - are often running on fumes and unraveling under extreme pressure as they scale.

Because, surprise surprise, your personal patterns around relationships and connection are so much more than just how you are in your private life.

It shows up in how you are with your executive team.

It shows up in how you are with your leadership.

It shows up in how you are with your business.

And if those patterns are insecure, reactive, or overloaded…

It will absolutely affect your ability to scale and succeed long term - sustainably, effectively, and efficiently. It affects your company’s bottom line. I’ll explain why in a moment.

Let’s imagine though, that the metrics look fine at your firm:

• Pipeline’s growing

• Churn’s steady

• Headcount’s scaling

Everything is ‘good’ on paper.

But in my experience, if you’re a high growth startup, the leadership team is very often going to be…more complicated. They’re going to be territorial. Tense. Trust is likely going to be low. Healthy delegation is highly likely to be nonexistent. And almost certainly, everyone will be over-functioning, overworked, overstressed.

It’s likely a culture of low trust and quiet resentment - where every decision is escalated, second-guessed, or politically fraught. No one feels safe enough to move fast. Everyone is terrified of failure. Or not being good enough for the job. And yet, everyone is ALSO being asked to move faster. And do more with less.

I know this so intimately because of my many years spent in behavioral science where I was a regional VP of a global behavioral science firm helping companies with their people strategies, but also in my own private work. So often I find myself consoling executives in tears in their office, on the phone to me, having panic attacks between board meetings. Or they’re pulling their hair out, frustrated with leadership team dysfunction, and how a direct report failed to do their job…again. Executives are so often fried from carrying emotional labor for fragile peers. And founders I work with are often wondering if they built the wrong team OR if they’re the bottleneck (often they are). No one is really sleeping all that well, and resentment is typically pretty high.

So yes, High growth company = often a total mess beneath the surface

And as someone who has studied human psychology for over a decade: No — your average “leadership development” program won’t fix it. Because you can’t train a team to delegate if no one trusts each other. You can’t teach feedback frameworks to leaders whose systems are in survival mode.

What you need is a secure leadership infrastructure — one that changes how your team operates under pressure. This is where emotional maturity, clear delegation, healthy conflict, and trust aren’t short term little fixes you learn in a “leadership model.” Instead, they become default settings, part of your operating patterns, part of your automatic behaviors.

So what does secure leadership actually look like? What do I mean when I talk about insecure patterns?

The way we learn to relate to closeness, trust, and pressure shapes how we lead, collaborate, and respond to stress at work too. For example, someone with a more anxious pattern may overwork to prove their value, constantly worry about what their boss thinks, or feel unsettled when they don’t receive immediate feedback. They might seem needy, volatile, very emotional, and micromanaging.

Meanwhile, someone with a more independence-first pattern may appear calm and independent - but avoid conflict, struggle with delegation, or resist vulnerability in team dynamics. Often in my experience, they may avoid telling the truth about their work and hide things.

The workplace becomes a mirror.

Many of us carry patterns around earning approval or safety, and we often replay those patterns in our careers - seeking approval, fearing rejection, or over-identifying with our performance. That’s why understanding your own relational patterns is a professional strategy.

1. The Grounded Pattern (what you want more of in your company)

Core Traits: Grounded, open, collaborative, and self-assured under pressure. Very cool, calm, and collected, authentic, able to be vulnerable, navigate hard conversations, and show up powerfully.

Workplace Patterns:

• Gives and receives feedback without spiraling.

• Can handle conflict with maturity—stays connected without becoming reactive.

• Delegates well and trusts others to deliver.

• Doesn’t take things personally and isn’t afraid to ask for help.

Example:

A team lead with this pattern might receive critical feedback from the CEO and use it to sharpen strategy - without seeing it as a personal attack. They’ll raise concerns early, resolve issues calmly, and advocate for their team without burning out or bulldozing others.

2. The Anxious Pattern (what I see a lot of)

Core Traits: Hyper-aware of others’ reactions, approval-seeking, and tends to personalize professional dynamics. Often quite emotional, reactive, ‘panic’ energy and loves to micromanage.

Workplace Patterns:

• Over-prepares or overworks to gain reassurance or avoid criticism.

• May catastrophize small signals (a boss’s silence = “I’m failing”).

• Struggles to set boundaries; says yes too often.

• Feels unsettled without external validation.

Example: Someone with this pattern might panic when a client delays replying to an email - assuming something’s wrong. They’ll work overtime to “fix it,” even if no one asked them to. Their performance is often stellar, but driven by internal pressure, not ease.

3. The Independence-First Pattern

Core Traits: Self-reliant, emotionally distant, resists vulnerability and over-values control. Prefers to be a lone wolf, do things alone, really doesn’t like conflict or emotions, gets overwhelmed easily, can be prone to hiding things.

Workplace Patterns:

• Keeps people at arm’s length—especially in leadership roles.

• Avoids uncomfortable conversations or downplays tension (”It’s fine”).

• May resist feedback or collaboration—prefers to do it alone.

• Struggles with visibility and receiving praise.

Example: A founder with this pattern may avoid difficult conversations with a co-founder or team member to “keep the peace,” but the result is simmering tension and lack of alignment. They may intellectualize problems to avoid dealing with uncomfortable emotions.

4. The Push-Pull Pattern (when trust is an issue!)

Core Traits: Craves connection but fears it, swings between closeness and withdrawal. Often has trust issues, hates to delegate, quite fiery and can be volatile emotionally.

Workplace Patterns:

• May alternate between being highly engaged and completely disengaged.

• Finds it hard to trust others and often second-guesses decisions.

• Can appear confident one day and chaotic the next.

• Sensitive to power dynamics—can feel easily threatened or betrayed.

Example: A high-performing consultant with this pattern might lead a killer pitch, then ghost the team for three days. They crave recognition and impact, but their inner instability causes inconsistency - and can confuse or alienate colleagues and clients.

Now crucially, these are all learned default patterns.

It’s not something your typical leadership development program or online learning tool is going to solve. That’s a superficial solution that doesn’t get to what’s actually driving the issue - which is how people have learned to operate in relationships.

Leaders must update these patterns to become more secure.

Google has spoken publicly about the role psychological safety plays in team performance - separate but related territory to the pattern work I do, and worth knowing about regardless. Secure, grounded leadership drives high performance.

And the best thing is, when you help people build more secure patterns, it’s SO much deeper than doing the band-aid leadership training that is so common. That stuff becomes obsolete so quickly and requires memory and discipline to apply. Whereas updating someone’s patterns at a deeper level is far more effective long term - because it sticks.

Can you imagine what your company would look like if everyone showed up from a place of security and groundedness?

• People speak directly - but kindly, and with warmth.

• Leaders own their mistakes without spiraling or hiding things.

• No one’s afraid to say, “I need help,” or “I disagree.”

• Meetings are efficient, fast, to the point - rather than drawn out and performative.

• Feedback is frequent, and effective, rather than feared and avoided.

• Conflict is addressed early and respectfully.

• Success is shared.

• Burnout is rare.

• Trust is strong.

• People feel valued, seen, safe, heard, and excited to be there.

• Work flows naturally and everyone’s in the zone.

In this culture, ambition and emotional maturity coexist. And the company grows because its people are growing with it. Deep pattern work that makes leadership actually scalable and growth actually sustainable.

-

Thanks for reading Wisdom Partners! Special thanks to Katarina Polonska for her insights. Find her at katarinapolonska.com

Subscribe now

Here’s a pattern that shows up in early-stage founder conversations more often than almost any other.

The founder has a big idea. Real vision. They can articulate it well. They also know it’s going to be hard to build directly. The technology is complex, the customer education required is heavy, the sales cycle is long, or the market isn’t quite ready. So they arrive at what feels like a clever workaround.

They decide to build a smaller, simpler business first. One that can generate cash quickly, prove some capabilities, build a customer base, and then eventually fund or evolve into the real thing they want to build. It’s a very expensive mistake.

Why building A to fund B looks like a good idea

The logic is seductive because it seems to solve two problems at once.

The first problem is capital. Your real idea needs runway you don’t have. If you can build a smaller business that generates revenue faster, you can bootstrap your way to the resources you need. No dilution. No investor pressure. Just cash you earned yourself.

The second problem is validation. If your smaller business succeeds, you’ve proven you can execute. You’ve built customer relationships. You’ve built a brand. All of that becomes an asset you can carry into the bigger idea when the time comes.

On paper, that’s a clean argument. In practice, it almost never works, and the reason it doesn’t work is that you’ve quietly turned one risky bet into two.

The math actually works against you

To get to your real idea, business A has to succeed and you have to successfully transition to business B. That’s not one probability. That’s a joint probability, and joint probabilities compound the wrong way.

If business A has a 40% chance of succeeding well enough to fund business B (which is generous for an early-stage business), and business B has a 40% chance of succeeding given adequate funding, your combined odds are 16%. You’ve cut your chance of ending up where you actually want to be by more than half.

That’s the mathematical case. The strategic case is worse.

Because business A isn’t the business you actually want to build, you’ll be a mediocre operator of it. Not incompetent. Mediocre. Your heart won’t be in the work. Your attention will keep drifting to business B. You’ll under-invest in the parts of A that don’t map to B, which will be most of the parts.

Meanwhile, business B is sitting in your head, unbuilt, aging. The market conditions that made it look attractive shift. Competitors show up. The window narrows. By the time business A has generated enough cash to fund B, B might not be as interesting as it was when you started.

And here’s the specific mode of failure to watch for. Business A tends to become a comfort trap. It’s generating cash. It’s paying salaries. It’s real. Walking away from it to bet on B feels reckless even when B was the whole point. Founders in this position often end up running A forever, with B as a permanent “someday” that never arrives.

The alternative: build a small version of the big idea

The move that actually works is deceptively similar to the A-to-B strategy, but it produces completely different outcomes. Instead of building a different business to fund your real business, build a small, complete version of your real business directly.

A slice of the pie is a partial implementation of your vision. One feature. One workflow. One customer segment. It only works if the whole pie eventually gets built, because a slice on its own doesn’t stand up.

A small pie is a complete instance of the vision, scaled down. All the essential elements of the big idea are present. It just serves fewer customers, in a narrower market, with a simpler feature set. It’s a real business that would still be a real business even if it never grew.

Concrete example. Say you want to build security software for enterprises. Big vision. Complex. Long sales cycle. Requires deep integration with customer systems. You’re not going to sell it in month one.

The A-to-B mistake is to build a penetration testing business first. Sell pentests. Generate cash. Use the cash and the customer relationships to eventually fund the security software you actually wanted to build. That’s building A to fund B. The pentest business and the security software business are related but structurally different. Different sales motion, different pricing model, different unit economics. Success in one doesn’t cleanly transfer to the other.

The small-pie alternative is to build a monitoring system that installs quickly, surfaces security alerts, and lets customers resolve them manually. That’s a real security product. It’s a scaled-down version of the eventual vision (which might include automated remediation, deeper integrations, and full workflow coverage), but every customer who buys the monitoring system is a customer who could buy the fuller product later. The muscle you’re building is the exact muscle you need. The customer relationships are the exact relationships you’ll want. Success at the small scale directly proves the bigger scale.

That’s the difference. Same amount of caution about starting too big. Completely different odds of getting to where you’re trying to go.

Where this pattern shows up most

The A-to-B trap is not just an AI-founder problem, and once you see the pattern you start noticing it everywhere.

The most common version is the services company that plans to become a software company. Founder starts an agency or a consultancy to generate cash, with the idea that they’ll build software on the side and eventually pivot the business into a product company. It almost never happens. Agencies are structurally different from software companies. The economics are different. The team you build is different. The customer conversations are different. Founders who try to run both end up running an agency that has some half-built software on the shelf, and they run it until they retire.

The small-pie alternative for that founder is to build the software directly, even if it’s tiny. One workflow. Ten customers. Real revenue at real software margins. Then grow.

Another version is the founder who launches a lifestyle business to fund their startup ambitions. Newsletter, coaching practice, digital course. All fine businesses. None of them turn into a venture-scale company. The founder ends up with a decent living and no startup.

If your goal is a decent living, that’s a great outcome. If your goal was the startup, you built the wrong thing.

The pattern to watch for is any strategy where the plan requires you to succeed at one type of business well enough to then start a different type of business. That’s a compounding bet. Almost never the right move.

The diagnostic

There’s a specific question worth asking anytime you’re tempted by the A-to-B path.

Is the business I’m about to build a smaller version of the business I actually want, or is it a different business that I hope will fund it?

If the answer is “it’s a smaller version and every customer is a plausible customer for the fuller version,” you’re on the right path. Build it.

If the answer is “it’s a different business, but it uses similar skills and I think I can pivot later,” you’re headed into the trap. The pivot is much harder than it looks from where you’re standing now. Success at the different business will make the pivot feel more, not less, dangerous.

Build the small version of the thing you actually want. Even if it’s tiny. Even if it doesn’t look impressive on a pitch deck. Even if it’s harder than it would be to build something adjacent that generates cash faster.

The founders who get to their real vision are the ones who started building it, in some form, from day one. The founders who never get there are the ones who built a bridge business that turned into a destination they never meant to reach.

Your idea is the point. Start it small, but start it. Don’t build something else and hope to work your way over.

Subscribe now

Here’s something shocking for you high-achievers:

Career success and overwork are strongly linked to higher divorce rates, often because the emotional connection at home gets neglected along the way.

And, even more awful, the divorce rate among entrepreneurs appears to run noticeably higher than the general population.

Yup, the higher you climb, the more you damage the emotional safe space and foundation that you assume would always be there.

Why does this happen?

Here are 3 reasons:

1. Emotional neglect by cognitive overload

High achievers often operate under chronic cognitive load (ask me how I know):

Their brains are constantly flooded with decision fatigue, problem solving, risk assessment, and strategic forecasting.

When you’re running companies, leading teams, and making high-stakes calls, then your executive functioning brain stays in overdrive.

It’s exhausting. And you’re always firefighting, never off, never really relaxed, right?

So when you’re in overdrive like this, what gets neglected is the attachment maintenance of your relationship - the small, consistent emotional deposits that healthy long-term relationships depend on.

Which makes total sense, you’re burned out and drained - but it’s a disaster for your relationship.

Think of your relationship like a garden, a living system.

Without tending it, without investing into it, it withers and dies under the weight of your “busyness”.

2. Shifting identity and the “parallel lives” phenomenon

As career success accelerates, your self-concept shifts - often quite dramatically.

You become someone different from who you were at the start of the relationship.

If this growth isn’t integrated relationally - if your partner isn’t brought into that evolution - you end up living parallel lives:

Sharing a house, kids, logistics, friends - but no longer sharing intimacy, your inner worlds, your hopes and dreams, your vulnerabilities. There’s a concept in relationship psychology for this - the idea that healthy relationships expand your sense of self. When that stops, emotional contraction begins - and resentment, distance, and loneliness take root.

3. Hyper-competence kills vulnerability

High-performing professionals like you are rewarded for control, composure, and results.

But intimacy runs on the opposite fuel: emotional openness, vulnerability, shared uncertainty.

If you’re wired to optimize, strategize, and control - it’s almost inevitable that your marriage becomes one more system to “manage” rather than a sacred space to be seen and known in. Over time, this creates emotional deprivation - where both partners feel unseen, unsupported, and deeply alone... even if everything looks successful on paper.

And guess what, that’s where infidelity happens, where disconnect grows, and things start to fall apart. And yes, this is all a disaster for your relationship and life more broadly.

Emotional burnout from feeling neglected at home will always bleed into your leadership. Your kids will always absorb the tension you think you’re hiding. And you’ll have personal regrets that haunt you long after the settlements are finalized.

Inaction and disconnection = no bueno.

So - how do you solve it before it’s too late?

You can’t fix this with surface-level advice - reading books on love languages (which have been widely critiqued by researchers, btw) is not enough. You also can’t just schedule a few date nights and think it will erase years of slow emotional growing apart.

You need a total relational operating system upgrade. Aka. You need to identify your blocks towards love and intimacy, clear them out at the source, and upgrade to a newer, better, more empowered and better version of yourself in love.

Because you deserve to demand the same level of excellence you have in your career in your personal relationship. If you’ve built a world-class career, it’s time to build a relationship that matches it - or exit with dignity and strategic clarity.

Because your marriage should be your sanctuary, not your liability.

Thanks for reading Wisdom Partners! Special thanks to Katarina Polonska for her insights. Find her at katarinapolonska.com

Subscribe now

Ask any early-stage founder how they priced their product, and you’ll usually get some version of the same answer.

They looked at what it cost them to deliver. They added a margin they thought was reasonable. Twenty percent. Fifty percent. Someone once told them software should have eighty percent gross margins, so they added eighty percent. They called it a price and moved on.

That’s the wrong instinct, and it’s a particularly expensive one in the AI moment because your cost structure is volatile enough that a cost-plus model can wipe out your margin without warning. But the deeper problem is that cost-plus pricing tells you almost nothing about what your product is actually worth to the person buying it.

The right question isn’t “what did this cost me to make.” It’s “what is this worth to the person receiving it.”

Why value-based pricing is a magic trick

The reason value-based pricing works, and the reason the best tech companies rely on it almost exclusively, is that it thrives on a gap that most other business models can’t exploit.

What something costs you to produce and what the customer receives from having it are usually two different numbers. Often wildly different.

If a customer pays you $50,000 a year for software that saves them a full-time employee, the value they’re capturing is not $50,000 minus your delivery cost. It’s the fully-loaded cost of that employee (probably $150,000+ once you factor benefits and overhead), plus whatever secondary benefits come from the work being done faster or more consistently. Your delivery cost might be $2,000 a year. The value they’re capturing might be $200,000 a year. Your margin between cost and value is not eighty percent. It’s ninety-nine percent.

That gap exists in almost every well-priced software product. It’s not exploitation. It’s how the value equation actually works when you’re delivering something the customer couldn’t produce themselves.

Which brings us to the harder question. When can you actually capture value that way?

Value-based pricing only works if you’re actually differentiated

Here’s the part most founders get wrong. They hear “value-based pricing” and think it just means “charge more.” So they raise their prices, watch conversion collapse, and conclude that value-based pricing doesn’t work in their market.

Value-based pricing depends on a specific condition. You have to be delivering something the customer could not get without you. Not something they could get slower without you. Not something they could get more expensively without you. Something they genuinely could not get at all.

The trap most tech founders fall into is thinking that being cheaper or faster than the alternative is a defensible position. It isn’t. Cheaper and faster are commodity dimensions. Someone else will be cheaper and faster next year. And even if they aren’t, being cheaper and faster doesn’t let you charge premium prices, because the customer can always fall back to the slower and more expensive option.

The number one thing you hear in AI companies right now is some version of “we can do X in 30 seconds instead of a week.” That’s cool. It’s also not really a business. It’s an efficiency improvement. Efficiency improvements get priced against the labor cost of the thing they replace, which puts a hard ceiling on your pricing power.

The real question, once you have the technology in hand, is what becomes possible that wasn’t before. Not what becomes cheaper or faster. What becomes possible.

Example from a Probate Startup

An AI company we’ve been watching built a system to handle all the paperwork required to submit an estate into probate court. On the surface, that sounds like a straightforward efficiency play. Do the forms faster, charge less than an attorney, take the market.

What actually happened is different, and it illustrates the value-based pricing point better than any framework could.

Because the software handles the paperwork automatically, the company is able to work with attorneys who take the cases at a discounted rate. The attorneys make more money because they can process more cases with less work. The customer gets probate resolved faster and for less money. That would be the expected value.

The unexpected value, and the thing that turned out to be worth the most, is what the AI enables that no attorney had ever offered. The system will actually listen to the customer. The customer can talk to it about what they’re going through as they work through probate. It listens. It gathers the information it needs from the conversation. It processes the grief alongside the paperwork.

That’s the thing no human attorney can offer because no human attorney has the time to sit and listen to a grieving client at that depth. It’s not a feature. It’s an unlock. It’s something the customer couldn’t have gotten anywhere else at any price.

And that’s what they’re actually willing to pay premium prices for.

The lesson isn’t that you should build AI grief counselors. The lesson is that the sharpest pricing power comes from finding the thing your technology makes possible that nobody has ever been able to offer before. That’s the thing worth building the business around. Everything else is a feature.

The one-of-one asset

The ideal end state of this thinking, and the thing tech companies specifically should be looking for, is what you could call a universally unique asset. One of one. Something nobody else can do because nobody else has the specific combination of technology, data, insight, or context that you have.

Most businesses will never reach that state, and that’s fine. But even short of it, the mental exercise is worth doing. What is the thing about our approach that literally could not be replicated? Not “would be hard to replicate.” The thing that could not be replicated at all because it requires an insight or an asset that only exists inside our company.

If you can find that thing, everything else in your pricing conversation gets easier. You’re no longer negotiating against a competitor who’s offering the same thing cheaper. You’re negotiating against the version of the world where the customer doesn’t have your solution at all, which is a completely different math.

One more thing, for AI-native companies specifically

Once you’ve solved the pricing side, the cost side becomes worth engineering hard. This is where AI-native companies leave a lot of money on the table.

Most of the AI products we’ve seen use significantly more tokens than they need to. Sometimes because the founder threw the largest available model at every problem. Sometimes because they never went back to optimize once the first version worked. Sometimes because they built with an AI where a deterministic solution would have worked just as well.

You can typically cut your token costs by 80 to 90 percent after your first working version, without any degradation in quality. Model selection alone often accounts for half of that. Better prompt engineering and harnessing gets you most of the rest. And genuinely asking “does this need to be AI at all” often reveals that half of your pipeline should just be code.

None of that matters if your pricing is broken. If you’re charging cost-plus on inflated costs, you have a bad business either way. But if you’ve done the value-based pricing work and you have real margin available, then the cost engineering compounds. Your margin goes from ninety percent to ninety-eight percent. That difference funds everything else you want to do.

The pricing model is the strategy. It tells you what kind of company you’re building.

Cheaper and faster are fine, as features. They are not a great business. The companies really worth building are the ones that unlock something that wasn’t possible before. Those are the ones that can charge what the value is actually worth because the customer has no other way to get it.

Everything else is an efficiency improvement, priced against labor costs, and headed for a race to the bottom.

Subscribe now

Most first-time founders operate on a version of the same advice: build something people want. It’s true. But it’s also almost impossible to act on because the assumption underneath it is that people can actually tell you what they want.

Nobody knows what they really want.

Not your customers. Not your prospects. Not even you. If you sit anyone down and ask them what they need, they’ll give you a version of what they can already imagine. What they can imagine is bounded by what they’ve seen before. What they’ve seen before is not the thing you’re trying to build. So the answer they give you tells you almost nothing about what would actually be valuable to them.

The gap between “people don’t know what they want” and “build something people want” is exactly where founders add value and make money. Closing that gap is the actual job. Almost everything else is downstream of doing this well.

People can’t tell you what they want. They can react to what you show them.

Humans are extraordinary at reacting. We do it all day, every day. Show a person something and they’ll immediately tell you whether it lands, what’s off about it, what’s missing. That instinct is fast, honest, and mostly unconscious.

That reaction is your actual data source. So the move, from day one, is to get things in front of the right people as fast as possible. Not because those first things will be right. Because their reactions will tell you what right looks like. You aren’t trying to ship a product yet. You’re trying to build a mental model of how your customer thinks by watching them react to real things.

For most of the last decade, this was expensive. You had to sketch prototypes on paper, mock things up in PowerPoint, cobble together no-code versions. Anything to have a thing to show that wasn’t just a description. The wall between “an idea in your head” and “a thing you can put in front of a customer” was tall enough that most founders skipped it and just started building the product.

That wall is gone. With AI, you can now generate high-fidelity prototypes in an afternoon. What used to take a week takes a night. Which means the main reason for sitting in a corner for months and building without customer contact, is habit. And that habit is expensive.

We should also note that there is another subtle reason many founders quietly build in a corner for months or years: Fear. Secretly, often unconsciously, they are afraid to bring their idea to customers. They are afraid to be wrong, afraid to feel rejected, afraid to have their dream burst. So, they procrastinate. They build more. They tweak. They refine. All with the excuse that it has to be just right before they show it to others.

Build something. Show it to someone. Watch their face. Learn. Iterate. Repeat. Do it a hundred times before you build the product you actually intend to sell. The founders who compress this loop are the ones who find product-market fit. The ones who don’t are still explaining why their idea is going to work six months from now.

Talk to buyers, not users

There’s a specific mistake almost every founder makes when they finally start doing this discovery work. They talk to the wrong people.

The instinct is to talk to the people who will actually use your software. Makes sense on the surface. They’re the ones with the day-to-day pain, so who better to describe it?

The problem is that the person who uses your software is almost never the person who decides to buy it. In enterprise and mid-sized organizations, the user is a frontline person, but the buyer is their boss, or their boss’s boss, or someone in a completely different function who owns the budget. In startups and small businesses, the founder might be both the user and the buyer, but the hats are different. What you’re paying for feels different from what you’re using.

If you only talk to users, you learn what would make their day slightly better. That’s real information. It’s not the information that closes deals. What closes deals is the felt pain of the buyer. What’s keeping them up at night. What they’re on the hook for. What their boss is going to ask them about at the next quarterly review. That’s the thing you have to solve for.

This is the reason enterprise software has always been so ugly. The user is not the buyer, and the buyer is the one who pays the bill. The buyer needs the strategic outcome. The user’s experience is a distant second consideration. Whether you like that reality or not, if you’re selling into a company with more than one decision-maker, you have to design your product for the person signing the check.

Go up the org chart. Talk to the CEO if you can. Talk to the person who owns the entire function you’re trying to serve. The buyer’s felt pain is what you’re building for. The user’s experience is a constraint you optimize against, not the target.

How deep is deep enough

Once you’re talking to the right people, the next question is how you know when you’ve actually understood their pain. This is where most discovery work stops too early.

The failure mode looks like this. You’re in a discovery call. You describe the problem your product solves. The buyer says “yeah, that would save us a lot of time” or “that would help us hit our numbers” or “that’s exactly what we’ve been looking for.” You think you’ve found the answer. You go back to the office and start building.

You haven’t found anything. You’ve found the polite, rational, top-of-mind response. That’s not the level where buying decisions actually get made.

The right move is to keep digging. What difference would that make? What does that problem have to do with the goal you just told me you have this quarter? What have you tried already? What happened? What are you actually worried about here?

The signal you’re looking for is emotional, not rational. You keep going until the person on the other side visibly shifts. They relax. They exhale. They say some version of “yes, that’s it!” That exclamation point, that deep sigh of anticipatory relief, that is the tell. That’s the moment they feel understood at a level they weren’t expecting.

A useful mental frame for what you’re digging toward — try to find the dreams they dare not to dream. Every buyer has a set of outcomes they consider realistic and a set they consider impossible. The realistic ones are what they’ll ask you for. The seemingly impossible ones are where the real value lives.

An import-export company hires a customs broker to fill out forms faster. That’s the realistic outcome. That’s what the RFP will describe. It’s also not why they actually pay premium rates to a broker they trust. What they’re actually paying for, if they’ve been through a difficult year in a difficult global environment, is a person who knows the guy who can call the guy and get the shipment out of the jam it’s stuck in. That’s the thing that keeps the importer up at night. That’s what they’d never write into a spec because they’ve assumed no software could ever do it.

Find that or the equivalent in your space. That’s the thing worth building around.

You don’t get to that layer by asking: “What do you need?” You get to it by putting things in front of people, watching their reactions, and asking one more question, and then one more, and then one more.

How this changes what you build

Once you’ve got a real mental model of your buyer and a real read on the dreams they’d not dared to dream, the “how much to build” question mostly answers itself.

You build the smallest possible version of the big idea. Not a slice of the pie. A small pie. This distinction matters. A slice of the pie is a feature that doesn’t stand on its own. A small pie is a complete version of the vision, sized down to something you can ship this month. When you show it to a design partner, they either say “when can I have this” or they don’t. If they don’t, you haven’t found it yet. Keep iterating.

The founders who do this well end up with a specific rhythm. They meet with a customer. They come home with an idea. They spin up a prototype overnight with AI. They show it the next day. They get a reaction. They iterate again. Compressed feedback loops, over and over, until the thing they’re building actually lands.

The founders who don’t do it well spend months in a corner building the wrong thing for the wrong person, and then wonder why nobody buys.

The gap between the two isn’t intelligence, and it isn’t work ethic. It’s whether you internalized the fact that nobody knows what they want, and then built your entire process around that reality instead of pretending otherwise.

Nobody knows what they want. You don’t either. But you can get in front of them, show them things, watch what happens, and build a version of the answer they’ll recognize when they see it.

That’s the job at the beginning. Everything else is downstream.

Subscribe now

Answering their own inbox. Sending invoices. Chasing collections. Rearranging their own calendar. Approving expenses that don’t matter. Editing the copy on the landing page nobody’s redesigned in a year. All of it feels productive because it’s being done. All of it is quietly a signal that the founder hasn’t yet made the shift from operator to CEO.

The reframe that helps most founders break the pattern is a simple visualization. Think about the version of you that runs a $10M company. Not hypothetically. Actually. That person exists in your future if you make the right calls now.

Now ask: would that person be doing what you’re doing right this second?

At that scale, no high functioning CEO is spending their morning triaging their inbox or arguing with a vendor over a $200 invoice. The $10M CEO’s day looks structurally different from the $500K founder’s day. Different meetings. Different questions. Different problems on the table.

The insight is that the shift doesn’t happen automatically when you hit the revenue number. It happens because the founder decided, somewhere along the way, to stop doing the work that the future version of them wouldn’t touch.

The founders who cross that threshold are usually the ones who started acting like the $10M CEO before the revenue caught up. The ones who don’t cross it are usually the ones who kept doing $20-an-hour work while their business needed them to be doing $500-an-hour work.

Two ways to apply the filter

This visualization works well when you can hold it in your head. Some people can. They can genuinely imagine the future version of themselves running a real company, and use that image as a decision filter throughout the day. If that works for you, use it.

The people who find future-self visualization too abstract have a mechanical version of the same question available. Ask what the task in front of you is actually worth per hour.

Rearranging your calendar? That’s a $20-an-hour task. Sending invoices? That’s a $50-an-hour task. Reviewing a legal contract you don’t understand? That’s a $200-an-hour task if you’re doing it, or a $400-an-hour task if you hire a lawyer to do it right. Talking to a top-three customer about their renewal? That’s a $2,000-an-hour task, because the outcome swings by much more than that.

Your calendar right now is a portfolio of those hourly values. Look at it honestly. If more than a quarter of your week is being spent on tasks worth less than $50 an hour, you’re not acting like a founder, you’re acting like an assistant in your own company.

The $10M CEO doesn’t have a quarter of their calendar in that bucket. They have almost none of it. Not because they’re above the work, but because they’ve made the arithmetic decision that their time is better spent elsewhere and hired accordingly. And, even better, because they know that focusing on the highest value work is how they can best serve their business and their people.

What this looks like in practice

Start with the easiest category. The stuff that shouldn’t be touching your calendar at any stage. Inbox triage. Scheduling. Travel booking. Basic bookkeeping. Expense approvals under some threshold you set once and never revisit. All of this can be handled by a virtual assistant for a small fraction of what an hour of your time is actually worth.

If you don’t have a VA yet, that’s the first move. If you have one and you’re still doing this work, the problem is you, not the VA. You haven’t handed it off. Hand it off.

Then, look at the harder category. The work you’re doing because you’re the best person in the company to do it right now, but that a $10M CEO wouldn’t touch. Sales outreach. Content writing. Onboarding calls. Recruiting screens. These are the ones that feel harder to delegate because you’re actually good at them, and the person you’d hand them to probably won’t be as good, at least at first.

The trap here is thinking the standard for handoff is: “Someone else can do it as well as I can.” That standard means you almost never hand anything off, because in year two of the company, you’re the best person at almost everything. The correct standard is: “Someone else can do it well enough that my time is better spent on the next thing.” If you like numbers, the standard is: “Someone else can do this 50-80% as well as me.”

The $10M CEO figured this out. They handed off work to people who weren’t as good as them at first, invested in getting those people up to speed, and used the freed-up hours to do the work that only they could do. That’s how the company got to $10M. Not by the founder being the best at everything, but by the founder being deliberate about which tasks needed their specific attention and which didn’t.

One honest thing

This isn’t easy, and it doesn’t feel good at first. The tasks you’re doing now, even the small ones, give you a sense of control. Handing them off means trusting someone else to do something you might do better. It means accepting that some things will be done at below your standard for a while, and being okay with that because it frees you to do the work only you can do.

The founders who scale past this point talk about the same emotional experience. It felt like letting go of something that was working. It required a specific kind of discipline, sitting with the discomfort of watching someone else do the thing worse than you would, without stepping in.

But that discipline is the shift. The version of you that runs a $10M company has practiced it a thousand times. The version of you that stays stuck at $500K is still stepping in.

Before you sit down to do anything that takes more than ten minutes, ask yourself: Would the future me who runs a $10M company be doing this right now?

Do that consistently for six months and the answer starts changing on its own. Your calendar shifts. Your work starts to look different. The version of you that runs the $10M company gets a little less hypothetical every week.

Subscribe now

That reflex works when you’ve got five people. It stops working somewhere between ten and twenty.

The to-do list becomes infinite. Important work lives permanently on the back burner. The founder feels a low-grade stress they can never quite resolve, because their list is genuinely growing faster than they can shrink it. And the company slows down, not because there’s less to do, but because too much of what needs to be done is stuck waiting on one person.

The fix is a small reflex change, but the consequences compound quickly. When something lands in front of you, before you decide to do it, ask two questions.

1. Who should own this?

2. What do they need from me to be aligned on how to do it?

That’s it. Those two questions, asked consistently, are the difference between a founder who scales past their own capacity and one who doesn’t.

Why the questions work in that order

The first question is about ownership. The second is about alignment. And the order matters, because most founders who try to delegate skip straight to giving instructions without ever transferring real ownership.

We wrote about this in our org chart blog (See: The Org Chart Won’t Save You). Declared ownership doesn’t stick. If you assign a task to someone with: “Hey, you own this now,” they experience it as another item on their plate. If you instead identify the right owner, get them to opt in, and then invest a few minutes in aligning them on how to think about it, they own it in the way you actually need them to.

The alignment part is where most founders undershoot. You know how you’d approach the work. Your instinct is to either do it yourself (fast, but doesn’t scale) or hand it off with minimal context (feels efficient, produces bad results). The middle path, and the only one that works, is spending real time on the “what do they need to be aligned” question.

That doesn’t mean telling them how to do it. It means giving them the why, the context, the constraints, and the goal, and letting them figure out the tactics. (See: The Slope of Autonomy). The why is yours to drive. The what is a shared conversation. The how belongs to them.

What this feels like in practice

The first few weeks of operating this way feel slower. You’re spending five or 15 or 50 minutes on alignment where you used to spend thirty seconds on delegation, or where you used to just do the thing yourself in an hour.

That math looks worse in the short run. It’s dramatically better in the long run, because you’re doing the alignment work once and reaping the productivity from it repeatedly. The owner starts making decisions you would have made, in the way you would have made them, without needing to come back to you.

Delegation is handing off a task and letting someone run with it. Replacement is a slower, more deliberate transfer that includes real alignment work. The tasks in your delegation zone (the ones that drain you and don’t produce revenue) can often be handed off with a few minutes of context. The tasks in your replacement zone (the ones that make money precisely because you do them) require the deeper investment.

The compounding effect

Founders who make this shift describe the same experience about six months in. Their to-do list shrinks even as the company gets larger. They feel less stressed even as they’re responsible for more. They notice that decisions are being made without them that would have required their input a year earlier.

That’s what actually scaling looks like from the inside. Not doing more. Owning less directly. Aligning more people to think and act the way you would in your absence.

The founders who don’t make this shift keep hitting a ceiling at the same place. Not because they aren’t working hard. Because they’ve made themselves the bottleneck to their own company’s growth.

The reframe is small. When something lands in front of you, don’t ask “when will I do this.” Ask who should own it, and what they need from you to do it well.

Do that consistently, and the to-do list stops growing. Your company starts moving faster. And the stress that comes from carrying everything yourself finally starts to lift.

Subscribe now

That story is true. It’s also incomplete.

The part that gets less attention is what happens on the other side of that collapse. When the cost of producing something falls to near zero, the ability to produce that thing stops being rare. Something else becomes rare instead. And in a world where anyone can write anything, generate anything, personalize anything, the thing that becomes scarce is trustability (being worthy of someone’s trust).

Over the last few months, thanks to Founder Real Talk, we’ve talked to founders across completely different industries who’ve independently landed on the same conclusion. AI matchmaking. AI-powered websites. Sales enablement. Agency work. AI safety infrastructure. None of them talk to each other. They’re solving different problems for different customers. And they’ve all arrived at the same thesis.

Trust is the new moat.

Why this is happening now

There’s a version of the “AI is coming for everything” argument that treats every industry as headed toward the same commodified endpoint. Content is commodified. Code is commodified. Design is commodified. Sales outreach is commodified. Everything gets cheaper, faster, and less differentiated, forever.

That framing is missing something important. When a category commodifies, buyers don’t stop caring. They start caring about something else.

You’ve probably heard people in Silicon Valley say, “Taste Is the New Moat.” Their argument: as generative AI collapses the cost of production, the real value comes in curation. Editorial judgment. Point of view. Knowing what’s worth making rather than what can be made.

We think trust is the second half of that same shift. Taste is what someone brings to the work. Trust is what other people extend to them. Both are human. Both are hard to fake. Both become disproportionately valuable in a world where output is free.

Here’s the mechanical version. AI has done two things at once. It has made it much easier to produce content that looks credible. And it has made it much harder to tell whether the credible-looking thing is actually credible. That gap, between what looks trustworthy and what is trustworthy, is where value is now concentrating.

Ben Gusberg at CAPE puts it in the sharpest form. Cold email conversion is collapsing because everyone has the same AI tools. In his words, “everyone is sending 10,000 emails a day that are perfectly personalized to you, and the conversion for those messages is going way down.” His numbers on the alternative are striking. Warm intros convert 34 times higher than cold email.

His framing: “In a world with all noise, how do you find signal? Ironically, we think that signal comes from humans.”

That’s the shape of the argument in one line. As synthetic communication floods the channel, the signal buyers actually respond to is human.

Check out Ben’s full episode on our YouTube channel here

What this means

The founders we talk to who are winning right now are betting on a specific set of things that AI can’t easily replicate.

Real relationships. The kind you build over years, with people who’ve watched you handle the hard version of something and stuck around. This is why in-person is resurgent. In-person can’t be automated or faked. Presence is a costly signal in a way that a cold email will never be, no matter how well-personalized.

Genuine thoughtful voice. Not a brand voice generated by a prompt. A perspective that comes from an actual human who’s spent enough time in a specific problem to have earned an opinion about it. The blog post that took someone twenty years of hard experience to write reads different than the one that took a language model twenty seconds, even when the surface content is comparable.

Reputation over time. In a world where anyone can spin up a plausible-looking company overnight, the founders who’ve been building the same thing for five years, showing up in public, taking responsibility for outcomes, have an advantage that new entrants can’t buy. Longevity is a form of trust that money can’t manufacture.

Safety and audit-ability. The regulatory version of trust. As AI gets deployed in high-stakes domains, the ability to prove your system won’t fail in the ways that matter becomes a hard requirement. The EU is already pushing regulation into force that requires companies deploying AI to demonstrate compliance. Trust is being written into law, not just competitive strategy.

All of these have one property in common. They can’t be produced at zero marginal cost.

What this looks like practically

If you’re a founder trying to decide what to build, or what to invest your reputation in, the takeaway is fairly specific.

Prioritize the parts of your business that can’t be commoditized. The customer relationships. The domain expertise. The judgment that tells you what to bother building and whether what you’ve built actually serves the customers you want. These are the parts that will still be worth something in five years, whatever else changes.

Be skeptical of building anything that depends on a temporary advantage in AI-generated volume. Cold outreach at scale, content flooding, spray-and-pray outbound. These tactics are already declining and will decline further. If your business model requires them to work, your business model is on borrowed time.

Invest in in-person more than the current defaults would suggest. Events, dinners, actual meetings. The economics have quietly shifted. In a world where the cost of digital contact is near zero, the value of physical presence is going up, not down. A dinner with ten of the right people is now doing what a thousand LinkedIn connections used to do.

Build your public presence on the assumption that trust will be the scarce resource for the rest of your career. Not audience. Not reach. Trust. Which means being right when you make a public call, admitting when you’re wrong, and being consistent about what you stand for. That’s a five-year game, and the people who started playing it three years ago are already ahead.

The reframe

The narrative about AI has spent two years focused on what it can do. The interesting question, and the one the founders we talk to are quietly answering, is what AI can’t do.

It can produce output. It can’t produce trust.

It can generate credible-looking content. It can’t give that content the weight of a human being who poured their heart into it.

It can automate the cheap parts of a relationship. It can’t automate the parts that make a relationship worth having.

The founders betting on the human side of that split are the ones we’d bet on. Not because AI is going away. Because the more powerful AI gets, the more valuable the thing it can’t do becomes.

Trust is the new moat. It always has been, actually. The change is that everything else just got a lot easier to imitate.

Subscribe now

They think they’re selling their technology. They spend fifteen slides on how the sausage gets made. They dive into the architecture, the algorithms, the technical breakthroughs. They’re proud of what they’ve built. They assume the investor will be equally impressed.

Or they think they’re selling their product. They walk through the feature set, the customer testimonials, the product roadmap. Everything is about how amazing the thing they’ve made is. They love their product. It’s their baby. Surely, the investor will love it too.

Or they think they’re selling an idea. This thing will change the world. This category is about to explode. This vision is huge and inspiring and could be the next Google.

Or they think they’re selling themselves. They lead with the resume. Where they went to school. Where they worked. The impressive brand names in their background. Sometimes investors even encourage this framing. “We invest in founders, not ideas.” So the pitch becomes a beauty pageant.

All of that is wrong, and often it results in pitches that don’t close

What you’re actually selling

You are selling part of a business.

Literally. That’s it.

When you close a round, the transaction is that an investor gives you cash and you give them shares. They now own shares of your company. Five percent, ten percent, twenty percent, whatever the number is. They will own that many shares until the business gets acquired, until they get bought off the cap table, or the whole thing collapses.

That is the transaction. Everything else in your pitch is in service of that transaction, or it shouldn’t be in the pitch. Once you internalize this, everything about pitch strategy shifts.

• If you’re selling technology, you’re basically applying for a grant. That’s a different transaction with different buyers.

• If you’re selling a product, you’re pitching to customers. That’s also a different transaction with different buyers.

• If you’re selling an idea, you’re a novelist. Ideas without execution don’t have investable value.

• If you’re selling yourself, you’re running for office. Investors may be flattered to be pitched this way, but they will probably not write the check.

Investors are buying part of a business. Your pitch deck exists to answer the question “is this business worth owning a piece of.”

What the pitch actually has to prove

Once you’re clear on what you’re selling, the pitch structure follows.

You need to prove that this is a real business. Not a cool project. Not an interesting technology. Not a founder with a good story. A business. Something that generates revenue, scales that revenue, and eventually becomes valuable enough that someone will want to buy it or take it public.

That means the pitch has to answer specific questions.

• How does this business make money? Not eventually. Now, or with a credible path to now.

• How will the revenue grow? What’s the go-to-market motion? What’s the acquisition cost, the retention curve, the expansion story?

• What does traction actually look like today, and what will it look like six months from now? Traction is not just what you’ve done. It’s what your existing progress predicts about what you’ll do next.

• Why can you specifically build this into a big business? This is where your background and skills become relevant. Not as a beauty pageant, but as evidence that you can execute on the specific plan you’re proposing.

• How does the investor get their money back? Eventually, the shares they’re buying need to convert into cash. That happens through acquisition, IPO, or secondary sale. Your pitch needs to make the exit path plausible without pretending to know exactly what it will be.

The product, the technology, the team, the idea. All of that is still in the deck. It’s just in service of a different central question. Instead of “look how amazing this is,” everything becomes “here’s why this can be a business that returns capital.”

We wrote a whole post on the 10 common pitch deck mistakes that come from misunderstanding this. It’s the tactical companion to this one.

The founder identity trap

There’s a second reason this reframe matters, and it has nothing to do with fundraising success. It has to do with what happens if the business fails.

When founders confuse themselves with the company, they set themselves up for a very specific kind of collapse. If the business fails, they conclude that they failed. With every threat to the business, they feel threatened in their core human value. The identity and the entity have merged. There’s no way to separate the two.

You’re not selling your self when you take investment. You’re selling shares in a specific business you’re building right now. The investors do not own you. They do not own your future ideas. They do not own your next company. They own a portion of this company, for as long as it exists in its current legal form.

If this business succeeds, great. If it doesn’t, you’re still you. You still have your capabilities, your relationships, your experience, your future. The investors don’t have any claim on those things.

Founders who understand this early tend to weather the hard parts of the journey better than founders who don’t. When things get bad, they can look at the situation honestly, because they aren’t personally dying with every piece of bad news. Founders who’ve merged their identity with the company can’t do this as well. Every setback feels existential because they’ve made it existential.

Separate the two. You’re a founder building a business. The business is a legal entity that produces goods or services and generates cash. You are a person. They are not the same thing. Investors are actually buying into the entity, not the person.

The reframe

The next time you sit down to work on your pitch deck, ask yourself one question at every slide.

Does this slide help someone decide whether they should own five percent of my business?

If yes, keep it.

If it’s just there because you love the technology, or you’re proud of the product, or you want the investor to like you personally, cut it.

Your pitch is not a demo. It’s not a resume. It’s not a manifesto. It’s a business case for why owning part of your company will produce a return.

Build the pitch around that transaction, and the rest of it gets easier.

Subscribe now

The meetings that produce the biggest leverage are also the hardest to sustain. Here’s why, and what to do about it.

HPMs are simple to set up. They’re genuinely challenging to maintain. Almost every founder who tries them lets them slip within a quarter or two, drifts back into the old rhythm, and then feels bad about it.

The slippage isn’t a discipline failure. It’s a design feature. HPMs are hard on purpose. The difficulty is actually where the value is.

The core reframe: HPMs are the end of a process, not the beginning

The single most important thing to understand about a high-performance meeting is that the meeting itself isn’t the real work.

The real work happens before the meeting. Owners prepare written material. Everyone reads it in the first fifteen minutes. The remaining forty-five are spent on the things that actually need discussion. If the meeting feels efficient because there’s nothing interesting to say, you’re doing it wrong. If it feels efficient because everyone came prepared and the meeting is where you collect the value of that preparation, you’re doing it right.

That distinction is why HPMs are hard. The default mode for how meetings work in most companies is the opposite. You show up. You riff. You improvise for an hour. You leave without much to show for it, but you also didn’t have to prepare, and neither did anyone else.

An HPM demands preparation from everyone. That’s expensive. It feels especially expensive at the beginning, before people have felt the payoff. If you’re a founder who runs on charisma and in-the-moment thinking (which many founders are), you’ll find HPMs deeply uncomfortable at first. They take away the improvisation you’re good at and force a discipline that doesn’t come naturally.

Key 1: The agenda is the actual product

The single biggest predictor of whether an HPM culture takes root or not is whether the founder sat down and did the hard work of designing a high quality agenda.

Not once. Every quarter. With each person who owns a section of the meeting.

That work looks like this. You sit down with the person who owns a function or a project. You talk through what success looks like for them. You agree on what they should report on, how they should measure it, and what kind of updates matter. You make it specific. You make it real. You leave with an understanding that will hold for at least a few months.

That is a lot of upfront time. But if you don’t invest this prep time, you end up with meetings where people just report vanity metrics and phone it in. Founders who do invest it end up with meetings that unlock genuine leverage.

Key 2: It’s on your team to prepare, and they’ll resist at first

The unlock for CEOs, once they get this, is enormous. In a functioning HPM culture, it’s your reports’ job to make sure the meeting is good, not yours.

You show up. You read the prep. You engage. You leave. The responsibility for the meeting being useful sits with the person reporting, not with you.

That is the great CEO relief. If you’re the founder currently drowning in requests of “Can you just look at this real quick?”, it can feel like getting swarmed by piranhas. Each request is tiny, but the compounding effect eats you alive.

Imagine those requests batching into a weekly forum where the person has prepared, thought it through, and is coming to you with a real ask. Every small interruption is redirected into a scheduled, contained conversation. The piranha bites stop.

But there’s a catch. Your team will resist this at first. Almost every implementation we’ve watched includes at least a few people who think the prep work is busywork. They’ll grumble. They’ll do the minimum. They’ll try to phone it in.

What you’re looking for, within a meeting or two, is the shift. You’ll hear someone say “I can’t believe how much we got done today.” That’s gold you’ve been working toward. Once they realize that putting real information into the prep gets them real help in the meeting, they lean in. Before that moment, you’re pushing a rock uphill. After it, they push it themselves. You just have to survive the first weeks.

Key 3: You have to resist taking over

The temptation, when your team’s first HPM prep isn’t very good, is to take over.

Don’t.

The failure mode is easy to fall into. Someone reports on their section. It’s shallow. It doesn’t cover the actual issue you know they’re facing. So you jump in, redirect the conversation, start driving it yourself. Now you’re the one running the meeting, they’re the one being interrogated, and the ownership dynamic you were trying to build has quietly collapsed.

The better move is to ask a pointed question. You know what’s actually going on. Use that knowledge to ask something specific that surfaces the real issue rather than lecturing them into it.

But here’s the part most leaders get wrong. The pointed question is only half the skill. The response to the answer is the other half, and arguably the more important half. When someone finally gets vulnerable and admits the thing they were dodging, what you do next determines whether they ever do that again. If you punish them, or turn it into a lecture, or use it as an occasion to demonstrate how much more you know than they do, you’ve just taught them to hide the next hard thing. On the other hand, if you say, “It’s great that we’re talking about this. How can I help?” then you’ve just built the muscle of honest reporting.

Key 4: Figuring out what to report on is genuinely hard in a startup

One of the recurring struggles for early-stage founders trying to run HPMs is knowing what to have people report on. The default answer, borrowed from bigger companies, is KPIs. Report on your metrics. Show the numbers.

The problem is that in a startup, the numbers are often too volatile or too small to be meaningful week over week. Ten customers becomes eleven becomes nine becomes twelve. Reporting on that in isolation tells you nothing.

The frame that tends to work better is unlocks. What are you trying to unlock next? Product-market fit. The next fundraise. The first repeatable sale. The tenth customer that lets you build a system around a real cohort. Every function in a startup is oriented around unlocking the next thing. If you organize reporting around what each owner is working to unlock, you get much more useful conversations than if you organize around fixed metrics that don’t yet mean much.

The unlock frame also protects against the demoralization problem. If you set a quarterly target of “10x sales” and miss it four quarters in a row, your team stops trusting the goal-setting process. If you say “The unlock this quarter is repeatable systems, which requires at least ten customers,” then you’re pointing at a real threshold. Hit it, and something opens. Miss it, and you know what you didn’t get to.

Key 5: You have to blow it up periodically

The last reason HPMs are hard is that, even when they’re working, they eventually stop working.

Humans are naturally good at optimizing. Once people get used to the format, they optimize for it. They report on the same things in the same order. The prep becomes easier because it’s routine. And routine, in the context of an HPM, is death.

The whole point of the meeting is the developmental stretch. If it’s easy, it’s not doing its job. The zone of developmental challenge, the middle band where things are hard but achievable, is where humans actually grow. Too much challenge and people give up. Too little and there’s nothing to push against.

The move, roughly two or three times a year, is to blow up the agenda. Destroy the format you’ve built. Design a new one that stresses the thing your team most needs to stretch on right now. Then, run that for a few months until it, too, becomes comfortable, and blow it up again.

It’s exactly like an exercise program. Do the exact same workout for three months, and it stops helping you. Same principle applies here.

One last thing: HPMs surface politics fast

There’s one more reason HPMs are hard to maintain, and it’s worth flagging separately. HPMs surface political dynamics very quickly. In a healthy team, that’s a feature. In an unhealthy one, it’s a threat.

The whole point of the meeting is that people show up and say the thing that needs to be said. If your organization has developed norms around not talking about the difficult things (the underperforming leader, the misaligned strategy, the customer who’s about to churn), the HPM becomes uncomfortable, and people find ways to route around it. They talk offline. They soften what they report. They hide behind vanity metrics.

That drift is your signal that something has gone off in the culture. The HPM didn’t cause it. The HPM revealed it, which is exactly what a good meeting should do.

If yours is drifting, the question isn’t how to fix the meeting. It’s what conversation your team no longer feels safe having, and what you’re going to do about that.

HPMs are hard because they demand the things most meetings let you avoid. Preparation. Ownership. Honesty. Discomfort.

The founders who stick with them do it because they’ve felt the payoff. The team is more aligned. The CEO is less drained. The important issues surface faster. The politics stay in check. All of those benefits are downstream of the hard work of building a good meeting.

The meetings aren’t the work. The meetings are where the work pays off. Keep the work going upstream, and the meetings take care of themselves.

Subscribe now

That number feels strange to write. We started the podcast in February, not entirely sure what it was going to be, not entirely sure we could sustain it. Two or three episodes a week. Four dozen founders. Roughly ten months of conversations we didn’t have when we set out to have them.

There’s a version of this post that would summarize the fiftieth episode. We’re not going to do that. The episode is already up, and it’s worth listening to (check our 50th episode special here). What we want to do instead is sit with what it’s been like on our side of it, and share some of what we’ve learned that only really surfaces when you look at the whole thing at once.

Starting something new is always a little disorienting

We work with a lot of founders. We coach them, advise them, help them build the companies they’re trying to build. That’s the day job.

Starting a podcast wasn’t the day job. It was closer to what we spend our time helping other people do. You have an idea. You aren’t sure who it’s for. You aren’t sure what the format should be. You don’t know if anyone will listen. You publish the first one anyway. Then you publish the second. Then you’re twenty deep and starting to see the shape of the thing you’re actually making.

That process turned out to be a useful exercise in a way we didn’t fully anticipate. We spend a lot of time talking about the founder journey. We got to live a very small, low-stakes version of it, again. The uncertainty at the beginning. The private “is anyone actually paying attention” phase. The moment where you stop asking whether it’s working and start asking how to make it better. It’s a very different feeling from the outside.

We came out of it with renewed empathy for what we’ve been asking our clients to feel their way through for years. Advice is easier than execution, which we already knew, but it’s one thing to know and another to be reminded.

The founders we met

The best part of the last eight months of podcasting has been the founders themselves.

Some of them are our clients. Some are people in our network. But a real portion of them are founders we would never have crossed paths with any other way. Different industries. Different geographies. Different stages. Some are ex-corporate operators who left a comfortable job to build something. Some are second-time founders who lost the first company and came back for another try. Some are running businesses that don’t look anything like the venture-backed, unicorn-chasing stereotype the tech press tends to focus on.

That range has been the gift. Founder Real Talk pulled us into a bigger picture of the founder journey. And what became obvious pretty quickly is that the core experience of being a founder rhymes across almost every industry, stage, and geography we’ve seen.

Which brings us to the three themes.

What kept showing up

Three patterns emerged across the fifty episodes, and they’ve reframed how we think about the work.

The first is loneliness. We knew this going in. We’ve written about it. We’ve built coaching materials around it. But hearing it from forty-nine founders in a row, in their own words, is a different thing than knowing it in the abstract or from our own experience. The specific quality of the loneliness surprised us. It isn’t the loneliness of being physically alone. It’s the loneliness of carrying something the people around you can’t fully carry with you, either because they work for you, or because they love you too much to be objective, or because they simply don’t have your context.

Almost every founder we talked to described some version of that. Different words, same experience. It made us more certain than ever that the actual product we can offer isn’t advice. It’s someone in the room who understands what you’re carrying and isn’t compromised by their proximity to it.

The second is that the hardest work of running a company is the people work. Specifically the firing. This one came up so often it stopped surprising us. Founder after founder told us they held on too long. They knew something was off, they hoped it would resolve, they didn’t want to have the hard conversation, and by the time they finally acted, the damage had compounded.

Nobody who talked about this said they wish they’d waited longer. Every single person said they wish they’d moved faster. That kind of consensus is rare. When you hear the same regret from fifty different people who otherwise share almost nothing in common, you start to believe it’s a real pattern rather than an anecdote.

The third is that the founder can’t be separated from the company. As one of our guests, Giulia, put it: “I am the nervous system of my business.”

Whatever the founder is carrying, the company is feeling. Anxiety, avoidance, unresolved conflict, unclear priorities. None of it stays in your head. It shows up in your team’s behavior, your product decisions, the culture that grows around you.

This is the theme that hits closest to what we do every day. It’s also the one that founders tend to resist the most, because the implication is that some percentage of the problem is always inside you. That’s a hard thing to hear when you’re already working eighty hours a week and doing everything you know how to do.

But it’s true. And the founders who make peace with it are the ones who tend to make it.

The gratitude part

We want to pause on something that’s not framework and not analysis. Just gratitude.

Every founder who came on the show gave us something. Their time, obviously. But also their honesty. Founders are trained to project confidence. It’s part of the job. Investors want to see it. Employees need it. Customers respond to it. Sitting down with a microphone and telling the truth about the hard parts of the last three years is not something founders are practiced at.

The forty nine people who did it anyway gave us something rare. We’re not going to pretend we’ve done anything heroic by hosting the conversations. The heroism was theirs, in being willing to say the thing they usually don’t say.

For our part, this project has become something we didn’t expect. It started as a way to help founders feel less alone. It’s turned into a way for us to feel more connected to the broader community of people doing this work. Every conversation reminds us why we started Wisdom Partners in the first place. Every episode is a small correction against the myth that founders are supposed to have it all figured out.

The next fifty episodes are going to be more of what’s worked and some things we haven’t tried yet. Deeper dives into some of the themes above with founders who’ve lived them at unusual scale or in unusual industries. We’ve got a full lineup of guests already scheduled and we’re going to keep pushing what these conversations can be.

If you’ve been reading the blog and haven’t listened to the podcast yet, go subscribe. Every episode is a conversation with a founder telling the truth about something the rest of the ecosystem tends to gloss over. It’s the same voice, the same worldview, the same commitment to the honest version of the founder journey that we bring to everything else we do.

You can find Founder Real Talk on Spotify and YouTube. Two to three new episodes every week. If something in an episode resonates, tell us. If you know a founder whose story deserves to be told, send them our way. This show works because founders keep showing up for each other.

Thank you to every founder who’s been part of the first fifty episodes. Thank you for trusting us with the hard parts. There’s a proverb that has meant a lot to us: it is an honor to receive an honest reply. You’ve all honored us and our listeners with your honesty.

Here’s to the next fifty.

Subscribe now

The top-down approach is what most people learned in enterprise. The executive team disappears for a week, comes back with five to seven company goals, and cascades them down. Each layer sets goals that supposedly ladder up to the layer above. It’s clean on paper. In practice, the people closest to the work weren’t consulted. The goals feel handed down. Nobody owns them; they just try to comply with them. And by the time everything cascades through all the layers, the quarter is a third over.

The bottom-up approach sounds like the fix. Ask each team what they think their goals should be. Roll them up. The executive team synthesizes and refines. This is the ideal model in a world with infinite time. In practice, it burns an entire quarter on planning itself. Almost nobody actually does it, and the ones who try usually give up halfway through.

The middle path isn’t a compromise between these two. It’s a different sequence.

The core principle is the one we’ve written about before. [@Luis Pieruzzini - include title and link to this article here.] It’s much easier for you to course-correct the team’s thinking than for the team to reverse-engineer yours. Planning should be designed around that reality.

The full sequence

Here’s what a well-run quarterly planning process actually looks like when you compress it. In practice, this is roughly two working days of actual meeting time, spread across a week to allow drafting in between.

Step 1: The framing group drafts directional guidelines. (Half a day)

Get two or three people in a room who have their pulse on where the business needs to go. This is not necessarily the CEO plus the org chart. It’s the people with actual context, wherever they sit. Sometimes it’s the CEO, a founder, and a senior operator. Sometimes it’s a CEO and a couple of function leads. The composition matters less than the caliber of thinking.

The job of this group is to draft directional guidelines. Not full OKRs. Not target numbers. Just the qualitative priorities for the quarter.

Something like: “Our biggest issues this quarter are increasing retention, growing sales in the enterprise segment, and reducing interest payments on our debt facility.”

That’s it. No percentages. No specific KRs. If you have strong feelings about a specific number, don’t hide the ball, name it. But mostly, this stage is about scoping, not committing. The goal is to give the rest of the organization enough guidance to think clearly, not to hand them a finished plan.

This is the phase where focusing on inputs matters more than outputs. What you produce here is a set of inputs to the team’s thinking. You’ll get outputs back from them in the next steps.

Step 2: Executive alignment on scope and ownership. (Half a day)

Bring in the executive team, or the layer of leaders who own each functional area. Walk them through the directional guidelines. Get their feedback. Refine as needed.

The critical part of this meeting is claiming ownership. By the time everyone leaves the room, each priority has a leader whose name is on it. Not shared ownership. Not “the marketing team.” A specific human who will come back with the OKRs for their area and be accountable for delivering them.

You also want to leave with rough agreement on the guidelines themselves. Not perfect. Rough. The point of this meeting is to give people enough scope to think inside the broad shape of the plan, not to lock the details of the plan.

Step 3: Owners draft OKRs with their teams. (One week, mostly async)

Each executive takes their area of responsibility and drafts real OKRs. Targets, guards, and diagnostics for each priority. (If those terms are new, we wrote about them in “Measuring What Actually Matters.”) [@Luis Pieruzzini include link here.]

For smaller teams, the executive can often just pull three or four people into a room and draft it collaboratively. For larger teams, most managers do this through one-on-ones. They draft, share, iterate. A lot of team members won’t have the context to make good top-down contributions, but they’ll have sharp opinions on the pieces that touch their work.

This step takes about a week. It’s mostly async. The leader is doing the driving.

Step 4: Executive review and dependency mapping. (Half a day)

The executive team reconvenes. Each owner presents their OKRs, what they’re going to achieve, how they’ll measure it, and, critically, what they need from the rest of the company to succeed.

This last piece is the one most companies leave implicit and then regret. If the sales lead’s plan assumes engineering will ship a specific feature by mid-quarter, that dependency has to be surfaced now, in the room, with the engineering lead present to confirm or push back. Otherwise, you’ll discover the misalignment in week eight, and it’ll be too late.

Expect a few iteration loops. The CEO gives feedback. Owners refine. Sometimes, it takes two or three passes across different meetings. That’s fine. What matters is that everyone leaves this stage with OKRs that are actually owned, with dependencies mapped and agreed upon.

Step 5: Publish via all-hands. (One meeting)

Roll out the quarterly plan in an all-hands meeting. The CEO frames the quarter at the beginning and closes at the end. Everything in between is the executives presenting their own OKRs. Not the CEO reading them out. Not the deck someone else built. Each owner gets up and says, “Here’s what I’m committing to, and here’s what I need to make it happen.”

That’s the sequence. Two working days of actual meeting time, spread across roughly ten calendar days. Some drafting and thinking in between. A published plan at the end.

Why the sequence works

The design of this process is doing two jobs at once.

Job 1 is producing a coherent set of quarterly goals. That’s the obvious thing.

Job 2 (less obvious but more important) is producing goals that are actually owned by the people who have to deliver on them. The reason the sequence starts with directional guidelines instead of specific OKRs is that specific OKRs handed down feel like assignments. Directional guidelines that owners then translate into OKRs feel like commitments. Potentially the same content on paper, but a wildly different psychological experience.

The core principle that runs through the whole sequence: you never set the goals in the final form yourself. The goals are always the summarization of what the people who own them decided. Your job is to shape the direction upstream and course-correct downstream. The middle part belongs to them.

How the cadence adapts down the org

The sequence above describes what happens at the top of the company. There are similar mechanics apply as you push it down through the layers, with one important adjustment.

The more junior the employee, the more directive their manager needs to be. A senior VP will draft their own quarterly goals and defend them. A mid-career manager usually needs some framing from their leader before they can draft. A junior individual contributor often needs to be told what the priorities are, not asked what they think they should be.

That’s not a violation of the principle. It’s the principle applied to reality. Ownership requires the context to make good decisions. When someone doesn’t have that context yet, forcing them to invent goals is not empowerment, it’s abdication and lack of support.

The middle manager’s job near the bottom of the cascade isn’t primarily to set goals. It’s to make sure their team has internalized ownership of the goals that got set. That happens in the invitation-to-challenge conversation. “Here’s where we’re going this quarter. You said you want to own X. Here’s what I think success looks like. What do you think? What am I missing?” The lower you go, the more developed of a plan you’re bringing to the person. But you still bring it as an invitation, not a decree.

One more thing to include: The executive hiring test

A useful tell for whether a senior hire is going to work out. When you’re at the final stage of hiring an executive, have them do exactly this planning process for themselves, for their first six months.

Draft directional guidelines. Propose OKRs. Identify dependencies. Present it back to you.

You get three things out of that exercise. (1) You see their analytical thinking. (2) You see whether they actually understand the mission and can translate it into priorities. And (3) when they start on day one, they know exactly what their job is (after you’ve helped them refine their perspective).

That’s more useful than any interview loop.

The bigger point

Most planning processes fail not because the goals are wrong, but because the process didn’t produce ownership.

You can write beautiful OKRs and cascade them cleanly and still end the quarter with a team that never really committed to them. Or you can produce slightly rougher OKRs through a process that made people co-authors of what they’re committing to, and watch the same team overdeliver.

The plan matters, but the way you produce it matters more.

Two days of well-designed meetings, spread across a week, will get you further than a month of the wrong ones. The trick is knowing which meetings actually count and running those well.

Subscribe now

That is not what most employees mean when they say they want autonomy.

What they actually want is the freedom to execute on your vision without having to come back to you for every decision. They want to achieve the outcome you’re trying to achieve, in the direction you’d choose, using the judgment they’d apply if they had your context. What they’re asking for isn’t independence from you. It’s the ability to represent you when you’re not in the room.

That distinction is nearly the whole game. Miss it and you’ll either micromanage a team that resents you, or over-delegate to a team that quietly drifts away from what you actually wanted.

The three layers

Every decision inside your company happens across three layers.

The why. Why are we doing this at all? What outcome are we ultimately after? What’s the mission we’re trying to serve?

The what. What specifically are we going to build or ship or do this quarter? What does success look like? How will we measure it?

The how. What tactics are we going to use? What tools? What sequence? What compromises are we going to make when reality doesn’t fit the plan?

These are not the same layer, and they shouldn’t be owned the same way. Real autonomy is a slope across these three, not a single toggle.

Layer 1: the Why (You drive 80 to 90 percent)

This layer belongs to you.

Your team wants you to own the Why. That’s why they took the job. They want to be part of something bigger than themselves, and they want you to tell them what the bigger thing is. Imagine how they would feel if you show up to the Monday all-hands and say, “So … what do you all think we should be trying to accomplish?” You have not empowered them. You have destabilized them.

They will contribute some to the Why—especially senior leaders, who should have real influence at this layer. But even the strongest senior leader wants to know that the founder has a view, believes in it, and is willing to defend it. A senior VP will happily help refine a Why, but they want it to be a real thing they’re reshaping, not a blank canvas.

The more junior an employee is, the more they want the Why to come from you, whole and unambiguous. This is the layer where founder clarity matters most.

Layer 2: the What (Roughly split: they draft, you refine)

This is where most leaders get it wrong, in either direction.

The command-and-control mistake is to hand your team a fully specified what. “Here are our quarterly goals. Here are the KRs. Go execute.” You’ve saved yourself a week of team-based planning … and destroyed any sense of ownership in the process. Your team is now compliant (hopefully), but not aligned.

The hands-off mistake is to say, “Figure out what we should be doing this quarter.” Then, you get frustrated when they come back with something that isn’t what you had in mind. You didn’t share your view. They aren’t mind readers.

The right move is a feedback loop. You share the Why in specific enough terms that direction is clear. You ask them to come back with What they think the what should be, given that Why. They draft it. You react, ask questions, push back where you disagree, help them see what they missed. You iterate until you’re both aligned.

At the end of that process, they’ve done maybe 60 percent of the driving on the What. You’ve done 40 percent, mostly through course-correction rather than dictation. And critically, they now own the What because they proposed the majority of it, even though your fingerprints are all over the final version.

This is the layer that carries the most weight, because it’s where alignment actually gets tested. If you get this layer right, the layer below almost takes care of itself.

Layer 3: the How (they drive 80 to 90 percent)

Once you’re aligned on the What, the How belongs to them.

You are not the tactician on their function. You hired them because they know things about execution that you don’t, or because you don’t have the time to be in the details. Either way, the How is their zone.

Your job at this layer isn’t to prescribe. It’s to observe. You look at how they’re executing not to correct their tactics, but to check whether their alignment on the What and the Why is actually solid.

Here’s the reframe. When an employee’s How is off, the problem is almost never that they’ve chosen bad tactics. The problem is almost always that you weren’t as aligned on the What or the Why as you thought. Their tactics are the diagnostic. What they choose to do reveals what they think you’re actually trying to accomplish.

If a new sales leader comes back with a hiring plan that focuses on a region you never intended to prioritize, the right question isn’t: “Why are you hiring in the wrong region?” The real question is: “What do we not agree on about where our sales team should focus?” Their How is telling you that your What wasn’t actually shared.

Fix that upstream, and the tactics correct themselves.

The shape of the slope

Put together, autonomy across a healthy leader-employee relationship looks like a curve rising from left to right.

At the Why, they have a voice, but you’re driving. At the What, they draft, you refine, and you converge together. At the How, they’re in the driver’s seat, and you’re watching for signal.

That’s the slope of autonomy. That’s what employees mean when they say they want autonomy. Not independence from your direction. Ownership over the parts of the work where their expertise is the point.

The founders who get this right report something interesting once it clicks. Their team starts spending real cognitive effort building a mental model of them. What would the founder say about this? How would they weigh these two options? What would they push back on? It’s like your personal chatbot within their minds.

Your team is doing this whether you want them to or not. Most founders don’t realize how much of their team’s time gets spent on this specific kind of prediction. The move is to shape that prediction deliberately, so the version of you living in your team’s heads is accurate enough to answer questions when you’re not there.

That’s the actual mechanism of scaled leadership. Not more meetings. Not more oversight. A team that can predict your judgment because you gave them enough alignment to build a working model of it.

The slope is a diagnostic. Wherever your team feels stuck, look at the layer before and ask whether you actually did the alignment work there. Almost every time, the answer is that you didn’t do enough of it.

Build the slope. The autonomy follows.

Subscribe now

That’s the entire craft of coaching in 20 seconds.

When you’re advising a founder or an executive, the temptation is to give them the answer. You’ve probably seen this problem before. You have a view. It would be faster to just tell them what to do. And sometimes that’s the right move. But most of the time, the version of the answer they arrive at themselves is more useful than the version you hand them, even when the content is identical.

The reason is simple. An answer you’re given is information. An answer you arrive at is understanding. The first one you follow. The second one you own.

The mechanics of coaching through questions

The move isn’t to pretend you don’t have a view. You often do have a view, and that view is exactly what should be driving the conversation. The trick is to use it to shape the questions, not to shortcut past them.

If you think a founder is undervaluing their product, you don’t say “you’re undervaluing your product.” You ask, “What’s the highest price you’ve ever heard a customer object to?” … and then “What happened when they objected?” … and then “How many of those customers still bought?” You’re guiding them toward the conclusion you already reached, but they’re doing the reasoning. When they arrive, they arrive with conviction because they built the argument themselves.

The compliment above is the giveaway that this is working. The founder feels like they figured it out. In some real sense, they did. What you contributed was the direction of the inquiry, not the answer at the end.

Most people who try to coach skip this step. They see the answer and jump to it, and the person on the other side of the table complies but doesn’t internalize. Six weeks later, the same problem is back in a slightly different form.

The same skill makes you effective with AI

Something interesting has happened as language models have gotten better. The people who get the most out of them are the people who already had this skill from coaching or leadership. The parallel is almost exact.

If you sit down at ChatGPT or Claude and tell it exactly what you want it to produce, you’ll get something reasonable. You’ll also get roughly what you were already thinking. The model is doing a competent job of predicting the output that fits the request you gave it. You’ve used it as a smart typewriter.

If instead you ask it good questions, you’ll often get answers that are better than what you were thinking on your own.

As a concrete example, Charles was working on a customer development pitch deck. The first pass from the model was flat. It missed the customer pain points that mattered most. The easy move would have been to say, “No, do it this way instead,” to describe what he already had in mind, and get back a deck that matched his existing thinking.

Instead, he asked the model a question: “What the customer actually cares about is X and Y. How would we design a deck that solves for those?”

The response came back with features and framings he hadn’t considered. Some of them were better than what he’d been thinking. The model didn’t just validate his direction. It extended it.

Why the question format beats the instruction format

There are two reasons this works.

The first is that questions activate the model’s reasoning in a way that instructions don’t. When you tell a model, “Write me a section that says X,” it optimizes for producing X. When you ask it “Given these constraints, how would you approach X?”, it has to reason through the constraints and generate an answer. This often surfaces considerations you didn’t know to include.

The second reason is the sycophancy problem. Large language models are trained to be helpful, which often means trained to be (overly) agreeable. If you tell the model your view and then ask it to help you execute on that view, it will mostly agree with you because agreement is what it’s rewarded for. You’ve built a fancy echo chamber.

Questions cut around this. When you ask the model to reason through a problem rather than execute on your conclusion, you get less flattery and more actual thinking. It’s the same reason a good coach asks questions rather than validating. Validation is comfortable. Thinking is useful.

The practical implication

Most founders using AI tools are getting a fraction of the value available to them, because they’re using the tools the way they’d brief a junior employee. They give it instructions. They accept what comes back. They edit for polish. This is helpful, but not transformative.

The expert move is to treat the model more like a peer with whom you’re thinking out loud. Actually talking to the model with the voice-to-text function helps create this more natural dialog. Describe the situation. Describe what you’re trying to solve for. Ask how it would approach the problem. Ask what considerations you might be missing. Ask what a smart person who disagreed with your framing would say. Ask what you’d need to be true for your current plan to fail.

Every one of those questions produces a better response than: “Write me a plan for X.”

The same is true of your team. The same is true of your board. The same is true of yourself.

The people who get the most out of any thought partner, whether human or machine, are the ones who learned to ask before telling. That skill compounds across every high-stakes conversation you have. It’s worth developing on purpose.

Because in a world where information is cheap and answers are everywhere, the differentiating move is knowing which questions to ask. That’s true whether you’re sitting across from a founder or opening a new chat window.

Subscribe now

• Should I raise another round?

• Should I replace my cofounder?

• Should I take the acquisition offer?

• Should I hire the executive?

• Should I keep pushing for growth, or slow down before my family pays the price?

But after years of working with founders, I’ve come to believe these aren’t primarily business decisions.

They’re leadership decisions.

And leadership decisions are rarely just business decisions. Every significant decision a founder makes is shaped not only by market conditions, financial projections, and competitive strategy, but also by fear, ambition, identity, relationships, values, the kind of life they hope to build, and the kind of world they want to help create.

That’s why the hardest founder decisions rarely feel straightforward. They’re tensions to navigate.

What founders actually ask for

People don’t usually come to Wisdom Partners saying they want better judgment.

Instead, they say things like:

• “I’m stuck between two bad options.”

• “I can’t tell whether I’m fooling myself.”

• “I don’t know who I can trust.”

• “My board wants one thing, but my gut says another.”

• “I think I’m becoming the bottleneck.”

• “I don’t know whether to raise, sell, or keep going.”

• “Everything feels blurry.”

On the surface, those sound like different problems, but they’re all moments when the stakes are high enough that thinking clearly becomes difficult.

The founder’s real challenge

Recently, I worked with several founders whose situations couldn’t have looked more different.

One wanted help creating an ownership culture so she could stop being the bottleneck in two growing companies. As we worked together, it became clear that the deeper question wasn’t organizational design. She wanted to build a company that wouldn’t consume the life she hoped to create as she prepared to become a mother.

Another founder came to us after losing a cofounder in the middle of fundraising. We spent plenty of time discussing strategy, but what he needed most was someone to think with as he carried the weight of leading alone.

A third founder wanted help preparing for the next stage of growth. We talked about strategy, but we also explored how his own assumptions, pace, and patterns of thinking were quietly shaping the company’s future.

Different industries. Different companies. Different questions. Yet the work was remarkably similar.

None of these founders lacked intelligence. None lacked information. All had capable advisors. What they needed was a trusted partner who could help them think clearly when business strategy, leadership pressure, and personal consequences became impossible to separate.

Better decisions require better judgment

People often ask whether Wisdom Partners provides coaching, consulting, or executive advising. Those sorta-kinda describe the format of the work, but not its purpose.

The purpose is to help founders make better decisions when the stakes are highest. We believe the way to do that is by strengthening judgment.

By judgment, I don’t mean instinct or intuition alone. I mean the ability to perceive reality clearly, weigh competing priorities, recognize tradeoffs, and make wise decisions under conditions of uncertainty.

The hardest founder decisions rarely come with clear answers. They require balancing short-term and long-term consequences, company needs and personal values, courage and caution, conviction and humility.

Pressure makes those decisions even harder. Urgency, uncertainty, responsibility, and isolation narrow our perspective, making it difficult to distinguish what is really true from what merely feels true.

No framework can make those decisions for you. No AI model can fully understand your context. Even as decision-making becomes more distributed, the founder’s judgment continues to shape the company’s highest-consequence decisions—and the culture in which everyone else makes smaller decisions.

How judgment grows

Founders face a difficult paradox. Good judgment is developed through experience and reflection. But surviving long enough to gain that experience requires enough judgment to navigate the hardest decisions along the way.

Developing good judgment is never finished. It grows through disciplined examination of difficult decisions and thoughtful partnership. That often means slowing down long enough to ask questions that are easy to miss when you’re operating at startup speed.

• What assumptions am I making?

• What is the forest I am not seeing because I’m surrounded by trees?

• What fears or ambitions might be distorting my perspective?

• What are the immediate, longer-term, and second-order consequences of this decision?

• Which option best aligns with the kind of company—and the kind of leader—I want to become?

We talk about all kinds of things with founders. Sometimes we discuss fundraising. Sometimes hiring. Sometimes organizational design. Sometimes conflict. Sometimes the conversation is deeply personal. More often than not, it’s all of those at once.

Authenticity and empathy create the trust required to examine difficult decisions honestly. Business experience keeps those conversations grounded in the realities of building a company. Together, they create the conditions for better thinking when it matters most.

Why this matters

As information, strategic frameworks, and AI-generated recommendations become increasingly accessible, actual judgment becomes even more valuable. In fact, good judgment is your most valuable asset as a founder. In many ways, your shrewd judgment is what you and your investors are betting on. (Judgment is the new moat.) The problem is that judgment gets clouded under pressure and entangled with all kinds of internal and external variables.

Technology can expand our options. Capital can accelerate growth. Talent can improve execution. But leaders still decide what to pursue, what to ignore, what to change, what to protect, and when to act. Those are judgment calls. They are immensely important, and they compound over time.

Small improvements in judgment don’t simply produce better individual decisions. They influence the people you hire, the culture you create, the risks you take, the opportunities you recognize, and ultimately the kind of company you build.

The work of Wisdom Partners

For years, I described our work as founder coaching. Today, I think there’s a better description.

Wisdom Partners exists to be the trusted thought partner founders turn to when the stakes are highest. When the biggest decision of your year arrives, you shouldn’t have to think through it alone. When the heat is highest, you want us in your corner.

You need someone who understands the realities of building companies, who genuinely cares about you as a leader, and who can help you see through the clouds of intense pressure. Better judgment is the result. Better decisions follow.

Because founders don’t have business problems and personal problems. They have leadership challenges that appear in both places.

And the leaders who learn to navigate those moments with wisdom don’t just build stronger companies. They build companies that contribute to lives worth living—for themselves, their teams, and the people they serve.

Subscribe now

The framework we use for this comes from Stephen Covey, who introduced it in The 7 Habits of Highly Effective People under Habit 1: Be Proactive. He called them the Circle of Concern and the Circle of Influence. Later leadership writers expanded it into a set of concentric rings, which is the version we teach because it maps more cleanly to how a founder’s day actually looks.

The idea is simple. Lots of things affect you. You don’t have a corresponding ability to affect all of them. Most people spend their emotional energy in inverse proportion to their actual leverage.

Here’s what the circles look like, from the inside out.

Most influence: your thoughts, attitudes, and actions

The innermost circle is you. What you think. What you feel. What you do. This is where your leverage is highest and where, paradoxically, most founders spend the least time.

Even here, control isn’t total. Nobody controls everything they think. Nobody controls every reflex reaction to a hard email or a bad meeting. The self-aware founder controls more than the reactive one, but nobody controls all of it. Triggers are called triggers for a reason.

But you have more control here than anywhere else in your life. You can change how you frame a setback. You can change what you decide to focus on tomorrow morning. You can change how you show up in a hard conversation. You can decide whether to send the email or sleep on it.

Most of your leverage lives here. Most founders barely tend to it.

Some influence: family, team, business, health

The next circle out is where you have real but partial influence. Your immediate family. Your friends. Your co-workers. Your home. Your business. Your health.

Your business belongs here, not in the innermost circle, and it’s worth pausing on that. You don’t fully control your business. You influence it heavily. You decide what to build, who to hire, how to spend, what to say yes and no to. But customers make their own decisions. Team members make their own decisions. Investors make their own decisions. You are the largest single influence on your company, and you are still not in control of it.

Same for health. You control what you eat, how you sleep, whether you exercise. You do not control cancer. You do not control accidents. You optimize possibilities. You never eliminate risk.

This is the second-highest leverage zone. If you’re doing the work in the innermost circle, this is where most of the visible output shows up.

Minimal influence: extended family, neighborhood, government

The next ring out is where you have some influence but not much. Your extended family. Your neighborhood. Your local government. Your industry ecosystem.

You vote. Sometimes your candidate wins. Sometimes they don’t. You can pick up trash on your street. You can’t paint your neighbor’s house. You can attend a founders’ meetup. You can’t rewrite how your city funds infrastructure.

Founders often get pulled into this ring by frustration. The industry should be different. The city should support startups better. The tax code should favor small companies. All might be true. None of it is where your leverage sits.

Contributing to change at this level can be meaningful and worthwhile. It should not be where most of your attention lives.

Almost no influence: macro trends, the economy, the climate

The outermost ring is where you have almost no influence at all. The price of oil. Interest rates. The venture funding climate. The broader economy. Weather. Climate. War and peace. The general vibe of the market.

You have some second-order influence. You recycle. You vote. You choose what to consume. Your individual actions do matter in an aggregated sense, and you should still do them. But the amount of attention founders spend here (in the form of anxiety, reading, doomscrolling, and comparing themselves to a market they can’t control) is wildly disproportionate to their ability to move anything in it.

This is the ring where founder attention gets destroyed the fastest.

Where founders actually lose the game

The specific application to founder life is worth calling out.

You cannot control the venture landscape. You cannot control whether capital is loose or tight this quarter. You cannot control which competitor closes a round next week or how much they raise or which fund led it. You cannot control interest rates, the IPO market, or whether the AI hype cycle inflates or pops.

The number of founder hours lost each year to obsessing over these things is staggering.

What you can control is your pitch deck. Your product. Your sales process. Your team. What you spend time on tomorrow morning. The email you send tonight. The conversation you have with your co-founder about what’s actually working. The people you choose to spend your remaining attention on.

Every hour you spend refreshing TechCrunch is an hour not spent on the circle where you have leverage.

The reframe

This is an attention allocation problem. If you spend 70% of your attention on the outer rings, you get almost no return on it, because your leverage there is close to zero. If you spend 70% of your attention on the innermost two rings, you get most of the possible return, because your leverage there is high.

Same amount of energy. Radically different outcomes.

The founders who endure are those who figure this out. They stop trying to control the macro. They stop measuring themselves against news headlines. They let the ecosystem be the ecosystem and put their finite attention into the tight core of things they can actually move.

That doesn’t make the outer rings go away. The economy still shifts. Competitors still raise. Markets still turn. All of that keeps happening whether you obsess over it or not.

The question is whether your response to those things is going to come from a place of leverage or from a place of reaction.

Focus on the center. Let the edges do what they’re going to do.

Subscribe now

You have eight to twelve productive hours in a day. The question is which of those hours are you doing the work that only you can do, and which are you doing work that is quietly draining you while producing very little. Most founders can’t answer that cleanly. Until you can clearly identify which work produces the best returns, no amount of productivity hacking is going to help very much.

The framework we use for this comes from Dan Martell’s book Buy Back Your Time. If you haven’t read it, it’s worth the time and money. The core tool is a simple 2x2 that maps everything you do against two axes: how much money it makes you, and how much energy it gives you.

Every task in your life sits somewhere on this grid. Where it sits tells you what to do with it..

The delegation zone: the easiest place to start

The bottom left is where most founders should start because it has the lowest stakes and the highest immediate payoff.

The rule is simple. If a task drains you and doesn’t produce revenue, either delegate it, automate it, or stop it entirely.

The elimination path is underrated. Lately, I have been unsubscribing from newsletters I kept “meaning to read” that just built emotional debt in my inbox. If you’re not reading it and it isn’t valuable most of the time, unsubscribe. The same principle applies to meetings that no longer need to exist, reports nobody reads, and processes that persist because nobody bothered to kill them. Cutting is often better than delegating because delegating still requires oversight.

The delegation path is where most founders leave money and hours on the table. The reason is usually that they haven’t tried, or they tried once with a bad hire and gave up.

The virtual assistant unlock

The single highest-leverage move for most founders in the delegation zone is hiring a virtual assistant. Even part-time. Even ten hours a week.

Here’s what it actually looks like in practice. You get an idea for something you want to send out. Normally you’d sit down and spend an hour and a half writing it, formatting it, finding the right people to send it to, personalizing the send. Instead, you spend five minutes explaining the idea to your VA. They come back with a draft that’s 80 to 90% of the way there. You spend fifteen minutes polishing. Total time from you: twenty minutes instead of ninety.

That’s a 4x multiplier on your output for the same amount of your time. Sometimes it’s 10x, depending on the task.

The math gets more interesting when you consider what you do with the freed hours. If you spend them in the production zone, you’re compounding the value. If you spend them on sleep, exercise, or family, you’re compounding a different kind of value that turns out to matter just as much for whether you last as a founder.

We’ve placed fifteen to twenty VAs from Latin America for founders in our network. Why do we recommend LATAM specifically?

• The time zones are close to US business hours

• The cultural context is closer to a US working environment than most alternatives

• The English quality is often stronger than what you get from Eastern Europe or Asia.

• Rates typically run $8 to $15 an hour depending on the level of the role.

The roles range widely. Straight administrative VAs. Video editors. Customer service. Business operations. Sales development. Whatever’s sitting in your delegation zone is likely something you can hire someone in LATAM to do for a fraction of what a US hire would cost, and often at a higher quality than you’d expect.

If this is something you want to explore, talk to our team here. We’ll help you scope the role, figure out what to hand off first, and match you with someone from our network.

The replacement zone: the harder work

Once the delegation zone is under control, the harder work begins.

The replacement zone is where founders get stuck. This is the top-left quadrant, the work that makes money precisely because you do it. Maybe you’re the best salesperson in the company. Maybe you built the marketing engine, and it runs on your intuition. Maybe your product intuition is the reason the roadmap doesn’t drift.

The instinct here is to hold on. “Nobody else can do this as well as I can” is technically true and strategically fatal. If the work drains you, holding it means you’ll eventually burn out while doing good work for your company. That’s a worse outcome than an imperfect handoff.

The move is replacement, not delegation. The distinction matters. Delegation is handing off a task and letting the person run with it. Replacement is a slower, deliberate transfer. You document your process, you train someone into it, you stay closely involved during the handoff, and you gradually pull back as they demonstrate competence.

One founder in our network was a marketing genius who decided to hand off marketing entirely. She hired a fractional executive, briefed her, and stepped away. Months later she realized the fractional exec was operating out of alignment with the company. Not because the hire was bad, but because the handoff had been too fast. The job wasn’t just tasks. It was judgment calls the founder had been making implicitly, and nobody had captured them explicitly.

The fix wasn’t to fire the executive. It was to re-engage. Regular check-ins. Explicit conversations about brand voice, positioning, priorities. Slower transfer. What she called delegation had actually needed to be replacement.

If the work makes real money for the company, don’t just hand it off. Replace yourself out of it. That means SOPs, close oversight, and a gradual widening of the trust zone as the new owner earns it.

The order of operations

Most founders try to do this backwards. They obsess over their production zone (which usually doesn’t need optimization because it’s already working), procrastinate on their replacement zone (which is the hardest), and let their delegation zone fester (which is the easiest to fix and the fastest to pay off).

The right order is the opposite. Start with the delegation zone. Get the drain off your plate first. Use the reclaimed hours to properly set up the replacement zone. Protect the production zone with everything you have. Don’t neglect the investment zone because it’s what keeps you functional over the long run.

The whole framework is a tool for one question? Are you using your time wisely?

Most founders find out, when they honestly map it, that the answer is no. And that gap between where their time is and where it should be is where the leverage lives.

Subscribe now

They’re comparing.

There’s a specific kind of comparison problem founders fall into, and it’s the most common psychological tax in startup life. The myth is that the only successful outcome is the unicorn outcome. Anything less than a billion-dollar valuation is a participation trophy.

This is wrong on two levels. It’s wrong about what makes a successful business, and it’s wrong about what changes your life.

The math nobody talks about

Run the numbers on a few exit scenarios and the unicorn obsession starts looking strange.

You hold 30% of a company that exits for $10M. You take home $3M.

You hold 30% of a company that exits for $50M. You take home $15M.

You hold 30% of a company that exits for $150M. You take home $45M.

Now ask the honest question. Is your life meaningfully different at $15M versus $45M? At $3M versus $15M? At any point along this curve, you’ve crossed into territory most people will never see in their lifetime. You’ve solved the question: “Do I ever have to work again?” You’ve solved your kids’ college, your parents’ retirement, your own peace of mind.

The marginal value of additional millions past a certain threshold is real but small. The marginal cost of chasing them, in years of your life, in stress, in time with the people you love, in health, is not small. It’s often enormous.

A $20M exit, the kind that gets zero headlines and doesn’t make anyone’s “founder to watch” list, lands you $6M if you held 30%. Most people would call that winning the lottery. Founders chasing unicorns somehow file it under failure.

Why this myth persists

Rob Walling at Tiny Seed Capital and the excellent podcast Startups for the Rest of Us, have been making this argument for years. A $10M or $20M or $50M exit can be fundamentally life-changing for a founder. They’re right.

But the louder voices in the ecosystem are big venture funds, whose business model only works if a small number of their bets become enormous. They need unicorns. Their math literally doesn’t function without them. So the narrative they push, intentionally or not, is that the only outcome worth pursuing is the unicorn (which coincidentally lets them return their fund).

That narrative is correct for them. It is often wrong for you.

You are not a venture fund. You don’t need a portfolio of bets where one wins and the rest die. You need one company. You need it to work. And “work” can mean a lot of things that don’t involve being on the cover of Fortune or Inc.

The comparison tax

There’s a second cost to chasing unicorns, beyond the math. It’s the constant low-grade misery of measuring yourself against outcomes that were never available to you in the first place. LinkedIn is to founders as Instagram is to teenage girls. It can foster unhealthy comparisons.

Your business is different. Your market is different. Your timing is different. Your team is different. The founder who raised $50M last quarter is solving a different problem in a different market with different investors and a different cap table. Their fundraise tells you almost nothing about whether you should be raising, what you should be raising, or whether you’re succeeding.

And yet most founders compare anyway, because comparison is the default human response to ambition. Don’t stop being ambitious; just be ambitious about the right thing.

What ambition can look like instead

None of this is an argument for being unambitious. If you’re a missionary founder who genuinely needs to see this thing through, who’s trying to solve a problem at massive scale, who would rather die on the hill than sell early, that’s a real and respectable path. Build the unicorn. Some people are wired for it, and the world is better for them existing.

This argument is against chasing unicorns by default. Against assuming that because the headline outcomes are the unicorns, the only outcome worth pursuing is one.

The alternative is to build a real business. A company that becomes profitable. A company that compounds over time. A company that, if it never gets acquired, you’d still be glad to be running in ten years. A company where your life is sustainable, where you’re not destroying yourself to hit the next milestone, where the work itself is the point.

If that company grows into something acquirable, great. If the right offer comes along at the right time, take it. $20M, $50M, $100M. Any of these probably changes your life. None of them will get your name on a billboard, and that turns out to matter much less than founders think.

The reframe

Stop chasing unicorns just because everyone else is. Stop assuming the only valid exit is the one that gets headlines. Stop measuring your trajectory against companies that got lucky in a different market at a different time.

Build the thing that makes sense for you. Build it in a way that doesn’t break you. And when an outcome arrives that would change most people’s lives forever, recognize it for what it is.

Winning doesn’t always look like a unicorn. Most of the time, it looks like a real business that quietly made its founders wealthy and their customers better off. That’s the actual game.

Subscribe now

His piece is worth reading in full. The data is striking. Salaries for specialized AI trainers have climbed past $180K at the top end. Demand for these roles has grown more than 150% in two years. As the machines got smarter, the value of human expertise went up rather than down.

The line from his piece that stuck with me most: “You can scale the production of answers. You cannot scale taste.”

I want to take Gangesh’s argument and apply it somewhere specific. If human judgment is the scarce input for training the most advanced AI systems on the planet, what does that say about the messier, higher-stakes problem of running a company?

The encyclopedia problem

Here’s how I think about using AI as your business advisor.

In 1985, having an encyclopedia at home was a real advantage. You could look things up. You could answer questions your neighbors couldn’t. It was a genuine information edge.

By 1995, every middle-class household had one. By 2005, physical encyclopedias had mostly migrated to software. By 2015, Wikipedia made the entire genre obsolete. The encyclopedia didn’t get worse. The moat just evaporated, because everyone had it.

That’s where AI sits in 2026 as a business advisor. ChatGPT and Claude can give you a credible answer to almost any general business question. They can frame your strategy. They can pressure-test your reasoning. They can role-play an investor objection or draft a board update. All of that is genuinely useful, and you should be using these tools.

But it isn’t a moat. Every founder you’re competing with has the same tools. The same access to the same models. The same ability to ask the same questions and get the same well-reasoned, slightly-too-polished answers.

If your competitive edge is “I regularly use an LLM,” you don’t have an edge.

What AI cannot do for you

A model can tell you what other founders in your situation have done. It can synthesize the conventional wisdom. It can list the seven frameworks for thinking about your hiring problem. What it cannot do is look at you, in your specific moment, with your specific blind spots, and tell you which framework is actually wrong for you. It also can’t tell if you’re not really being honest with yourself or with it.

That requires three things AI doesn’t have:

1. It requires reading the room. Not the room in a strategy doc, but the actual room. The way you said something, the thing you didn’t say, the place you got defensive. A good coach catches the half-sentence you backed away from.

2. It requires having watched a hundred other founders navigate the same problem and remembering which ones got it right and which ones flamed out, and why. That’s pattern recognition built from experience, not from training data.

3. And it requires the willingness to disagree with you in a way that actually lands. AI is trained to be helpful, which often means trained to be agreeable. A coach worth paying for is willing to tell you that you’re wrong, and to keep telling you until you actually hear it.

The deeper thing

There’s something even harder to name that gets lost in this conversation, which is that humans only get really honest with other humans.

I sit across from founders every day. The things they actually need to work on, the real questions underneath their stated questions, almost never come out in the first five or even 20 minutes. They come out when there’s enough trust in the room that the founder is willing to stop performing competence.

The moment someone stops performing and starts actually thinking (with both the mind and the heart) is the moment coaching becomes valuable. And it doesn’t happen with a chatbot. It happens with another human, present, paying attention, who has earned the right to ask the next question.

This is simply how humans are built. We’re a social species. Our deepest cognition happens in dialogue with other humans we trust. You can simulate a form of that with AI. You cannot replicate the impact.

What this means for you

Gangesh’s bet is that the next decade goes to companies with the best people wielding the tools, not the ones with the most tools. I think that scales down to the individual founder too.

The AI tools are a commodity. You have them. So does your competition. The differentiator now is the judgment you bring to using them, which is itself sharpened by working with people who have judgment sharper than yours.

Use the tools. Use them aggressively. Let them handle the analytical, repetitive, synthesize-able work so you have more bandwidth for the work that actually moves your company forward.

But don’t confuse access to information processing power with access to wisdom. They’re not the same thing. They were never going to be the same thing. The data is now confirming what the best founders already knew.

The machines are getting smarter. Your need for a real human across the table is getting more important, not less.

Subscribe now