One set of numbers, head office to branch.
For lenders and NBFCs with branch networks. Portfolio, sourcing, processing and collections — defined once, signed off, and drillable from the board number to the last field unit.
It is where we have gone deepest. A listed Indian lender runs on it today.
A lender’s numbers break on the way down
Every loan lands in a core system. Nobody trusts the summary.
The month starts with building the deck
The review pack is assembled by hand at the start of every month. By the time it reaches the CEO, the numbers are weeks old.
Every function counts differently
Sourcing, processing and collections each define a case, a disbursal and a delinquency their own way. The same meeting gets three numbers.
Below the region, it goes dark
The national figure is easy. Which branch is dragging it is not — until someone asks for a special cut and waits for it.
Every return starts from scratch
Board and regulatory reporting draw on systems with different definitions, so each cycle the numbers are rebuilt and reconciled again.
Three layers, on a lender’s floor
Definitions first
Our engineers sit with credit, collections and finance. We start with what the numbers mean — portfolio, PAR and delinquency buckets, disbursals, collections — written down, owned and signed off before anything is built.
Built for how you lend
The board pack that builds itself. Branch and collections scorecards. Agents that read the same definitions and flag the branches and accounts that need a human. Planning against live actuals.
The One OS underneath
Your hierarchy in the data — national, zone, region, area, branch, field unit. Every figure drills down it. Read-only connectors to your LOS, LMS and core systems; nothing is migrated.
In production
One engagement, told straight. We’ll print outcomes here when they’re measured and the client has signed off — not before.
A listed Indian lender
A national network — zones, regions, areas, branches, and field units below them — with thousands of people between the CEO and the customer. Name shared in conversation with their permission, not on the web.
Numbers nobody could stand on
Reporting assembled by hand every month. Definitions contested between functions — sourcing, processing, collections each counting differently. Below the regional level, performance was effectively invisible until someone asked for a special cut.
All three letters in one contract
Phase 1: core metrics defined, documented and signed off — portfolio, onboarding and conversion funnels, loan processing, collections — and executive dashboards drillable from the national figure to the last field unit. Phase 2: role-based rollout across the organisation, people and hiring metrics, a review of field tooling. Phase 3: an AI layer over the governed metrics and live business planning.
Live and expanding
In production with leadership today, phased engagement underway. Engineers embedded, definitions holding, and the monthly argument about whose number is right — retired.
Safe for a regulated lender
Hosted in India
Hosted on our cloud in India by default. Or inside your own cloud account, if you would rather hold the keys.
We never write to your books
Connectors are read-only. The One OS reads from your loan systems and never writes back to them.
A branch manager sees the branch
Permissions follow your hierarchy, and every definition change is logged — who, when, and what it was before.
A tenant of your own
Your own database and environment. We don’t train AI models on your data, and you choose which models run.
Bring the number your branches argue about
Collections, PAR, disbursals — pick the one head office and the branches count differently. We’ll show you what settling it looks like: one phase, ninety days, fixed fee.