Origination, servicing, collections and the ledger — and the compliance, support, marketing, people, procurement and legal work around them — on one data model, behind one control panel. A configurable rules engine you own, journeys you draw, DPDP handled by policy, and AI doing the reading a credit officer would otherwise do by hand. Built to be run by the team you already have.
A CRM nobody likes, an LOS from one vendor, an LMS from another, a collections tool bought separately, and a finance team reconciling all of it in spreadsheets at month end. Six licence fees, six support queues, and no single view of a customer.
They are not integrations of separate products. A lead, an application, a loan, a collection case, a complaint and a vendor invoice are records on the same book, and every app reads and writes it directly. One sign-in; each role sees only its apps.
Applications, KYC on three rails, bureau, BRE, multi-lender offers, underwriting, sanction and disbursal — every vendor call visible on the file.
Whole-rupee schedules on reducing balance, mandates, repayments with a proper waterfall, charges, foreclosure quotes, restructuring, closure and NOC.
DPD derived nightly, buckets, cases auto-allocated to tele and field agents, promises to pay, a copilot that writes each agent's call list.
Append-only double-entry ledger. Disbursal, receipt, payroll, vendor invoice and write-off post as they happen; month-end accrues and provisions.
One customer record across leads, applications and loans, with a 360 that survives the loan being closed and a next-best-action.
Consent registry, KFS and disclosure evidence, 14 RBI digital-lending controls, grievance register with the 30-day clock, bureau reporting, regulatory calendar.
Each lender's borrower journey as a versioned document: reorder steps, swap providers, set signing rules, publish. The next application runs it.
Every complaint on one desk with the loan beside it. Tier SLAs L1 → L2 → grievance officer → Ombudsman; escalations land in the compliance register.
Segments as live rules over the customer master with consent enforced, campaigns, templates, attribution from the first tap, CAC by channel.
Directory tied to console access, leave, Indian payroll posting to the ledger, and incentives computed from cured cases and disbursals.
Requisitions routed by an approval matrix and frozen at submission, vendor onboarding with RBI outsourcing checks, POs, three-way match, payment.
Boundary conditions (go / no-go), refer rules, segments that shape the offer, pluggable models with champion–challenger–shadow, a simulator, versions. The borrower journey runs the published version.
Data-principal requests with a footprint scan across every app, auto-suppression by a retention policy, legal holds with the basis stated, DPO decision, breach register with the 72-hour clock.
Demand notices at 60 DPD, Sec 138 / arbitration / Lok Adalat matters with statutory clocks derived from the file, hearings, panel counsel, settlements that post to the loan under an authority matrix.
Monitoring across lenders: buckets, PAR, vintages, lender-wise exposure and reports — the view a CXO opens on a Monday.
AI is a layer, not an app: the underwriter, credit memo, collections copilot and customer assistant sit inside LOS, Collections and CRM. Sign-in is needed to open an app — demo credentials are on the sign-in page.
One lender wants DigiLocker; another insists on CKYC; a third accepts a document upload. One wants video KYC before sanction, another after. In most platforms each of those is a release.
In MODNAR a journey is a versioned document attached to a lender's product, drawn as a flow: drag a step, drag it past the sanction diamond to run it later, insert on an arrow, publish. The next application runs the new flow — and applications already in progress keep running the version they started on.
Both the borrower journey and the LOS stage tracker render from the same definition. There is nowhere left to hardcode the order.
Not a chatbot in the corner. The credit memo is written from the bureau report, the bank statement analysis and the KYC record — the same evidence a credit officer would read, assembled into the document they would have spent forty minutes writing.
The recommendation comes with the factors it weighed and the ones that gave it pause, so an underwriter can disagree with the reasoning rather than argue with a score.
Every AI decision is stored with its inputs and its output, so a decision from six months ago can still be explained.
Not a single-lender product that will be made multi-tenant later. Every record carries its tenant, and isolation is enforced by row-level security in the database rather than by developer discipline in the application.
Each lender gets its own branded journey on its own subdomain, its own products, its own credit policy and its own users — operated from one platform.
The isolation is a database policy you can read on screen and a query you can run to prove.
The decision policy is the secret sauce of any lender, and it should never sit inside a vendor's release cycle. In MODNAR the BRE is configuration: boundary conditions that say go or no-go, refer rules, segments that shape the offer, and the models behind them.
Rules today; a scorecard as challenger on a slice of traffic; a PD model scoring in shadow until it earns the seat. Swapping a model is a role change on one screen. A simulator shows what any change does before it is published, and every version can be rolled back.
The borrower journey decides on the published version and records which one — so a decision from last quarter is explained by last quarter's policy, not today's.
Bureau, PAN, DigiLocker, account aggregator, penny-drop, eSign, mandate, payout. Each call is logged against the application that triggered it, with the request, the response, the HTTP status and the latency in milliseconds.
Open any application and the whole vendor conversation is there in order — including the retries, and including the calls that failed.
The same log answers the operations question and the finance question: what happened, and what it cost.
One sign-in. Each person sees the apps their role opens and nothing else. Users, roles and permissions are managed in one place and enforced in every app — not repeated per module.
Identity, RBI registration, GRO, product terms, a journey template and a brand colour. A nine-point go-live checklist across Legal, Compliance, Product, Engineering, Finance and Ops. Sandbox first; live means live on the borrower's offer listing.
Credit policy, pricing, KYC, fair practices, outsourcing, litigation — where a policy is live configuration it links into the app that enforces it, so the document and the rules cannot drift apart. Review calendar, versions, owners.
Palette, tenant name and mark applied to every app and the borrower journey in one save. Users & roles, banks, configuration, tenants and the audit trail live in one admin console — and only there.
A schedule on reducing balance, and a balanced journal entry behind every event. Here is a ₹5,00,000 personal loan at 16% over 36 months — the EMI never changes, but what it pays for does.
Every external service is a sandbox stub for now — the gateway is built so a live provider is a configuration change, not a rewrite. Everything else is real, and you can run it yourself: apply as a borrower, then open the LOS and find your application waiting.
The fastest way to judge this is to put one of your own products into it and push a real application through, end to end. That takes an afternoon — and you keep whatever we configure.
Start the conversation →