A creator-monetization venture needed local payments to work on day one. We ran a build-buy-partner analysis, scored four OTT vendors, and partnered for the proof of concept. The vendor won mostly because M-Pesa came "already integrated." Two months and four thousand dollars later, it still did not take a single shilling.
This is the honest version of a partnership: how we chose, what we were sold, what actually showed up, and the decision gate we built with a few founders who have been burned before. Personal details and the vendor's brand are redacted. Everything else is straight from the record.
Give creators a way to sell content in Kenyan shillings through M-Pesa.
Compared technology partners, ran the engagement and challenged delivery against the agreed requirements.
The payment integration remained blocked at the July 2026 review. The case records the recovery options, not a completed launch.
In the creative sector, the talent problem is mostly solved. People shoot, edit and publish from a phone. What stays broken is the money. Ad-share on the big platforms pays cents, takes a cut, and owns the audience. The creator never holds the customer relationship, and almost never gets paid in the currency their fans actually spend.
For African audiences that gap is sharper. The wallet that matters is mobile money, M-Pesa first, and none of the off-the-shelf creator tools speak it well. So a filmmaker with a following and a library of work still has no clean way to charge 200 shillings for a film and have it land, tonight, from a phone in Nairobi.
The venture thesis was simple to say and hard to ship: give a creator their own branded streaming storefront, on web and in the app stores, where fans subscribe or pay per view, in Kenyan shillings, over M-Pesa. Own the audience, own the pricing, keep the margin.
Before writing a business plan, I wanted a proof of concept in front of real fans in weeks, not quarters. As founder I owned the whole call: the sourcing, the money, the integration work, and the decision about whether the first partner was worth keeping. What follows is that decision, documented.
The fastest way to learn whether fans will pay is to let them try, not to spend six months building the till first.
The reasoning behind partnering for the POCStanding up an OTT platform from scratch, apps, transcoding, DRM, billing, a payment stack, is a year of work and a serious burn before a single fan is charged. Three paths went on the table, scored against one question: what gets a paying fan on the platform quickest, without betting the runway?
Partner for the proof of concept, build later once the numbers earn it. The strategy was right, and I would make the same call again. The risk was never the path. It was picking the right partner to rent it from.
I ran a weighted vendor scorecard, four OTT platforms across functional fit, ease of use, technical alignment, vendor viability and total cost. Two capabilities were non-negotiable: M-Pesa and pricing in Kenyan shillings. Without those, nothing else on the sheet mattered.
We evaluated white-label OTT platforms on the capabilities a creator storefront actually needs, then weighted them against price. Vendors are anonymized. One capability decided it: only one platform claimed M-Pesa was already integrated.
The scorecard did its job. Given what each vendor claimed, Vendor A was the right pick, and M-Pesa was the right thing to weight above everything. The flaw was quieter: every green mark in that column was a sales claim, not a tested feature.
The vendor's own marketing set the expectation: launch an OTT platform instantly, a thousand-plus enterprise features, native apps on every screen, and the payment rails our market runs on, ready to go. We took it at its word and paid to start.
None of this was catastrophic on its own. Software is fiddly. What made it a pattern was the one column that mattered most on the scorecard, M-Pesa, being the one that would not move.
Here is the engagement from first inquiry to the latest invoice, drawn straight from the email and ticket record. Dates are exact. The vendor's brand and every person's contact detail are removed.
A few exchanges tell the whole story. Names, emails and every credential are blacked out. The words are unedited.
Public reviews told the same story before we signed. A reference check against the vendor's Trustpilot page would have surfaced the exact pattern, slow delivery, ticket ping-pong, features that work in the demo and not in production. That check cost nothing and I skipped it. It is the first item in the gate below.
Sunk cost whispers "just wait one more week." To answer it with something better than hope, I sat with a handful of founders who have run SaaS partners into the ground and back, and turned their advice into a gate. First the three doors, then the rules for walking through them.
Trust the next "it's done," keep the monthly running, hope M-Pesa fires this week. Costs runway, keeps no leverage, and rewards the behavior that got us here.
RejectedRestructure to milestone-gated payments with UAT sign-off, hold the 15% discount against delivery, set one hard M-Pesa deadline, and start building the M-Pesa piece in parallel so we are one decision from independent.
RecommendedCut losses, move to the runner-up or self-host. Clean, but throws away eight weeks of setup and restarts the same integration risk with a new party. Held in reserve if the deadline slips again.
In reserveThe playbook underneath door two, distilled from people who have paid this tuition already:
M-Pesa being "already integrated" was the single reason this vendor topped the scorecard, and it was the one feature that never worked. Every green mark in that column was a claim from a sales deck, scored as if it were a fact. A free trial and thirty minutes in a sandbox, pushing one real test payment to one real phone, would have turned the deciding capability from a promise into proof, before any money moved.
Weight the deal-breaker heaviest, that part was right. Then make the vendor prove it before you weight it at all.
Weighted vendor scorecards, build-buy-partner calls, and the unglamorous work of holding a partner to delivery without burning the runway. I can help you evaluate a partner, define delivery milestones or plan a recovery.