FIELD NOTE 86
The Scan They Asked For.
Offer it as an opt-in courtesy that works with the company's existing IT provider, send it only after the recipient replies, and make the booking link…
Read the field note →INSIGHTS · MSP SALES & GROWTH
Practical writing on MSP marketing, prospecting, qualification, pricing, and the evidence that makes the next conversation useful.
These notes cover the commercial decisions an MSP makes before and after a first meeting: who fits, what to say, how to qualify the work, and how to price it without turning evidence into a guarantee.
FIELD NOTE 86
Offer it as an opt-in courtesy that works with the company's existing IT provider, send it only after the recipient replies, and make the booking link…
Read the field note →FIELD NOTE 88
MSP marketing that produces meetings, not impressions: niche keywords, a free evidence offer, content that answers real questions, and one number to track.
Read the field note →FIELD NOTE 89
How MSPs get clients in 2026: pick a niche, let the website qualify, work partnerships and referrals, then walk into every first meeting with evidence.
Read the field note →FIELD NOTE 90
Referrals built your MSP and will not scale it. Five outbound plays, run in parallel, that turn an MSP sales strategy into predictable pipeline in 2026.
Read the field note →FIELD NOTE 91
A working MSP prospecting plan: define the target, write the value line, set a number, pick two channels, personalize with evidence, follow up on schedule.
Read the field note →FIELD NOTE 92
Assess scope, delivery effort, ownership and commercial fit before quoting. Separate observed evidence, customer confirmations, gaps and unassessed areas.
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 95
Scope smaller engagements without underpricing. Validate delivery work, expectations and potential licensing changes before quoting.
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 101
MSP sales self-doubt changes what you notice. A founder's lesson on the sentence that makes an opportunity visible or invisible, and how to write over it this week.
Read the field note →FIELD NOTE 102
Why MSP renewals stall when activity replaces proof, and how to bring dated evidence, ownership, and a verifiable next choice into the QBR.
Read the field note →FIELD NOTE 103
Why MSP prospects go quiet after a first meeting, and how one evidence-backed condition, owner, and next choice keeps the conversation moving.
Read the field note →FIELD NOTE 104
How a technical MSP translates a supported finding into business language without changing the source, boundary, or truth.
Read the field note →FIELD NOTE 105
Compete with a cheaper MSP by comparing evidence, scope, exclusions, and proof of completed work. Confidence alone cannot establish the better offer.
Read the field note →FIELD NOTE 106
Why MSP lead generation without closed deals is a meeting-to-decision problem, and how to inspect the handoff before buying more volume.
Read the field note →FIELD NOTE 107
What larger, more sceptical buyers need from an MSP: dated observations, clear limits, delivery ownership, and a proof path that survives scrutiny.
Read the field note →FIELD NOTE 108
How MSPs can learn why proposals win or lose by recording the buyer's decision, evidence, scope, and stated outcome instead of guessing.
Read the field note →FIELD NOTE 109
Compare seven MSP prospecting tools in 2026 by their job: dated evidence, buyer research, contact discovery, technical context, and follow-up.
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 130
Read MSP customer acquisition benchmarks from Kaseya's 2026 survey. Separate reported challenges from close rates and build an evidence-led sales process.
Read the field note →FIELD NOTE 136
Build an MSP sales proof checklist covering outcomes, dated findings, scope, authorization and verification. Use Kaseya's framework without sales guarantees.
Read the field note →FIELD NOTE 137
Use SCOUTz reports, Report Plays and link-open boundaries to keep MSP proposal follow-up tied to a real finding and next decision—not generic chasing.
Read the field note →FIELD NOTE 138
Build your MSP proposal template around SCOUTz findings, client-safe reports and evidence-linked work plans, so scope does not start from a blank document.
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.