Skip to content

Managed IT service providers · Buyer persona

Write down who actually signs, who objects and who will judge you at renewal.

A buyer persona for a managed IT service provider is a written profile of each person in the decision: the founder who feels the pain, the finance head who approves the spend and the in-house IT executive who may resist you. GullySales interviews your best clients and turns what they say into profiles your proposals and replies are written against.

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

An IT technician checks network equipment with an office manager

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 6 Oct 2026.

For managed IT service providers

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

  • “Three people hold the decision, and they want different things”

    The founder wants the problem gone, the finance head wants a fee that does not move, and the IT executive wants to keep their role. A single proposal aimed at all three satisfies none.

  • “The trigger is an event, not a need”

    Nobody shops for managed IT in a calm month. A resignation, a failed audit questionnaire, a lost laptop or a ransomware story from a peer pushes the buyer to call. The persona should name those events.

  • “The old vendor is part of the buyer's story”

    A buyer coming off a freelancer or a hardware AMC carries a grievance: slow replies, no documents, surprise bills. Your first meeting is judged against that memory, and the persona should record it.

  • “The renewal reader never saw a ticket”

    The person who approves renewal at the end of the year opened no support request and saw no patch. Writing them down as a separate persona changes what you send them before the invoice.

What we do

What we deliver for managed IT service providers.

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

  1. Client interviews

    Conversations with a handful of your current clients about what triggered the search, who they asked and what nearly stopped them.

    Result: You hold the buyer's own words, not guesses made in your office.

  2. Persona sheets by role

    One page each for the founder, the finance head, the administration manager and the in-house IT executive: goals, fears, questions and what they read.

    Result: Each role has a page the sales team can open before a call.

  3. Trigger-event list

    The resignations, audits, office moves and vendor failures that start a search, mapped to the page or message that meets each.

    Result: Every event has a matching reply ready.

  4. Objection answers by persona

    Short written answers to the freelancer comparison, the per-user fee and the fear of being replaced.

    Result: The same objection is answered the same way by every salesperson.

  5. Proposal opening lines by role

    A first paragraph for each persona so the proposal begins with the reader's own concern.

    Result: A proposal can be checked against the persona it was written 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

Each person in the decision asks a different question about you.

Founder or managing director
Asks what happens when the system fails on a busy day and who they call, and wants a single named person, not a ticket number.
Finance head or CA advising the firm
Asks what is included per user, what is billed extra and how the agreement ends, because they own the budget and the exit.
In-house IT executive
Wants to know whether you replace them or work beside them, and who holds admin rights once you are in.
Office manager who logs the calls
Judges you by whether someone picks up and understands the problem, and by whether the engineer explains it in plain words.
Auditor or customer's security team
Asks for evidence of backups, access control and asset records, and will check whether you can supply them on request.

Who it is for

This is written for these managed IT service providers.

  • Per-user support for growing offices without an IT team
  • Resident engineer and IT facility management providers
  • Microsoft 365 and Google Workspace managed service partners
  • Co-managed IT for companies with one in-house IT person
  • MSPs serving CA firms, clinics and other compliance-heavy offices
  • Backup and endpoint management specialists
  • IT support firms for factories and export units
  • Remote-first providers serving offices in several cities

Not for

It is not the right fit if.

  • You have signed too few clients to know who actually decided, so the persona would be guessed.
  • Your pitch is one fixed package sold to anyone, and the roles around the buyer do not change what you say.
  • You expect the persona to replace conversations with real clients, which it cannot do.

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.

How many personas does an MSP need?
As many as there are distinct roles in a decision, which is three or four in this trade. A profile for every possible visitor is not useful. Start with the people who appeared in your last few wins.
Can we build personas without surveying clients?
You can draft from your sales notes, then test the draft with real clients. A persona that nobody has checked is an opinion. A short conversation with a few clients corrects it.
Should the in-house IT person get a persona?
Yes. They can end a deal by raising one worry in a meeting. A persona that records their concern, job security, lets you offer co-managed support and name their role in it.
What is the biggest concern for an MSP serving a clinic or a CA firm?
Confidentiality of client files. These buyers hold sensitive records, so their question is who can see their data and what is logged. Answer it in writing, and check the sector's own rules and your client's professional body before you make claims.
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.

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.