FIELD NOTE 04
What a Domain Can Tell You—and What It Can’t.
Understand what public-domain evidence establishes, which internal conditions remain unknown, and when customer-approved Microsoft 365 access is needed.
Read the field note →INSIGHTS · MICROSOFT 365
Field notes on identity, MFA, guest accounts, connected applications, and what a read-only Microsoft 365 source can support.
FIELD NOTE 04
Understand what public-domain evidence establishes, which internal conditions remain unknown, and when customer-approved Microsoft 365 access is needed.
Read the field note →FIELD NOTE 05
Related: [Guest accounts now outnumber employees two to one](/insights/microsoft-365-guest-accounts) Hand a business owner a security questionnaire and…
Read the field note →FIELD NOTE 06
Related: [MFA adoption statistics for small business](/insights/mfa-adoption-statistics-small-business) Somewhere in your client's filing cabinet, or more…
Read the field note →FIELD NOTE 08
Every MSP I've ever met complains about the same thing. Outreach is miserable. Cold calls go nowhere, email campaigns get deleted, and the marketing dollars…
Read the field note →FIELD NOTE 09
Every Microsoft 365 tenant I've seen scanned has at least one, and most have a dozen: an application, connected years ago, holding permissions nobody can…
Read the field note →FIELD NOTE 10
Every MSP is preparing for the conversation where clients ask about adopting AI. I have news: the adoption already happened. It just didn't go through you,…
Read the field note →FIELD NOTE 16
When we designed the SCOUTz collector architecture, we made a decision that cost us features and I'd make again tomorrow: the platform does not read…
Read the field note →FIELD NOTE 20
Related: [SaaS security in 2026](/insights/saas-security-2026) There's a booming category of tools that will hand you a security score for any company on…
Read the field note →FIELD NOTE 22
Here's a mistake I made for years and watch other MSPs make daily: assuming clients care about security the way we care about security. We think in…
Read the field note →FIELD NOTE 23
Think about how an MSP walked into a first meeting ten years ago. A business card, a folder of references, maybe a co-branded brochure from whatever vendor…
Read the field note →FIELD NOTE 25
There's an uncomfortable fact at the front door of this whole business, and I'd rather address it head-on than hope nobody notices. The read-only domain…
Read the field note →FIELD NOTE 26
I've talked a lot about the free domain review as a conversation starter, so it's time to open the hood. What does a read-only domain review actually…
Read the field note →FIELD NOTE 28
Every company has an offboarding checklist, and almost every one of them contains the same hole. Collect the laptop. Disable the account. Forward the mail…
Read the field note →FIELD NOTE 31
RMM, PSA, EDR, backup, SOC, documentation, AI: most MSPs can buy roughly the same categories of tools. A competitor can copy a stack faster than they can…
Read the field note →FIELD NOTE 32
Picture two browser tabs before a first meeting. One can read the company's public domain records without asking anyone for access. The other cannot open…
Read the field note →FIELD NOTE 35
An MSP opens an application list and sees ChatGPT, Copilot, an AI meeting assistant, and three products whose AI features arrived during ordinary updates.…
Read the field note →FIELD NOTE 42
Putting AI in a service description does not create an AI service. It creates a claim. A real managed offering needs a defined customer, a supported use…
Read the field note →FIELD NOTE 43
More talent helps. It does not repair a workflow that asks every new technician to rediscover the same process. MSPs lose capacity in the spaces between…
Read the field note →FIELD NOTE 49
The usual MSP sales process loses information at every handoff. Marketing has the campaign context. Sales has CRM notes. The assessor has scanner output.…
Read the field note →FIELD NOTE 51
I have stood at a conference kiosk looking at a perfect dashboard on the big monitor while the actual demo ran on a laptop turned away from the room. The…
Read the field note →FIELD NOTE 53
There is always another list available. More companies, more contacts, more titles, more phone numbers, more records to move into a sequence. Those tools…
Read the field note →FIELD NOTE 56
The modern buyer does not wait for the MSP to explain what an MSP is. They can compare websites, reviews, service lists, certifications, vendors, pricing…
Read the field note →FIELD NOTE 59
Software companies occasionally describe sales technology as if the relationship is an inefficient step waiting to be automated. We do not believe that.
Read the field note →FIELD NOTE 61
Trust is easy to discuss when the claim is flattering. It matters more when the sentence limits the sale. SCOUTz does not guarantee more leads, a shorter…
Read the field note →FIELD NOTE 64
The breach slide usually starts with a familiar email address in large type. Then the label grows teeth: exposed credential, active risk, compromised user.…
Read the field note →FIELD NOTE 65
Strong cybersecurity claims require evidence that can support their certainty. Fear-based labels weaken credibility when the source proves less.
Read the field note →FIELD NOTE 67
Explain the condition, scope, ownership and verification behind an MSP recommendation before comparing tools and price. Evidence does not guarantee a sale.
Read the field note →FIELD NOTE 70
An AI application name is a starting point, not a conclusion. ChatGPT installed does not prove active use. An enterprise application registration does not…
Read the field note →FIELD NOTE 71
Related: [Shadow AI in small business](/insights/shadow-ai-small-business) AI discovery is not one capability. The phrase is used for several evidence…
Read the field note →FIELD NOTE 72
The Domain Scan earns a responsible reason to talk. It does not close the deal, finish discovery, or prove what is happening inside the company. The…
Read the field note →FIELD NOTE 80
Understand how CRM, contact data and security evidence support different parts of MSP sales preparation—and what a useful prospect brief should contain.
Read the field note →FIELD NOTE 81
Two products can review the same Microsoft 365 environment and answer different questions. BetterTracker publicly describes 365 Scout and its wider platform…
Read the field note →FIELD NOTE 85
For a while I described SCOUTz as a product that was not built by vendors. The line sounded sharp. It was also incomplete. It told you who I wanted to…
Read the field note →FIELD NOTE 87
Credibility, a plan, and trust. A domain scan produces expertise and earns the appointment. The consented cloud review produces the facts the plan is built…
Read the field note →FIELD NOTE 93
Shadow AI means AI use outside an organization’s approved governance. An application name or permission grant alone does not establish that use is unapproved. Establish the evidence, then confirm purpose, ownership and approval.
Read the field note →FIELD NOTE 94
Kaseya's 2026 SaaS Security Report covers 27.6 billion events across 50,000+ small businesses. The findings that matter for MSPs, and how to use them in sales.
Read the field note →FIELD NOTE 96
69% of SaaS accounts in small businesses are guests, per Kaseya's 2026 data. Why Microsoft 365 guest access sprawls, the risk, and the cleanup MSPs can sell.
Read the field note →FIELD NOTE 97
Only 27% of small businesses enforce MFA and 56% of accounts have it off, per Kaseya's 2026 SaaS data. What the MFA gap means and how MSPs close it.
Read the field note →FIELD NOTE 98
A step-by-step SCOUTz playbook for using public domain evidence to prepare an MSP conversation, earn consent, and hand a clearly bounded next step into delivery.
Read the field note →FIELD NOTE 100
The same MSP sales pitch can land with a founder and fail with a CFO. Start with the consequence each decision-maker is responsible for, then make the evidence fit the question.
Read the field note →FIELD NOTE 112
A 2026 workflow for turning customer-authorized, read-only Microsoft 365 observations into a dated MSP sales briefing with evidence, insight, proof, and clear limits.
Read the field note →FIELD NOTE 113
A complete 2026 workflow for turning a public-domain review into a traceable first-call evidence packet with sources, dates, limits, and verification questions.
Read the field note →FIELD NOTE 114
Public records and direct security tests are different activities. Review authorization, federal and state law, evidence limits and MSP outreach requirements.
Read the field note →FIELD NOTE 116
Understand CAN-SPAM requirements for rep-sent security reports: truthful claims, sender identity, postal address, opt-outs and the separate collection question.
Read the field note →FIELD NOTE 117
Use a 50-state research map to separate statutory access, consent, defenses, civil remedies and pending verification. No blanket scanning permission or risk rating.
Read the field note →FIELD NOTE 118
Document who authorizes a prospect assessment, its systems, methods, permissions, recipients and stop conditions. OAuth is scoped access, not legal clearance.
Read the field note →FIELD NOTE 119
Read Arizona's access definition and computer-tampering provisions together. Distinguish knowing access, authority, disruption and public-source MSP observations.
Read the field note →FIELD NOTE 120
Review California Penal Code § 502 access, data use, computer services and qualifying civil loss. Read-only operations do not by themselves establish permission.
Read the field note →FIELD NOTE 121
Examine Florida's knowledge requirement, authorized-security exception and conviction-linked civil remedy. Keep public observations and direct requests distinct.
Read the field note →FIELD NOTE 122
Read official Texas Penal Code §§ 33.01 and 33.02 for access, effective consent and the limited security-contract defense. Scope and purpose still need review.
Read the field note →FIELD NOTE 123
Read Pennsylvania § 7611 alongside § 7605's authorization defense. Examine implied consent, reasonable belief, confidentiality, restitution and jurisdiction.
Read the field note →FIELD NOTE 124
Examine Michigan's access and computer-service provisions, plus the aggregate-loss definition. Public-source evidence, permission and civil claims remain distinct.
Read the field note →FIELD NOTE 125
Read Massachusetts § 120F on knowing unauthorized access, authentication notice and failing to terminate access. No password is not universal permission.
Read the field note →FIELD NOTE 126
Review Washington's barrier-based authorization definition and white-hat research conditions. Commercial purpose, other laws and verification gaps still matter.
Read the field note →FIELD NOTE 127
Compare continuous security posture assessment with static reports. Use dated domain and Microsoft 365 evidence to guide an MSP buyer's next decision.
Read the field note →FIELD NOTE 128
An Applications Center for MSPs should connect permissions, licenses, AI features, history and trust. Review each client app without treating unknowns as clean.
Read the field note →FIELD NOTE 129
An AI Center for MSPs should separate connected apps, vendor AI features, agent identities, device evidence and Copilot seats. Turn each source into a decision.
Read the field note →FIELD NOTE 131
Verify Microsoft 365 MFA enforcement beyond registration. Compare capability, policy coverage, sign-in evidence and unknowns before making a client claim.
Read the field note →FIELD NOTE 132
OAuth app governance needs more than a permissions list. Separate access, ownership, activity and compromise evidence in a defensible Microsoft 365 review.
Read the field note →FIELD NOTE 133
A Microsoft 365 external sharing audit must separate access from leakage. Review links, guest access, business purpose and activity without inventing a breach.
Read the field note →FIELD NOTE 134
MSP AI demand vs revenue: interpret Kaseya's 48% and 13% survey findings, avoid false market-size claims, and define an evidence-led client service boundary.
Read the field note →FIELD NOTE 135
A service principal login success alert is not proof of compromise. Review identity, permissions, credentials and activity before making a Microsoft 365 claim.
Read the field note →FIELD NOTE 139
Use SCOUTz reports, findings and work context to train MSP sales teams on evidence-led discovery, consent, scope and technical handoffs.
Read the field note →FIELD NOTE 140
Use SCOUTz to prepare MSP sales discovery questions from company context, domain findings and approved cloud evidence, without rebuilding the brief each time.
Read the field note →Bring dated evidence, clear limits, and useful questions.