Articles
Notes on running workforce monitoring
Written for the people who deploy this: what breaks across multiple clients, what the agent does and does not collect, and how to roll it out without creating a problem for the client.
Running monitoring across clients
Employee monitoring for MSPs: what breaks at multi-tenant scale
Account sprawl, cost that tracks your clients' hiring, and access scoping that was never built for staff who serve some clients and not others.
Per-user vs. per-admin pricing: the math for MSPs
A worked comparison at 3, 6, and 12 clients — including the case where per-user billing is genuinely cheaper.
Adding workforce visibility as an MSP service line
What to package, who actually buys it, how to price the delivery, and when to refuse the engagement.
Deploying it without incident
Deploying a monitoring agent through your RMM without a support wave
A staged rollout: representative test device, uninstall verification, controlled groups, and reconciling the endpoints that never checked in.
Notice, consent, and monitoring: a deployment checklist for MSPs
Who has to be told, what a notice usually covers, and what to document before collection starts. Not legal advice.
What the agent collects
Counts vs. content: why the distinction decides your exposure
Counting keystrokes and recording them are different products, with different legal, antivirus, and human consequences.
Screenshot monitoring without creating a liability
What is fixed by the platform, what you actually control, and how to tell when a client is the wrong fit for the product.
Try it on one client
One client, one Windows device, 14 days. No card required.