HelloGrowthCRM Feature
A workspace built for loan DSAs: your lender panel, eligibility against the whole panel at once, one file tracked across every lender from login to disbursal, and payout accounting that survives a slab change — on the same CRM that handles the borrower.
Quick answer
HelloGrowthCRM's Loan DSA module gives Indian loan agencies a lender panel with empanelment status, an eligibility engine that applies FOIR, income-multiple and LTV caps across every panel product, multi-lender file tracking through login, query, credit, sanction and disbursal, effective-dated payout slabs, payout receivables with reconciliation, sub-DSA wallets, and a margin P&L that nets payout in against payout out.
It loses money on files it wins. The enquiry is worked, the file is logged, the loan disburses — and then the payout arrives short, or late, or against a slab nobody wrote down. On a generic CRM none of that is visible, because a generic CRM was never built to know what a disbursed file is worth. Here is where it goes:
✗ The slab moved and nobody noticed
Payout percentages change monthly by lender, product and volume, and festive campaigns come and go. If you value a file at today's rate instead of the rate in force on its disbursement date, your invoice and the lender's statement will never agree.
✗ Receivables live in someone's head
The file disbursed, so the payout is coming. Which lender, how much, against which disbursement, and did the full amount actually land? Without a receivable per file, a short payment is absorbed rather than queried.
✗ Sub-DSA payouts eat the spread
Gross payout looks healthy until you subtract what partners are owed. If payout-in and payout-out are tracked in different places, the margin you are actually keeping is a quarterly surprise instead of a number you run on.
✗ Borrowers go cold while you are logging files
A loan enquiry has a shelf life measured in minutes. An unanswered borrower simply calls the next agency, and that loss never appears in any report because the lead was never worked at all.
Each of these is an accounting problem wearing a sales-software costume, which is why bolting a spreadsheet onto a general CRM never quite closes it. HelloGrowthCRM puts the panel, the file, the slab and the payout on one system, so the money side of a disbursal is recorded by the same action that records the disbursal.
Built for Indian agencies running home loan, LAP, personal, business, auto and education loan files across a multi-lender panel.
Hold every lender you are empanelled with and the products they offer, each marked active, on hold or inactive. Rates, processing fees and payout percentages live on the product, so the panel is a working reference rather than a spreadsheet someone maintains.
Check income, obligations, CIBIL and property value against the whole panel at once. FOIR, income-multiple and LTV caps are applied and the tightest one wins — returning the products that qualify, the maximum eligible amount, an indicative EMI, and the payout to you.
Put shortlisted offers side by side with EMI, total interest, processing fee and total outgo, so the borrower compares like for like. Export it as a PDF to send — the sheet that wins the file, produced from the panel instead of assembled by hand.
One loan file can go to several lenders. Each submission moves through login, query raised, credit, sanction and disbursal — or rejection — so you always know which lender is where, instead of chasing five bankers to find out.
Payout percentage varies by lender, product and volume band, and changes with festive campaigns. Slabs carry the dates they were in force, so a file is valued at the rate that applied on its disbursement date — not today's grid.
Every disbursed file records what the lender owes you. When the lender's payout statement arrives, each line is checked against the sanctioned amount and payout rate recorded on that file — short payments, missing lines and extras are classified and a dispute task is raised, so a shortfall is queried rather than absorbed.
Partners who process files for you get their own network record and wallet, with what they have earned and what is owed. Kept deliberately distinct from connectors, who only introduce a borrower for a flat referral cut.
Payout in, minus payout out to sub-DSAs, minus cost — per file and per period. The number an agency owner actually runs on is the spread that survives, not the gross payout the lender announced.
Compute what a borrower saves by moving from their current lender's rate to yours — monthly and across the remaining tenure — so the BT pitch is a number on a page instead of a claim on a call.
Attach a loan-protection or property policy to a disbursed file and the second payout is computed as a percentage of the annual premium, with per-policy defaults you can override. The attach earns twice on work already done.
An unanswered borrower calls the next agency. Response-time SLA statistics and unassigned-owner counts combine into one leakage view, so the enquiries going cold are visible while they can still be saved.
Export a printable list of the borrower files you select — name, phone, call status, loan amount and city — in one action, for a banker drop, an audit, or your own records.
The reason a DSA ends up running three systems is that no single one covers the whole arc. The enquiry belongs in a CRM, the file belongs in a tracker, and the payout belongs in a spreadsheet — and the joins between them are where the margin disappears. On HelloGrowthCRM it is one arc:
1. Enquiry answered fast
The borrower enquiry lands as a CRM lead with an owner and a response clock. Speed-to-lead and unassigned counts surface the ones going cold, so the file is won before a competing agency calls back.
2. Eligibility across the panel
Income, obligations, CIBIL and property value are checked against every panel product at once. FOIR, income-multiple and LTV caps apply and the tightest wins, returning what qualifies and what it pays.
3. One file, several lenders
Submit to the lenders that fit and track each submission separately through login, query raised, credit, sanction and disbursal, so you always know which banker owes you an answer.
4. Payout valued and collected
On disbursal the payout is valued at the slab in force that day. When the lender's statement arrives, each line is checked against the sanctioned amount and rate on that file, and the result is netted against sub-DSA payouts into margin.
Because the borrower record and the loan file are the same record, nothing is re-keyed and nothing is reconciled at month end. The call that qualified the borrower, the WhatsApp that chased a document, the submission that got sanctioned and the payout that settled all sit on one timeline — which is also what makes an audit or a lender query a lookup rather than an excavation.
Home loan & LAP agencies
Secured files where the LTV cap decides the sizing, property documents ride along with the file, and payout slabs differ across every bank on the panel.
Multi-product DSAs
Personal, business and auto loan files running side by side, each with its own eligibility caps and payout grid, all visible in one pipeline instead of one tab per lender.
Agencies with a sub-DSA network
Partners processing files under the agency's empanelment, with wallets for what they have earned and a margin view of the spread that actually survives.
Connector-led agencies
Referrer-only partners who introduce borrowers for a flat cut, kept on a separate leaderboard so a referral is never accidentally paid on a file-processing slab.
Balance transfer specialists
Teams whose pitch is the saving itself — monthly and over the remaining tenure — computed from the borrower's current outstanding, rate and tenure rather than estimated.
Agencies cross-selling insurance
Loan-protection and property policies attached to disbursed files, earning a second payout on the annual premium for work the team has already done.
What changes once the payout lives with the file:
Dated
Payout slabs
Valued at the rate in force on disbursal
Netted
Margin, not gross
Payout in, less payout out, less cost
One
Record per borrower
Enquiry, file and payout on one timeline
What is the Loan DSA module in HelloGrowthCRM?
It is a dedicated workspace for direct selling agents and loan agencies, built on top of the CRM. You keep your lender panel and their products, check a borrower's eligibility against that panel, submit one file to several lenders, track each submission from login to disbursal, and then account for the payout you have earned. Because it sits on the CRM, the borrower enquiry and the disbursed file are the same record — not two systems that have to be reconciled.
How does the eligibility check work?
You enter the borrower's income, existing obligations, CIBIL score and, for secured products, the property value. The engine evaluates every product on your panel and applies the three standard DSA caps — the FOIR cap, the income-multiple cap, and the LTV cap on secured products — then takes whichever is tightest. You get the products that qualify, the maximum eligible loan, an indicative rate and EMI, and the payout the file would earn you.
Can it handle payout percentages that change every month?
Yes. Payout slabs are effective-dated per lender, product and volume band, including limited-period festive campaigns. The rate applied to a file is the rate that was in force on its disbursement date — not whatever the grid says today. That is the difference between a payout figure you can invoice against and one you have to argue about.
Does it track what lenders owe me, and what I owe my sub-DSAs?
Both. Payout receivables record what each lender owes on disbursed files. When a lender's payout statement arrives, reconciliation checks each line against the sanctioned amount and payout rate recorded on that file, and flags short payments, missing lines and extras — raising a dispute task so a shortfall gets queried. Separately, the sub-DSA network tracks what you owe partners who process files for you, and Margin P&L nets the two: payout in, minus payout out, minus cost.
What is the difference between a sub-DSA and a connector?
A sub-DSA processes files for you and is paid a share of the payout, tracked with a wallet. A connector only introduces a borrower and takes a flat referral cut — no file processing. HelloGrowthCRM keeps the two deliberately separate, because paying a referrer on a sub-DSA slab is one of the easier ways for an agency to quietly lose margin.
Is the Loan DSA module built for India?
Yes. It is India-first: amounts are in rupees, the products are the ones an Indian panel actually carries — home loan, LAP, personal, business, auto and education loan — and the payout accounting is built around how Indian agencies are paid, including TDS on the payouts you pass to sub-DSAs. It works alongside the rest of the CRM, so calling, WhatsApp and follow-ups run on the same borrower record.
How do I switch the Loan DSA module on?
The loan desk is part of the financial services industry module, so it appears once your workspace industry is set to Financial Services — under Settings, in your company profile. It is off by default so agencies in other sectors do not see loan screens they will never use. Your workspace runs one industry module at a time, so switching replaces the previous vertical's screens. No separate purchase and no add-on: it is included in your plan.