Alfred AnyanInsights
← All insights

The Third Polite Refusal Naledi Heard, and What It Almost Cost Her

Contemporary coffee shop interior with coffee menu and brewing equipment.

Photo by Melike B on Pexels

South Africa’s rise in startup rankings is evidence of a stronger ecosystem, but it does not prove that a particular customer will pay for a particular product. For a founder, the useful signal still comes from the moment a prospect must exchange money, time or reputation for the promised result.

On Tuesday morning, Naledi, an invented composite of several early-stage founders I have met, sat in a Johannesburg café with a cold flat white and two browser tabs open. One showed the news that South Africa’s startup ecosystem had grown 31.3% in StartupBlink’s 2026 index, behind only Saudi Arabia and Türkiye among G20 countries. The other held notes from her third customer interview.

The rankings were moving up. Her payment question was going nowhere.

The third polite refusal

Naledi was building an AI tool for small service businesses. It turned scattered voice notes, emails and meeting notes into draft client follow-ups. The demo worked well enough to create the response founders want to hear: “I can see us using this.”

Then she asked what would happen next.

The first prospect wanted to test it after the next busy period. The second asked whether she could send a free version to the team. On Tuesday, the third said the product solved a real problem, then explained that software spending required someone else’s approval.

Naledi asked whether they would introduce her to that person.

There was a pause. The prospect suggested they reconnect later instead.

That pause mattered more than the enthusiasm before it. Three interviews had produced praise, feature requests and no movement toward payment. Naledi had enough runway to keep building for a few months, but the next product decision would consume most of it. She could add the integrations prospects mentioned, or stop and test whether the problem had a buyer attached to it.

If she chose wrong, she would finish a better demo for people who still could not purchase it.

Ecosystem momentum can hide company-level weakness

A rising ecosystem creates real advantages. It can attract attention, talent, capital and more people willing to attempt difficult companies. Founders should welcome that progress.

The danger begins when public momentum becomes private evidence.

Naledi could tell herself that the market was early, buyers needed education and the ecosystem’s growth would eventually carry demand toward her. Each statement might contain some truth. None answered the immediate question: who had enough pain, authority and budget to buy her product now?

I have seen founders make this substitution across African, European and US markets. A market report says a category is growing. A conference room fills up. A LinkedIn post travels further than expected. Those signals reduce the emotional difficulty of continuing, but they do not reduce the commercial uncertainty.

Interest is cheap because agreement carries no consequence. Payment forces a customer to rank the problem against payroll, existing software, internal politics and every other request waiting for approval.

That is why a customer interview should be judged by the decision it produces, a distinction I explored in how Sipho learned to judge meetings by decisions. A compliment describes the conversation. A next step changes the opportunity.

Naledi changed the next question

By Tuesday afternoon, Naledi had removed the integrations from her immediate product plan. She did not abandon the idea or dismiss the three interviews. She changed what the next interview needed to prove.

Instead of asking whether another founder liked the demo, she would ask about the last time a client follow-up was missed. What happened? Who noticed? What did the delay cost? Who could approve a purchase? Which existing expense would this product replace or defend?

Then she would ask for a commitment proportionate to the product’s stage: a paid pilot, a deposit, or a meeting with the person who controlled the budget. The exact amount mattered less than the presence of a real trade-off.

This can feel premature when the product remains rough. Founders often want to earn the right to ask for money by building more first. Limited runway reverses that logic. The less time you have, the earlier you need evidence that somebody will cross a boundary for the result.

That boundary may also expose a different problem. The person feeling the pain may lack purchasing authority. The overseas customer may demand a local hire before signing. The contract may pull the roadmap away from the product you intended to build. Those are harder findings than “people love the idea,” but they are findings you can use.

Wednesday’s smaller plan

The next morning, the rankings were still good news. Naledi simply stopped asking them to answer a company-level question.

She opened a fresh page and wrote down three names: the person with the missed follow-up, the person accountable for the lost client, and the person who could approve spending. Her next five conversations would need to reach all three roles, even if one person held more than one of them.

She also set a stopping condition. If those conversations produced more praise without a paid test or access to a budget owner, she would narrow the customer, change the problem or pause the build. No new integration would be allowed to disguise the missing commitment.

South Africa’s ecosystem can climb while Naledi’s first version fails. Both facts can be true. By Wednesday, she had a plan built for that reality, and one question ready for her next call: “What would have to happen inside your company for money to move?”

Comments

No comments yet.