BPO, KPO and contact centre companies · Buyer persona
Know who starts the search, who checks the risk and who signs.
A buyer persona for a BPO, KPO or contact centre company describes the people at a client who start, assess and approve an outsourcing move. GullySales works on writing them down from your own wins and losses so each page and call speaks to the right person.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

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.
Also for BPO, KPO and contact centre companies
- Digital marketing for BPO and contact centres
- Lead generation for BPO and contact centres
- SEO for BPO and contact centres
- Social media marketing for BPO and contact centres
- Content marketing for BPO and contact centres
- CRM for BPO and contact centres
- Follow-up systems for BPO and contact centres
- WhatsApp for BPO and contact centres
Sales and marketing for BPO, KPO and contact centre companies, the overview.
Last updated 14 Nov 2026.
For BPO, KPO and contact centre companies
Where it usually goes wrong, and what we would do.
“The operations head wants the problem gone”
This person has a backlog, a missed target or a quality complaint. They need a vendor who understands the process and can start a pilot without a long build.
“The finance head wants a predictable cost”
They ask how pricing works, what is included and what changes if volume moves. Vague answers on cost slow the deal.
“The legal and security reviewer wants clean answers”
This person checks data handling, recording consent, access controls and exit. A vendor that has written it down gets through faster.
“The procurement lead wants comparison”
They need a comparable document pack, references with permission and a clear commercial structure.
What we do
What we deliver for BPO, KPO and contact centre companies.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
Four written personas
Operations, finance, legal and security, and procurement, with questions and fears. Each covers the role, what the person is judged on, what they read, whom they trust and the question they ask first and last.
Result: Your team knows the person on the call.
A message map
What to lead with, what proof to offer and what to avoid for each persona. For each persona it sets the sentence the page leads with, the proof offered next and the document sent after the call.
Result: Each page speaks to a reader.
A question bank from past pilots
The questions raised at each stage, grouped by role. Questions are grouped by role and stage, so the sales head knows which one a legal reviewer will ask during a pilot.
Result: New deals start from what you already know.
A stakeholder map
A sheet to record who is involved at each prospect. It marks who started the search, who checks risk, who holds budget and who signs, and records the person who is missing from the conversation.
Result: You can see who has not been met.
A review against lost deals
A check of what the lost prospects asked and what was missing.
Result: Personas follow real decisions.
A first-time founder persona
A small business owner moving a back-office task to a vendor asks who will pick up the phone, what happens when a key person leaves and whether the vendor is too large to care. Written plainly, this persona changes how the first call opens.
Result: The first call opens with the founder's questions.
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
The roles in an outsourcing decision and what each wants answered.
- Head of operations with a stretched team
- Wants to know how a process is handed over and who they will speak to when it breaks. Asks about team structure and escalation.
- Finance head reviewing cost per task
- Wants a clear pricing model and what falls outside it. Asks what changes when volume rises or falls.
- Information security reviewer
- Wants access control, device rules and the recording policy in writing. Will not progress without a written answer.
- Procurement lead comparing vendors
- Wants a standard format to compare scope, terms and references. Asks for the same documents from every vendor.
- Founder outsourcing for the first time
- Wants to know what to prepare and whether a small account matters to you. Asks on WhatsApp before email.
Who it is for
This is written for these BPO, KPO and contact centre companies.
- Voice and non-voice BPO providers
- Inbound and outbound contact centres
- Back-office and data processing providers
- Knowledge process outsourcing for research and analytics
- Finance and accounting outsourcing
- Collections and customer service outsourcing
- Chat, email and social support providers
- Healthcare and insurance claims processing
- Multilingual and regional language support teams
Before you decide
When this may not be the right fit.
- You win every deal through one existing relationship, so there is no buyer research to act on yet.
- You have no record of why past deals were won or lost, so profiles would rest on guesses.
Before you decide
Agree the work. Know how to judge it.
Buyer personas for BPO and contact centres: 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 BPO, KPO and contact centre companies. Anything missing is noted in the written scope, with who will supply it.
- Proposals, call notes and decision emails
- A set of past proposals and the correspondence that decided them, with names removed if you prefer. They show who raised which concern. Without them the sheets rest on memory, and each carries a note saying so. Add the stage reached by each bid and the date it ended, so we can see where each role comes in.
- Introductions to clients and lost prospects
- A few people you are comfortable asking, including at least one who chose another vendor. Personal introductions get honest answers. If you cannot arrange any, the sheets rely on your files and are marked as less certain. Say also which of them will speak plainly about a lost deal, and we approach those first.
- A list of deals that stalled, with the reason
- Deals that went quiet at a security review, a price discussion or a procurement round, with what you know of why. These show where each role blocks. If the reason is unknown, we say so and ask the sales head to guess in writing. Add also deals that moved fast and the reason, since speed is as informative as delay.
- A decision on confidentiality for the notes
- Your instruction on which files we may read and whether names appear in our working notes. They never appear in the final sheets. If no decision is made, we work only from documents with names removed. Say also whether notes from personal calls may be used, and whether anyone at the buyer asked for confidentiality.
- Time from the sales head to review
- An hour set aside to read each persona and mark what is wrong. The sales head knows these people better than we do. Without a review, the sheets stay as our reading of the files and carry a note that nobody at your company has confirmed them. If the sales head cannot spare an hour, a shorter call can do, and unreviewed sheets stay marked as drafts.
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
Name the roles that matter in a deal
We agree with the sales head which people at a client company to write up: the operations head, the finance head, the legal or security reviewer, procurement and, for smaller buyers, the founder. You say which role has stopped the largest number of deals, so we begin there. We also ask which role was missing from the room when a deal was lost, since that is the person we are least likely to know.
- 2
Pull the files from won and lost bids
We read proposals, meeting notes and email threads from past deals, noting who asked what and at which stage. The sales head tells us which deals to treat as typical. Confidential names are removed before we begin. Names, volumes and prices are removed before the files reach us, and we keep a short note of what was removed.
- 3
Speak with buyers or former buyers
With your introduction, we hold short conversations with a few current or past clients and, if possible, one that chose another vendor. We ask what triggered the move, what they feared and who had the last word, and we promise no quotes with names. We also ask what they would tell a colleague who was thinking of choosing you, and note the words they use.
- 4
Compare their words with your file notes
We set what buyers told us beside what your files say, marking where the reasons given at the time differ from the reasons given now. The sales head reviews the differences and tells us which one rings true. We also write down where the sheets disagree with the way your sales team talks about buyers now.
- 5
Write each persona and the questions it asks
We write one sheet for each role: what they want solved, what they fear, the document they ask for and the question they ask first. You and the sales head correct each, and any line that reads as a stereotype is rewritten. Each sheet also names the document that role asks for, such as the security summary or a sample report, so the team can have it ready.
- 6
Test the sheets against the next live deals
We give the sales team a short guide to using the sheets in calls and proposals, then read the next live deals against them. You decide which sheet to change, judged by where deals actually stalled. We also note which sheet predicted the stall and which did not, so the next round of changes rests on evidence.
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.
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.
Do small and large buyers need different personas?
Who really decides?
How do we learn what they fear?
Who in the buying company really decides?
Do we need a persona for the buyer's customer?
How do small-company founders differ from large-company buyers?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
More for BPO, KPO and contact centre companies
Related work to consider.
Closest to this: strategy and research
Also for BPO, KPO and contact centre companies
Or start from the overview: sales and marketing for BPO, KPO and contact centre 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.