Why Scaling Gets Harder at $500 Million

Listen to an AI audio recording of this newsletter

I was out in the Pacific Northwest speaking to the executive team of a fast-growing consumer products company.

The company had brought together its leaders not just from the United States, but from Japan and Europe. It was only the second time leaders from the entire organization had been in the same room together.

There was an energy in the room that I have learned to recognize.

It is the energy of a company that knows it has something special.

The company had already built a remarkable business. It had created a distinctive category, earned a loyal customer base, and developed a strong identity. Its products were sold around the world, and the company had reached the point where many organizations begin asking the same question: how do we keep growing without becoming harder to run?

Most companies do not fail because they cannot start. They fail because they cannot scale.

Before my trip out to Oregon, I ordered a pair of the company’s shoes and wore them on stage that day.

I wanted to experience the product myself. And, frankly, I wanted to remind myself of something important: great companies are usually built around a product or service that solves a clear job for the customer.

The challenge is that the systems that help a company get to, say, $500 million are rarely the same systems that will get it to $2 billion.

At a smaller scale, a business can rely on heroics. A few exceptional people know how everything works. Teams coordinate informally. Problems are solved through conversations, workarounds, and institutional memory.

But as a company grows, that approach breaks.

The temptation is to respond by creating more complexity.

A new customer channel? Create a new team. A new geography? Create a new process. A new product line? Write another SOP.

Over time, the company becomes an organization chart built on top of an organization chart. Every new opportunity requires a new layer. Every new layer creates more meetings, more approvals, and more friction.

The company grows, but the business becomes less scalable.

The Paradox of Scale

This is the paradox of scale.

You need more complexity, but not too much.

You need enough structure to support growth, but not so much that the structure itself becomes the thing slowing growth down.

Measuring Your Scale Quotient

I often think about this through what I call a company’s Scale Quotient: its ability to add revenue faster than it adds cost and complexity.

A high-Scale-Quotient company can add revenue faster than it adds cost and complexity.

A low-Scale-Quotient company grows by adding people, processes, and exceptions at the same rate as revenue.

The critical question is simple: Is this truly scalable?

And the answer is only yes if it becomes cheaper, simpler, or easier to do more of it.

If every new customer requires a new custom workflow, it is not scalable. If every new market requires a completely different operating model, it is not scalable. If every new channel requires an entirely new SOP, it is not scalable.

One of the leaders in the room described the challenge perfectly. As the company expands into new channels, new regions, and new customer segments, there is a constant temptation to create channel-specific rules, region-specific systems, and product-specific processes.

The logic seems sound in the moment. Japan is different. Europe is different. Wholesale is different from direct-to-consumer. E-commerce is different from retail.

All of that is true.

But if you respond to every difference with a new process, eventually you create a company that cannot move.

Start With the Job To Be Done

The better question is: what is the Job To Be Done?

What is the underlying need the system exists to serve?

If you can identify that job clearly, you can design a system flexible enough to handle future growth without needing to be rebuilt each time.

For example, the job is not “create an SOP for selling through a new channel.”

The job is “create a repeatable way to introduce our products into any new channel.”

That subtle shift matters.

Because once you define the job at the right level, you can design for reuse.

The same is true with geography. The goal is not to build a separate process for Germany, Japan, or France. It is to create a global operating system that can flex to local needs without being reinvented every time.

The best scaling companies build modularity.

They create a common core and flexible edges.

Common Core and Flexible Edges

​Apple​ is one of the best examples.

Apple sells essentially the same iPhone, MacBook, and iPad around the world. There is not one iPad for the United States and a completely different one for Germany.

The company has designed a common global platform. It then makes only the few changes that truly matter: power adapters, language settings, regulatory requirements, and a handful of localized apps or services.

The core stays the same.

The same principle can be seen in ​McDonald’s​. The company does not reinvent its operating system every time it enters a new country. The kitchen layout, supply chain, training model, and restaurant economics remain largely consistent. Then the company layers in local variation where it matters: a Teriyaki Burger in Japan, a McSpicy Paneer in India, or a Croque McDo in France.

Global consistency. Local flexibility.

That is a high Scale Quotient.

Contrast that with companies that build entirely separate systems for every region, customer segment, or acquisition.

I have seen organizations with three CRM systems, four pricing models, six customer service workflows, and different reporting structures in every geography.

At first, it seems customer-centric.

In reality, it creates confusion internally and inconsistency externally.

The customer experiences delays. Employees spend more time navigating the organization than serving the customer.

Complexity becomes a hidden tax.

And hidden taxes are what prevent a company from making the leap from $500 million to $2 billion.

Three Questions Leadership Should Ask

During our conversation, I encouraged the team to think about every new initiative through three questions:

1. What is the Job To Be Done?
2. Are we building a solution for today’s needs or a platform for future needs?
3. If this succeeds and becomes 10 times larger, will delivering 10X require significantly less than 10X complexity?

Those questions can change how leaders think.

Because the biggest mistake growing companies make is designing processes only for today’s needs.

The smarter approach is to build an operating model that can accommodate future channels, markets, and partners before they arrive.

If you know you may one day sell through wholesale, e-commerce, owned retail, marketplaces, and strategic partners, design for that now. If you know you may expand into Asia and Europe, do not hard-code every system based on the United States.

Design for optionality. You cannot scale everything. You have to identify the few things that truly create value and standardize them relentlessly. Then you preserve flexibility only where it matters.

As I looked around the room filled with leaders from three continents, I realized this company is at exactly that moment.

The company has enough momentum, enough product strength, and enough market opportunity to become much larger. In many ways, it already appears to be well on its way. The opportunity now is not to change course, but to ensure the systems beneath that growth are built to support what comes next.

But the next stage of growth will not come from working harder.

It will come from increasing the company’s Scale Quotient. From building systems that can grow without growing more complicated.

From recognizing that scale is not about creating more SOPs. It is about creating the right SOPs.

The ones that allow you to do more tomorrow than you can today, without having to reinvent the company every time you grow.

Learn how to design SOPs that scale by joining ​Outthinker.com​ today.