Technology & Security
Every client on a different stack is a support bill you pay forever. Choose a stack you can support, harden every client the same way, and prove it when an insurer asks.
- Pick a PSA, RMM, backup and security stack for your size.
- Apply the same security baseline across every client.
- Keep the evidence cyber insurers and auditors ask for up to date.
One Record for Every Vendor Contract, so a Price Rise Doesn't Catch You Out
The email lands on a Tuesday: "Important update to your pricing." You open it, and there it is, a 40 percent jump on the tool you resell to every client.
Find Your Problem
Six parts of the stack behind the service. Start with the one you could least prove to a client today.
Choosing the Stack
PSA, RMM, backup, security and documentation, and the order to decide them in.
1 resourceHardening and Baselines
The configuration a client gets by default, and the proof that they got it.
1 resourceBackup and Restore
What is backed up, how it is tested, and the day it is needed.
1 resourceSecurity Frameworks and Evidence
The framework a client's insurer accepts, and the evidence that satisfies it.
1 resourceAutomation and Scripting
The work a script should do, and the review before it runs anywhere.
1 resourceVendor Management
Contracts, renewals, price changes and the record of what changed.
1 resourceLatest Articles in Technology
All Articles →One Record for Every Vendor Contract, so a Price Rise Doesn't Catch You Out
The email lands on a Tuesday: "Important update to your pricing." You open it, and there it is, a 40 percent jump on the tool you resell to every client.
Pick a Security Framework Your Clients' Insurers Will Actually Accept
Picture this: a client forwards their insurer's cyber insurance proposal form.
Which Tickets to Automate, and the Review Before a Script Runs Anywhere
You're staring at another flood of auto-generated tickets and you know half of them are the same task wearing a different client name.