Blake Erickson on Scaling a Business Without Becoming Its Ceiling

Blake Erickson was running a business he said had reached roughly $11 million in annual revenue, building a real estate portfolio, operating a media company, recording a podcast, and working on other products when he recognized the problem: he had confused adding things with scaling. He described that realization when I asked about the decision that led him to go all-in with Dr. Benjamin Hardy at Scaling.com (our conversation on Spartan Leadership).

I wanted to understand what made him willing to let go of businesses and commitments he had worked to build, so we talked through his 2024 decision to sell and focus on one direction (watch the conversation). That decision is worth examining before you add another offer, hire another person, or put a bigger number into next year's plan.

You can build a company that depends on more of your effort every year. You can also build one that requires you to think differently, develop stronger people, and surrender responsibilities you have become comfortable owning. The uncomfortable part is that the second path may require you to stop doing things you are good at.

That is the challenge I want you to carry through this conversation. Before asking how your business can get bigger, examine what you are protecting that keeps it dependent on you.

A Bigger Goal Should Change the Decisions You Make Today

Blake organized his approach around three principles: Frame, Floor, and Focus. He described the frame as the future you are operating toward, the floor as the standard required to support that future, and focus as what you choose to pursue and what you filter out (Blake's explanation).

I like the practical demand inside that sequence. A larger goal has little value if your calendar, decisions, and standards remain exactly the same. Writing an ambitious number does not resolve an unclear role or make a weak process dependable.

Blake explained that Scaling.com began with a goal of reaching $120 million in annual recurring revenue within three years, describing the goal as a tool for changing the team's thinking and decisions rather than a result they had already achieved (our conversation). That distinction matters. An aspiration should not be presented as an accomplishment, and a bold target should never become an excuse to ignore financial reality.

The useful question is what the goal forces you to reconsider. Would you still sell the same mix of services? Would you keep making every meaningful hiring decision yourself? Would you continue trying to become competent at work someone else already does exceptionally well?

In the episode, I pointed out the value of asking forward-looking “what if” questions instead of using them to punish yourself for past decisions (that exchange with Blake). What if you recruited an operator who had already led a company through the stage you are approaching? What if one distribution partnership deserved more attention than five separate initiatives?

Those questions give you something to investigate. They do not obligate you to make a reckless hire or spend money you cannot afford. They expose assumptions you may have mistaken for permanent constraints.

Start with a defined future and a deadline. Then identify one decision you would make differently if you took that future seriously. A goal begins to serve you when it changes the quality of the work you do this week.

Raising the Standard Requires Humility About Your Own Role

When Blake discussed the people and systems required at a larger scale, I stopped to clarify something: growth does not automatically mean firing the people who helped you build the company (our discussion about talent). I wanted that point to be unmistakable. Ambition does not excuse careless leadership.

Blake agreed and described how people inside his organization had moved into different seats as the business changed, with humility about fit as the underlying principle (Blake's response). A role can change. Its responsibilities can expand. A person may need development, a different assignment, or support from someone with experience they do not yet have.

I want founders to apply that same scrutiny to themselves. It is easy to announce that everyone else needs to grow. It is harder to acknowledge that your own preferences may be shaping an organization around what keeps you comfortable.

If you insist on approving every decision, you have designed a business around your availability. If you hire people who never challenge your thinking, you have reduced the chances that someone will identify a mistake before it becomes expensive. If your standards disappear whenever a conversation becomes uncomfortable, the team has learned which standards are real.

During the conversation, I shared how my integrator challenges my ideas, distinguishing what is useful, what cannot be acted on yet, and what should not move forward (my example from the episode). That kind of honesty is valuable. A capable person who disagrees with you can protect the business from your enthusiasm.

The floor you set has to include your behavior. Give people clear expectations before judging their performance. Distinguish between a lack of ability and a lack of direction. Provide feedback while there is still time to use it.

Then make the decision the evidence supports. Respect for a person and honesty about a role belong in the same conversation. Avoiding that conversation can leave both the individual and the business stuck.

Before deciding who needs to change seats, ask where you have failed to define the seat. Then ask whether you are willing to let a qualified person lead it differently than you would.

Every Responsibility You Take Back Has a Future Cost

Blake offered a practical way to diagnose founder dependence: examine how many decisions happen without you, how often work gets completed without your follow-up, and whom you can trust to own a role without your involvement (his diagnostic questions). Those questions are more useful than a vague promise to delegate better. They reveal where ownership actually lives.

I shared an example of an entrepreneur who found himself handling plumbing work at a property because he knew how to do it, then connected that habit to the development opportunities owners take away when they repeatedly step in (the example in our conversation). The task can be small while the pattern is significant. Knowing how to do something does not settle whether you should be the person doing it.

Your ability can become a convenient excuse. You tell yourself the handoff takes too long. You know exactly how you want the result. You can finish it before anyone else understands the problem.

That reasoning might win this afternoon and leave next month unchanged. When you repeatedly rescue a responsibility, the person assigned to it never gets to experience full ownership. You stay busy, they stay dependent, and both of you become frustrated.

I also shared the four responsibilities a mentor gave me while I was running my financial firm: recruit great talent, develop that talent, build a strong culture, and run strong financials (my account in the episode). I kept those responsibilities on a note near my computer as a filter for requests that came my way (the same discussion).

That filter still gives a founder something concrete to work with. Look at the last five problems you personally absorbed. Which genuinely required your authority or judgment? Which could have become an opportunity to clarify ownership?

Responsible delegation needs boundaries. Define the result, the decisions the person can make, the budget or risk limits, and the point at which they should escalate. Agree on a review date instead of interrupting the work every time you become anxious.

You still owe people development and accountability. Handing over responsibility without clarity creates confusion, while handing it over and continuously taking it back teaches people to wait for you. Give a capable person a complete assignment and enough authority to carry it.

Going All-In Requires a Reason Stronger Than Restlessness

Blake's decision to focus on Scaling.com followed a relationship with Ben Hardy that began at a conference in 2021 and developed through continued conversations (Blake's account of their partnership). His story was not simply about making a dramatic exit. He described confidence in the work, existing leverage, and an opportunity to serve people in an area he wanted to pursue for the long term (his explanation of the decision).

That is an important distinction for anyone tempted to imitate the headline. Selling everything is not a universal prescription. Neither is keeping every commitment because you once worked hard to create it.

I want you to examine the reason underneath the move. Are you moving toward a purpose you can articulate, or trying to escape the ordinary difficulty of your current responsibilities? Have you evaluated the opportunity, or are you simply tired?

Conviction deserves due diligence. Talk through the financial implications. Consider the people affected. Establish what must be true before you proceed and what would tell you your assumptions were wrong.

Our conversation also moved into faith, where Blake described his business as a means of serving God and explained that his beliefs and his work could be integrated (our discussion of faith and business). That connects directly to the Spiritual Bridge. Your purpose should influence the way you build, the commitments you honor, and the opportunities you decline.

I do not want a founder to interpret “all-in” as permission to give the business every part of their life. A business goal should be evaluated alongside the responsibilities you have to your family, your health, your faith, and the people who rely on you.

The Five Bridges of Kairos give that evaluation a structure: Spiritual, Internal, Relationships, Environment, and Legacy. A plan that acknowledges all five can ask more of you than a revenue target alone. It asks whether the success you are pursuing is consistent with the life you say you want.

Name the work you want to commit to. Name what that commitment will require you to stop. Then name what you refuse to sacrifice in the process. Those decisions belong together.

Lasting Change Has to Survive an Ordinary Week

At the end of the episode, Blake offered his unpopular belief that people can change but rarely sustain the change, and I responded that I have changed and have seen others change while acknowledging the work it requires (our closing exchange). I think that tension is worth keeping. Belief in someone's capacity should be accompanied by honest attention to their behavior.

It applies to the founder as much as the team. You can leave a conversation convinced you will delegate, simplify, or stop chasing every opportunity. The test arrives when an employee makes a decision you would have made differently or an attractive opportunity competes with the priority you already chose.

That is where your commitment becomes observable. Do you coach the person or take the responsibility back? Do you evaluate the opportunity against your criteria or abandon those criteria because the idea feels exciting?

Choose a change small enough to observe and important enough to matter. Decide what evidence you will review in thirty days. Ask someone who sees your behavior clearly to tell you when you return to the old pattern.

I want this conversation to produce more than agreement. Let it lead to one ownership decision, one clearer standard, or one commitment you are prepared to stop carrying. Give that decision a place in your week and someone who can hold you to it.

Action Items From This Conversation

1. Write a future that changes a present decision. Choose a meaningful business outcome and a deadline. Under the Internal Bridge, identify the assumption about your own capacity that you need to examine. List three options you have not seriously investigated.

1. Audit the responsibilities you still own. List your recurring roles, then choose one complete responsibility to transfer. Use the Environment Bridge to document the result, decision authority, boundaries, and review date before the handoff.

1. Clarify one seat before judging its occupant. Write down what the business needs from that role now. Under the Relationships Bridge, have an honest conversation about expectations, support, development, and fit, including your own contribution to the problem.

1. Remove one competing commitment. Identify an initiative that consumes attention without supporting the future you chose. Connect the decision to the Spiritual Bridge by explaining what meaningful work that attention will serve instead. End, pause, or delegate the commitment responsibly.

1. Review behavior in thirty days. Choose one trusted person to check whether you have actually honored the handoff or boundary. Use the Legacy Bridge to ask whether your actions are developing people who can lead without your constant intervention.

Five Bridges Challenges

• Spiritual: Write one sentence explaining whom your business exists to serve and why that matters to you. Which current commitment conflicts with that purpose, and what will you do about it this week?

• Internal: Identify a responsibility you keep because being needed makes you feel valuable. What would a secure, disciplined version of you do to help someone else own it?

• Relationships: Ask one capable person, “Where do I make it harder for you to take ownership?” Listen without defending yourself, then agree on one specific change you will make.

Inspire & Impact, Josh