Skip to content
GullySales

Home loan providers · CRM

Hold one record for each borrower, from first enquiry to the last EMI.

A CRM for a home loan provider is the system that records each enquiry, document, call and file stage in one place, whatever the source. GullySales works on the fields, the stages and the handover rules so that branch, DSA and website enquiries land in the same record.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

Realistic editorial illustration of banks at work in India

What CRM means

A CRM is the record where every enquiry, call and quote is kept against a customer, replacing separate notebooks, spreadsheets and memory. GullySales sets up or cleans an existing CRM and reports from it by enquiry outcome rather than by activity logged.

Last updated 14 Nov 2026. Rules for this trade differ by state and professional body, and they change. We describe restrictions in general terms, so check the current position with your own council or adviser before you publish anything.

For home loan providers

Where it usually goes wrong, and what we would do.

  • “Files live in separate heads”

    A branch officer remembers one file, a DSA remembers another, and the website form sits in an inbox. When someone leaves, the file goes with them. A shared record outlives any one person.

  • “Stages are the product”

    A home loan has recognisable stages: enquiry, documents, login, valuation, legal check, sanction, disbursal. A CRM that mirrors these lets a manager see where files wait, not only how many exist.

  • “Partners need a view too”

    A builder's sales head asks where a buyer's file stands. A broker asks the same. A limited view or a regular answer from a named officer stops the chasing calls that eat branch time.

  • “Existing borrowers are the next lead”

    A borrower three years into repayment may want a top-up or a transfer to another property. The record should mark consent and loan history so the next offer is made with care and rules respected.

What we do

What we deliver for home loan providers.

The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.

  1. Field and stage design

    The fields on an enquiry, the stage names and the exit reasons, agreed with branch, credit and operations staff.

    Result: Branch, credit and operations staff name each stage the same way.

  2. Source and duplicate rules

    How a branch, DSA and website enquiry from one borrower are matched to a single record, and who owns it.

    Result: The same borrower is not logged as three people.

  3. Partner tagging

    A field for the builder, project and broker linked to each file.

    Result: You can list files by builder and project.

  4. Stage reminders

    Prompts for the officer when a file is waiting on a document or on the borrower, with an owner on each.

    Result: No file waits without a named person.

  5. Consent and history fields

    Clear fields for permission to contact and for the borrower's loan history, for top-up and transfer outreach.

    Result: Outreach to existing borrowers has a recorded basis.

How the result is measured

  • Enquiries logged in the CRM
  • Data completeness
  • Reports generated from CRM data

Recorded as a baseline before work starts, so every later report has an honest comparison.

Fields worth keeping

Fields a home loan file needs beyond what the loan system already holds.

The loan system tracks accounts. These fields track the person and the partner behind the file, and sit beside it.

Borrower type
Salaried, self-employed, balance transfer, plot or construction, set by the officer on the first call. It routes the file to the right checklist and reports.
Source and introducer
Builder, broker, branch walk-in or online, with the name of the person who sent the buyer. The sales head uses it to see which partners bring files that reach sanction.
Project or property
The project name and unit for the flat, or the plot details. The credit team checks that against the approved list before the officer spends time.
Documents received and missing
Ticked by the officer or the document executive as papers arrive. It drives the reminder message and tells the borrower what is pending.
Stage and reason for any pause
Login, valuation, legal check, sanction or disbursement, updated by the officer holding the file. A reason such as awaiting the builder stops the file looking abandoned.
Consent and last contact
The date and mode of consent, and the last call or message. It stops the same buyer being rung twice and keeps messages within what was agreed.

Who it is for

This is written for these home loan providers.

  • Housing finance companies with a regional footprint
  • Banks' home loan desks and retail branches
  • Lenders focused on salaried first-time buyers
  • Affordable housing lenders serving self-employed borrowers
  • Home construction and plot loan specialists
  • Balance transfer and top-up focused lenders
  • Lenders with builder and project tie-ups
  • NRI home loan desks

Before you decide

When this may not be the right fit.

  • The credit team keeps files in a tool nobody else can see, so a second record would only drift out of date
  • Officers will not enter stages on the day they happen, so the record would show last week's file

Before you decide

Agree the work. Know how to judge it.

CRM for home loan providers: use these checks to prepare, choose the scope, and review what changes.

Bring the right evidence

List the records your team uses and show how an enquiry becomes an order today. Bring examples of duplicate entries, missing owners, and reports that require manual correction.

Make the scope clear

Agree the stages, required fields, access roles, and integrations before configuring the system. Separate software subscriptions from setup, data work, and training.

Check the work in use

Ask the people who will use the CRM to complete a real handover and find the next action without help. Check that the management report can be traced back to individual records.

Know when to change course

If the process is unclear, buying a more complex CRM adds more places for confusion. Start with the minimum fields and rules the team can use consistently.

These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.

Before we start

What to have ready before the work starts.

The records, access and decisions this work needs from home loan providers. Anything missing is noted in the written scope, with who will supply it.

The present register, however untidy
The spreadsheet, notebook or system where files are tracked now. It does not need cleaning. We read how people actually record things, and without it, the stages we design describe a process on paper rather than the one your team follows.
A named owner for the CRM
One person in sales or operations who decides on fields, stages and access after we leave. It cannot be us. Without an owner, every request becomes an argument, and the setup drifts back to separate spreadsheets within a season.
The list of users and what each may see
Branch officers, credit staff, managers and any partner users, with the files each may open. Compliance should read the list. If it is missing, we limit access to the strictest setting and loosen later, which slows the first days.
Your data protection and retention position
Where borrower data may be stored, who may export it and how long it is kept. Your adviser decides, and we follow. Without a position, we build nothing that moves personal data and the migration stays small.
Time from two officers for testing
Two officers who will use the system, available while the test copy is built. They should be people who forget nothing and complain freely. Without them, the testing is done by us, and the surprises arrive on the day you switch over.

How it works

How the CRM work runs

The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.

  1. 1

    Trace one file from enquiry to sanction

    We follow a real file, with names hidden, through every hand it passes: the officer who took the enquiry, the person who collected documents, the valuer, the legal reviewer and the sanctioning authority. You tell us where each stage is recorded today, perhaps a spreadsheet, a notebook or the core system. What exists afterwards is a stage map that is yours, not a template.

  2. 2

    Decide the fields and the stage names

    With sales and credit together we choose the few fields each stage needs and the words your team uses for the stage, such as login, valuation raised or legal pending. You decide who may change a stage. We cut any field that nobody would read, because every extra box is a reason for an officer to skip the screen.

  3. 3

    Set source, duplicate and partner rules

    A borrower may arrive from a builder desk, ring the call centre and fill the web form. We write the rule that merges these and keeps the first source, and the rule for tagging a builder or broker on each file. You decide whose name appears when two partners claim one buyer. The rules are tested on last year's files.

  4. 4

    Build in a test copy and load sample files

    The configuration is made in a test copy of the CRM with a small set of old files loaded. Officers click through a day's work and tell us what is slow, missing or confusing. You approve changes. Nothing touches live data until the officers who will use it say the stages match how they work.

  5. 5

    Run reminders and consent fields through checks

    We switch on stage reminders, such as a pending document or a valuation without a report, and test that each reaches the officer who owns it. The consent and history fields are checked with your compliance lead. You decide who may see borrower histories. Any rule that fires wrongly is corrected in the test copy first.

  6. 6

    Switch over and read the first reports

    Live files move in the order you decide, with the old register kept read-only for a while. We sit with the officers during the first days of use. Then we compare the stage counts with the numbers recorded before: files logged, files stuck at documents and files moved to sanction. You decide who owns the system and its rules.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales management. A target, a review routine and someone who owns the number.

  1. Step 1

    Sales audit

    Find where deals are being lost and what to fix first.

    Start here if you cannot say where orders are lost.

  2. Step 2

    Sales process design

    One written way to sell, from first enquiry to repeat order.

    Start here if every salesperson sells differently.

  3. Step 3 · you are here

    Sales management

    A target, a review routine and someone who owns the number.

    Start here if the team has targets and no routine.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

Do we need a new CRM?
Not always. Your loan origination system may already hold the file. The question is whether enquiries and partner sources are recorded before login. We add a light layer in front, rather than replacing what works.
How do we keep borrower data safe?
Follow your own data policy and the rules that apply to lenders, which differ and change. Restrict who sees what, log access and keep documents inside the lending system. Check particulars with your compliance and security heads.
Will staff actually use it?
Only if it saves them work. We build the fields around the questions they already answer, use their stage names and remove entries nobody reads. A field no one uses is a field we delete.
Should partners be able to log in and see their buyers' files?
Give a partner only the stage and the missing-document list for the buyers they introduced, never income details or the credit decision. They stop calling for updates, and borrower data stays with those who need it. Agree the view with your compliance officer.
Can we keep using our core banking or loan origination system?
Yes. A CRM here tracks the sales journey before and around the loan, while the core system holds the account itself. We map which system owns which fact so the same figure is not typed twice, and decide whether the two are connected by a feed or kept separate. Your IT team or the system vendor makes any connection, since they hold the keys. We design the stages and fields and tell you what to ask them for.
What happens if officers refuse to update it?
We treat that as information about the design, not a failing in the officers. We ask what the screen costs them in time and which field they find pointless, then remove or move it. The sales head also needs to read reports from the CRM in review meetings, because files absent from the system should not be discussed. If officers see that the record is what gets read, they keep it up.
How much does it cost?
There is no price list, because the work differs by business. The fee is scoped after we have read your brief and spoken to you, and put in writing before anything starts, split into our time, your media spend and production.
How long is the contract?
The term is agreed in writing after we have spoken, along with the fee and the reporting. It is never a default twelve months, and renewal is decided on the numbers against the baseline recorded at the start.
How soon will we see results?
It depends on the trade, the channel and what is already in place. After we have read your brief and spoken to you, we say what we would expect to move first and how it will be measured against the baseline. Nothing here is guaranteed.
Who will actually do the work?
The person you speak to before anything starts. We work from one office in Nagarbhavi, Bengaluru, with no account managers in between.

Your next practical step

Tell us what you are trying to grow, and we will read it before we call.

Eight short steps, mostly taps. Skip anything you would rather answer on the call.