Four bench-tested workflows: MSP field triage, internal-IT bench maintenance, repair-shop intake-to-handoff, and the independent power user keeping a personal fleet alive.
You roll between SMB customers all day. Every site is a different mess and your USB stick is your office.
A folder of fifteen single-purpose freeware utilities, half of them either abandoned, signed by sketchy publishers, or bundling McAfee. Sysinternals covers ten things; you're hand-rolling the rest. Every customer engagement is a different combination of tools, with no consistent deliverable to hand back.
You support a fleet under one roof. The tier-1 helpdesk needs a consistent triage flow; you need scheduled maintenance running in the background.
Tickets come in as “my PC is slow” and you can't deploy fifteen different utilities through your endpoint manager. RMM agents handle patching but don't do registry recovery, BSOD minidump triage, or OEM debloat. Your senior tech is the only one who knows the right Sysinternals incantation for half of these.
/maintenance, /cleanup, /affinity-watcher) for unattended scheduled jobsWalk-in customers, bench queue six deep, junior techs who need guardrails, and a customer who wants to see what they're paying for.
Every machine through your shop needs the same intake-to-handoff workflow, but every tech does it slightly differently. The customer wants “proof you fixed it.” Your turnaround time gets eaten by inconsistent processes and tickets that come back two weeks later for the same problem.
You're the unofficial helpdesk for the family, the neighbors, and a small fleet of personal machines. You don't bill, but you still want pro tooling.
Every Christmas you inherit another machine to maintain. The free utilities you used to trust have been bought out, abandoned, or quietly turned into bundleware. You want one tool you can carry around, run on a parent's machine without explaining what's happening, and leave no residue when you're done.
Volume licensing, OEM bundling on machines you sell, white-label or co-branded shells, custom modules, and NET 30 / PO purchasing. The public Stripe plans only go so far — we handle the rest by hand.