How it works

The journey starts with the customer,
not the product.

A customer has a need. A Smart Agent in their community helps them find the solution that fits, checks they are eligible, and submits a complete application to the institution. Every step is recorded once, on one platform, and each party sees the part that concerns them.

See the journey Become an agent

The model

From selling to serving

Traditional agents are given a product and sent to find people to sell it to. mBenki agents are given a customer and the tools to find the product that fits.

Traditional agency model

Product › Agent › Prospect › Pitch › Application

mBenki model

Customer › Need › Discovery › Matching › Choice › Qualified application


Who is involved

Three parties, one platform

The platform is called mBenki Nexus: two mobile apps and one web console, all connected to the same record.

The customer

mBenki Go

  • Finds a nearby agent and checks the agent is genuine
  • Sees what products are available and which they qualify for
  • Can self-serve through the same workflows the agent uses
  • Reviews the agent afterwards

The agent

mBenki Pro

  • Captures the customer's need and preferences
  • Matches and screens against each institution's rules
  • Completes the application with consent and KYC documents
  • Carries a Digital ID and tracks commission

The institution

mBenki Lead Manager

  • Lists products and sets eligibility rules
  • Receives complete applications and decides
  • Pays commission on outcomes, not activity
  • Reads demand signals, including from customers who did not proceed

Institutions: the full platform detail is on the Financial Institutions page


The journey

What happens, step by step

  1. 1

    The customer has a need

    School fees, stock for a shop, an emergency, an asset. They may already know which institution they want, or only what problem they need solved.

  2. 2

    They find an agent

    At a shop, a kiosk, a market, or on social media. The agent is a person in their community, not a call centre. The customer can check the agent's code before going further.

  3. 3

    The agent captures the need

    How much, how fast, what repayment shape, which kind of provider. The platform returns the solutions that fit, and the customer compares and chooses.

  4. 4

    Eligibility is checked on the spot

    The institution's own rules sit in the system, so the customer gets an instant, accurate answer at the touchpoint rather than a callback days later.

  5. 5

    The application is completed once

    Consent is captured. KYC documents are attached. The record is created with location and time, and reaches the institution complete.

  6. 6

    The institution decides, the agent stays

    Approved or declined, the outcome is recorded with the reason. The agent remains the customer's point of contact for disbursement, repayment, claims and questions, and is paid on the outcome.


Two ways in

The customer decides where to start

Institution mode

"I want a loan from IZWE."

The customer already knows the provider. The agent facilitates access to that institution's solutions and takes them through the application.

Solution mode

"I need K5,000 for stock by Friday."

The customer knows the need but not the provider. The agent captures it, the platform matches and discovers, and the customer chooses.


Built-in trust

Four things that make it safe to use

  • Certification No agent trades until they have completed training and KYC. Certification gates account activation.
  • Verification Every agent carries a Digital ID with a code the public can check at verify.mbenki.com before transacting.
  • Consent An enquiry only becomes a lead once the customer has consented. Agents are trained on the difference.
  • Review Customers rate the agent who served them through a PIN only the customer receives. Agents cannot review themselves.

The record

The conversations that end in no are recorded too

Most channels only know about the customers they win. mBenki records every interaction — what was asked for, what was offered, what was declined, and why — geotagged and timestamped. For an institution that means knowing who it is not reaching. For a regulator or funder it is a map of where the access gap actually is.

See the data product