Expansion stops making sense when the plan depends on repeating a result nobody has explained. Before adding three countries, a founder should know why customers in the current market renew, what they would miss if the product disappeared, and which parts of that value can survive a new context.
In 2003, LEGO was losing money after years of expansion into new products, themes and businesses. The company had moved far beyond the plastic brick, but management could not clearly see which experiments created durable customer value and which consumed cash.
The outcome was uncertain. LEGO had a famous brand and products sold around the world, yet those advantages had not protected the business from a deep financial crisis.
LEGO had expanded beyond what it understood
Jørgen Vig Knudstorp became LEGO’s chief executive in 2004. His task was not to find another exciting direction. He first had to establish what the company was good at, which products earned money, and why children and parents kept choosing LEGO.
David Robertson and Bill Breen document the turnaround in Brick by Brick. Their account shows a company that had pursued growth through theme parks, clothing, media projects and increasingly complex product lines while losing control of costs and drifting from the play system customers valued.
Expansion had created activity without enough understanding.
Knudstorp’s response included cutting costs, reducing complexity and returning attention to the core construction system. LEGO did not abandon new ideas. It imposed a harder condition on them: new products had to connect to a reason customers already chose LEGO.
That distinction matters for a founder leaving an investor call with three new countries written in a notebook. The investor may have asked about market size, hiring and speed. The more important question may have arrived quietly that same morning, when customers in Accra renewed.
Why did they renew?
A renewal contains more information than a market map
A country can look attractive on a slide because it has a large business population, rising software adoption or familiar customer problems. None of that establishes that the current product has found a repeatable reason to exist.
A renewal gets closer.
Perhaps the Accra customers renewed because the product removed a manual step from a weekly process. Perhaps one employee had become the internal champion. Perhaps support from the founder compensated for gaps in the product. Perhaps leaving would require rebuilding records elsewhere.
Those explanations lead to different expansion decisions. A workflow advantage may travel. Founder-led support probably will not. A customer who remains because switching feels difficult provides weaker evidence than one who would actively recommend the product.
This is why I would delay the country decision long enough to examine the renewals. I would speak with the renewing customers and ask about the last time they used the product, the task they completed, the alternative they considered, and what would happen if access ended next week.
I would also inspect the uncomfortable cases: the customer who reduced usage, the buyer who renewed after repeated follow-up, and the account where one person uses the product while the rest of the team ignores it. Those cases can reveal whether retention comes from product value, sales effort or inertia.
This is the same evidence problem behind Kojo’s customer knowledge gap. Runway becomes fragile when a founder commits capital before understanding the customer decision beneath the revenue.
Three countries create three new explanations
Entering Nigeria, South Africa and Germany would add more than geography. Each market could change how buyers discover the product, who approves it, what support they expect, how they pay and which alternatives they compare.
The product may still work. The sales motion may not.
A founder with limited runway therefore needs a portable explanation of value before building a regional plan. I would write the explanation in one sentence using evidence from actual renewals:
“Customers renew because the product helps this person complete this recurring task with less cost, delay or risk than their current alternative.”
If the sentence requires several caveats, the evidence is still local. If it depends on the founder joining every onboarding call, the operating model has not become repeatable. If different customers give unrelated reasons, the company may be serving several small use cases rather than one expandable market.
That does not forbid expansion. It changes the next move from launching in three countries to testing one assumption in one country.
The test might be a small set of sales conversations, a paid pilot with clear boundaries, or a waiting list built around the specific job Accra customers already pay to complete. The goal is evidence before fixed costs. Kwame’s approach to a pilot contract applies the same discipline: learn without allowing the opportunity to rewrite the whole company.
Put the renewal call before the expansion meeting
LEGO’s recovery did not come from refusing growth. Knudstorp’s team rebuilt the company around a clearer understanding of the core system, then pursued innovation with tighter financial and customer constraints. The brick became a boundary for deciding what belonged.
A founder can create the same boundary before Monday.
Call the Accra customers who renewed on Friday. Record the task they hired the product to do, the moment they would notice its absence, and the parts of the experience that depended on personal help. Compare those answers before approving a country, recruiter or launch date.
The expansion decision can wait for that evidence. Three new markets will still be there after the founder understands the one already paying.
Comments
No comments yet.