Your app has the users. What it doesn't have is the ten vertical services those users would pay for — pharmacy, ticketing, loans, classes. Building each is a year of roadmap and a hire per domain. The older alternative is the one malls figured out: be the corridor, not the shop. Open a catalog of governed mini-programs, let vetted third parties run the service, and take a share of the transaction. You didn't build the pharmacy; you hosted the shelf it sits on.
The math is what founders under-rate. A marketplace take on flows that already happen inside your app is incremental margin at near-zero marginal cost. The user was already in your app to chat, to pay, to scroll; the mini-program turns that attention into a taxable transaction without a fresh acquisition dollar. In markets where the dominant rails are wallets — GoPay, GCash, Pix, M-Pesa — the host wallet already clears the payment, so the take is clean and local, not a 30% card toll routed offshore.
| Revenue lever | What the mini-program does | Why the host keeps the spread |
|---|---|---|
| Transaction share | Third party runs the service | You own the surface and the wallet |
| Shelf rent | Featured placement in catalog | Attention you already earned |
| Lead gen | Local merchant pays for discovery | The map entry is yours |
| Data products | Opt-in, aggregated insight | The loop is yours to read |
Here's the pushback the "build it all" teams won't like. Vertical depth is expensive and slow, and your first pharmacy will be worse than a dedicated pharmacy app. But you were never going to be the best pharmacy; you're the place people already are. A portable mini-program runtime lets a hundred vetted services plug in through one contract, one compliance pass, one wallet. The revenue wasn't in owning the pharmacy; it was in owning the corridor between the user and every pharmacy.
And the loop is the moat. More services pull more users, more users pull more merchants, more merchants deepen the catalog. That's the network effect that turned Chinese super-apps into the default front door for daily life — and the take rate compounds with it. A single paid feature is a line item; an open catalog is a tax on a growing economy you didn't have to staff.
The local angle is the unlock. In Indonesia, Brazil, Kenya, the Philippines, the winning services are local — a warung's reorder, a motorcycle taxi's fare, a telco's top-up. Those don't come from a Silicon Valley roadmap; they come from local merchants who already serve the block. Mini-programs let them plug in with the host's identity and wallet, so the host monetizes the local economy instead of competing with it.
I won't pretend the model is free. A catalog is a trust problem: every merchant you feature is a name on your risk ledger. Compliance, refunds, dispute handling, and KYC are now yours to govern or to delegate badly. A bad pharmacy in the catalog is your scandal, not theirs. The honest risk is treating the catalog as passive income and skipping the curation and audit that make it safe. We shouldn't.
But the direction is clear. The users are already in the app. The merchants already serve the block. The wallet already clears. The only missing piece is a runtime that carries a proven Chinese open-catalog model into the app a Jakarta or São Paulo user opens to spend. Build that catalog, keep the governance local, and the revenue shows up without you building the shop.
Sources
- StatCounter — Mobile market share — why a host app, not a new download, is the realistic front door.
- Think with Google — Consumer behavior — how users discover and pay for services inside apps.
- World Bank — Private sector development — where local merchant and micro-enterprise demand actually shows up.
- web.dev — Web platform guidance — the runtime and performance basics behind a portable mini-program.
- MDN Web Docs — Web tech reference — the standards a portable commerce UI should build on.