Use cases · 10 narratives · 6 retail · 4 B2B

The same house. Ten kinds of work.

Each story below names a real persona, a real input, and the path Mukodi runs end-to-end. Helpers hand off across floors; the Courtroom signs every consequential verdict. Outcomes are anonymised but verified.

Audience
10 of 10 storiesTap any card to read the full flow
Featured story · #1 of 10

First salary, first system.

A typical narrative arc — input, helpers in sequence, verdict, audit. Use this as the template for the other nine.

Priya, 24 · QA engineer in Coimbatore · first job
·Priya gets her first salary on the 30th. She wants a system that holds her plan together — not a spreadsheet she will abandon by month two.
  1. Scene 01 · Sign in once, in Tamil
    Priya enters her phone number, types a 6-digit OTP, and picks Tamil as her language. The app reads everything back to her in Tamil from the next screen.
  2. Scene 02 · Connect her salary account
    She picks her bank from the Account Aggregator bottom sheet, consents on her bank's screen, and watches her last six months of transactions land — categorised, tagged, and totalled.
  3. Scene 03 · See her own health score
    By that evening, Mukodi has computed a financial health score from her income, EMI, and savings rate. The reasons are written in plain Tamil; the trend line shows the next three months.
  4. Scene 04 · Set a first goal
    Priya sets a six-month emergency fund target. The app shows a P10–P90 forecast band instead of a fragile single line — and tells her, gently, which month she is most likely to fall behind.
  5. Scene 05 · Ask Mukodi a question
    She asks, in Tamil, whether she should pre-pay her education loan or build her emergency fund first. The answer comes back with three reasons, each linked to her own transactions.
Helpers on call
Read full use case
How to read this page

The legend behind the chips.

Retail

Each story names a persona (first job, gig worker, retired teacher, household lead, leaving the app cleanly) and walks through the scenes Mukodi runs to support them. Every step links to the feature page and the model behind it.

B2B

Each story names an operator (lender, insurer, PSP, lender product team) and walks through how the API surface delivers the outcome — score, verdict, extraction — with the audit chain a regulator can verify from outside.