I deleted the slide because “Africa is a huge opportunity” told the audience nothing about what a buyer would pay to fix. I replaced it with one costly workflow a buyer in Kigali could describe from memory, including where it broke and what happened next.
An hour before the Innovate Africa panel, I was looking at a map of the continent on my laptop. The slide had market language, arrows and the kind of ambition that survives because nobody can test it during a short panel discussion.
Then I thought about Emmanuel, an invented composite of the buyers founders often meet in Kigali. He runs operations for a growing distribution company, keeps his phone on silent during meetings and still checks it whenever the warehouse team calls.
That morning, he was holding a printed order sheet beside his laptop. A customer had changed a delivery after the sales team recorded it. The warehouse was working from an earlier message. Finance had already prepared an invoice using the first quantity.
The truck could leave with the wrong order. If it did, Emmanuel would have to explain the return, the wasted trip and the delayed payment.
For one beat, there was no safe outcome. Stopping the truck would delay every delivery behind it. Letting it leave could turn one mismatched message into a lost customer.
The map was hiding the buying decision
The deleted slide made the opportunity look large. It did not make the purchase feel necessary.
A continent-sized market can support an investor conversation. A buyer still has to decide whether your product deserves attention this week, while payroll, customer complaints and unfinished work compete for the same budget.
Emmanuel would not describe his problem as “fragmented operational infrastructure across an emerging market.” He would say, “Sales changed the order, the warehouse did not see it, and now I need to know which version is correct.”
That sentence contains more product direction than the map.
It identifies the people involved, the information that moved, the point of failure and the consequence. A founder can investigate that. You can ask how often it happens, what Emmanuel checks before stopping a truck and who pays when the mistake reaches the customer.
“Large opportunity” gives you nowhere to start.
One workflow gives the product edges
I replaced the map with the order-change workflow.
The revised slide followed a single piece of information. A customer changes an order. Sales records the change. The warehouse needs the current version. Finance needs the same quantity before issuing the invoice. Operations needs proof that each handoff happened.
Now the product had edges.
It did not need to become a general system for every company operating across Africa. It needed to make one change visible to the people who could act on it before the truck left.
That narrower description also exposed the difficult questions. What happens when connectivity drops? Can a team member confirm a change from a phone? Which record wins when two people edit the order? Does the buyer need automation, or would a clearer approval step solve most of the problem?
Those questions are less impressive on a conference slide. They are far more useful when runway is limited.
I have seen the same mistake while building AI and automation products. A demo can summarize documents, classify requests and trigger actions, yet still fail because nobody decided what should happen when the data is incomplete. The real work begins where the smooth demonstration ends.
That is also why making the cash step visible matters. A product becomes easier to evaluate when the buyer can see the exact point where money, responsibility or risk changes hands.
The smaller story carried more authority
On the panel, the workflow gave me something concrete to defend.
I could explain why the order change mattered. I could point to the decision the product needed to support. I could admit what remained unresolved, including conflicting edits and the temptation to automate before understanding who had authority to approve the final version.
That honesty made the argument stronger.
Founders sometimes widen the story when they feel pressure to sound ambitious. They add countries, sectors and future capabilities. The pitch grows while the buying reason disappears.
A buyer in Kigali, Accra, Lagos, Berlin or Atlanta rarely begins with your total market. They begin with the failure they are tired of paying for. The local details will differ, but the test stays useful: can one person describe the broken moment without borrowing your product language?
If they can, you may have a problem worth building around. If they cannot, another market-size slide will not create one.
Start with the call that could go wrong
Emmanuel stops the truck.
He asks sales to confirm the revised quantity, sends the approved change to the warehouse and tells finance to hold the invoice until the records match. The product opportunity sits inside that tense interval, between discovering the mismatch and making a decision everyone can trust.
The next morning, his team does not need a speech about digital transformation. They need one current order, one visible approval and fewer calls asking which message is correct.
Before your next pitch, open the slide with the largest claim and try deleting it. Replace it with a named buyer, one broken workflow and the specific loss that remains possible if nobody fixes it in time.
Then see whether the product still matters.
Comments
No comments yet.