Banking the global gig economy from Nairobi

Context

The problem that started Payd was personal. Benaiah was a freelancer working with clients in Zurich, Berlin, and New York while banking from Nairobi. Every invoice lost 15 to 30 percent to correspondent banking fees, exchange spreads, and wires that took three to five business days to clear — if they cleared at all. He was not alone. There are an estimated 400 million independent workers globally, and a disproportionate share of them live in markets where the cost of getting paid is a tax on their existence.

The obvious consumer play — "a better Wise for Africa" — was crowded and hard. The less obvious play was that the same infrastructure needed for a great consumer product was infrastructure that growing businesses needed even more. Agencies paying distributed contractors. Companies running global payroll across M-Pesa, MTN, SWIFT, and SEPA in the same transaction batch. Platforms needing to move money for their users without becoming a bank.

Payd could either be a consumer fintech competing on UX, or an infrastructure company that happens to have a beautiful consumer front-door. We chose the second.

Moved Fast

In the first ninety days we shipped what a bigger team would have scoped as a six-quarter roadmap:

• USD and EUR virtual accounts with dedicated account numbers, wired into SWIFT, SEPA, and ACH through a licensed partner network.
• Direct mobile money integrations with M-Pesa and MTN — the most-used rails on the continent — so a freelancer in Lagos could receive a wire from Munich and spend the proceeds at a corner kiosk in Ikoyi by end of day.
• Stablecoin settlement rails on ten chains, giving us a low-cost cross-border layer that settled in seconds and let clients choose between fiat and digital dollar delivery depending on market conditions.
• A payment-link primitive that let anyone generate a branded checkout in thirty seconds and receive from any of the above channels.

The rule we ran was "ship something in production every Friday, or explain what broke." That cadence did two things. It forced decisions. And it compounded — every shipped primitive was a lego brick the next week could stand on.

Failed Forward

The B2C-first hypothesis almost killed us. We spent a full quarter optimising consumer onboarding — shaving it from 40 minutes to 3 — and celebrated each milestone. The metric we should have been watching was not signups. It was volume per user. B2C users send small amounts infrequently. The unit economics do not close at under-$50 average transaction sizes when payment partners charge fixed minimums.

We learned this the hard way. Two cohorts of acquisition spend produced great vanity metrics and a P&L that refused to work. The failure was useful because it was sharp. We did not have to argue about it. The data was the data.

The pivot was to stop chasing consumers and start chasing the businesses paying them. Agencies, marketplaces, platforms, and payroll operators all had the same pain we were trying to solve for their workers — but at 50x to 500x the average ticket size. Same infrastructure. Same integration surface. Completely different unit economics.

Within two quarters, B2B and B2B2C volume crossed 65 percent of total. Six months after that, it crossed 70 percent. The consumer side remained — and remains — because it validated the rails and kept us honest about end-user experience. But it stopped being the business.

Built

What exists today:

A money OS for borderless work. USD and EUR virtual accounts open in three minutes with no paperwork. Stablecoin settlement across ten chains. Direct mobile money across the continent. A business suite covering global payroll (batch payments with single approval, automated scheduling, multi-channel delivery per country), spend management with role-based access and real-time tracking, and invoicing with customisable templates and automated reminders. A WhatsApp-native interface that lets users send, receive, and manage their account from the app they already spend four hours a day inside.

Partnerships with regulated payment providers and virtual asset service providers across every corridor we operate in, so Payd is compliant by construction — not retrofit.

Compounds

Payd is the flagship of B3n Labs not because it is the biggest product on the studio's books, but because it proves what Labs is for. Every month, two things get stronger on their own without us pushing them.

First, distribution compounds. Every business customer brings 50 to 5,000 end users, who become their own viral loop. The WhatsApp interface did not just improve retention — it turned every user into a distribution channel because referring a friend now happens in the same thread they send voice notes in.

Second, rails compound. Each new corridor, each new mobile money operator, each new stablecoin added to settlement makes every existing customer more valuable. A payroll client signed twelve months ago is 3x more useful to themselves today than they were at signing, without us shipping them a single product update.

This is what Labs is supposed to produce. Not a product. A compound.