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.

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 managed IT service providers
- Digital marketing for managed IT service providers
- SEO for managed IT service providers
- Local SEO for managed IT service providers
- Lead generation for managed IT service providers
- Content marketing for managed IT service providers
- Email marketing for managed IT service providers
- PPC ads for managed IT service providers
- CRM for managed IT service providers
Sales and marketing for managed IT service providers, the overview.
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.
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.
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.
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.
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.
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
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 does an MSP need?
Can we build personas without surveying clients?
Should the in-house IT person get a persona?
What is the biggest concern for an MSP serving a clinic or a CA firm?
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?
From the blog
Further reading for managed IT service providers.
6 min read · 6 Oct 2026How MSPs write a proposal the finance head will signA managed IT proposal is signed by someone who compares your per-user fee with a salary. Write down what it covers, what it excludes and how support is raised, and the comparison gets easier.
5 min read · 6 Oct 2026How buyers choose between IT, software and SaaS vendorsTechnology buyers take a name from a peer, test it against an engineer and sign after a finance check. This post follows the choice in four stages and shows where vendors drop out.
6 min read · 7 May 2026LinkedIn for a technology company: what to post and who to approachA technology founder often gets more notice from buyers by posting practical lessons from delivery than company news. Here is what to post, which roles to approach and what to say in the first message.
More for managed IT service providers
Everything else we would do for you.
Closest to this: strategy and research
Also for managed IT service providers
Or start from the overview: sales and marketing for managed IT service providers.
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.