Evidence-linked delivery
Generic work plan · MSP validates scope, change control, and rollback
SCOUTz starts with the decisions an MSP must make before, during, and after an assessment, then adds only the evidence and tools that support those decisions.
The first SCOUTz whiteboard did not start with a scanner box. It started with rooms: the first meeting, the technician's desk, the client review, and the QBR months later. I kept asking what each person needed to know and which fact had to survive the handoff. Only then did the scanner earn a place on the board.
The reason SCOUTz has a Decline path is a custom car builder with a cable TV show and a contract worth nearly 20% of my revenue.
"Tony was a nightmare wrapped in a TV smile. He nickel-and-dimed every invoice. Paid 45-60 days late. Demanded services outside our scope... Tony's face went red. 'You can't fire ME. I'm the CLIENT.' 'Not anymore.'"
Walking out cost me $45,000 in unpaid invoices and very nearly cost me payroll. I tell the whole story in the book. What matters here is what it taught me: the most expensive clients rarely look expensive on the invoice, and no scan score can make that judgment for you. SCOUTz gathers the evidence. The MSP decides who deserves to be a client. I built it in that order on purpose, because I learned the other order at retail price.
From The 3AM Test by Steve Copeland.
We started with the questions at the other end. What should the MSP know before the meeting? What can we actually prove? What does the technician need to investigate next? What does the client need to understand? What work should follow? How will anybody know the work changed the condition?
Once those questions are the starting point, the product shape changes. The Domain Scan exists because the MSP needs a responsible view before authorization. The Cloud Scan exists because consented evidence should replace assumptions after the relationship moves forward. Tools exist because one focused answer can be worth more than another hundred observations.
Fix Guides exist because detecting a condition without explaining the implementation path leaves the hardest part on the floor. Work Plans exist because findings need owners, sequence, effort, and verification criteria. Studio exists because the engineer, seller, account manager, and client need the same truth expressed for different jobs. Rescan exists because closing a ticket is not proof.
That is also why simply adding scanners is not the roadmap. New evidence sources matter when they help answer a real question with appropriate access and defensible confidence. They do not matter because a larger number looks good next to a competitor's logo.
SCOUTz was built around the manual thinking MSPs still do between prospect and client, scanner and conversation, finding and work, fixed and verified. The technology serves that workflow.
Real evidence. Real language. Better conversations. That was the direction before the first dashboard, and it is still the direction now.