Fintech companies · CRM
Keep one record for the user in KYC and one for the bank in procurement.
A CRM for a fintech company holds two kinds of records: the user moving through onboarding and the institution moving through demo, pilot and contract. GullySales sets up the fields, stages and tags so both are visible, using the tool you already run or one suited to your size.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

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 fintech companies
Where it usually goes wrong, and what we would do.
“The product database is not the CRM”
Account events live in the product, and conversations live in the sales tool. When the two are not joined, a sales manager cannot see that a prospect's pilot users have gone quiet. Pushing a few key events into the CRM is more useful than copying all of them.
“An institution needs several contacts under one account”
The CTO, the CISO, the risk head and legal each hold a piece of the decision. A CRM that lists only one contact per bank hides who has been convinced and who has never been met.
“Consent belongs on the record”
Messages to users depend on consent and opt-out status. A CRM that stores the source, the permission and the date lets marketing send what is allowed and stop at once when a user asks.
What we do
What we deliver for fintech companies.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
A stage design for each journey
User stages from install to funded account, and account stages from first call to contract.
Result: Each person or bank sits in one visible stage.
Account and contact structure for lenders
One account per institution with every role, last conversation and open question.
Result: A new team member can read the history of a bank.
Event sync from the product
The few events that matter, such as KYC step reached, funded and dormant, passed into the CRM.
Result: Support and sales see the current state of a user.
Consent and opt-out fields
Stored source, permission and unsubscribe status for each person.
Result: A message list can be filtered by permission.
Dashboards by cohort
Counts by source, stage and cohort for both journeys.
Result: Spend and effort are judged on accounts.
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
These are the fields that keep a user's journey and a bank's pilot visible.
- KYC step reached
- Synced from the product by the engineering team. It lets support and marketing see where a user stopped without asking them to explain again.
- Consent and channel preference
- Captured at sign-up and updated when the user changes it. It decides who may be messaged and by which channel, and records the date.
- Partner lender for the user
- Filled automatically from the product. It lets a message name the right lender and keeps one lender's offer away from another's customer.
- Institution account with its contacts
- The sales owner adds the product head, risk officer and procurement contact under one account, so no one is lost when the sponsor moves.
- Pilot stage and written scope
- Updated by the pilot owner after each meeting. It shows which banks are in demo, pilot or contract, and what each agreed to test.
- Source of the first touch
- Set from the first page, ad or introduction. It lets you compare which sources bring funded accounts and which bring pilots.
Who it is for
This is written for these fintech companies.
- Digital lending apps working with an NBFC or bank partner
- Investment and wealth apps for first-time investors
- Insurance technology platforms selling policies online
- Credit score and personal finance apps
- B2B software for banks, NBFCs and cooperative lenders
- Business accounts and neobank-style apps run with a partner bank, for startups and small businesses
- Accounting, billing and expense tools for small businesses with a finance element
- KYC, collections and risk technology sold to regulated lenders
Before you decide
When this may not be the right fit.
- Your product database already holds users and you have no one to decide what the sales view should add to it.
- Your team has no rule for who may see a user's identity documents, and putting them in a shared tool would widen the risk.
- You are a young company with a few bank conversations, where a simple sheet can run the pilots until the numbers grow.
Before you decide
Agree the work. Know how to judge it.
CRM for fintech 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 fintech companies. Anything missing is noted in the written scope, with who will supply it.
- Exports from the current sheets and tools
- Every spreadsheet, address book and tool that now holds users or lenders, exported as it stands. Duplicates and gaps are acceptable. Without these, the CRM starts empty and the sales team keeps working in sheets, which defeats the purpose and splits the record the day you switch over.
- A list of product events available to send
- A note from your developers on which events the product can send out, such as account created, KYC passed or first loan disbursed. A rough list is acceptable. If events cannot be sent, stages are updated by hand, and hand-updated stages fall behind the product within days.
- The consent and opt-out rules in force
- A written statement of what each user agreed to receive and how they can withdraw, with the compliance head's name. Existing policy text is acceptable. Without it, the consent fields are built from guesswork, and outreach to users who opted out becomes possible by mistake.
- A decision on what stays out of the CRM
- A short list of the details that must remain in the product or the lender's system, such as identity numbers, bank statements and credit reports. Your compliance head decides. Without that list, staff may paste sensitive documents into notes, and we cannot remove them afterwards.
- One person to own the CRM data
- A named person with time to correct records, add fields and say no to requests. Part of a role is acceptable. If nobody owns it, fields multiply, stages drift apart and the dashboards stop matching the product after a few releases.
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
Trace both journeys on a whiteboard
We sit with your product, sales and support leads and draw two journeys: a user from install to funded account, and an institution from first call to signed contract. At each step we write what happens, who acts and what you need to remember. You decide which steps your team must see in the CRM and which belong in the product database only.
- 2
Choose the tool and the record shape
From the whiteboard we decide whether your current CRM can carry both journeys or a lighter tool will do. The user record holds the onboarding step and consent. The institution record holds an account, the several contacts inside it and the pilot status. You approve the fields before we configure anything, so nothing sensitive is added by accident.
- 3
Set up a test copy first
We build the stages, fields and views in a test copy of the CRM, with invented users and one invented lender. Your sales lead moves a few records through every stage and tells us what looks wrong. You decide whether the test copy is ready, and the live system is untouched until you do.
- 4
Connect product events and test the rules
A developer on your side sends events from the product, such as KYC submitted or first funding made, to the CRM. We test that each event moves the right record, that consent and opt-out fields travel with it, and that no sensitive document or full account detail is copied across. Any mismatch is fixed before staff are asked to rely on it.
- 5
Walk the sales and support teams through it
We run a session for each team using their own cases: a user who stopped at the selfie step, a bank that asked for a second demo. They enter, move and close records while we watch. You note who still hesitates, and we change the screens or the instructions until the team can work without asking.
- 6
Switch over and read the first cohort view
On the day you choose, the old sheets are closed and the CRM becomes the only record. We name an owner for the data and set up the cohort views for users and the pipeline view for institutions. Later we read them against the baseline captured before the switch, and you decide which stages to merge or add.
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.
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
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
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.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
Do we need a new CRM?
How do we handle sensitive financial data?
Can sales and support share it?
Which sensitive details stay out of the CRM?
Can the CRM replace the product's admin panel?
What if our bank partner wants to see our pipeline?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
More for fintech companies
Related work to consider.
Closest to this: leads and follow-up
Also for fintech companies
Or start from the overview: sales and marketing for fintech companies.
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.