CRM
Lead → KYC → Borrower 360
The front of the funnel, on the same data model as origination and servicing. Capture leads, qualify them, run KYC, and build a borrower 360 that the rest of the Suite treats as the source of truth.
From first touch to a complete profile.
- 01
Capture the lead
Intake from web, partner, DSA, or API. Deduplicate against existing borrowers so a returning applicant isn't a new record.
- 02
Qualify & assign
Score interest, route to the right queue or officer, and track every touch on a single timeline.
- 03
Run KYC
Collect and verify identity and address documents. KYC integrations are enabled on onboarding with your keys. Bureau reports are pulled by you with your own bureau membership; direct bureau pull is on the roadmap.
- 04
Build the borrower 360
Consolidate identity, contact, documents, consents, and history into one record the LOS and LMS read from directly.
Built for real lead operations.
- 01Multi-source lead intake (web, DSA, partner, API)
- 02Borrower deduplication
- 03Assignment & queue routing
- 04Activity & communication timeline
- 05KYC document capture (verification on onboarding)
- 06Consent capture & audit trail
- 07Borrower 360 shared with LOS/LMS
- 08Tenant-isolated data
See where borrowers fall out.
Acquisition data that reconciles with loan outcomes, because both live on the same record.
- 01BuiltFunnel by source and agent
Leads → qualified → converted → disbursed, with conversion rates and a breakdown by lead source and by agent.
- 02RoadmapStep-level drop-off across the journey
Lead → application → KYC → decision → mandate → disbursal, filterable by source and cohort, so you can see exactly where a campaign's borrowers fall out.
Built = implemented and tested in our codebase.Partial = core logic built, not production-ready.On onboarding = adapter built, enabled with your vendor credentials.Roadmap = not built yet.Gradexa is in active development; no production lenders yet.
Who picks up what.
Structure first, automation second. Branches, roles and owners are in place; distribution by workload is next.
- 01BuiltBranch and role structure
Staff belong to branches with defined roles; leads carry an owner, collections cases an agent, grievances an assignee; channel and assisting officer are recorded on every application.
- 02BuiltAutomatic escalation on delinquency
Each DPD bucket carries its own action, from reminder to field visit to legal, and cases are created by the daily job without anyone clicking.
- 03RoadmapWorkload-based routing
Leads, tickets and collections cases distributed by team, role and current load, with time-based escalation when nobody acts.
Built = implemented and tested in our codebase.Partial = core logic built, not production-ready.On onboarding = adapter built, enabled with your vendor credentials.Roadmap = not built yet.Gradexa is in active development; no production lenders yet.
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.