Skip to content
Gradexa
CRM · LOS · LMS

The Suite

Full-stack lending infrastructure on one data model. Single-repayment and EMI loan products (EMI over 3–12 months, reducing balance) — originated, decided, disbursed, and serviced without stitching four vendors together. The Credit Engine sits at the center.

Request a demo About the Credit Engine
  1. 01
    CRM
    Lead · KYC · borrower 360
  2. 02
    LOS
    Application · product selection
  3. 03
    Credit Engine
    Knockouts → 10-grade pricing
  4. 04
    Decision
    Grade · offer · fired rules
  5. 05
    LMS
    Disburse · service · collect

One data model end to end — no re-keying, no lossy hand-offs. Every decision is traceable back to the rules that fired.

Three modules, one record

Each module, deep enough to run on.

Adopt the whole Suite or start with one module. Because they share a data model, adding the next one doesn't mean another migration.

01CRMLead → KYC → Borrower 360Capture and qualify leads, run KYC, and build a single borrower 360 that every downstream stage reads from.
02LOSApplication → product → decision → e-sign → disbursalOrigination that selects the product (single-repayment or EMI), calls the Credit Engine inline, applies the priced offer, collects e-sign, and moves to disbursal — one workflow.
03LMSServicing · per-installment DPD · collections · NPAServicing for both products: single-repayment payoff and EMI schedules with per-installment DPD, part-payment recomputation, pre-closure, collections queues, NPA classification, and RBI-ready reporting.

One data model

A lead in the CRM becomes an application in the LOS becomes a serviced loan in the LMS — the same borrower and loan records throughout. No exports, no re-keying, no reconciliation drift between systems.

Tenant data isolation

Multi-tenant by design, with each tenant's data isolated. Run the same engine that can power your own lending product, on your own book.

Honest product scope

Single-repayment and EMI loan products are supported today — EMI on 3–12 month tenures on a reducing balance, with part-payment, pre-closure, and per-installment DPD. The data model and workflows are built to extend further. Bureau reports are pulled by you with your own bureau membership and parsed by the engine; direct bureau pull is on the roadmap. NACH mandates are partial: core logic built, not production-ready.

Next step

See it decide on a real bureau report.

Request a demo and we'll walk you through the Credit Engine and the Suite on your scenarios. Honest about what's built today, what's partial, and what's on the roadmap.

Request a demo Read developer docs