FIND
Company context and prospect intelligence.
HOW IT WORKS
Find. Assess. Explain. Act. Verify.
The same evidence thread moves from the first account signal to the client conversation, the work plan, and the proof that the observable state changed.
THE COMPLETE SCOUTz JOURNEY
Show the progression—not a pile of features.
The same source-aware evidence thread moves from account research to the work the MSP owns and the proof a supported condition changed.
DISCOVER
Bounded public Domain evidence.
CONVERSE
Evidence, unknowns, and better questions.
CONSENT
The customer approves a defined deeper source.
ASSESS
Read-only Cloud evidence within stated coverage.
UNDERSTAND
Findings, evidence, business context, and tools.
PLAN
Fix guidance, ownership, sequence, and verification.
HAND OFF
PSA, RMM, Microsoft, security, and delivery systems.
VERIFY
Rescan the condition the source can observe.
MSP WORK PLAN
READ-ONLYEvidence-linked delivery
Work itemOwnerVerify
Validate business ownervCIOAttestation
Review permission needEngineerSource check
Apply approved changeEngineerChange record
Rescan observable stateSCOUTzComparison
Sequence · Review → approve → deliver → verifyGuidance does not authorize a change
Generic work plan · MSP validates scope, change control, and rollback
DOMAIN → CONVERSATION → CLOUD
Domain earns the conversation. Cloud strengthens the advice.
Before permission, public evidence creates relevance and questions. After permission, supported tenant evidence can replace selected assumptions. Neither stage guarantees a sale.
DOMAIN
Public · passiveWhat can we observe? What does it support? What remains unknown?
CONVERSATION + CONSENT
Purpose · boundaryExplain the unknown, the source needed, what will not be read, and who authorizes access.
CLOUD
Authorized · read-onlyWhat is configured? Who or what is affected? What should change, wait, or stay alone?
MICROSOFT 365
READ-ONLYTenant security review
74OBSERVED POSTURE
480Identities
59Controls
38.2%Secure Score
52/55Sources
Privileged accessReview
MFA coverageObserved
Application consentAttention
Consented, read-only configuration and metadata · no mail, files, or content
DOMAIN SCANcreates relevance and better questions≠AUTOMATIC SALE
FINDING → WORK → VERIFY
A finding should lead somewhere.
The handoff is a feature. SCOUTz prepares the evidence and work context; the operational stack executes; SCOUTz returns only where a supported source can verify change.
FINDING
Condition, source, evidence, boundary.
INVESTIGATE
Questions and environment context.
FIX GUIDE
Cautions, prerequisites, rollout, rollback.
WORK PLAN
Owner, sequence, effort, dependencies.
HANDOFF
PSA, RMM, Microsoft, EDR, backup, SOC.
WORK
The MSP performs the authorized change.
VERIFY
Rescan or appropriate validation.
FINDING DETAIL
READ-ONLYApplication consent needs review
EVIDENCE STATEOBSERVED
COVERAGEPARTIAL
SOURCEMicrosoft 365
OBSERVED23 Aug 2026
Why it matters
A broad permission grant deserves an owner, business purpose, and activity review before any change is recommended.
Investigate next
Confirm ownerValidate useReview permissions
Generic application · illustrative evidence states · no customer data
RESCAN + VERIFY
READ-ONLYBaseline compared with current evidence
BASELINE8 open12 Aug 2026
→CURRENT3 open23 Aug 2026
Email authenticationVerified changed
Application ownerAttested
External serviceStill observed
Verification is limited to the source and condition actually checked
Lead → call → appointment → generic discovery → PDF → proposal → “just checking in”
Company → prospect intelligence → Domain evidence → conversation → consent → Cloud evidence → plan → decision
HOWEVER YOU FOUND THEM
Do not start the meeting at zero.
SCOUTz prepares the company context, outside-in evidence, unknowns, and questions before the first conversation. Deeper evidence arrives only after the prospect authorizes it.
The workflow helps the MSP prepare, interpret, recommend, and verify. It does not automate the relationship, promise the decision, or replace the person accountable for the advice.
Find
Build an account brief from SCOUTz-owned observations, public events, approved enrichment, and clearly labeled inference.
Assess
Run the domain review without customer access. Add Microsoft 365 only after customer approval and disclose every unavailable source.
Explain
Review the evidence, attacker view, business context, 3AM questions, and the report appropriate for each audience.
Act
Investigate the environment, use guidance and cautions, assign an owner, build the work plan, and deliver through the MSP’s process.
Verify
Rescan the observable controls, compare the new state with the baseline, preserve the proof, and bring it into the next client review.
We do not sell the answer before we ask the question.
Discover the condition. Understand the context. Review the available evidence. Recommend the outcome. Then the MSP selects the solution, vendor, service model, and commercial package.
The handoff is part of the workflow, not an exit failure.
SCOUTz prepares source-linked work for the MSP’s PSA, RMM, Microsoft administration, security, backup, or project system. Execution stays in the operational stack; SCOUTz returns only where supported evidence can verify the result.
RESCAN + VERIFY
READ-ONLYBaseline compared with current evidence
BASELINE8 open12 Aug 2026
→CURRENT3 open23 Aug 2026
Email authenticationVerified changed
Application ownerAttested
External serviceStill observed
Verification is limited to the source and condition actually checked
SCOUTz OPEN BETA
Point SCOUTz at the question. Walk in with a defensible answer.
Bring a real MSP workflow and see how SCOUTz turns evidence into the next defensible action. The review runs without an agent or install and never changes configuration automatically.
SCOUTz prepares the conversation. The relationship and the sale stay yours.