End-to-End Loan Process Automation · From Sales Enquiry to EMI Reminders
Version
1.0
Date
27 April 2026
Status
Proposed
Duration
3 Months
Proposed by
Vaishnavi Bhardwaj
Prepared for
Leadership and the RM Team
Based on SOP across
6 Stages · 70+ Steps
Today, the loan brokerage workflow runs largely on Excel sheets, WhatsApp groups and the discipline of individual RMs. The SOP is well-defined across six stages and 70+ steps, but execution depends on people remembering to act on T, T+1, T+2... timelines. This causes silent slippage: delayed follow-ups, missing documents at login, PD queries that lose a day, and post-disbursal hand-offs that drift.
This proposal outlines an end-to-end automation system — a single internal platform — that mirrors the existing SOP exactly, but turns every step into a tracked task with auto-reminders, auto-notifications, and a single source of truth for every case from first client meeting until the final EMI.
The uploaded SOP defines a 6-stage process. We mapped every step to identify automation opportunities. The table below summarises the current state — each row is a candidate for automation.
| Stage | Steps | Roles | Timeline | Key Pain Points |
|---|---|---|---|---|
| Sales Enquiry | 15 | Leadership, RM | T → T+4 | Manual data entry, manual followups, eligibility check delays |
| Documentation | 10 | RM | Pre-Login | Documents lost in WhatsApp, blank forms, missing checks before login |
| Sanction Process | 15 | RM, Leadership, Reviewer | T → T+10 | Verifications, valuation, PD queries — no central tracker |
| Post-Sanction | 4 | RM | T+10 | ROI / charge mismatches caught late, sanction conditions overlooked |
| Disbursal | 15 | RM, Leadership | T+11 → T+15 | Stamp papers, PDC cheques, NOI payment, mail trail — fragmented |
| Post-Disbursal | 6+ | RM, Leadership | T+16 → 1st of month | Loan details captured manually, LOD requests slip, monthly folder check skipped |
Imagine the same SOP, untouched, but operated by a system that:
Crucially, nothing in the existing SOP changes. The system enforces it.
The platform is organised into nine modules, each tied directly to the SOP. The numbered SOP step references in brackets refer back to the existing sheets so the team can map old to new at a glance.
What it does: Replaces the Pipeline Excel sheet with a structured CRM record per case. Captures client details once via a mobile-first form (Leadership can use it during the very first meeting). Auto-creates a WhatsApp group with the client (via WhatsApp Business API), auto-shares the loan-product-specific document checklist, and auto-assigns the case to an RM based on rules (region/product/load).
Automation rules: If product is selected → checklist template auto-populates. If applicant is non-financial → fields hide automatically. If property OC pending → flag as "OC risk" on the case dashboard.
What it does: Follow-up engine pings RM at T+1 and T+2 if pending docs are not in the system. CIBIL pull via bureau API (one-click) once consent is captured. Banking statement parser computes 6-month average balance, bounces, salary credits. GST API pulls last 12 months of turnover where applicable. Eligibility engine takes all inputs + ongoing loans + product → returns indicative eligibility per bank. Bank matcher recommends the right bank/product fit; Leadership confirms. Commercials sheet (ROI, processing fee, tenure) generated and shared on the WA group with one click.
Why this matters: Solves the SOP rule "clarity on any case to not take more than 5 days". If commercials are not confirmed by T+4, the case auto-escalates to Leadership.
Document portal (web + mobile) per case — uploaded once, used everywhere. Pending-docs auto-list generated against the bank-product checklist. OCR + KYC matching (PAN, Aadhaar, GST, Udyam) so RM does not retype data into bank forms. Bank form pre-fill: the system fills the bank's own form using captured data — "no blank forms" enforced. Pre-login validator blocks file submission if mandatory checks (e.g. property docs, signed bank form) are missing. Auto-WhatsApp "file submitted" message to the client (uses existing SOP template, Step 10).
Login tracker records date/time of login, banker name, application reference. Verification scheduler books home/office verification slots and reminds the client on WA + email. Legal & Technical tracker stores status and reports against the case. Valuation reminder with valuer details + auto follow-up. PD scheduler confirms time/date with the client; sends PD training notes (templated) by RM. Query log records every banker query with an SLA timer; assigned to RM with auto-escalation to Reviewer for "tricky" queries (per SOP). Sanction letter intake: RM uploads sanction letter; system parses key fields (ROI, charges, conditions, sanction amount).
Sanction audit (Post-Sanction, Steps 1–4): Auto-compares parsed sanction ROI / processing fee / charges against the commercials confirmed at Stage 1. If deviation > tolerance (configurable), flags Leadership immediately. Special conditions surfaced as a checklist on the disbursal screen — RM cannot mark complete without ticking each. Loans > ₹2 Cr or flagged "tricky" → auto-routes to Senior Approver for sign-off (per SOP rule).
Disbursal workbench (Disbursal, Steps 1–15): Pre-disbursal checklist: docket prep, stamp paper, notary, signed docs, PDC cheques, security cheques. "No blank cheques" rule enforced: PDC fields must be entered before being marked "collected". Auto-mail templates: security cheque confirmation, seller A/C confirmation (fresh purchase), NOI payment confirmation. Banker mail extractor: when banker replies with EMI date, account name, account number, bank, registered email/mobile, the system reads the email and auto-fills these into the case. Cheque handover log + souvenir handover reminder (within 2 days).
Loan-level record: amount, EMI date, EMI amount, account number, bank, registered email/mobile, loan account number. Auto-shares LOAN DETAILS and REPAYMENT DETAILS on the WhatsApp group (templates already defined in your SOP). Auto-pins the same details into the WA group description (so they are always the first thing visible). LOD + repayment schedule auto-request to the bank on the configured Saturday. Sync with the KUJ system once received. Monthly folder integrity check (1st of every month) — runs a checklist on each client folder, flags missing docs to RM.
This module did not exist in the SOP — and it is the single biggest revenue / retention lever once disbursal is done. The EMI engine starts the day the loan is disbursed.
Reminders to the client: 3 days before EMI — WhatsApp + email reminder with EMI amount, account, balance check nudge. 1 day before EMI — WhatsApp reminder. On EMI day — WhatsApp + SMS. Bounce / dishonour detection: if the bank notifies a bounce (parsed from email or via API where available), an immediate alert is sent to the RM and the client; recovery workflow kicks in.
Reminders to the RM and Leadership: Daily "EMIs due tomorrow" digest, grouped by RM. Weekly bounce report. Cases with > 1 bounce in 90 days → escalation list for Leadership.
Long-term retention & cross-sell: Top-up eligibility flagged after 12 successful EMIs. Balance Transfer opportunity alert if external rates drop below client's ROI by > 50 bps. Annual interest certificate auto-requested from the bank in March, auto-shared with the client for tax filing. Birthday + anniversary touch-points (WhatsApp/email) — keeps the relationship warm.
This is the brain that enforces the SOP across all stages. It works on three levels: tasks, escalations, and digests.
Tasks: Every SOP step becomes a task with an SLA (T, T+1, T+2 …). Tasks are owned by the role defined in the SOP — RM, Leadership, Reviewer, Senior Approver. Tasks appear on the owner's app + WhatsApp daily digest.
Escalations: Missed SLA by 24 hours → reminder to the owner. Missed SLA by 48 hours → notified to Leadership. Stuck > 5 days at "bank confirmation / IP discussion" → auto-escalation (per SOP rule). Loans > ₹2 Cr → Senior Approver auto-tagged at Post-Sanction.
Digests & dashboards: RM daily digest (8am, WhatsApp): "Today's tasks", "Overdue", "Client follow-ups". Leadership digest: pipeline summary, stuck cases, sanction-due-this-week, disbursal-due-this-week. Live web dashboard: filter by stage, RM, bank, product, value.
WhatsApp Business API integration (WATI / Interakt / Gupshup) — official, not phone-number-locked. Pre-approved message templates for each milestone (login, sanction, disbursal, EMI reminders, top-up, BT). Email templates for banker confirmations, seller confirmations, NOI confirmations. Group description auto-update with loan + repayment details on disbursal. Single "client view" with full conversation history per case.
Since the team currently runs on Excel + Google Sheets, this is a clean greenfield. The recommendation prioritises: (a) speed to launch, (b) low ongoing cost, (c) Indian-context fit (CIBIL / GST / WhatsApp), and (d) ability for an internal admin to make small changes without engineering help.
| Layer | Recommendation | Why |
|---|---|---|
| CRM / Pipeline | Custom build on a low-code base (Zoho Creator / Bubble) OR full custom (Node.js + Postgres) | Low-code = launch in 6–8 weeks. Full custom = better long-term fit if scale > 200 cases/month |
| Wati or Interakt (official WhatsApp Business API) | Indian players, bulk + 1:1, group messaging via business profile, pre-approved templates | |
| Document storage + OCR | Google Drive / S3 + AWS Textract or Google Document AI | Cheap storage; mature Indian KYC OCR support |
| Bureau / KYC | CIBIL bureau pull via Surepass / Signzy / Karza | Aggregator APIs covering CIBIL, PAN, Aadhaar, GST, Udyam in one contract |
| Bank statement parser | Perfios / FinBox / NeSL | Used by every major NBFC — accurate parsing of any bank PDF |
| Workflow / reminders | n8n (self-hosted) or Make.com | Visual rule engine — non-engineer admin can edit reminder rules |
| Email parsing | Custom Node.js worker with Gmail / Outlook API | Reads banker emails for sanction letters, EMI confirmations, etc. |
| Notifications | WhatsApp (Wati) + SMS (MSG91) + Email (SendGrid) | Multi-channel, Indian providers, low per-message cost |
| Dashboards | Metabase or Looker Studio | Free/low-cost, drag-and-drop reporting, embeds in the app |
| Hosting | AWS Mumbai (or DigitalOcean BLR) | Data residency, low latency for Indian users |
A 3-month engagement broken into three monthly milestones. Each month ends with a working, demonstrable build that Leadership signs off before the next month's invoice is raised. Nothing is left to "after launch."
Modules covered: 1, 3, 9 (Lead Capture & Pipeline, Documentation Hub, Communication & Templates)
Process mapping with Leadership, 2 RMs and Reviewer. Final spec. AWS Mumbai / Postgres / WhatsApp Business API account setup.
Replaces the Pipeline Excel sheet. Mobile-first lead capture form. Auto-assign to RM by region/product/load. Case dashboard live.
Per-loan-type checklist engine. Document portal (web + mobile). Pending-docs auto-list. "No blank forms" rule.
WhatsApp Business API live (Wati / Interakt). Auto-create client WA group, auto-share checklist, "file submitted" template. M1 demo + sign-off.
Modules covered: 2, 4, 5, 8 (Eligibility & Bank Matching, Bank Submission & Sanction Tracker, Sanction Audit & Disbursal Workbench, Follow-up & Reminder Engine)
CIBIL pull (Surepass / Signzy). Banking statement parser (Perfios / FinBox). GST API. Eligibility engine + bank matcher. Auto-escalation if commercials not confirmed by T+4.
Login tracker, verification scheduler, legal & technical tracker, PD scheduler, query log with SLA timer, sanction letter parsing.
Auto-compare parsed sanction vs commercials. Loans > ₹2 Cr auto-route to Senior Approver. Disbursal checklist, PDC, NOI, banker mail extractor.
Every SOP step becomes a task with SLA. Auto-escalations (24h / 48h / 5 days). Daily 8am RM digest on WhatsApp. M2 demo + sign-off.
Modules covered: 6, 7 + analytics & polish (Post-Disbursal Loan Book, EMI & Repayment Engine, dashboards, training)
Loan-level record (EMI date, account, registered email/mobile). Auto-share LOAN DETAILS + REPAYMENT DETAILS on WA group. LOD auto-request. KUJ sync. Monthly folder integrity check.
T-3 / T-1 / T-0 EMI reminders to client. Bounce detection. Top-up flag after 12 EMIs. BT alert (> 50 bps drop). Annual interest certificate auto-request. Birthday / anniversary touch-points.
Leadership dashboard (pipeline, stuck cases, lender mix, RM scorecard, bounce report). Metabase / Looker Studio embeds. Final security review & VAPT.
3 days structured UAT. 2 days on-site training (Leadership + all RMs + Reviewer). Data migration from Excel. Soft launch on real cases. Handover docs + admin guide.
All figures in Indian Rupees · GST applicable as per current law · pricing valid 30 days from issue.
| Milestone | Deliverable trigger | Amount | GST | Total |
|---|---|---|---|---|
| Month 1 · Foundation | CRM + Document Hub + WhatsApp groups + templates live & signed off | ₹ 2,00,000 | ₹ 36,000 | ₹ 2,36,000 |
| Month 2 · SOP Enforcement | Eligibility + Sanction tracker + Disbursal workbench + Reminder engine signed off | ₹ 2,00,000 | ₹ 36,000 | ₹ 2,36,000 |
| Month 3 · EMI & Launch | Loan Book + EMI Engine + dashboards + UAT + training + go-live | ₹ 2,00,000 | ₹ 36,000 | ₹ 2,36,000 |
| Total | ₹ 6,00,000 | ₹ 1,08,000 | ₹ 7,08,000 |
Est. third-party cost at 200 cases/month: ₹15,000–₹30,000/month. We help negotiate volume rates at no extra cost.
By signing, both parties confirm acceptance of scope, monthly deliverables, timeline and commercial terms. Variations require a written change order signed by both parties.
The same SOP roles continue. What changes is the surface they work on — a single app with role-aware queues.
| Risk | Impact | Mitigation |
|---|---|---|
| Bank email formats vary; parser may miss fields | EMI / loan details captured incorrectly | Manual override + RM verification step before "loan live". ML parser improves over time. |
| WhatsApp Business policy on group automation | Some group actions may need manual confirmation | Use 1:1 templated messages where group automation is restricted; group description updates are allowed. |
| Adoption resistance from RMs used to Excel + WhatsApp | Low utilisation, double-entry | Phase 1 mirrors current behaviour exactly. Mobile-first. Leadership to enforce "if it isn't in the system, it didn't happen". |
| CIBIL / bureau API costs per pull | Unit economics on small loans | Use a pull-only-on-confirmation rule + monthly volume contract with Surepass / Signzy. |
| Data security (financial documents, PAN, Aadhaar) | Compliance / reputation | AWS Mumbai, encryption at rest + in transit, role-based access, audit logs, periodic VAPT. |
The platform's value will be measured against the targets below.
Target: 30–40% reduction in 6 months
Target: +10 percentage points
Target: 2x within 12 months
Target: < 5% of total tasks
Target: near zero
Target: > 70% (proxy for client engagement)
Target: net new revenue line within 6 months of go-live
Once Phase 0 is signed off, the team will see Phase 1 (Pipeline + Document Hub + WhatsApp templates) live within 6–8 weeks.
Quick reference so the team can see exactly which module owns each existing SOP step.
| SOP Sheet | Steps | Owned by Module |
|---|---|---|
| Sales Enquiry | 1–6 (client meeting, details, WA group, checklist, pipeline entry) | Module 1 |
| Sales Enquiry | 7–10 (follow-ups, eligibility, CIBIL/banking/GST) | Module 2 + Module 8 |
| Sales Enquiry | 11–15 (bank confirmation, commercials, transfer to ongoing) | Module 2 |
| Documentation | 1–10 (pending docs, bank form, login, file submission, group update) | Module 3 + Module 9 |
| Sanction Process | 1–15 (login, verifications, valuation, PD, queries, sanction letter) | Module 4 + Module 8 |
| Post-Sanction | 1–4 (conditions, ROI check, commercials, disbursal date) | Module 5 |
| Disbursal | 1–15 (docket, stamp papers, signing, PDC, NOI, banker mail, handover) | Module 5 + Module 9 |
| Post-Disbursal | 1–6 (loan details, group description, LOD, KUJ sync, monthly folder check) | Module 6 + Module 7 |
| — | EMI reminders, top-up, BT, anniversary touch-points | Module 7 (NEW) |
Your SOP is unusually well-defined for a brokerage of this size. That is the single biggest reason this automation is feasible at all — most teams need 6 months just to write down what they do. You have already done that work.
What is missing is enforcement. This proposal turns a good SOP into a system that runs itself, lets the team scale without losing control, and quietly opens up a post-disbursal revenue stream that today is being left on the table.
Happy to walk through this.
LoanFlow OS · End-to-End Loan Process Automation Proposal
Proposed by Vaishnavi Bhardwaj · 27 April 2026 · Confidential