PRODUCT ROADMAP · UPDATED SEPTEMBER 2026

What SCOUTz can do now—and what we are validating next.

SCOUTz is being built with working MSPs. This roadmap separates capabilities available today from work still being tested, expanded, or considered.

Know what was checked. Know what still needs an answer.

A capability can be available while a source, permission, license, or field remains unavailable for a particular account. SCOUTz keeps that difference visible.

AVAILABLE NOW

Start with evidence the MSP can use today.

Availability still depends on the stated source, permission, license, and coverage boundary. A missing source never becomes a clean result.

PUBLIC EVIDENCE

Outside-in domain review

Review supported DNS, email-authentication, certificate, web-response, exposed-service, and security-contact evidence without tenant credentials.

Explore domain evidence →
WITH CUSTOMER CONSENT

Microsoft 365 review

Use customer-approved, read-only collectors for supported identity, application, permission, security, license, and managed-device context.

Review the Microsoft 365 boundary →
EXPLAIN AND DELIVER

Reports and evidence states

Keep observed findings, unavailable coverage, unknowns, business meaning, and recommended next questions visible for the MSP and client audience.

See current report examples →

IN BETA VALIDATION

Prove the workflow before widening the promise.

These areas are being tested with MSP partners. They are not general-availability claims.

MULTI-CLIENT WORK

Faster work across more accounts.

Improve application response, scan execution, evidence review, and report rendering as the team validates performance at greater scale.

REPORT EXPERIENCE

Clearer outputs for each audience.

Keep improving report relevance, evidence explanation, layout, and the path from a finding to the next responsible action.

BUILT WITH THE CHANNEL

The roadmap is not being written in a conference room.

Open Beta partners bring the workflows, objections, and unanswered questions that expose what a product still needs to earn.

A product built for the MSP community without the MSP community in the room eventually gives itself away. The best products are shaped in the real work—by the owners, sellers and technicians who know where the process breaks after the demo ends. SCOUTz is being built that way on purpose.

Steve Copeland, Founder of SCOUTz
Community input shapes the roadmap. Validation determines the label.

Feedback can move a capability forward, change its boundary, or remove it. Nothing is presented as available until the supported workflow has been built and validated.

COMING SOON

Four distinct product areas. Four different jobs.

Release dates are not announced. Each capability set still depends on testing, connected sources, permissions, and beta acceptance.

01 · DEFINE02 · BUILD03 · VALIDATE04 · BETA
CLOUD REVIEW
STAGE 1 OF 4Source mapping

Google Workspace review

Extend customer-approved cloud evidence beyond Microsoft 365.

  • Identity and administrator context
  • OAuth and connected-application inventory
  • Configuration, license, and coverage boundaries
Help us build it →
DEVICE EVIDENCE
STAGE 1 OF 4Coverage definition

Broader Apple device review

Move beyond the Apple inventory currently visible through supported Intune evidence.

  • Enrollment and ownership context
  • Supported operating-system and encryption posture
  • Management-source coverage and gaps
Help us build it →
APPLICATION GOVERNANCE
STAGE 2 OF 4Evidence model build

Deeper AI and SaaS review

Give the MSP a defensible view of business application use without claiming access to employee content.

  • Application presence and publisher context
  • Consent, permissions, owners, and activity signals
  • Review decisions and supplied agent metadata
Help us build it →
REPORT PRODUCTION
STAGE 3 OF 4Partner validation

Visual Report Studio

Turn supported evidence into an audience-specific report before export.

  • Plan and reorder report sections
  • Preview client-safe and operator views
  • Review evidence states before approved export
Help us build it →

RECENT PRODUCT RELEASES

What shipped, what it does, and who can use it.

Public tools are available on this site. Workspace capabilities are available to approved Open Beta partners and remain subject to their stated source and permission boundaries.

RELEASE 01 · PUBLICAVAILABLE NOW

Public Domain Score

Run one bounded review of a domain’s observable external posture without creating an account.

  • DNS and email-authentication records
  • Certificate and web-response evidence
  • Exposed-service and security-contact context
Run the public score →
RELEASE 02 · PUBLICAVAILABLE NOW

Domain Fix Lab

Turn a supported public finding into a configuration draft the MSP can review before making a change.

  • Named, single-purpose fix generators
  • Local browser-based preparation
  • Copy-ready records with implementation notes
Open Domain Fix Lab →
RELEASE 03 · CLOUDOPEN BETA

Microsoft 365 Review

Add customer-approved, read-only tenant evidence when public observation cannot answer the question.

  • Identity, administrator, and application context
  • Consent, permission, license, and coverage states
  • Supported security and managed-device evidence
Review the access boundary →
RELEASE 04 · REPORTINGOPEN BETA

Evidence Reports

Separate client-safe explanation from operator detail while keeping the source and evidence state attached.

  • Client-safe and operator report formats
  • Observed, inferred, unknown, and unavailable states
  • Business meaning and responsible next questions
Open sample reports →
RELEASE 05 · SALESOPEN BETA

Prospect Intelligence

Prepare an MSP seller with account context and defensible evidence before the first meeting.

  • Company and public-event context
  • Source-labeled opportunity hypotheses
  • Discovery questions, unknowns, and next actions
Explore prospect intelligence →
RELEASE 06 · DELIVERYOPEN BETA

Guided Remediation

Carry a supported finding into investigation, work planning, MSP-owned action, and verification.

  • Investigation prompts and implementation cautions
  • Work-plan and handoff guidance
  • Observable verification criteria
See the remediation workflow →
Under consideration does not mean promised.

Ideas stay outside the release ledger until the team can name the user, decision, source, boundary, and acceptance test. Some will move forward. Some should not.

HELP SHAPE WHAT SHIPS NEXT

Bring the workflow that gives your team trouble after the demo ends.

Open Beta feedback helps SCOUTz decide what to improve, validate, or leave out.