You might not have a targeting problem — you might have a persona problem
Picture this: your team spent three months building a content strategy, launched a Google Ads campaign, optimized your service pages, and pushed out a dozen blog posts. And the leads? Silent, or going nowhere. Before blaming the channel or the agency, ask one question: do you actually know who you are marketing to — not in the vague “IT decision-makers at SMBs” sense, but really know them? What keeps them up at night, where they go when they’re quietly researching, what they’ve already tried and been burned by, and what finally gets them to pick up the phone.
Most B2B buyers work through a dozen or more pieces of content before making a vendor decision. By the time someone fills out your contact form, they’ve already read your site, your competitors’ pages, and formed an opinion. If your messaging wasn’t speaking directly to them at every one of those touchpoints, you were never really in the running.
Why the usual persona does not work
Most MSP buyer personas amount to a stock photo, a made-up name, a job title, and three bullets about “wanting reliable IT support” — a description that fits literally every company on the planet. That kind of persona doesn’t tell you which keywords to target, what tone to use, or why your last email campaign got a 1.4% open rate. A persona that actually moves revenue is rooted in real behavior: how this person evaluates vendors and where they go quiet, what they’ve already tried and why it failed, the language they use when complaining about their current MSP, and which content format they actually trust — a case study, a video testimonial, a peer review. Precise, data-grounded personas convert meaningfully better than generic outreach, and the gap comes from relevance, not bigger budgets. When someone reads your content and thinks “this was written for me,” they don’t just click — they remember you.
There is no universal template
The right persona for an MSP focused on healthcare IT in Toronto looks nothing like the right one for a firm focused on legal clients in Dallas — the buying triggers, compliance anxieties, and tone that lands are all different. What follows are three example personas, built to show how to think about this, not a template to copy directly.
The practice owner who just wants it to work. Picture a multi-location dental practice owner with zero interest in what a VLAN is. What she cares about: when the team arrives at 8am, everything works — records load, the appointment system is up, payments process — and when something breaks, someone fixes it fast without her having to chase anyone down. She came to managed IT through necessity, often after a previous provider took hours to respond to a ticket that was costing real money in staff downtime. She’s swayed by testimonials from other practice owners, real response-time guarantees, HIPAA compliance handled invisibly, and a single point of contact who already knows her setup. The message that lands: “we handle your IT completely so you can focus on your patients, not your technology.”
The tech-savvy executive who is done tolerating average. Picture a VP of Technology at a fast-growing startup who has built tech teams for over a decade — not outsourcing because he can’t handle IT, but because his internal team is stretched and he refuses to let security ops become a liability. He’ll read your SLA before your homepage, verify your response-time claims, and ask pointed questions about your escalation procedures that most MSPs can’t answer well. He’s swayed by verifiable uptime and resolution metrics, documented security processes, proof you’ve worked with similarly regulated or high-growth companies, and transparent pricing. He sees through overselling immediately — the message that lands is “we don’t ask you to trust us, we give you the data to verify it yourself.”
The IT manager who has been let down before. Picture someone who inherited a mess from a previous MSP that was slow and opaque, who spent months escalating tickets with no explanation, and got pulled into leadership’s office after a preventable outage. He’s not necessarily the final decision-maker, but he can absolutely kill a deal if he doesn’t trust the provider. He’s swayed by SLA adherence backed by references he can actually call, a clear onboarding process, real 24/7 monitoring with fast escalation, and honest communication when things go wrong. He doesn’t need to be sold on managed services — he needs to be convinced you’re different from the last one. The message that lands: “we know what it feels like to be left hanging, which is exactly why we built our support model the way we did.”
Building your own
Start with your CRM: which clients stayed longest, paid the most, and referred others — and what do they have in common beyond industry and size? Listen back through sales calls for the specific objections and phrases people use to describe their problem; that’s the exact language to reuse in your content and ads. Pay attention to search intent — a healthcare IT director searching “HIPAA IT compliance checklist” is in a completely different headspace than one searching “managed IT services for hospitals,” and your content needs to meet each of them differently. And get into the communities where your prospects talk when nobody’s selling to them — LinkedIn groups, industry Slack channels, niche forums — because those conversations are the most honest research available.
What changes when you get this right
Solid persona work sharpens everything downstream: your SEO targets the exact phrases buyers use when they’re ready to evaluate, your content speaks to real pain in real language, and your ads earn the right clicks instead of just more clicks. Sales cycles shorten because prospects arrive pre-qualified, and close rates improve because you’ve stopped trying to convince people they need IT services and started showing the right people why they should choose you.
If your pipeline feels inconsistent or you’re attracting the wrong kind of client, the fix usually starts here — before the keywords, before the ads, before the content calendar. Start with who. Everything else follows.