How IT and MSPs can use newsletters to build trust with clients
Most clients do not understand what their managed service provider actually does. A monthly newsletter fixes that, and quietly reduces churn at the same time.
If you run a managed service provider or an IT consultancy, your biggest churn risk is not a competitor. It is the client deciding that "IT is just IT" and shopping on price. A monthly newsletter is the cheapest way to remind them that what you do is not a commodity.
Here is how to make it work.
The MSP visibility problem
Good IT work is invisible by design. Backups run. Patches install overnight. Phishing emails get filtered before anyone sees them. The client has a quiet quarter, looks at the invoice, and starts wondering if they could pay less.
This is the classic operational paradox: the better you do your job, the less your client sees of it. And the less they see of it, the more replaceable you look on a spreadsheet.
A newsletter is the cheapest way to make the invisible work visible. Done well, it shows your clients (and the prospects on the same list) that the threat landscape is genuinely changing, that your team is on top of it, and that switching providers carries real risk.
What the newsletter is actually for
Three jobs.
The first is education. Translate what is happening in cybersecurity, cloud infrastructure, and AI into language the average finance director can understand. They do not need a CVE number. They need to know "phishing emails are getting harder to spot because the AI tools attackers use are getting better."
The second is positioning. Show that your team is paying attention to the right things. The newsletter is evidence of competence in a way a sales call cannot be.
The third is friction reduction. When the client gets a request from a vendor or a board member ("can you switch us off Microsoft 365 onto something cheaper?"), the newsletter has already done some of the work of explaining why that is not as simple as it looks.
It is not for selling new services. It is for keeping the existing relationship feeling worth it.
What goes in the newsletter
Five sections cover most of what is useful.
A short summary of the threat landscape. Two or three paragraphs on what attackers are doing this month. Phishing trends, ransomware patterns, supply chain stories. Plain language. No jargon. End with the single thing readers should do this month.
Industry news that affects buyers. Microsoft licensing changes, cloud price moves, new regulatory pressure (DORA, NIS2, GDPR enforcement decisions, sector-specific rules). Pull from official sources and the trade press, then write a one-paragraph take on what it means for a typical client.
A small case study. One thing your team did this month that the client would otherwise never know about. "We blocked X attempts at Y this month. Here is what happened in the one we found most interesting." Anonymise. Be careful with detail. The point is to show ongoing vigilance, not to brag.
A practical tip. One thing the reader should do this week. Could be a setting in Microsoft 365, a habit for handling email, a question to ask their team. Two paragraphs is enough.
A soft pointer to your other work. New service offering, blog post, webinar, hire. Single paragraph. Optional.
The whole thing should take a busy operations director five minutes to read and leave them feeling slightly more secure about the world.
Frequency
Monthly is right for most MSPs. Weekly is too noisy because IT topics do not change at that speed for non-technical readers. Quarterly is too slow to feel like a regular touchpoint.
Pick a date. The first Tuesday of the month, every month. Predictability matters more than perfection. If you miss one, ship the next on schedule rather than trying to make up the gap.
Who is on the list
Three groups.
Existing clients. The whole point of this exercise. Add the IT and operations contacts for every client account, plus the finance director where they exist as a separate person. Be explicit at the start of the relationship that the newsletter is part of how you communicate, so it does not look like spam later.
Past clients. The ones who left to save money on price. Most of them are quietly regretting it within twelve months. The newsletter keeps you on their radar for the moment they want to come back.
Prospects from your network. People who attended a webinar, met you at an event, or filled in the contact form but did not become clients yet. The newsletter is the cheapest way to be there when their current arrangement starts to break.
Avoid buying email lists from any of the lead-generation services that target IT buyers. The deliverability damage is severe and the conversion rate is essentially zero.
Compliance, briefly
If your clients are in regulated industries (financial services, healthcare, education), be careful about the threat-landscape content. Avoid implying that any specific client has been targeted, even anonymised. Keep case studies generic enough that no real organisation can be identified.
If you operate in the EU or UK, GDPR applies to your subscriber list. Get explicit consent on sign-up. Make unsubscribes one-click. Do not assume that someone giving you a business card means they have consented to a marketing newsletter; the cleanest practice is to ask explicitly when they sign up.
Measuring what matters
Open rate is a useful health check. MSP newsletters with engaged audiences tend to land in the forty-to-fifty-five percent range, which is high for B2B because the audience is small and self-selected.
Reply rate is the more useful metric. A good MSP newsletter generates the occasional reply from a client asking about something specific. Those replies are how the newsletter pays for itself: each one is a conversation that might have not happened otherwise.
The numbers that matter most are slow ones. Net revenue retention from the client base. The proportion of churn that comes from price-shopping. Both should improve over twelve to twenty-four months for an engaged list. Neither will move in the first quarter.
What to avoid
Three things kill MSP newsletters more often than they should.
Writing in IT-pro voice. The audience is not other IT pros. It is the finance director, the COO, and the office manager. If your newsletter sounds like a conference talk for engineers, you will lose the people who actually sign the renewal.
Selling on every send. The promotional content should be a small minority. Constant pitching trains the list to delete on sight.
Inconsistent sending. Three editions in two months, then silence for a quarter. Subscribers either unsubscribe or unconsciously file you in the "scattered" bucket. Worse for an MSP than for most other businesses, because consistency is supposed to be your selling point.
A workflow that does not eat your team's week
The honest answer to "how do I find time to write this every month" is the same as for any small team: do less writing, more curating.
Set up a system that pulls in industry news from the sources you already follow. Tools that aggregate and score content from multiple feeds make this much faster. ContentCrab is built for this kind of monthly curated digest, but the discipline applies in any tool: minimise time spent producing original prose, maximise time spent picking and commenting on what is already out there.
Once the system is in place, monthly writing time should be two to three hours. That is small enough to fit into a busy operations week, large enough to produce something genuinely useful.
The MSPs that run a steady newsletter for two years tend to share a common experience. Renewals get easier. Cold-pricing pressure eases. Clients who never replied to a single newsletter still mention they read it when they renew. The compounding is slow but real.
Six months to start seeing it. Twelve months to feel it. Two years to have a quietly valuable asset that lowers your churn and raises your average client tenure.
Cheers.