Founders lose investors when a familiar comparison hides the local problem their product solves. The pitch gets stronger when the founder names the missing financial infrastructure, shows its cost, and explains the decision the product makes possible.
At 4:17 p.m. in a small meeting room in Accra, Efua clicked back to the second slide of her demo. She was a composite founder, drawn from patterns I have seen while building and discussing products across African, European and US markets. Her laptop fan was loud enough to fill the pause.
“Think of us as Stripe for Africa,” she had said.
One investor leaned forward. “Which part of Stripe?”
Efua started listing capabilities: collections, payouts, reconciliation, merchant records. Each answer opened another comparison. Was she competing on developer experience? Payment acceptance? Geography? Price? The investor’s questions were reasonable, but they were pulling the conversation away from the decision Efua had built the product to handle.
Her fundraising window was narrowing. If this meeting ended with “interesting, but crowded,” she would have to postpone an engineering hire and tell two prospective customers that the integration date had moved again.
She closed the deck.
The comparison created the wrong test
Efua stopped explaining the category and described a Thursday afternoon instead.
A small distributor had received customer payments through several channels. The operations lead could see money arriving, but could not match every payment to an order, confirm what was available for payout, or give the finance team one reliable total before the working day ended. Three records disagreed. The next stock order depended on knowing which figure was real.
Efua’s product gave that team a way to connect the incoming payment records to the underlying orders, investigate exceptions, and approve a payout from a shared view.
The investor’s next question changed.
“Who currently owns that reconciliation?”
That was the question Efua needed. It moved the discussion from resemblance to responsibility, from a global brand name to a specific person carrying a specific operational risk.
“Stripe for Africa” had offered speed at the start of the pitch. It also imported someone else’s product boundaries. Stripe means different things to different listeners, so every listener silently supplies a different feature set, market assumption, and standard of comparison.
The shortcut saved ten seconds and cost Efua the next ten minutes.
Missing infrastructure is part of the product story
When I hear founders use a familiar US or European company as shorthand, I usually ask what must be true for that comparison to work.
Does each payment arrive with a reliable reference? Can the buyer, merchant and order be matched without a phone call? Does one person control the full workflow? Can the team treat a successful payment notification as settled money? What happens when the records disagree?
Those questions reveal the infrastructure the comparison quietly assumes.
A product built in Accra, Lagos or Johannesburg may sit inside a workflow spread across bank transfers, payment providers, spreadsheets, messaging threads and manual approvals. The important product decision may have little to do with copying a well-known interface. It may concern how the system establishes enough confidence for someone to release goods, approve a payout or close the day.
This is also why demo conditions matter. A clean transaction can make the product look finished while avoiding the moment customers will judge most harshly. I explored that tension in Should We Pause a Fintech Launch When the Demo Conditions Do Not Match Customers?.
The strongest pitch explains the missing layer in plain language: what information fails to travel, who reconstructs it, and what decision remains blocked until they do.
The founder still needs a narrow claim
There is a danger in abandoning the comparison. The pitch can expand into a speech about African financial infrastructure, regulation, inclusion and market potential. The founder sounds informed while the product disappears.
Efua avoided that by keeping one boundary clear. She was solving the reconciliation and approval problem for a particular operating workflow. She did not claim to rebuild the continent’s payment system. She showed where existing rails left a gap and why a customer would pay to close it.
That discipline matters because infrastructure problems tempt founders to describe everything connected to them. A buyer rarely funds an entire diagnosis. They pay for one costly uncertainty to end.
The same rule applies to product demos. If twelve features appear before the buyer understands the decision at stake, breadth becomes a liability. Kwame’s twelve features lack a reason to buy. His runway is at risk. examines that failure from another angle.
For Efua, the narrow claim also made the roadmap easier to defend. A requested feature either helped the operations lead match, investigate or approve, or it waited.
Rewrite the sentence before adding another slide
Efua reopened her deck and removed the comparison from the first slide. She replaced it with the operational break she had shown in the room: payments arrive, but the records needed to reconcile them do not arrive together.
Then she described the person left holding the gap and the decision that person could not safely make.
The room did not suddenly become easy. The investor still questioned sales cycles, integrations and whether customers would change their current process. Those were useful objections because they tested Efua’s actual business.
Her next meeting began without a borrowed category. On the table beside her laptop sat the same paper cup of coffee, already cold. This time, the first question was about the finance lead who could not trust the total before approving a payout.
That was the conversation she had been trying to reach.
Comments
No comments yet.