Expansion should pause when the board cannot describe one customer in the company’s strongest market with enough detail to explain why they buy, renew and refer others. A growth plan built above that gap usually scales assumptions faster than revenue.
At 4:18 p.m. in a boardroom in Accra, Kojo had one slide left and six months of runway. He is a composite founder, drawn from a pattern I have seen across early-stage African software companies: a small team, early revenue and pressure to turn one working market into a regional story.
The investor across from him wanted three new countries added to the plan. The logic sounded reasonable. The product was live. Revenue had started to move. Competitors were announcing expansion. If Kojo waited, someone else might take the ground first.
Kojo closed the presentation and asked, “Can you describe one customer in Ghana who would be genuinely upset if we disappeared next month?”
Nobody answered.
The silence exposed a customer knowledge gap
The investor could describe the market. He knew the broad customer category, the estimated opportunity and the countries that looked attractive on a map.
He could not describe the person making the buying decision.
Kojo asked again, more specifically. What happened during that customer’s week before they bought? Which task kept failing? Who approved the spend? What did they stop paying for after choosing this product? Which part of the product would they defend during a budget review?
The room stayed quiet.
That silence did not prove expansion was wrong. It showed that the company had not yet explained why its strongest market worked. Opening in another country would add sales calls, payment questions, support demands and local buying habits before the team understood the demand already in front of it.
The bad ending was now clear. Kojo could follow the board’s recommendation, spread his team across four markets and reach the next fundraising conversation with more activity but no market he could explain. If revenue softened, nobody would know whether the problem was the product, the positioning, the sales process or the expansion itself.
Six months of runway could disappear inside that ambiguity.
Market strength lives in specific buying decisions
Founders often describe a strong market through totals: active accounts, monthly revenue, pipeline value or inbound leads. Those numbers matter. They still leave a harder question unanswered.
Why did this particular customer choose you now?
A useful customer description contains a decision, not a demographic. “A logistics company in Ghana” gives the team little to work with. “An operations lead who still checks every delivery exception manually on Friday afternoon because one missed update could cost the next contract” gives product, sales and onboarding teams something concrete.
The difference becomes important when AI or automation sits inside the product. A capable demo can attract attention across several markets. Attention does not tell you which workflow has enough pain, frequency and budget to support a company.
I keep coming back to the operational detail. Who notices the problem first? What happens if they ignore it? What workaround are they already using? Who has authority to replace that workaround?
That same discipline appears in the procurement workflow where one incomplete supplier record changed the trust decision. The product question only became clear when the failure was traced to the person expected to act on the output.
Expansion should carry a known pattern into a new market
Kojo returned to the whiteboard with less than an hour left in the meeting. Instead of debating countries, he wrote down the company’s best-understood customer.
The customer managed a recurring operational process. The existing method depended on spreadsheets, messages and one experienced employee remembering what needed attention. The buyer paid because a missed step threatened revenue and customer trust. The product earned its place when it made the next action visible without asking the team to rebuild its entire process.
That description changed the expansion discussion.
The board could now ask which new market contained buyers with the same problem, purchasing authority and urgency. It could examine where the pattern changed. Perhaps approval sat with a different role. Perhaps the current integration mattered less. Perhaps the pain existed, but buyers solved it through a service provider rather than software.
This is a stronger expansion test than placing flags beside large market estimates. It also protects a small team from mistaking geographic activity for learning.
The same risk appears when a company moves toward the US because the slide looks convincing before a buyer has confirmed the assumptions. I explored that tension in the US expansion plan built on unconfirmed buyer behaviour.
The next board pack began with one customer
Kojo did not leave the meeting with approval for three launches. He left with a narrower assignment: interview recent buyers and lost prospects, identify the repeated buying situation, then choose one expansion market where that situation could be tested without splitting the company.
The board asked for a market-entry plan after that work.
On Monday morning, Kojo removed the regional map from the opening section of the next board pack. In its place, he put one customer, one recurring problem, the current workaround, the buying trigger and the reason the product survived budget scrutiny.
Only then did he add a second market.
Before your next expansion discussion, try the same test. Put the map away. Ask everyone in the room to describe one customer whose decision they understand from the first sign of pain to the payment. If the descriptions conflict, that disagreement is the work.
Comments
No comments yet.