Skip to content
GullySales

Microfinance companies · CRM

Move groups, villages and officer promises out of diaries and into one shared record.

A CRM for a microfinance company is a shared record of villages, groups, leaders and leads that survives when an officer is transferred. GullySales sets up the fields, the stages and the habit of entering them, and keeps loan accounts and collections in your own core system.

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

Microfinance institutions: show a real physical business scene illustrating Members, groups and centres. Record each member inside her group and centre, so member dues and the group total are worked from identical entries and never adjusted by hand.

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 microfinance companies

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

  • “The diary is the company's memory”

    Every village's history sits in an officer's notebook. When the officer leaves, the new one starts as a stranger. A CRM keeps the leader's name, the last visit and the promise made.

  • “Marketing records must stay apart from loan records”

    Credit data and repayment history belong in your lending system under its rules. The CRM holds only the sales side, such as groups interested and visits planned, so it never becomes a second loan book.

  • “Entry must work on a phone with weak signal”

    An officer will not type in a long form at a village gate. Few fields, local-language labels and the ability to save offline decide whether the record is used at all.

What we do

What we deliver for microfinance companies.

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

  1. Field and stage design

    A short list of fields and stages from first contact to group formed, built with your officers.

    Result: The record matches how the field actually works.

  2. Village and leader records

    Each village with leaders, groups, rival lenders noted and the last visit.

    Result: A transferred officer picks up where the last one stopped.

  3. Lead and reason-lost log

    A place to note why a group did not form, in the officer's own words.

    Result: The company can read the reasons, not guess them.

  4. Repeat-loan reminder list

    A list of borrowers who may be due a conversation about another loan, after your own checks.

    Result: Nobody depends on an officer's memory for the repeat conversation.

  5. Access rules and training

    Who sees what, kept to the sales side, with a short training for officers and managers.

    Result: Officers know what to enter and what to leave out.

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 an officer fills in before leaving the village.

Village and taluk
Filled by the officer at the first visit, from a fixed list. It lets the branch manager see which villages have no entry and which have three.
Group leader name and mobile
Entered by the officer at the group meeting. It lets the next officer or a transferred colleague reach the leader without asking the borrowers.
Stage: met, interested, group forming, formed, lost
One choice from a short list, updated at each visit. The branch manager reads the count at the meeting instead of asking each officer.
Reason lost
Picked from a short list: rival lender, leader declined, too few members, household refused. Over time it shows where the branch should stop calling.
Next visit date
Set by the officer before leaving. It feeds the reminder to the officer's phone and shows the manager which promised visits have not happened.
Repeat-loan conversation due
Set by the branch on the borrower's schedule, with no balance shown. It tells the officer which returning households to speak to next.

Who it is for

This is written for these microfinance companies.

  • NBFC-MFIs working through joint liability groups
  • Self-help group linkage lenders
  • Microfinance companies in rural Karnataka and neighbouring states
  • Urban microfinance for small shopkeepers and home-based workers
  • Small finance bank microfinance arms
  • Microfinance companies adding individual business loans
  • Women's livelihood and dairy-linked lenders
  • Company branches opening in a new taluk

Before you decide

When this may not be the right fit.

  • Your officers have no phone that holds a signal in the villages they cover, so entries would be made days later from memory.
  • You want loan balances and collections in the same tool, when your core lending system already holds them and should stay the only record.
  • No branch manager will read the record, which means the fields would be filled in once and then abandoned.

Before you decide

Agree the work. Know how to judge it.

CRM for microfinance companies: 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 microfinance companies. Anything missing is noted in the written scope, with who will supply it.

Branch registers of groups and leaders
The registers are the source for the first load. They may be handwritten, as long as they can be read. Where a branch has no register, the officers dictate and a clerk writes, and that branch begins with fewer records.
A decision on where loan data stays
Confirm in writing that loan accounts, balances and collections remain in the core system and are not copied to the CRM. We configure access around that. Without it, we default to keeping the record to marketing and visit information only.
One officer from each region as a tester
Pick one officer per region who will tell us the screens are wrong. They test on their own phones. If an officer's phone is too old, tell us the model, and we test on it, or you supply a device.
A named owner of the record
Someone must decide the stages, remove leavers and answer questions after we leave. This is the area manager or the head of operations. When nobody is named, officers stop entering data within a few visits.
The rule for transferring an officer's villages
Tell us how a village moves when an officer is transferred, and who approves. The record follows that rule, so the new officer inherits the history. If no rule exists, we draft one for you to approve.

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

    Draw the path from village to repeat loan

    We start with a whiteboard session with the area manager and two officers. We draw the real path: village visit, leader meeting, group formed, training, first loan, repeat loan. You say where the company loses people. The stages we agree become the record's stages, and any stage that officers do not recognise is removed before we build anything.

  2. 2

    Decide what the record holds

    With your compliance head we list the fields: village, leader, group, lead source, next visit, reason lost. We write down what stays out: loan balances, collections, Aadhaar and other identity details, which remain in your core system. You approve the list. A shorter list is entered more reliably than a long one.

  3. 3

    Set it up and test on an officer's phone

    We build the record in the tool you choose and test it on the phone an officer actually carries, over a weak connection. The screens use the local language. An officer enters a visit in front of us, and we count the taps. Whatever takes too long is cut, since a record that is slow gets filled in at night from memory.

  4. 4

    Load the villages and the leaders

    We bring in the village list, the leaders' names and the groups from the branch registers, which the branch clerks check page by page. You decide whether old leads are brought in or only current ones. Names enter only with the fields agreed in the second step, and the clerks sign off each branch before officers see it.

  5. 5

    Train the branch with its own data

    We hold a short session at each branch using that branch's own villages, not a demonstration set. Officers enter a real visit, correct a mistake and find a village. The manager sees the dashboard for the branch. We write a one-page guide in the local language and leave it on the branch wall.

  6. 6

    Switch over and read the first report

    On a date you set, the diary stops and the record starts, and the area manager reviews the first report with us. We compare the number of villages, leaders and groups on the record with the old registers. You decide who owns the record and who may change the stages. We report what the record shows and promise no growth.

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 new software?
Not always. Your core lending system may allow a sales module, or a simple CRM may do. The choice is made after seeing your field process and your data-protection rules.
Is borrower data safe in a CRM?
Safety depends on access rules, hosting and your policy. GullySales keeps personal data to what the sales side needs and follows your data-protection instructions. Ask your own adviser about the lender's legal duties.
Will officers actually use it?
Only if it is quicker than the diary. That is why the first version has very few fields and works on a basic phone, and why branch managers read it at their meetings.
Can the CRM hold Aadhaar or KYC details?
No. Identity documents belong in your core lending and KYC system under your data-protection rules. The sales record holds village, leader, stage and next visit only. Fewer personal fields means fewer ways to lose a household's data when an officer's phone is lost.
Can officers keep a paper diary alongside the CRM?
For a short period, yes, because switching all at once is hard on someone who has kept a diary for years. After the agreed switch date the record is the only place that counts, and the area manager reviews from it alone. Two records drift apart within days, and the officer then enters nothing in either. We set the switch date with you in the last step and ask the manager to stop accepting diary pages as updates after it.
What happens to the data if we change the software later?
You can take it with you, because the fields are plain and exportable and the data belongs to the company. We keep the field list and the stage list in a document that does not depend on any tool, so a new system can be set up from it. Before choosing the tool we check that it exports to a spreadsheet and that your company, not GullySales, holds the administrator login.
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.