Skip to content
GullySales

Fintech companies · Buyer persona

Describe the borrower, the investor and the bank committee in their own words.

A buyer persona for a fintech company is a written description of who is deciding and what they fear. Because the product serves users and institutions, GullySales builds separate personas for each, from your support chats, sales calls and onboarding drop-offs.

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

A fintech representative demonstrates a payment terminal to a shopkeeper

What buyer persona means

A buyer persona is a plain description of the kind of customer who actually buys from you. It includes what they search, what worries them and who else they ask before deciding. GullySales builds this from real enquiries and past sales rather than a generic template, then uses it to write every page and advert.

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 borrower fears the lender, not the form”

    A small shop owner needing working capital worries about hidden charges and harsh recovery. The persona should record that worry in the user's words, because the page and the ad have to answer it before the form.

  • “The first-time investor fears a loss they cannot undo”

    This person wants to start with a small sum and needs to hear that small is acceptable. The persona records the amounts they talk about, the people they ask and the words they use for risk.

  • “A bank has a committee, not a buyer”

    The innovation lead, the CISO, the risk head, the head of operations and legal each care about something different. A persona for each role, with the question they bring to a meeting, lets sales prepare one answer per person.

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.

  1. User personas from real conversations

    Descriptions of the borrower, investor and policy buyer built from support chats and exit prompts.

    Result: Each persona uses the user's words, not marketing words.

  2. A buying committee map for lenders

    Each role in a bank or NBFC, what they own, what they fear and what they need to see.

    Result: Sales knows who to write to about what.

  3. An objection list

    The recurring doubts in each group with the plain answer and the document that supports it.

    Result: Every common doubt has an answer on file.

  4. Channel notes

    Where each persona looks for information, such as search, WhatsApp, a friend, LinkedIn or a conference.

    Result: Spend is tied to where each persona actually looks.

  5. A persona review routine

    A check against new support tickets and sales notes so the descriptions do not drift.

    Result: Personas are revised when the evidence changes.

How the result is measured

  • Enquiry match to persona
  • Conversion rate by persona
  • Content aligned to persona

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

Who is asking

These are the people who decide, use or fear a fintech product.

A first-time borrower who is wary of the lender
Wants to know who lends the money, what happens if an EMI is late and who to ring when the app cannot answer. The form is secondary.
A small shop owner who wants a business account
Wants to know which bank holds the money, whether their accountant can see the statements and what the app does when a payment is stuck.
A first-time investor afraid of a loss
Wants to see in plain words what can go wrong and what they can withdraw, before they believe anything about the benefits.
A bank product head scouting vendors
Wants to know which institutions already use the product, how long integration takes and what the pilot will ask of the bank's own team.
A bank risk or information security officer
Wants a security paper, an audit route and the name of the person who answers the technical questions, before the product head can proceed.

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.

  • You have not read your own support chats and onboarding drop-offs, so a persona would be an opinion about users.
  • Your product has only one audience at present, and one persona already holds what you need.
  • You plan to profile users using data they gave for another purpose, which consent and data rules may not allow.

Before you decide

Agree the work. Know how to judge it.

Buyer personas for fintech companies: use these checks to prepare, choose the scope, and review what changes.

Bring the right evidence

Write the decision the research must support, such as entering a market or choosing a buyer group. Separate what you know from sales records from what the team currently assumes.

Make the scope clear

Agree which buyers to speak to, which sources to review, and what access you can provide. Include lost enquiries and people who chose another supplier, where they are willing to take part.

Check the work in use

Look for source dates, sample limitations, and evidence that disagrees with the preferred answer. A recommendation should show how it follows from the findings.

Know when to change course

Do not treat a few positive conversations as proof of demand. Test the proposed offer with an actual buying decision before committing to a wider launch.

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.

Support chats from the last few months
Chat or ticket extracts with names and account numbers removed. Messy is acceptable. They hold the fears in the user's own words. Without them, we describe a typical user from general knowledge, and a persona built that way is the stock photograph the later pages then repeat.
The reasons users gave for leaving
Any record of why users stopped during onboarding: an exit survey, a call note or a ticket. A few lines are acceptable. If none exist, we infer from the step where users stop, and an inference is weaker than a stated reason and is marked as such.
Introductions to two or three lenders
A named contact at a bank or NBFC that has run a pilot or declined one, and your permission to approach them. A phone call is enough. Without these, the lender persona rests on your own account of the committee, and your account may be kinder than theirs.
Demo and pilot objection notes
The notes your sales or partnership team kept after demos, questions from security questionnaires and reasons a pilot did not proceed. Handwritten notes are acceptable. Without them, the committee map names the roles but not the doubts each role holds.
A decision on which products to cover
A short written choice of the products the personas must cover now, such as the lending app, the investment app or the institutional software. Without it, one persona tries to describe a borrower, an investor and a bank officer together, and describes none of them well.

How it works

How the buyer persona 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

    Choose which people to describe first

    We start with a short meeting where you tell us which users and which lender roles matter first: a salaried borrower, a first-time investor, a small business owner, a bank technology head. We agree on how many personas the evidence can support, and we write down which of your products each one touches before we ask anyone for records.

  2. 2

    Pull support chats and sales call notes

    You give us support chat extracts, onboarding drop-off reasons, demo notes and the objections a bank raised after a pilot, with names removed. We read them for the exact words people use about fear, cost and trust. You pick which ten or so conversations we should hear first, because they show the user or lender you care about first.

  3. 3

    Interview a few users and a few lenders

    We talk to a small number of users who finished onboarding, some who left, and executives at lenders you have worked with. The questions cover what they were afraid of, who they asked and what almost stopped them. You make the introductions, and you can ask us to drop any person you would prefer not to approach.

  4. 4

    Check what we heard against the numbers

    We lay each finding beside the funnel and the pilot record: a fear of hidden charges should show up where users stop, and a lender's concern about data should show up in the stalled pilots. A claim that the records do not support is marked as unproven, and it stays in the document only with that mark.

  5. 5

    Read the drafts together with sales and support

    We bring the draft personas to a session with the people who talk to users and lenders. They correct what we got wrong and add the objection nobody wrote down. Support hears the sharpest version of a fear, so we ask them to read each persona aloud as if speaking to that person. You decide which corrections change a persona and which are one person's view, and the revised drafts, with the corrections marked, are what everyone then works from when writing pages and sales notes.

  6. 6

    Turn personas into a message map

    We attach each persona to the pages, messages and sales questions that follow from it, and set the baseline measures: onboarding starts, funded accounts and pilot conversations for each group. Later, we read these against the persona to see whether the description held, and you decide which persona to rewrite.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales process design, at stage 0, foundation. The audit comes before it, and sales management keeps it running.

  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 · you are here

    Sales process design

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

    Start here if every salesperson sells differently.

  3. 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.

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.

Is a separate persona needed for every product we offer?
Start with the audiences whose behaviour differs: borrowers, investors and institutions. Split further only when the questions asked are really different.
Where does the evidence come from?
From your own support chats, onboarding drop-offs, sales call notes and reviews. We do not invent demographics or quote outside statistics.
Who should read the personas?
Product, growth, support and sales. A persona kept only by marketing does not change what the product says.
Who should be in the room when we read the personas?
Support, product, sales and the compliance head. Support knows what users ask, product knows where they stop, and compliance knows what may be said to them. A persona read by only marketing repeats what marketing already believes.
How many people should we interview?
A handful per group is enough to find the main fears, and more only if the answers keep changing. For users, include both those who finished and those who stopped. For lenders, include a technology or risk person, not only the business sponsor. We also read your records, so the interviews confirm and add detail; they are not the only evidence in the document.
What if our support team is too busy to join the review?
Ask for a shorter session with one senior support person and one salesperson, not the whole team. They read the drafts and mark what is wrong. We bring the questions in a short list, so their time goes to correcting facts. A persona that skipped this review is marked unreviewed, and we treat it with caution when writing pages.
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.