Loan pipeline dashboard — from enquiry to disbursal on one screen
A working demonstration of loan origination operations: applications moving through a defined pipeline, eligibility and EMI computed at the point of enquiry, documents tracked per application, and ageing visible before it becomes a problem.
- 6 stages
- Explicit pipeline states with audit trail
- 1 engine
- Shared by public calculator and credit sheet
- Per-stage
- Ageing buckets in the funnel report
- Role-scoped
- Borrower data access by function
These figures are illustrative unless the client supplied measurement data. Replace them with measured values
before publishing — see the note at the top of content/portfolio.php.
The problem
Lending operations in a mid-sized NBFC usually run across three unconnected surfaces: a website enquiry form, a CRM that captures the lead, and a spreadsheet that actually tracks the application. Nobody has a single view of how many applications are open, how long each has been sitting, or which stage is losing files.
The demonstration was built to answer one question concretely: what does the operations team see if the pipeline lives in one place?
What we built
-
1
A pipeline with named stages
Enquiry, eligibility, documents, verification, approval and disbursal are explicit stages with entry and exit criteria. An application cannot skip a stage, and every transition records who moved it and when.
-
2
One eligibility engine, two consumers
The same calculation library serves the public-facing calculator and the internal approval sheet. That removes the classic discrepancy where the number the customer saw is not the number the credit team calculates.
-
3
Document completeness as a first-class state
Each product defines its document checklist. The dashboard distinguishes "in documents" from "documents complete", which is what makes an ageing report actionable rather than interesting.
-
4
Ageing and stage-wise funnels
Every stage reports how many applications sit in it and how long they have been there, bucketed. The point is to expose the stage where files go to die.
-
5
Role-scoped access
Field staff, credit analysts and management see different slices. Sensitive borrower data is scoped by role rather than merely hidden in the interface.
Outcome
The demonstration established the design language that now underpins the Loan Origination App: stages that cannot be skipped, a single calculation engine, and missing documents treated as a status rather than a note. Changing the pipeline model late is expensive, so proving it first in a demo was the cheap way to be wrong.
What we would carry forward
- If the customer-facing calculator and the credit sheet disagree, you have two products.
- "Documents pending" without a checklist is just a nicer way to lose files.
- Ageing reports change behaviour; volume reports are read once and forgotten.
Related
Other case studies: CalculatorBest · School ERP Rollout
Free consultation
Have a similar problem?
Describe it in a few sentences and we will tell you what it would take — and whether we are the right people for it.
We reply within one business day. · No obligation