What Greg Castle’s Founder Test Reveals About Execution Due Diligence

Venture investors spend enormous effort evaluating an opportunity before making an investment. They study the market, technology, competitive landscape, financial model, capitalization, customers, and founders.

But eventually, every investment thesis has to pass through an organization.

The strategy has to become priorities. Priorities have to become coordinated work. Leaders have to make decisions. Functions have to manage dependencies. Capital has to be allocated. Problems have to surface early enough to solve them. The organization has to learn when assumptions prove wrong.

That raises an important diligence question:

Can this founder and management team actually execute the investment thesis?

In a Tech Scenes conversation with Greg Castle, Managing Partner at Anorak Ventures, we spent considerable time talking about what makes exceptional founders different. Castle has been investing in frontier technology for more than a decade, with roots going back to his early involvement with Oculus. He has watched founders attempt to bring entirely new technologies into markets where timing, capital, talent, customer adoption, and technical development all have to come together.

Castle's belief is clear: building an outlier company requires an exceptional founder.

But something else he said is just as important for investors.

When I asked about the ability to scale, Castle emphasized that the skill is in learning—surrounding yourself with great people, processing enormous amounts of information, distilling it, and executing against what you learn.

That distinction matters.

An investor is not only underwriting the founder who exists today.

The investor is underwriting that founder's ability to build an organization capable of becoming something much larger tomorrow.

That is where execution due diligence begins.

What Is Execution Due Diligence?

Execution due diligence is the assessment of whether a company's founder, leadership team, and organizational systems are capable of translating the investment thesis into coordinated action and measurable progress.

It is different from evaluating whether the strategy is attractive.

It asks whether the organization can execute that strategy.

It is different from evaluating whether individual executives have impressive backgrounds.

It asks whether those executives can operate effectively together.

And it is different from examining historical financial performance.

It looks at the organizational capabilities that will influence future performance.

This matters because companies do not execute investment theses on spreadsheets.

People execute them.

More precisely, teams of people execute them through systems of decisions, priorities, accountability, communication, coordination, and learning.

The larger and more complex the organization becomes, the more those systems matter.

An Exceptional Founder Is Not the Same as an Execution-Ready Organization

Castle described successful entrepreneurship as an extraordinarily difficult undertaking. Founders attempting to create companies worth billions of dollars need uncommon determination, persistence, confidence, and the ability to shape a future that does not yet exist.

I agree.

I have worked with hundreds of founders and leadership teams, and many of the best founders I have encountered possess an almost unusual capacity to learn, adapt, persuade, and keep moving through uncertainty.

Those qualities can create enormous early advantages.

The founder may personally hold the company's strategy in their head.

They may connect Product to Sales through informal conversations.

They may know every employee.

They may understand what customers are saying because they still speak with many of them personally.

They may resolve disagreements between executives simply because everyone knows the founder has the final answer.

They may identify problems before any reporting system surfaces them.

The company can appear highly responsive because the founder is acting as an extraordinary organizational integration layer.

Then the company grows.

Ten people become 30. Thirty become 75. Seventy-five become 150.

Functions become teams. Teams develop subteams. New executives join. More customers create more information. More capital creates more initiatives. Decisions become distributed across an organization rather than concentrated around a few founders.

The question changes.

It is no longer simply:

Can the founder execute?

It becomes:

Can the founder build an organization that can execute?

That is a very different capability.

The Three Layers of Execution Readiness

When considering execution readiness, I find it useful to look at three interconnected layers: the founder, the leadership team, and the operating system of the organization.

Weakness at any one layer can eventually constrain the investment thesis.

Founder Execution Capacity

The first layer is still the founder.

Castle's observation that scaling depends heavily on learning is important here.

A founder cannot possibly know everything required to scale a company before experiencing the problems scaling creates. The organization will encounter new markets, management challenges, financing environments, talent decisions, technical constraints, customer dynamics, and competitive threats.

The founder's existing knowledge matters.

Their learning velocity matters even more.

Can they absorb information that contradicts their assumptions?

Can they distinguish meaningful signal from noise?

Can they surround themselves with people who know things they do not?

Can they change direction without losing conviction in the larger mission?

Can they move from doing the work personally to building people and systems capable of doing it?

That last question becomes increasingly important.

A founder may be an extraordinary product leader, engineer, salesperson, or technologist. But as the organization scales, their job increasingly becomes building the environment in which other talented people can succeed.

Execution diligence should therefore consider not simply whether the founder is impressive, but whether the founder is becoming more capable as the organization becomes more complex.

Leadership Team Execution Capacity

The second layer is the leadership team.

One of the patterns I have seen repeatedly across growth companies is that a collection of exceptional executives does not automatically create an exceptional leadership team.

In fact, experience can introduce a different type of complexity.

The new CMO brings the operating methods that worked at their previous company. The CRO brings another system. Product has its planning philosophy. Engineering operates on its own cadence. Finance has another model. Everyone is capable. Everyone has evidence that their approach works.

And suddenly the company contains several individually rational operating systems competing with each other.

The diligence question should therefore go deeper than résumés.

Does the leadership team have a shared understanding of where the company is going?

Do leaders agree on the major priorities required to get there?

Are cross-functional dependencies visible?

Is ownership clear when an objective requires several departments?

Can leaders disagree, make a decision, and move forward?

Or does every meaningful cross-functional disagreement eventually escalate back to the CEO?

Those are execution questions.

A leadership team can contain remarkable talent and still have weak organizational execution capacity if the team cannot coordinate that talent toward a shared outcome.

The Operating System Is the Third Layer of Diligence

The third layer tends to become more important as the company grows: the organization's operating system.

I do not mean software.

I mean the system through which the organization repeatedly translates strategy into execution.

How does the company define where it is going?

How does that direction become an annual plan?

How are the most important near-term priorities selected?

How does the organization distinguish strategic objectives from ongoing business performance?

How is ownership assigned?

How are cross-functional dependencies surfaced?

How does leadership know when something is going off course?

Where are unresolved problems collected and solved?

How frequently does the organization review progress?

How does learning from one quarter change the next quarter?

When those mechanisms are informal, they often depend disproportionately on particular people.

Usually the founder.

When those mechanisms become organizational habits, execution becomes more resilient.

This is one of the fundamental ideas behind Peak OS. Mission, longer-term direction, annual planning, OKRs, KPIs, Roles and Responsibilities, operating rhythm, Triage, and organizational learning are not independent management tools.

Together, they form an execution system.

For an investor, the relevant question is not whether a company uses Peak OS or any particular methodology.

The more important question is:

Does this company have a coherent way to execute?

How Do You Assess Founder Dependency Before Investing?

Founder dependency can be difficult to recognize because it often looks like strong leadership.

The CEO knows everything.

The CEO attends the important meetings.

The CEO solves the hardest problems.

The CEO helps close the biggest customers.

The CEO recruits key employees.

The CEO settles disagreements.

The CEO communicates the strategy.

At an early stage, much of this is necessary.

The diligence issue is whether the organization is developing capabilities around the founder as it grows—or merely expanding the number of things that eventually flow back to the founder.

One way to explore this is to ask members of the leadership team similar questions independently.

Where is the company going over the next three years?

What does success look like this year?

What are the three most important organizational priorities right now?

What are the biggest execution risks to achieving them?

Who owns those risks?

Which decisions require the CEO?

Where is the company currently off course?

The precise answers matter.

The consistency of the answers matters just as much.

If every leader tells a materially different story, the company may have founder clarity without organizational alignment.

That creates risk.

How Can an Investor Distinguish a Talent Gap From an Operating-System Gap?

This is another useful execution-diligence question.

Suppose a company repeatedly misses important commitments.

One explanation is talent.

Perhaps the company needs a different sales leader, a more experienced CFO, additional engineering leadership, or a stronger operations executive.

That happens.

But replacing people does not automatically solve execution problems.

If ownership remains unclear, priorities change continuously, cross-functional dependencies remain invisible, and the leadership team lacks a shared operating rhythm, the new executive may eventually encounter the same problems as the old executive.

Sometimes the apparent people problem is actually a system problem.

The reverse is also true.

A strong operating system cannot compensate indefinitely for a leader who lacks the experience, capability, values alignment, or motivation required by the role.

The goal of execution diligence is to separate these conditions.

Ask:

Is the role itself clearly defined?

Does the executive understand what outcomes they own?

Does the rest of the leadership team understand what that executive owns?

Does the executive have the authority required to deliver those outcomes?

Are the dependencies surrounding the role visible?

Is the person capable of performing the role at the company's next stage?

If the system around the leader is unclear, replacing the leader may reproduce the problem.

If the system is clear and the leader repeatedly cannot execute within it, the talent diagnosis becomes much stronger.

Look for Execution Before the Financials Reveal It

Traditional financial results are critical, but many execution problems develop before they materially appear in the financial statements.

A product dependency slips.

Sales makes commitments Product does not understand.

Hiring plans exceed the company's actual ability to onboard people.

Two executives believe they own the same decision.

Nobody owns another decision.

A major quarterly objective moves off course, but leadership does not revisit the assumptions behind it.

The CEO becomes the connective tissue across an expanding set of functional teams.

Individually, these may appear small.

Together, they can reveal execution drift.

This is why organizational visibility matters for investors and boards.

A strong operating picture should make it easier to see what the organization is trying to accomplish, how the business is performing, what is off course, where ownership sits, and which unresolved issues could materially affect the plan.

The objective is not to give investors access to every operational detail.

That would create a different problem.

The objective is to understand whether management has enough visibility to run the company effectively—and whether the board has enough visibility to understand execution risk without becoming management.

What I Have Learned From Hundreds of Teams

Working with hundreds of leadership teams has made several execution patterns difficult to ignore.

First, smart people do not eliminate the need for organizational systems. The more capable the executives, the more important it can become to create a shared way of operating because each person arrives with credible experience and established methods of their own.

Second, alignment is much easier to assume than verify. Leadership teams frequently believe they are aligned until they are asked to independently articulate the strategy, priorities, ownership, and definition of success.

Third, founder dependency can remain hidden during periods of strong growth. A highly capable CEO can compensate for weak coordination for a surprisingly long time. The weakness becomes more visible when complexity accelerates, the organization grows quickly, or the founder's attention becomes constrained.

Fourth, repeated misses often contain organizational information. Missing a target once may simply mean an assumption was wrong. Repeatedly missing commitments for similar reasons can indicate that the organization is not converting experience into learning.

Fifth, organizational execution is not static. A system that worked at 25 employees may stop working at 100. The leadership team that successfully reached one stage may need new capabilities for the next one. Execution readiness therefore needs to be understood in the context of where the company is going—not merely where it has been.

These patterns are why execution due diligence should not be treated as a one-time judgment about whether management is "good."

The better question is whether the organization is capable of continuing to evolve as the investment thesis demands more from it.

Execution Due Diligence Is Really About the Future Organization

Most investment decisions contain an implicit organizational assumption.

The company will hire the team.

The product will ship.

Enterprise sales will scale.

International expansion will work.

The acquisition will integrate.

Manufacturing capacity will increase.

Margins will improve.

New executives will strengthen the company.

Every one of those statements depends on organizational execution.

A financial model can describe what needs to happen.

Execution due diligence asks whether the organization is being built to make it happen.

That means evaluating the founder.

But it also means looking beyond the founder.

Can the leadership team operate as a real team?

Can strategy become visible priorities?

Can priorities become owned work?

Can the organization identify when reality differs from the plan?

Can leaders solve the resulting problems without everything escalating to the CEO?

Can the company learn faster because it has more people—or does additional scale simply create more complexity?

These are not secondary operating questions.

They are questions about whether the investment thesis is executable.

From Founder Underwriting to Organizational Underwriting

Castle is right that exceptional companies often require exceptional founders.

The founder remains central.

But as a company scales, the unit of execution changes.

At the beginning, much of the company's capability may reside inside the founder and a small group around them.

Over time, that capability has to move into the organization.

The founder's learning becomes organizational learning.

The founder's clarity becomes organizational alignment.

The founder's relationships become teams and functions.

The founder's judgment becomes distributed decision-making.

The founder's ability to see the entire company becomes organizational visibility.

The founder's personal execution rhythm becomes an organizational operating rhythm.

That transformation is what allows a venture-backed company to grow beyond the capacity of any one extraordinary individual.

For investors, boards, and operating partners, that creates a broader diligence question than whether the founder can build the company.

Is the founder building an organization that can build the company?

That may be one of the most important execution questions in the entire investment thesis.

Related Insights

What Is Peak OS?

What Is Organizational Execution?

What Is Organizational Intelligence?

What Is a Business Operating System?

What Is Operating Rhythm?