First salary, first system
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.
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.
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.
Karthik has earnings from three platforms and no payslip to show a lender. Mukodi turns the receipts into a story a credit team can read.
Mohan does not want to type on a phone keyboard. Mukodi listens to him in Telugu and answers in Telugu — by voice, in text, or both.
Anjali's messages turn anxious for a week. Mukodi notices the tone, softens its replies, and surfaces a helpline instead of pushing a goal banner.
Rashid decides to stop using Mukodi. He wants every record gone — not buried, not aggregated. The app gives him the receipts.
A mid-size NBFC wants to compress a three-day underwriting cycle into thirty minutes — without sacrificing the audit trail their risk committee reads.
An insurer wants to run KYC at scale without paying a human reviewer for every easy case — and without an off-the-shelf OCR that bills per page.
A payments service provider wants verdicts that fire before the UPI leg authorises — not minutes after, when the money is gone.
A lender wants a complete origination loop — discovery, KYC, score, decision, signature, audit — without stitching five vendors together.
Whether a user types, speaks, snaps, files, forwards, or asks — Mukodi reads the input, classifies the intent, and writes one canonical memory. Six modes, one ledger.
A typical narrative arc — input, helpers in sequence, verdict, audit. Use this as the template for the other nine.
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.
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.