Banks · Churn analysis and reduction
Find out why the salary account went quiet before the customer closes it.
Churn analysis for a bank looks at why account holders close accounts, let deposits mature without renewal, move their salary or repay a loan early and leave. GullySales reads your account records, speaks with customers who left, and hands your branches a cause map and a list of accounts showing the same signs.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What churn analysis and reduction means
Churn analysis and reduction examines why customers stop buying or renewing and identifies changes that address those causes. GullySales reviews your customer records, tests the reasons through conversations with recent leavers, and hands your team an evidence-backed cause map, an at-risk customer list, and specific corrective actions.
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 banks
Where it usually goes wrong, and what we would do.
“Closure is the end of a long quiet period”
A customer rarely closes an account on the day they decide to leave. The salary credit moves first, then the card use falls, then the balance drains, then the account is dormant, and only later does a closure form appear. By the time the branch notices, the relationship ended some time before. Analysis looks for the early signals in your own records so that a banker can ask a question while the account is still active.
“Different products leave for different reasons”
A fixed deposit holder who does not renew, a home loan customer who transfers the loan to a rival, and a savings customer who opens an account elsewhere are three separate problems. One average figure for the whole bank hides all of them. We separate departures by product and by customer type, such as salaried, retired, small trader or student, because the reason and the remedy differ for each.
“The stated reason is not always the real one”
A customer who closes an account tells the counter staff 'I am moving house' or 'no particular reason'. A conversation weeks later may reveal a long queue, an unexplained charge, a failed transfer that was never resolved or a rival's better mobile app. Branch exit forms capture the polite answer. Real reasons come from direct, careful conversations with recent leavers, carried out with their consent.
“Retention offers can cost more than they save”
A branch rushes a rate concession to every customer who asks to close, including those who would have stayed, and those who never held a profitable relationship. Analysis separates the customers worth a personal call from those for whom the cause is a process fault the bank can fix for everyone. Pricing decisions remain with your product and risk teams; we show them who is leaving and why.
What we do
What we deliver for banks.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
Definition of a lost customer by product
A written agreement of what counts as leaving for each product: an account closed, a salary credit stopped, a deposit not renewed, a loan foreclosed to another lender, a card unused. Without a shared definition, branches count different things and the totals cannot be compared. The definitions are approved by your own product heads.
Result: Each product has one written definition of departure that every branch applies.
Departure timeline from your records
For a sample of accounts that closed or went dormant, a timeline showing the sequence of events before the departure: last salary credit, last card use, last branch visit, complaints raised, product changes. The pattern shows which signs appear first and how long the gap between sign and closure was for each product.
Result: A named list of early signs exists for each product, drawn from your own account histories.
Conversation findings from former customers
Notes from structured conversations with customers who left, conducted by phone or at the branch with their agreement, using an agreed question list and no sales pitch. Findings are grouped into causes and written without names. Customers who decline are not contacted again, and your compliance team approves the question list.
Result: Each cause on the map is backed by what former customers said, not by branch opinion.
Cause map ranked by product and segment
A one-page map linking each cause to the products and customer groups it affects: slow service, fees not understood, an app that failed, a rival's offer, a life event. Each cause is marked as one the bank can fix, one it can soften or one outside its control. Ranking uses your own counts, never a general benchmark.
Result: The three causes that weigh heaviest for each product are named and marked as fixable or not.
At-risk account list with a call guide
A list of live accounts showing the early signs found in the timeline, passed to the relevant branch or relationship manager with a short guide on how to open the conversation. The guide asks about the customer's needs and does not read like a retention script. Branch staff decide whom to contact.
Result: Each branch receives a named list of accounts showing the agreed early signs.
Corrective action list with owners
A list of the changes that address the main causes: a clearer fee notice, a faster transfer resolution step, a maturity reminder, a different onboarding call. Each action names a department owner and a way to see whether it worked, using the same departure definition recorded at the start, with decisions left to your management.
Result: Every corrective action has a named owner and a measure taken from the original definition.
How the result is measured
- Customer loss and revenue loss against the agreed baseline
- Chosen departures compared with unattended lapses
- Departure patterns by account group and acquisition source, where recorded
Recorded as a baseline before work starts, so every later report has an honest comparison.
Who it is for
This is written for these banks.
- Private sector bank branches
- Public sector bank branches
- Regional rural banks
- Cooperative banks
- Small finance banks
- Business correspondent networks
- NRI-focused branches
- MSME-focused branches
Before you decide
Agree the work. Know how to judge it.
Churn analysis and reduction for banks: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
Review repeat orders, inactive customers, and reasons for leaving. Separate a normal buying interval from a customer who stopped because of an unresolved problem.
Make the scope clear
Choose the customer group and the reason to contact them. Agree how complaints, renewal decisions, and additional offers are handled, including when a sales message is inappropriate.
Check the work in use
Track the response through to a retained or repeat order, with discounts and service costs visible. Record why the customer returned rather than crediting every repeat purchase to the campaign.
Know when to change course
If customers leave because delivery is unreliable, fix that before offering a loyalty reward. Repeated promotions can hide the cause without improving the experience.
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 banks. Anything missing is noted in the written scope, with who will supply it.
- Closed and dormant account export
- A list of accounts closed, gone dormant or not renewed, with product, branch, opening date and customer type, and with personal identifiers removed. Churn analysis depends on this list. If records exist only in branch registers, a sample of those registers is enough to begin, though the findings then rest on a smaller base.
- Your data protection and consent rules
- The policy on using customer data for analysis and on contacting former customers. Conversations with leavers need your compliance team's agreement on who may be approached and how. If the policy is unclear, we pause the conversations and work from records only, until your adviser confirms the position.
- A branch manager who knows the customers
- One person from a busy branch who can read a timeline and say whether it looks right. Records show events, but a manager recognises that a closure followed a dispute or a loan top-up refusal. Without this person, our reading of the records is a guess.
- Complaint and service logs
- Whatever record exists of complaints, failed transactions and service requests, even if it is a register or a shared sheet. A large share of departures follows an unresolved problem, and the log lets us see whether one preceded a closure. If none is kept, tell us, since that gap is itself a finding.
- A decision on who owns the follow-up
- The person with authority to act on causes, and the person who will pass at-risk lists to branches. Analysis without an owner becomes a report. If pricing or process decisions sit with different heads, name both before we begin, so the corrective actions land with someone.
How it works
How the churn analysis and reduction 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
Agree what leaving means for each product
We start with your product heads and decide, in writing, what counts as a customer lost for savings, salary, fixed deposit, loan and card relationships. The same word means different things in different branches, so the definition is fixed before any count is made. This also becomes the yardstick we use to read the result at the end.
- 2
Pull the departure records you can share
Your team supplies an export of closed, dormant and non-renewed accounts with product, branch, opening date and customer type, with names removed or masked as your data protection rules require. We do not need passwords or direct system access. Where a field is missing, we say so, and the cause map states what it could not cover.
- 3
Rebuild the months before each departure
For a sample from each product we line up the events preceding the departure: salary credits, transactions, visits, complaints and product changes. The timelines reveal the order of the early signs and which accounts show them while still open. Your own staff check a few timelines against what they remember of the customer to confirm the records read correctly.
- 4
Speak with customers who have left
With your compliance approval and the customer's agreement, we hold short, neutral conversations using a fixed question list. We ask what changed, what they compared and what would have kept the account open. Notes are anonymised. Customers who decline or do not answer are left alone, and no conversation turns into an offer unless your bank has authorised one.
- 5
Build the cause map and the at-risk list
We set what customers said beside what the records show, and rank causes within each product. Accounts that show the early signs go to the relevant branch as a list, with the call guide. Your management decides which causes to act on first, since some involve pricing, technology or policy beyond the branch's authority.
- 6
Read results against the first definition
After the bank has acted on some causes, the departure definition and counts recorded at the start are used again on the new records. We compare the same products and branches, say what moved and what did not, and mark where the effect cannot be separated from other changes such as a rate revision or a competitor's launch.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales process design, at stage 7, after the sale. The audit comes before it, and sales management keeps it running.
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.
Step 2 · you are here
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3
Sales management
A target, a review routine and someone who owns the number.
Start here if the team has targets and no routine.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
How do we reduce customers leaving our bank?
Can you contact our former customers directly?
Do you need access to our core banking system?
Is dormant the same as churned?
Will you recommend discounts or rate changes?
How do we know the work made a difference?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
From the blog
Further reading for banks.
6 min read · 6 Oct 2026How buyers decide which lender or adviser to trustPeople choosing a bank, lender, adviser or insurer start with a name someone gave them, then check you before calling. See what they look for.
7 min read · 21 Sept 2026How to advertise to airport travellersA terminal is a small number of regular flyers counted many times, and the crowd changes completely between the six o'clock bank and the summer holidays.
6 min read · 29 Jan 2026Local search for a financial services office: profile, reviews and what you can sayHow a financial services office can set up its Google Business Profile, ask for reviews and reply to them without breaking client confidentiality.
More for banks
Related work to consider.
Closest to this: customers after the sale
Also for banks
Or start from the overview: sales and marketing for banks.
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.