Why Founders Need a Place Where the Pitch Stops: A Lesson From Greg Castle of Anorak Ventures

Founders have an unusual leadership responsibility.

They have to create belief in a future that does not yet exist.

They need investors to believe. Employees need to believe. Candidates need to believe. Customers and partners need to believe. At difficult moments, sometimes the founder needs to believe strongly enough for everyone else.

But there is another responsibility that is just as important:

Inside the leadership team, the company needs a place where the pitch stops and reality becomes the priority.

That distinction surfaced during a Tech Scenes conversation with Greg Castle, Managing Partner at Anorak Ventures.

Castle has experienced the founder role himself. Before becoming a venture investor, he ran a company for six years. Toward the end, the business was struggling. He described sitting there opening overdue bills while simultaneously taking calls from prospective investors and talking about the opportunity ahead.

Think about the mental transition required.

One moment, the founder is confronting everything that could go wrong.

The next, the founder has to communicate conviction about everything that could go right.

Castle described this as one of the extraordinary forms of context switching founders have to manage.

I see the same tension constantly in my work with founders and leadership teams.

Founders are expected to project confidence, but their organizations also need them to create an environment where people can say:

This isn't working.

We're off course.

I don't think we'll hit the commitment.

Our assumption was wrong.

I need help.

We have a bigger problem than we thought.

A company needs both realities.

Externally, the founder often has to create belief.

Internally, the organization has to discover truth.

The danger begins when pitch mode becomes operating mode.

Confidence Is Part of the Founder's Job

Castle described some of the best founders he has backed as operating near a very thin line between confidence and arrogance.

Maybe arrogance is not quite the right word. During our conversation, we also talked about irrational optimism—the unusual conviction required to attempt something most people would consider improbable.

That characteristic is not inherently negative.

It may be essential.

An entrepreneur building a new market, frontier technology, or venture-scale company constantly encounters reasons the business should not work. The technology is difficult. The market is early. Capital is scarce. Candidates have safer opportunities. Customers are skeptical. Competitors are moving.

A founder cannot respond to every obstacle by losing conviction.

Part of leadership is maintaining belief through uncertainty.

But confidence and organizational learning serve different purposes.

Confidence says:

We can figure this out.

Organizational learning asks:

What exactly do we need to figure out?

A company gets into trouble when the first question prevents the second one from being asked.

When Does Founder Optimism Become an Execution Risk?

Optimism becomes dangerous when protecting the narrative becomes more important than understanding reality.

This rarely happens because a founder consciously decides to hide problems.

It happens gradually.

The company misses a target, but everyone has a reasonable explanation.

A product milestone moves, but there are legitimate technical reasons.

Sales is behind, but several large deals are still expected.

An executive raises a concern but sees that the CEO is uncomfortable with the direction of the conversation, so the executive softens the message.

Another executive watches that exchange and learns something important: bad news should arrive carefully.

Over time, the organization can develop its own version of pitch mode.

Updates become explanations.

Explanations become rationalizations.

Off-course work stays "almost on course."

Leadership meetings become exercises in managing perception rather than understanding execution.

Nothing about this requires dishonesty.

Often everyone genuinely believes what they are saying.

That is what makes the problem difficult to detect.

The organization is not necessarily lying to itself.

It simply lacks a reliable system for testing what it believes against what is actually happening.

The Leadership Team Needs a Different Kind of Conversation

During our Tech Scenes discussion, I told Castle that one of the first things I establish when working with a leadership team is that the environment has to be transparent.

That does not mean hierarchy disappears.

Someone still owns the decision. The CEO is still the CEO. Functional leaders retain their responsibilities and authority.

Transparency is not the same as consensus.

It means the team is expected to put the important information on the table before making decisions.

That includes the things that are not working.

I've sometimes described unresolved organizational issues as boulders being carried in a backpack while climbing a mountain. The team can keep climbing with them for a while, but every unresolved issue consumes energy and makes the next part of the climb harder.

The instinct in many companies is to avoid unloading the boulders because doing so can initially feel uncomfortable.

The leadership team would rather focus on progress.

But surfacing problems is progress when the alternative is carrying them for another quarter.

The best operating environments make truth easier to surface before it becomes painful to confront.

How Do You Get Executives to Surface Problems Earlier?

Telling people to "be more transparent" rarely changes much.

Transparency needs a system.

This is one of the reasons operating rhythm matters.

A strong operating rhythm creates predictable moments when the leadership team is expected to compare the plan with reality.

Not occasionally.

Not only when something goes badly enough to attract the CEO's attention.

Every week.

Every quarter.

Every year.

When that rhythm becomes normal, surfacing an issue becomes less emotionally loaded.

The question stops being:

Who screwed up?

It becomes:

What changed, what did we learn, and what do we need to do next?

That shift is important because senior executives are highly sensitive to signals about how information will be received.

If admitting something is off course feels like admitting incompetence, people will naturally wait until they have a solution before raising the problem.

By then, the organization has lost valuable time.

If "off course" is simply a normal operating state that triggers discussion and problem-solving, issues move through the organization faster.

That is organizational intelligence.

The company becomes better at detecting changes in reality and turning those changes into decisions.

Make the Plan Visible Enough to Challenge

It is difficult to have an honest execution conversation if nobody agrees on what was supposed to happen in the first place.

This is one reason teams sometimes leave meetings with completely different interpretations of how things are going.

One person believes Product is behind.

Product believes the timeline changed.

Engineering believes additional requirements were added.

Sales believes the original launch commitment still stands.

Everyone has a defensible story.

The problem is that there is no shared operating picture against which those stories can be tested.

A clear plan changes the conversation.

When a company has aligned around a longer-term direction, a One-Year Plan, near-term objectives, business metrics, owners, and timing, the team has something concrete to compare reality against.

The plan is not valuable because the future will unfold exactly as predicted.

It won't.

The plan is valuable because the difference between the plan and reality creates information.

That difference is where learning begins.

Without a plan, a missed outcome can be explained almost indefinitely.

With a visible plan, the team can ask much better questions:

What assumption changed?

Did we underestimate the work?

Did another team create a dependency we did not see?

Is the objective still important?

Are we missing a capability?

Is ownership unclear?

Did the market change?

Do we need to change the plan?

Those are far more productive questions than debating whether things are "going well."

What Should Happen When Something Goes Off Course?

This is where many operating systems fail in practice.

Companies create goals.

They create OKRs.

They create dashboards.

They create metrics.

Then something goes red.

And nobody has defined what happens next.

The metric gets discussed.

Someone explains why it is off course.

The team says they will keep an eye on it.

A week later, the same conversation happens again.

Measurement without a problem-solving mechanism creates visibility without action.

In Peak OS, an off-course OKR, KPI, commitment, or significant issue can move into Triage.

Triage provides a structured place to determine what deserves the team's attention and then move from discussion to action.

The intent is important.

The point is not to punish the person who owns the issue.

The point is to use the collective intelligence of the leadership team to understand the situation, consider alternatives, and decide what happens next.

That is a very different culture from one in which executives arrive at a meeting prepared primarily to defend their area.

One culture is trying to protect individual credibility.

The other is trying to improve organizational performance.

Transparency Does Not Mean Radical Openness About Everything

There is an important distinction here.

A founder does not need to share every fear with every employee.

Executives do not need every operational detail.

The board should not become an extension of management.

Customers certainly do not need to experience every internal uncertainty.

Different audiences need different information.

The goal is not radical transparency.

The goal is appropriate visibility at the level where decisions have to be made.

The leadership team needs visibility into the information required to run the company.

Functional teams need visibility into the priorities, dependencies, decisions, and performance information required to execute their work.

The CEO needs visibility across the organization without being forced into every operational detail.

The board needs enough execution visibility to understand meaningful risks, assumptions, progress, and changes without taking over management.

Those are different views of the same organizational reality.

A strong operating system helps the company maintain one reality while presenting the appropriate level of that reality to different stakeholders.

That is very different from creating a different story for every audience.

How Can a CEO Project Confidence Without Creating False Optimism?

The answer is not to become less optimistic.

It is to separate confidence in the mission from certainty about the current plan.

A CEO can strongly believe in where the company is going while acknowledging that a particular tactic is failing.

A leadership team can believe deeply in the opportunity while recognizing that an important assumption was wrong.

A company can remain ambitious while revising an unrealistic objective.

In fact, the strongest confidence may come from knowing that the organization can identify mistakes and adapt.

This is where founders can model a particularly important behavior.

Instead of reacting defensively when something moves off course, ask:

What are we learning?

Instead of immediately explaining why a miss happened, ask:

What do we believe caused it?

Instead of treating disagreement as resistance, ask:

What does someone else see that we may not?

Instead of personally solving every issue, ask:

Who should own the decision?

Those questions send a signal.

The leadership team learns that challenging the current operating reality does not mean challenging the mission.

That distinction creates room for much better conversations.

Founder Learning Has to Become Organizational Learning

One of the other themes Castle and I discussed was the importance of learning in exceptional founders.

He described scaling partly as the ability to process massive amounts of information, distill it, surround yourself with great people, and execute on what you learn.

That is an extraordinary founder capability.

It is also insufficient once the organization becomes large enough.

A founder can no longer be the only learning system in the company.

Product is learning something.

Sales is learning something else.

Engineering is encountering constraints.

Finance sees changes in the model.

Customer Success detects patterns in retention.

Marketing sees shifts in acquisition.

The question is whether those observations remain local or become organizational intelligence.

This is why learning loops matter so much as companies scale.

The operating rhythm should continuously collect signals from across the organization, compare them to what leadership believed would happen, create conversations around meaningful differences, make decisions, and then carry those decisions back into execution.

Over time, the organization develops a capability the founder may have originally possessed alone:

the ability to update its understanding of reality quickly.

That is one of the most important transitions from a founder-led company to a scalable organization.

The Board Needs Reality Too

The same principle extends to the board.

Founders understandably want board meetings to go well.

They are speaking with people who invested in their vision and who may influence financing, hiring, strategy, governance, and ultimately the CEO's future.

That can create pressure to package the story.

But boards cannot provide useful governance if they are always operating from a polished version of reality.

The answer is not to dump every organizational problem into the board meeting.

The answer is to provide a coherent operating picture.

What did we expect?

What happened?

What changed?

What are we learning?

What are the major execution risks?

What has management decided to do about them?

A CEO who can present that clearly does not look less capable.

The CEO demonstrates command of the organization.

There is a meaningful difference between saying, "Everything is great," and saying, "Here is where we are off course, here is what we have learned, and here is what we are doing about it."

The latter can be a much stronger form of confidence.

The Best Teams Make Reality Safe to Discuss

Founders will always need to tell stories about the future.

That is part of entrepreneurship.

Castle's own experience captures the difficulty beautifully: confronting overdue bills in one moment and communicating the opportunity to potential investors in the next.

The answer is not to stop selling the vision.

The answer is to ensure that somewhere inside the organization, selling stops.

There has to be a recurring place where the leadership team can stop defending, stop performing, and stop managing the narrative long enough to understand what is actually happening.

That place should not depend on an occasional offsite or a crisis serious enough that everyone finally speaks openly.

It should be built into how the organization operates.

The plan is visible.

The metrics are visible.

The objectives are visible.

Off-course work is surfaced.

Issues have somewhere to go.

Decisions have owners.

The team reviews what happened and learns from it.

That is what an operating rhythm can provide.

The founder can continue creating belief in the future because the organization is continuously developing a better understanding of the present.

Both are necessary.

The pitch creates conviction.

The operating system creates truth.

The strongest founders learn to lead with both.

Related Insights

What Is Peak OS?

What Is Organizational Execution?

What Is Organizational Intelligence?

What Is a Business Operating System?

What Is Operating Rhythm?