Skip to content
GullySales
Tell us what you need

SaaS and software companies · Buyer persona

Describe the person who signs, the person who uses and the person who blocks.

A buyer persona for a software company is a written picture of each role inside a target account: who feels the problem, who approves the spend and who can stop the deal in security review. GullySales builds these from your closed-won and closed-lost deals, so the sequences and pages speak to a real role.

Tell us what you needor call +91 80958 58589

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

Realistic editorial illustration of saas and software companies at work in the United States

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 SaaS and software companies

Sales and marketing for SaaS and software companies, the overview.

Last updated 5 Oct 2026.

For SaaS and software companies

Where it usually goes wrong, and what we would do.

  • “The user who signs up is rarely the person who pays”

    A product lead starts the trial, a finance head holds the budget and an IT manager checks the vendor. One persona for all three produces a message that fits none of them, and the trial never turns into a contract.

  • “Job titles hide what the buyer actually does”

    Head of operations means one thing at a twenty-person company and another at a listed group. A persona written from titles alone sends the same email to both, and one of them deletes it.

  • “The blocker is usually missing from the deck”

    Deals stall with a security reviewer, a procurement desk or an engineer who built a rough version in-house. Nobody wrote that role down, so no message was ever aimed at the person who could say no.

  • “Closed-lost notes hold the sharpest wording”

    When a prospect explains why they chose a rival or did nothing, they use their own words for the problem. Those lines belong in the persona, and most CRMs only keep them as a one-word reason code.

What we do

What we deliver for SaaS and software companies.

Every deliverable, what it covers for you, and the result it is there to produce. Nothing here is an extra.

  1. Role maps for the champion, the approver and the blocker

    One page per role showing what each cares about, what they read, what they fear and what they need to see before agreeing.

    Result: Your AEs can name who sits in each seat on a live deal.

  2. Persona language mined from calls and lost deals

    Recorded calls, support tickets and closed-lost notes read for the exact phrases buyers use about the problem.

    Result: Open the sequences and the wording matches what your customers actually say.

  3. Objection sheet by role

    The questions each role raises, with an answer your team can give without improvising, including the awkward ones on security and switching cost.

    Result: A new rep handles a technical objection from the written sheet.

  4. Persona-matched trigger list

    The events that put each role in motion, such as a new head of function, a funding round or a competitor's price change.

    Result: Every outbound message in the sequencer carries a stated reason tied to a role.

  5. Fit and misfit criteria

    A short list of the accounts and roles that buy well and the ones that sign, churn and complain.

    Result: Lead scoring in your CRM reflects the written criteria.

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.

Read the full B2B and B2C buyer persona development page

Who is asking

Write a card for the signer, the user and the blocker in a software purchase.

Each row is a role on the buying side. Fill in names and titles from the accounts you have actually sold to.

Head of operations who signs
Wants the cost, the contract term and what changes for the team before agreeing. Needs a one-page summary to forward to the finance head.
Team lead who signed up for the trial
Wants to see the product do one job on their own data in the first session. Needs a short setup guide and a person to ask.
IT or security reviewer
Asks where the data sits, who can access it and what the vendor's security answers are. Have the questionnaire answers ready before the call.
Finance head checking the budget
Wants the price, the billing terms and the invoice details. Needs a clear quote that matches the purchase order process.
Founder at a small customer
Buys on a card and decides alone in a single sitting. Needs the plans and the cancel terms on one page, and no demo to book.

Who it is for

This is written for these SaaS and software companies.

  • Seed and Series A B2B SaaS still selling founder-led
  • Bootstrapped vertical SaaS with a small team
  • Product-led companies adding a sales motion
  • Developer tools moving upmarket into team plans
  • Healthcare, fintech and other compliance-heavy software
  • Agencies and services firms productising a platform
  • Marketplaces with a supply side to recruit
  • Companies with a full AE bench and no pipeline to feed it
  • Software companies entering the US from another market

Not for

It is not the right fit if.

  • You have sold to fewer than a handful of accounts, so a card would describe a buyer you have not met
  • You have not yet asked any customer who signed, who used the product and who raised an objection

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

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

    Build the personas

    Findings are written into short, usable persona documents rather than a long report.

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

  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.

Tell us what you need
How many personas does a SaaS company need?
As many as there are distinct roles in a typical deal, usually a user, an approver and a blocker for one product. A second product or a different company size can add more. We start with the roles in your last few closed deals.
We have no customer interview data. Can we still build one?
Yes. Closed-won and closed-lost records, sales call recordings, support tickets and onboarding notes already hold the language. Where there is a gap, we suggest a handful of short customer calls, which you would need to arrange.
Does the persona replace our ideal customer profile?
No. The ideal customer profile describes the company that fits. The persona describes the people inside it. You need both, and the second is built on the first, so GullySales checks the account definition before writing any role.
Should we have a separate persona for Indian and overseas buyers?
Add a note, not a new card, where the buying process differs, such as who signs or how invoices are raised. Reason: the role stays the same while the paperwork changes. Split only when the questions the buyers ask are clearly different.
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.
What do you need from us?
Your brief, and a conversation. After that, access to whatever this work touches, such as your website, your accounts or your enquiry record, and time with the people who handle your enquiries.
What if we are not happy with the work?
Tell us and the plan changes. Everything is reported against the baseline, so a number that is not moving is visible to both sides. The term is in your written scope, and the refund and cancellation policy sets out the rest.

From the blog

Further reading for SaaS and software companies.

All articles

More for SaaS and software companies

Everything else we would do for you.

Closest to this: strategy and research

Also for SaaS and software companies

Or start from the overview: sales and marketing for SaaS and software 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.

Tell us what you need