The Capability Is Not the Company

Selling Technology When the Market Isn't Buying It

AI-generated podcast of the article….

---

You built the engine. Not a knockoff or MVP—an actual engine. Fast, clean, modular. A thing of beauty. It handled millions of transactions, parsed invisible signals, translated noise into insight. It was the kind of infrastructure other startups wish they had under the hood. And yet, no one cared. Not really. Not the way you needed them to. In meeting after meeting, you explained what your technology could do. Real-time scoring. Seamless integrations. Invisible infrastructure that makes credit underwriting smarter, cheaper, faster. But the questions were always the same: "Can I give someone a loan with this algo today?" “So it’s not a wallet. It’s the thing behind a wallet?” “Does it give me a diagnosis, or just raw genetic data?” "So I have to build the rest myself?"

Each question chipped away at the fantasy that building capability was enough. Because here, in this market, it often isn't. In the U.S., that same engine—possibly less elegant—would get funded off the deck. There, the story is the company. Here, the story is the outcome. What they see is what they buy. And what they buy is not potential. It's proof.

In emerging markets, engine businesses stall not because they aren't valuable, but because value has to arrive prepackaged, pre-proven, and pre-translated into something someone can use right now. Selling infrastructure in a market that lacks infrastructure means you end up having to build everything yourself anyway.

That’s why the companies that scale here often look full-stack, even if they didn’t set out to be. The capability may be your edge, but the market won’t reward it until it’s wrapped in something they can touch, trust, and transact with. You don't earn the right to sell the engine until you've given them the ride.

Emerging market customers prefer solved problems to abstract tools. They want the loan, not the score. The water, not the purification tech. The ride, not the routing algorithm. When people are used to solving problems manually, every new tool has to outperform the human workaround. If your engine demands imagination, configuration, or translation—it's already too far from the finish line.

Engine businesses also assume a broader ecosystem to plug into: identity verification APIs, digital payment rails, enforcement mechanisms, a culture of software abstraction. But in many emerging markets, these layers don’t exist, or if they do, they’re unreliable. So an engine that needs a chassis, wheels, road, and fuel becomes a burden, not an asset. Suddenly, you're not selling your product—you're selling the cost and complexity of building an entire company around it. And most operators, even the ones who believe in you, are too busy keeping their own plates spinning to sign up for that kind of lift.

Stripe vs. Paystack: Who’s the Engine, Who’s the Car?

The other friction point is emotional. When your value is abstract, you ask people to trust what they can't see. But in markets where trust is hard-won and quickly lost, tangibility becomes a proxy for credibility. Car businesses let users experience the outcome before understanding the technology. Engine businesses ask for belief before delivering results. And belief—especially here—doesn't come cheap.

Even the act of buying differs. In Silicon Valley, you might pitch to a head of innovation who has a budget and a backlog. In Accra, you're pitching to someone who is CEO, COO, and customer support all in one. They're stretched, stressed, and skeptical. They need the thing that works now, not the thing that could work later. Car businesses collapse the surface area of decision-making. Engine businesses expand it. That's the difference between "let's try it" and "we'll get back to you."

This doesn't mean engine businesses can't succeed here. But they must disguise themselves as cars first. They have to show up as complete, usable, beneficial—even if what you're really doing is gathering data, refining algorithms, or building modular rails underneath. You lead with the ride. You earn trust. And only then, once people start asking what's under the hood, do you show them the engine.

The paradox is this: in a market where selling technology feels impossible, the best technology companies often hide their tech. They don't start with the capability. They start with the result. And over time, as the market gets used to the outcome, the sophistication underneath becomes a selling point, not a stumbling block. The capability becomes visible. But only after it's already valuable.

So yes, build the engine. Make it brilliant. But don’t stop there. Because in markets like these, the capability is not the company. The company is what people believe, buy, and tell others about. And that usually starts with a car they can drive today.

Shout out to my friend JR, who always reminds me that I told him that “engines are not cars” and that I must tell everyone why.