A market ranking can earn a founder the meeting, but it cannot explain why a customer buys, hesitates or walks away. Investors may use the number to notice a market; they still need the founder to show what is happening inside it.
Consider Lwazi, an illustrative composite founder in Cape Town. At 9:10 on a Thursday morning, he stood beside a borrowed screen in a small meeting room, clicking through a pitch for software that helped independent wholesalers manage orders from regular business customers. His opening slide carried the number everyone had recently discussed: South Africa’s startup ecosystem had grown 31.3% in StartupBlink’s 2026 index, trailing only Saudi Arabia and Türkiye among G20 countries.
The ranking worked. One investor leaned forward and asked about timing. Another wanted to know why South Africa had moved so quickly. Then a third pointed to Lwazi’s customer slide and asked, “Why did the last shop owner stop using it?”
Lwazi had an answer about market size. He had an answer about smartphone adoption. He had no answer about that shop owner.
The number opened a door it could not carry him through
The meeting changed after that question. The ranking had framed South Africa as a market worth watching, but Lwazi was raising money for one company solving one problem for one customer.
He explained that the shop owner had completed onboarding and entered several orders. Usage stopped during the second week. Perhaps the interface had confused her. Perhaps her staff had returned to WhatsApp. Perhaps she had never felt enough pain to change how the shop worked.
Each possibility sounded reasonable. None came from the customer.
The investment was now in doubt. Lwazi needed the money to keep his engineer through the next product cycle. Without it, he would have to pause development or take a contract that had nothing to do with the roadmap. The meeting ended with polite interest and a request to return when he understood the drop-off.
That outcome matters because rankings create a useful form of borrowed attention. They tell outsiders that activity, capital and company formation are moving. They cannot tell an investor why a wholesaler in Cape Town abandoned an order screen on a Wednesday afternoon.
A national ecosystem can rise while a particular customer remains unconvinced. South Africa’s ranking can move faster than a founder’s runway. Both facts can be true at once.
Lwazi went back to the abandoned order
With four days before his follow-up, Lwazi called the shop owner. She answered between deliveries and agreed to walk through the last order she had tried to enter.
The problem appeared before the product tour had properly begun. A regular buyer had changed the quantity after sending the order. The shop owner could correct it in the message thread both parties already used and keep moving. In Lwazi’s product, she feared that changing the entry would leave her staff working from a different total.
She did not describe this as a software problem. She said she could not risk sending the wrong quantity to someone who bought from her every week.
That sentence gave Lwazi more than another data point. It revealed the decision underneath the behaviour. His product asked her to exchange a familiar, visible conversation for a system whose record she did not yet trust. The cost of being wrong was a damaged customer relationship, not a few extra clicks.
I look for this distinction when assessing an AI or SaaS product. A founder may describe the task they automate, while the customer is protecting something larger: cash expected on Friday, a long-standing buyer, a staff member’s confidence or the ability to correct an error without escalating it.
Demand becomes clearer when the founder can name what the customer fears losing.
Evidence starts where the category ends
Lwazi changed the follow-up deck. He kept the ranking, but moved it behind the customer problem. The first slide now described the moment an order changed after it had been recorded and the shop owner had to decide which version her staff could trust.
He also narrowed the next product test. Instead of adding more dashboard features, his team would test whether one buyer and one shop employee could see the same corrected order without returning to the message thread. The question was specific enough to fail.
That matters. A broad market argument tends to absorb bad news. If adoption is weak, the market may be early. If customers leave, perhaps education is needed. A narrow customer claim gives the team less room to hide. Either the corrected order earns trust, or it does not.
The same discipline appears in Ruth’s refusal to validate an AI product before more building. A founder learns more from one clear refusal than from a slide full of general enthusiasm.
Keep the ranking, then earn the next slide
At the follow-up meeting, Lwazi did not pretend one call had proved the business. He said what he had learned, what remained uncertain and what the next test could disprove.
The ranking still had a role. It explained why an investor might pay attention to South Africa now. Lwazi’s customer scene explained why his company might deserve attention within that movement.
For founders, the practical move is simple. Put the market signal in the deck, then ask what question it will trigger. If the answer depends on a customer you have not spoken to, make the call before the meeting.
Lwazi left his final slide unchanged that evening. On the first slide, he replaced the large ranking figure with one corrected order and the relationship that could be lost if the total was wrong.
Comments
No comments yet.