Self-regulatory organisation for India's NBFC microfinance lenders

Turning a member data portal into a governed, quality-checked reporting platform.

DATA PLATFORM - ADMIN REVIEWMEMBER UPLOAD3 QC cautions flaggedADMIN VETTINGAPPROVEDPENDINGReleased by admin onlyDISTRICT RISK INDEXPEER COMPARISONPUBLISHED REPORTUpdates on releaseMobile responsive
The brief, as we understood it
“
Finish the platform we already run, sharpen its analytics, and give our members a way to submit data that we can trust before it reaches a published report.
- Our reading of the brief handed to Milleniance at the start of the engagement
01 - The challenge

A live platform whose value depends on data nobody vetted.

The platform had been in production since late 2023 and Milleniance was already maintaining it. It gave a self-regulatory body and its lender members a shared place to see sector data. But the next stage of its usefulness depended on things it did not yet do well: a regulator-facing module still to be completed, custom reports whose selections were not working, district-level data that administrators could not reach, and a layout that did not adapt to phones.

The larger gap was upstream. Members are the source of the data, and there was no structured route for it to arrive - no rules-based checks at the point of entry, no review step, no way to stop an unchecked figure from surfacing in a published report.

  • Core modules, including the self-regulatory organisation's own view, still to be completed
  • Custom reports and district-level access not working as needed for administrators
  • No mobile-responsive layout for a member base that works from phones
  • No governed path between a member's upload and a published report
UPLOAD AUPLOAD BUPLOAD CUPLOAD DNOGATEPUBLISHEDREPORTunchecked
02 - The approach

Sequence by dependency. Release by milestone.

The 15 objectives were grouped into three stages so that each one built on something already working. Stage 1 covered the modules and everyday improvements that members would notice first - the regulator module, email authentication with delivery reports and usage logs, CSV import changes, comparative analytics with additional datasets, page-level feedback, a publication module, UI and UX work and mobile responsiveness.

Stage 2 tackled custom reporting, district-level access, the district risk index map linked to a pin-code database, and a code review and security check. Stage 3 added the piece that changes how the platform is trusted: a data-collection module with quality checks and an intermediate admin layer. Each stage was tied to defined deliverables and dates, and the client owns the platform, source code and documentation handed over at the end.

  • Stage 1 - core modules, authentication, analytics, publication and mobile
  • Stage 2 - custom reports, district risk maps, code review and security check
  • Stage 3 - member data forms, quality checks and admin vetting
STAGE 1Core modulesAUG-SEP 24STAGE 2Reports & securitySEP-DEC 24STAGE 3Data ingestionFEB 25
03 - What we built

One platform. Four capabilities that make its numbers trustworthy.

Governed data ingestion
Members enter data through forms with rules-based checks that flag issues as cautions in real time. An intermediate admin layer vets each submission before it reaches the main database, and published reports update only when an administrator releases the new data.
Peer-comparison analytics
A separate comparative-analysis module lets members benchmark against peers, with datasets from additional regulated entities added so the comparison covers more of the sector.
District-level risk views
A district risk index map linked to a pin-code database, plus district-level data available in custom reports for administrators - so risk can be read at the level where decisions are made.
Secure, accountable operations
Email authentication alongside mobile sign-in, delivery reports, monthly usage logs, a fortnightly backup facility, page-level feedback and a code review and security check across the platform.
Built on

A stack chosen to keep member data governed from the first keystroke to the published report.

Responsive web application Role-based member and admin access Rules-based data validation Email and mobile authentication Usage analytics and delivery logs Scheduled backups
05 - What the engagement covered

A defined scope, staged delivery, and a platform the client owns outright.

15
Scoped objectives on a single platform
3
Milestone stages, each tied to defined deliverables
12mo
Contracted term covering build and maintenance
1
Client-owned platform, with source code and documentation handed over

"If the numbers in your reports depend on data nobody checks before it goes in, the fix usually starts at the upload form, not the dashboard."

Let's see if we're the right fit

Thirty minutes with a senior platform architect, before either of us commits to anything.

No sales deck, no discovery call with someone who hands you off afterwards. We look at where your data comes from, who checks it and what your reports need to be able to stand behind. We respond within one business day.

Talk to a Senior Platform Architect →