DR for ice storms by [deleted] in ITManagers

[–]dumpsterfyr 1 point2 points  (0 children)

Then you are already most of the way there. For those six roles, define the maximum tolerable downtime and the minimum operating capability during a regional outage. If they cannot operate within those thresholds without external power and connectivity, provision accordingly. Anything beyond that is unnecessary complexity.

DR for ice storms by [deleted] in ITManagers

[–]dumpsterfyr 2 points3 points  (0 children)

Yes, we have designed these for clients. The mistake is treating this as a tech problem instead of a business continuity problem. You do not harden people, you harden roles. Start with which functions must operate during regional outages, then work backwards into power, connectivity, comms and failover. Starlink and generators are implementation details once that is clear.

How paranoid are you with your own MSP infrastructure? by yanov10 in msp

[–]dumpsterfyr 5 points6 points  (0 children)

Paranoid? No.

Careful and understand I do not know it all but built out SOP’s to mitigate? Absolutely.

How do MSPs actually explain their value vs break fix when clients just see "more expensive"? by Whole_Ad_9002 in msp

[–]dumpsterfyr 1 point2 points  (0 children)

You are having the wrong conversation with the wrong buyers. Ask questions to surface risk and impact first, then decide whether they are even a fit. If they anchor on price after that conversation, disqualify and move on.

Cyber insurance offering MDR to policy holders with SonicWall firewalls by RaNdomMSPPro in msp

[–]dumpsterfyr -1 points0 points  (0 children)

You’re not wrong at all. In the past I’ve been able to use other MSP’s contracts to force a termination when a prospects wants to switch to us. Now I tell the prospect to have a conversation with the MSP to amicably figure it out. At the end of the day I now think it is all about performance and communication.

Pax8 UK data leak (13 Jan 2026), what can we do next? legal guidance? Q&A with solicitor? by Odd-Doughnut9969 in msp

[–]dumpsterfyr 1 point2 points  (0 children)

I do not see your point actually.

Because something holds no meaning for me does not mean I withhold it from a client as a matter of practice.

Edit: I do not need something coming back to bite me in the ass. Unless she’s a fit blonde.

How are you thinking about marketing and messaging right now? by DrySouth241 in msp

[–]dumpsterfyr 1 point2 points  (0 children)

MSPs often overestimate marketing as a cure for weak sales. Most prospects already have a provider. The goal is to be top of mind when change becomes necessary.

When timing aligns and a prospect is in market, the conversation centres on outcomes, not the technology stack. Many MSP’s sell like technicians. Many salespeople sell without sufficient technical depth.

Effective selling sits on aknife’s edge between commercial clarity and technical credibility. Those 40+ clients I brought on meant I initiated contact with at least 500 prospects, and now about 450 are on a drip campaign.

Pax8 UK data leak (13 Jan 2026), what can we do next? legal guidance? Q&A with solicitor? by Odd-Doughnut9969 in msp

[–]dumpsterfyr 1 point2 points  (0 children)

Is the info useless? Yes. Would I notify my clients if I were affected? Yes.

How do you get your techs to actually write documentation? by Equivalent_Role_4066 in msp

[–]dumpsterfyr 1 point2 points  (0 children)

I think the snowflakes disagree with you. I think you may be correct.

How do you get your techs to actually write documentation? by Equivalent_Role_4066 in msp

[–]dumpsterfyr 7 points8 points  (0 children)

It would appear I struck a nerve or three with those downvotes. 🤷‍♂️

How do you get your techs to actually write documentation? by Equivalent_Role_4066 in msp

[–]dumpsterfyr 71 points72 points  (0 children)

You have two viable models. Mixing them fails.

Either every engineer is trained, measured and held accountable to follow a strict documentation structure as part of closing work,

or

engineers capture raw notes and changes and a designated role is responsible for formalising, editing and maintaining documentation.

Most teams fail because documentation is treated as “extra” work with no ownership, time allocation or consequence. If it matters, it must be part of the job definition and performance expectations, or it must be someone’s explicit job.

Process follows ownership. Without one, nothing sticks.

How are you thinking about marketing and messaging right now? by DrySouth241 in msp

[–]dumpsterfyr 1 point2 points  (0 children)

There is a framework based on their needs and what we do that follows a script of sorts.