Principles

Scaling sounds like the natural next step for every company.

Once the product is ready, you need to find more customers. As the customer base grows, you need to hire more people. Once the domestic market is working, you need to expand abroad. As sales grow, you need to invest in marketing, automation, and management.

But scaling is not simply about getting bigger.

Scaling means replicating a working model in a way that allows the value created to grow faster than the cost and complexity required to create it.

For that to happen, a company must have something that can actually be replicated.

If the model does not work, scaling will not make it better. It will spread the flaw to more customers, increase costs, and make it harder to correct the wrong direction.

That is why a company’s first question should not be: “How can we scale faster?”

It should first ask: “Do we already have something worth scaling?”

Scaling is not a way to fix problems

Companies often start scaling too early because growth seems like the solution to almost every problem.

When money is tight, they look for more customers.

When profits are low, they hope greater volume will help.

When the team is overloaded, they hire more people.

When sales are unstable, they increase the marketing budget.

When the domestic market does not work out, they try entering a new market.

But more customers do not fix poor unit economics.

More employees do not fix unclear accountability.

A larger marketing budget does not fix a weak value proposition.

A new market does not solve a problem the company has been unable to solve in its existing market.

Scaling is an amplifier.

It magnifies both a company’s strengths and its flaws at the same time.

That is why, before scaling, a company must fix whatever greater volume would replicate.

A company should not scale before the customer problem has been validated

A customer may buy a product for many different reasons.

They may know the founder. They may want to try something new. The price may be exceptionally attractive. The solution may have been tailored specifically to them. The sales pitch may be highly persuasive.

A handful of deals does not yet prove that the company is solving a sufficiently important and recurring problem.

Before scaling, the company must know:

- what problem actually compels the customer to act; - how costly it is to leave that problem unsolved; - why the existing alternatives are not good enough; - who feels the problem most acutely; - who makes the purchasing decision; - what makes the customer trust the company’s solution; - what outcome the customer is actually paying for.

If there are no clear answers to these questions, the company is most likely scaling an assumption.

It can put more money into marketing, but that will not make a vague problem more important. It can hire more salespeople, but they cannot consistently sell a solution when the reason to buy it is unclear.

First, the problem must be validated.

Only then can sales of the solution be scaled.

A company should not scale when the right customer is unclear

Not every paying customer is a good customer for the company.

Some customers buy quickly but later require a disproportionate amount of support. Some generate substantial revenue but make so many special requests that serving them becomes unprofitable. Some are a good fit for the product but are too expensive to acquire.

If a company has not decided which customer it creates the most value for, scaling will start bringing in every kind of customer.

Sales celebrates the revenue. Marketing reports a growing number of enquiries. Management sees the customer base expanding.

At the same time, the company’s internal complexity begins to grow.

Different customers want different features, pricing, service, contracts, and workflows. The product moves in several directions. The team cannot decide which customer need matters and which does not.

The company begins adapting its model to customers the model was never designed for.

The goal should not be simply to scale the number of customers.

The goal should be to scale the ability to find, sell to, and serve the right customer.

A company should not scale when every sale depends on the founder

A founder can often sell before the company has a genuine sales model.

They know the product, the market, and the customer’s problem better than anyone. During a meeting, they can change the offer, make quick exceptions, and draw on their personal credibility.

This can produce good results.

But the founder’s ability to sell and the company’s ability to sell are not the same thing.

A sales model becomes repeatable only when other people can also:

- find a suitable customer; - capture the customer’s attention; - understand their real problem; - present the right value proposition; - address the main objections; - reach a decision within a reasonable time; - do all this without the founder’s constant involvement.

If every important deal still requires the founder, rapidly expanding the sales team makes little sense.

New salespeople will bring the founder more meetings, questions, and proposals that need their help to close.

The company is not scaling sales.

It is scaling its dependence on the founder.

A company should not scale when every new customer needs a new solution

If serving every customer starts from scratch, the company does not yet have a scalable service or product.

It has a project-based ability to solve problems.

That can be a highly valuable and profitable business. But it cannot be scaled in the same way as a standardised product or service.

Before scaling, the company must distinguish:

- which part of the solution is common to all customers; - which part depends on the customer’s specific circumstances; - which exceptions it is willing to make; - which exceptions make a customer unprofitable; - which stages of the work can be standardised; - what can be automated; - what knowledge still exists only in the minds of a few people.

If every new customer adds new features, processes, and manual work, the company’s complexity will grow faster than its revenue.

At some point, no one will know what the company’s actual product is.

Sales sells one thing. Customers expect another. Product development builds a third. Operations tries to keep every version running at once.

That kind of model should not be scaled.

It must first be clarified.

A company should not scale when the unit economics do not work

If a company does not know how much it costs to acquire and serve one customer, it also does not know whether growth creates or destroys value.

Revenue growth can conceal very poor economics.

A company may spend more to acquire a customer than that customer will generate over the entire relationship. The price of the service may cover the direct work but not sales, management, development, customer support, and fixing mistakes.

Founders may work without drawing a market-rate salary and use that to regard the service as profitable.

Scaling introduces real costs:

- sales salaries; - marketing; - middle management; - support functions; - technology; - quality control; - recruitment; - onboarding; - financing.

If the model works only in a small company where the founder performs several roles for free, it may not work at all at greater scale.

A company should not scale until it understands at least:

- the true cost of customer acquisition; - the total cost of serving a customer; - gross margin; - customer payback period; - customer lifetime value; - the impact of cancellation or churn; - the cash requirements created by growth.

If every new customer generates a loss, greater volume will not save the company.

It will simply run out of money faster.

A company should not scale when customers do not stay

Acquiring new customers can create the impression that the company has found a working model.

But if existing customers leave, the problem may not be sales volume.

The problem may be the value being created.

Customer churn, low usage, a lack of repeat purchases, or a constant need for discounts all suggest that the solution may not be important enough, well executed enough, or positioned correctly.

If a company scales sales before fixing retention, it creates a leaky system.

At one end, it pays heavily to bring in new customers. At the other, existing customers leave.

Revenue may grow for a while because new customers arrive faster than old ones leave. But growth becomes increasingly expensive. Marketing must continually replace lost customers before it can generate genuine growth.

Before scaling, there must be clear evidence that the customer receives the promised value.

A purchase alone is not a good sign.

A good sign is that the customer uses the solution, achieves the outcome, stays with the company, and recommends it to others.

A company should not scale when quality depends on heroic effort

Sometimes a company works only because a few people put in an unreasonable amount of effort.

The founder corrects other people’s work in the evenings. The most experienced specialist handles every difficult case. Project managers keep information in personal spreadsheets. The best customer support agent knows every exception by heart.

From the outside, the company may appear to work very well.

In reality, quality rests on the memory, energy, and sense of responsibility of a few individuals.

When such a company scales, the workload grows, but the time available to those key people does not.

Eventually, they can no longer prevent, review, or fix every problem. Quality falls sharply, and management may feel that the problem appeared overnight.

In reality, the problem was there from the beginning.

Low volume simply concealed it.

Before scaling, quality must come from the system:

- clear standards; - effective processes; - visible accountability; - suitable tools; - staff training; - rapid feedback; - addressing the root causes of mistakes.

Heroic effort may help a company survive a crisis.

It cannot serve as a scaling model.

A company should not scale when accountability is unclear

In a small team, people can solve many problems through direct communication.

If something is left undone, they ask the person sitting next to them. If a decision must be made quickly, they go to the founder. If accountability is unclear, someone more proactive takes it on.

That no longer works in a larger company.

When accountability and decision rights are unclear, every new person increases the need for coordination.

There are more meetings, more rounds of approval, and more work that no one can clearly identify an owner for.

People may be busy, but important outcomes remain unachieved.

Before scaling, the company must be clear about:

- who is accountable for each outcome; - which decisions they can make independently; - which resources they have at their disposal; - how the outcome is measured; - when an issue must be escalated; - who resolves cross-functional conflict.

If accountability cannot be assigned to one person or a clearly defined role, more people should not be added to that work.

More people do not automatically create more accountability.

In a poor system, they dilute it.

A company should not scale when the wrong people are in the wrong roles

Scaling places greater demands on both employees and leaders.

A role someone could handle with ten employees and twenty customers may require an entirely different set of capabilities with a hundred employees and a thousand customers.

A good specialist may not be a good manager. A versatile early-stage problem solver may not be suited to running a standardised process. A strong salesperson may not know how to build a sales team.

This does not mean the person has become less capable.

The company’s needs have changed.

Before scaling, management must honestly assess:

- which capabilities the next phase of growth requires; - who can grow into the next phase with the company; - whose role needs to change; - which competencies are missing; - which leaders can genuinely carry accountability; - which critical outcomes depend on the wrong person.

If the company scales before making these decisions, today’s small mismatches become tomorrow’s major bottlenecks.

The wrong person in a critical role does not limit only their own performance.

They limit the performance of everyone who depends on them.

A company should not scale when its leader cannot let go of control

Scaling changes the CEO’s role.

The leader can no longer personally be the company’s best salesperson, chief product manager, direct supervisor of every employee, and final resolver of every problem.

If every important decision has to pass through the CEO, the company will never scale beyond the CEO’s capacity to make decisions.

Hiring more people does not reduce dependence on the leader if those people are not genuinely given the authority to decide.

Then every new hire brings the leader more:

- questions; - approvals; - meetings; - reports; - conflicts; - decisions.

The company grows in headcount, but its decision-making capacity remains unchanged.

Before scaling, the leader must be willing to:

- hand over activities; - hand over some decisions; - accept different ways of working; - evaluate outcomes rather than adherence to their own method; - allow people to make recoverable mistakes; - focus on the company’s system rather than individual problems.

If a leader wants a larger company while retaining the same degree of personal control, they want two contradictory things.

A company can grow beyond its leader only if the leader allows it to depend less on them.

A company should not scale when it lacks the money to do so

Scaling usually requires money before it begins to generate a return.

The company must hire people, build capabilities, purchase marketing, develop the product, and finance customer delivery.

If growth costs arise immediately but sales revenue arrives later, the need for working capital increases.

It is therefore not enough to ask whether scaling could eventually be profitable.

The company must know whether it can survive until then.

Before scaling, it must be clear:

- how much money growth requires; - when the money will be spent; - when the investment will begin to pay back; - how much slower growth might be; - what happens if sales do not go to plan; - which costs are reversible; - when growth must be halted; - how much of a buffer remains for correcting mistakes.

A scaling plan that works only if everything goes right is not a plan.

It is wishful thinking.

A company should not scale simply because an investor or the market expects it to

Not every company needs to grow according to the same logic.

A venture-backed technology company may aim to capture the market quickly, even if doing so requires temporary losses and substantial capital.

A bootstrapped company may prioritise profitability, controlled growth, and the owners’ long-term freedom.

A service company may increase value through better customers, higher prices, and more efficient work without multiplying its headcount.

None of these models is inherently better.

The problem arises when a company copies someone else’s growth model without understanding what kind of company it wants to build.

Headcount, capital raised, and rapid market expansion are not measures of success in themselves.

They are tools.

Before scaling, management must decide:

- what kind of growth it actually wants; - over what timeframe; - with what level of risk; - how much control it is prepared to relinquish; - what kind of capital this requires; - what kind of company this will create; - whether the owners even want to run that kind of company.

If these questions have not been answered, a company may achieve substantial growth only to discover later that it has built something no one actually wanted.

When is a company ready to scale?

A company does not need to be perfect before it scales.

Not every process needs to be final and not every risk needs to be eliminated. Scaling itself will always reveal new problems.

But the company must have enough evidence that its underlying logic works.

A company that is ready to scale can answer at least the following questions:

- Who is our right customer? - What important problem do we solve for them? - Why do they choose us over the alternatives? - Are sales repeatable without the founder? - Does the customer achieve the promised outcome? - Does the customer stay and buy again? - Does each new customer create economic value for the company? - Is delivery of the service or product sufficiently standardised? - Can quality be maintained at greater volume? - Do critical processes work without heroic intervention? - Are accountability and decision rights clear? - Are the right people in the right roles? - Can the management model support a larger organisation? - Does the company have enough money and a sufficient buffer to finance growth? - Does management know which metrics would trigger a halt to growth or a change in direction?

If the answers are based on hope, a single success story, or the founder’s personal capabilities, the model is not yet ready to scale.

Not everything that can be scaled should be scaled

The purpose of scaling is not simply to make the company bigger.

The goal is to increase the company’s ability to create value without cost, complexity, and management workload growing at the same rate.

If every new customer requires the same amount of new manual work, the model does not scale.

If every new employee creates more work for the leader, management does not scale.

If every additional euro of revenue increases the cash shortfall, the economics do not scale.

If quality still depends on a few individuals, the company’s capabilities do not scale.

Before scaling, a company does not need to prove that everything always works.

It must prove that it understands why something works, can repeat it, and can quickly detect when it stops working.

A working system is worth scaling.

Confusion must be reduced first.

Because the greatest problem facing a company moving in the wrong direction is not that it is moving too slowly.

The greatest danger is giving it more money, people, and speed.

Mikk OrglaanChalleng.ist