B2B SaaS startups · Buyer persona
Write down who feels the pain, who approves the spend and who stops the deal.
A buyer persona for a B2B SaaS startup describes the people inside a customer company who use the product, sign for it and can block it, with the words each of them uses. GullySales builds these from your closed deals and lost deals instead of from guesses.
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.
Last updated 18 Oct 2026.
For B2B SaaS startups
Where it usually goes wrong, and what we would do.
“The user, the buyer and the blocker are three people”
The operations lead who needs the tool, the owner or CFO who pays, and the IT or security head who can stop it want different things. A pitch aimed at only one leaves the other two unconvinced.
“The last ten wins describe the persona better than a workshop”
Looking at who actually signed, what job they held and what triggered the search gives a more reliable profile than a brainstorm. The patterns in closed deals are usually plainer than the team expects.
“Lost deals show the persona you misjudged”
When a deal ends in no decision, the reason can be a missing stakeholder. Recording who was in the room and who was absent shows whom the next pitch needs to include earlier.
“A persona in a slide deck changes nothing”
If the profile is not used when writing outbound messages, naming pages or scoring signups, it is decoration. It has to appear in the CRM fields and in the first lines of the scripts.
What we do
What we deliver for B2B SaaS startups.
Every deliverable, what it covers for you, and the result it is there to produce. Nothing here is an extra.
Persona write-ups for user, buyer and blocker
One page each: job title, daily problem, words used, what they fear, what they need to see.
Result: Anyone writing for a role can see in one page what that person cares about.
Win and loss review of past deals
A sheet listing roles involved, trigger, objections and outcome for each recent deal.
Result: The persona is backed by real deals, and the evidence is listed.
Objection map by role
A list of the questions each role asks, with the best answer and the document to send.
Result: The team answers a security question with a page rather than an improvised reply.
CRM fields for roles
Fields that record each contact's role in the buying decision on every account.
Result: You can see which accounts have no buyer or blocker contact yet.
Persona-based message review
Existing website, deck and email copy checked against each persona and rewritten where it speaks to nobody.
Result: Each public page names the reader it is for.
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
A software deal has a user, a buyer and a blocker, and each asks different questions.
- The user who found the product
- They ask whether it does their daily task. Show a working view of that task, not the full feature list.
- The owner or finance head who pays
- They ask what it costs per user, what happens at renewal and how long the set-up occupies their team.
- The IT or security reviewer
- They ask where data is stored, who has access and how it can be exported. Prepare the answers before the demo.
- The champion who leaves the company
- The deal stalls when they move. Record a second contact at each account to carry the deal.
- The buyer abroad on a dollar price
- They ask about invoices, tax and support hours in their time zone. A clear pricing page answers most.
Who it is for
This is written for these B2B SaaS startups.
- Early-stage SaaS selling to Indian SMEs and mid-market firms
- Vertical SaaS for one trade, such as clinics, schools, dealers or builders
- Developer tools and APIs sold to engineering teams
- HR, payroll and compliance software for growing companies
- Finance and accounting tools sold through CA firms
- Indian-built SaaS selling to buyers in the US, UK or Middle East
- Spin-offs from services firms that turned an internal tool into a product
- Bootstrapped founders who have not raised and cannot hire a sales team yet
Not for
It is not the right fit if.
- The product has no paying customer yet, so a persona would be a guess; talk to buyers first.
- The team sells to one person who both uses and buys, so three separate roles would be invented.
- The write-up would live in a slide deck that nobody opens during a call or when writing a message.
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
Understand the current view
We start with how your team currently describes the customer, since the gap between belief and reality is the finding itself.
- 2
Audit past enquiries and sales
We look at recent enquiries and closed deals to see who actually bought, not who was assumed to buy.
- 3
Interview customers and staff
Structured conversations with recent buyers, held as talk about the last purchase and not a questionnaire. We ask what happened before they called, who else was involved and what they compared. Customers agree before we contact them, and their answers are reported without names.
- 4
Build the personas
Findings are written into short, usable persona documents rather than a long report.
- 5
Apply to your marketing
We show where each persona should change a page, an ad or a script you already have. The sales team reads the drafts and says which ring true. A persona they do not recognise is rewritten.
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.
How many personas do we need?
What if we only have a few customers?
Can the persona be different for small and large buyers?
Can the persona differ for small and large buyers?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
What do you need from us?
What if we are not happy with the work?
More for B2B SaaS startups
Everything else we would do for you.
Closest to this: strategy and research
Also for B2B SaaS startups
Or start from the overview: sales and marketing for B2B SaaS startups.
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.