One list, one next action
Each line has a button for its next action. The item clears when the job is done, so your day starts with current work rather than another dashboard to interpret.
PRODUCT
SCOUTz helps an MSP find the reason to talk, earn consent for deeper assessment, guide the work, and prove what changed without losing the source behind the story.

EVIDENCE · INSIGHT · PROOF
Keep the dated observation and source.
Separate the finding from its possible consequence.
Assign an owner, prerequisites and estimated effort.
Your hourly rate in Settings × LOE in hours.
Reassess against the baseline; record what changed.
EVIDENCE · INSIGHT · PROOF
Published domain, DNS, email authentication, certificates and external evidence.
Supported Microsoft 365 identity, app, permission, licensing and configuration evidence.
No message bodies, private files, chats or prompts. Unread is not clean.
EVIDENCE · INSIGHT · PROOF
Research the account and supported public evidence.
Explain one condition; confirm its business context.
Earn permission for the appropriate deeper review.
Agree scope, perform the work and verify the observation.

WHAT'S NEW IN SCOUTz · OPEN BETA
Start with the work recorded in your SCOUTz workspace: first opens of shared report links, waiting approvals, upcoming reviews and proposals awaiting a reply. Today brings those items together in the order to work through them.
Each line has a button for its next action. The item clears when the job is done, so your day starts with current work rather than another dashboard to interpret.
An opened link is a reason to check the agreed next step—not proof of buying intent. SCOUTz prepares the conversation; the MSP owns the relationship and closes the deal.
Honest by design: every count names its source. A check SCOUTz could not read stays “Not read”—not “none” or “all clear”. Microsoft 365 reviews use client-consented, read-only access and do not read message bodies, files, chats, documents or prompts.
SCOUTz begins with the company, the legitimate sources available now, and the questions created by what is observed or still unknown. It does not begin with a product answer and work backward until the account fits it.
Why evidence comes before the product answer →Prospect Miner, Sales Intelligence, public events, and source-labeled opportunity context.
Domain Tools first; consented Microsoft 365 and cloud context when the customer is ready.
Findings, evidence, attacker view, business meaning, 3AM Test, and audience-specific narratives.
Investigation prompts, guided remediation, work plans, reports, and MSP-owned delivery.
Rescan the observable state, preserve proof, and bring movement into the next QBR.
BEFORE AUTHORIZATION
Use public domain findings, company events, and optional enrichment to prioritize research. Every signal retains a source type and boundary. An inference is never presented as an observed fact.
Explore sales intelligence →AFTER AUTHORIZATION
Customer-approved, read-only collectors add supported Microsoft 365 configuration and metadata. Coverage gaps remain visible instead of lowering risk by omission.
Explore Microsoft 365 →Because imported inventory is context, not independent discovery. A PSA reflects what was recorded. An RMM reflects what it manages. SCOUTz starts with supported observation, preserves what remains unknown, and then correlates those other views so the difference can produce a better question.
Read the discovery-engine thesis →THE PRODUCT BOUNDARY
Once the work becomes operational, the MSP already has systems built to execute it. SCOUTz should make that handoff better, not force a replacement of the stack the MSP already trusts.
Research the account, preserve the source, establish the boundary, and earn the deeper conversation.
Connect the cited condition to investigation, scope, ownership, cautions, and verification criteria.
PSA, RMM, Microsoft administration, security, backup, documentation, and project systems execute.
Rescan only what the supported source can observe and show the result without overstating it.
WORKING OPERATOR EXPERIENCE
ANONYMIZED PRODUCT CAPTURES
These captures come from the working SCOUTz application. Identifying details are removed; illustrative diagrams elsewhere on the site are labeled separately.
Screens are representative working-application captures, not customer records. SCOUTz never uses a generated interface as proof that a capability exists.
Bring dated evidence, clear limits, and useful questions.

Dated interface captures. Counts and labels reflect the captured review, not platform-wide totals or a promise of coverage.