For a client

IziClub

For coaches and creators selling a community: courses, feed, coaching and a public page where members pay, by card or mobile money.

Live since
2026
Shipped in
one month
A verifiable fact
Wave, Orange Money, MTN and card
Affiche IziClub
  1. The brief

    French-speaking coaches and creators in West Africa already sell a community — on WhatsApp, with a payment link on the side and reminders sent by hand. They needed one place for the courses, the feed, the coaching and the payment, where the money lands with them, no middleman.

    Three requirements from day one: a flat subscription and zero commission on what members pay; the local payment methods — Wave, Orange Money, MTN, Free Money — next to the card; and one public page per club, shareable as a single link.

  2. What I shipped

    IziClub, a complete SaaS where every creator gets their own club, with:

    • courses in modules, lessons, videos and quizzes, hosted on the platform or elsewhere;
    • a community feed — posts, reactions, threaded comments, mentions — and a document library;
    • coaching, one-to-one and in groups, with scheduling built in, and a calendar for lives and workshops;
    • members, roles, a leaderboard and badges;
    • a public page at izi.club/club-name, with the pitch, testimonials and paid sign-up on the spot.

    Two plans, Starter and Pro, on a monthly subscription you can cancel any time, and member payments through local mobile money or by card via Stripe — in the creator’s name, to the creator’s account.

  3. The hard part

    Two things, intertwined. First, isolation per club: each club is a space of its own — its members, its content, its payments, its public domain — on a single database and a single codebase. A request can never see another club, whatever a hurried developer gets wrong; that is built into the access layer, not into every screen.

    Then multi-provider payments in each creator’s name: Wave, Orange Money, MTN and Stripe share neither flows, nor confirmations, nor failures. It took one notion of a payment on the product side — requested, confirmed, failed, refunded — and one adapter per provider to fill it, with direct payout to the creator and follow-ups when a confirmation runs late.

  4. The outcome

    Clubs that run: a creator publishes a course in the morning and sees members pay in the afternoon, with whatever they carry in their pocket. The product takes a subscription, never a cut — it says so on the home page, and the code holds to it.

  5. What’s next

    A project like this one? Let’s book 30 minutes: you tell me what you want to launch, I tell you if it’s doable.

    Book a call