What changed
HYPOTHESIS (secondhand, unverified in provided input): Microsoft is ending the free 365 Business Premium nonprofit grant on a fixed effective date, forcing thousands of small nonprofits to either pay up or migrate to a cheaper compliant stack. No primary source for the grant-end date or terms was provided in this input — this is the single load-bearing fact and it is currently UNCONFIRMED.
Why now
IF the grant termination is real, the fixed effective date synchronizes an otherwise diffuse long tail of small nonprofits into one dated buying window, and MSP communities reportedly (INFERENCE, signals 2057/2064 referenced but not included) want a productized package to resell. Dated cliffs are the best solo-founder demand spikes because outreach timing and messaging write themselves.
Converging signals
The convergence arrived with an EMPTY signals array and EMPTY demand_evidence. The pattern (roster-enumerated obligated class + survival-grade stick + synchronized deadline) is analytically sound and matches the founder's proven ELDT shape, but every leg — grant-end date, MSP demand, nonprofit willingness to pay — is presently inference, not evidence.
Customer pain
HYPOTHESIS: A small nonprofit with no IT staff losing Business Premium loses Intune, Defender, and email security in one stroke — operational continuity risk, not an abstract compliance nag. The pain is real IF the license change is real, but no complaints, threads, or job posts were supplied to prove anyone is experiencing it yet.
Who pays
Two candidate buyers: (1) MSPs serving nonprofit clients — the stronger payer; they already bill monthly, need a packaged answer for dozens of affected clients at once, and buy tools that make them look prepared; (2) individual nonprofits — weaker; notoriously budget-averse and conditioned to free help (TechSoup, Microsoft docs, volunteer boards). Lead with MSP white-label; treat direct-to-nonprofit as list-building for the MSP pitch.
Solved today
INFERENCE: Microsoft's nonprofit hub and TechSoup publish free general guidance; MSPs improvise per-client assessments manually; most small nonprofits will do nothing until something breaks. Nobody appears to sell an org-specific downgrade-impact dossier generated from public data — but that gap is unverified.
Why current solutions are bad
Generic guidance doesn't tell a specific org what THEY lose, what the cheapest compliant fallback stack costs for THEIR seat count, or give a sequenced migration runbook. MSPs doing this manually per client can't scale it across a synchronized deadline hitting all clients at once.
Proposed product
A generator: input a nonprofit's domain + seat estimate → output a branded dossier (current-stack detection via MX/SPF/DNS, exact feature loss on downgrade, cheapest compliant fallback — 300 free Business Basic seats + security add-ons — with dollar deltas, migration runbook with sequenced steps). Sold direct as a one-off report and white-labeled to MSPs as a per-client or flat-rate tool. Targeting engine: IRS Exempt Organizations BMF (public, free) cross-referenced with MX records to find likely grant holders.
MVP version
1) Script: pull 1,000 BMF orgs, resolve MX/SPF, measure Microsoft-hosted rate (the stated testable prediction, ≥30% threshold). 2) Template dossier: one hand-polished example for a real nonprofit. 3) Landing page offering a free 'grant-cliff impact report'. Total build: 2-3 weeks, near-zero infra cost — well within the founder's runway per the capital lesson (confidence 0.90).
30-day build
Week 1: VERIFY THE MANDATE — primary-source Microsoft's grant-end announcement, effective dates, and fallback terms before writing any product code; if secondhand thread is wrong, kill immediately. Weeks 2-3: run the MX-detection test on 1,000 BMF orgs; build the dossier generator. Week 4: 100-contact outreach (50 nonprofits, 50 MSPs via r/msp and MSP peer groups) offering the free impact report; success gate = ≥5 booked calls or white-label inquiries in 7 days, exactly as the hypothesis specifies.
60-day build
If gate passes: convert free reports to paid migration runbooks ($199-$499 one-off) and close 2-3 MSP white-label deals ($99-$299/mo per MSP or per-client pricing). Automate dossier generation end-to-end. If the gate fails on nonprofit side but MSPs bite, pivot fully to MSP tooling.
90-day revenue plan
Realistic: $2-6k cumulative from a handful of MSP white-label subscriptions plus one-off dossiers, riding the pre-deadline urgency window. The deadline does the selling; revenue concentrates in the 60-90 days before the effective date.
Distribution path
Cold email against the IRS BMF filtered by MX proxy (the enumeration IS the channel — founder's proven ELDT motion), plus MSP communities (r/msp, MSP Facebook/Discord groups) where the topic is reportedly already circulating. No ad spend, no marketplace approval, no relationship sales — demonstrated value via the free report.
Pricing hypothesis
Direct: free impact summary → $199-$499 full dossier + runbook. MSP white-label: $99-$299/mo or $29-49/client-report. Keep it impulse-priced for a no-IT-staff nonprofit and margin-positive for an MSP reselling at 3-5x.
Technical difficulty
Low. BMF is a public CSV; MX/SPF resolution is trivial; the dossier is deterministic templating + license-price math; Claude-assisted runbook generation. Hardest part is keeping fallback-stack pricing current with Microsoft's licensing churn.
Legal / regulatory risk
Low. Public data (BMF), CAN-SPAM-compliant B2B outreach, no client credentials or portal submission required for the dossier tier. Modest care needed with Microsoft trademark usage in marketing.
Platform dependency
HIGH and asymmetric: the entire opportunity exists at Microsoft's pleasure. If Microsoft delays, softens, or grandfathers the grant (it has reversed licensing decisions before — INFERENCE), demand evaporates overnight. This is the falsification condition the hypothesis itself names.
Founder fit
Strong but one notch below ELDT. Matches: roster enumeration from public records (BMF), reading a mandate, packaging a compliance response, per-transaction pricing, cold-outreach-with-proof motion. Differs critically: there is NO portal to file into and NO legal compulsion to buy — the 'stick' forces a decision, not a purchase, so the forced-buyer lesson (confidence 0.80) applies only partially. The obligated class must merely act; they can act for free.
Breakout potential
The generator pattern is reusable: every vendor license cliff, grant sunset, or forced migration (Google Workspace nonprofit changes, VMware/Broadcom-style repricing) is the same dossier engine pointed at a new roster. A 'license-cliff radar' subscription for MSPs is the expansion product with recurring revenue.
Final recommendation
CONDITIONAL GO — but gate everything on 48 hours of verification before any build. Step 1 (free): primary-source the Microsoft announcement. Step 2 (cheap): run the 1,000-org MX test. Step 3: the 100-contact outreach test. Each gate is days and near-zero dollars; the hypothesis is well-formed with explicit falsification criteria. Lead with MSP white-label, not direct-to-nonprofit. Do not score this as a proven forced-buyer play until demand_evidence exists — currently it is a strong pattern-match with zero attached evidence.
Next action
Today: fetch Microsoft's official nonprofit licensing announcement and confirm the grant-end date and fallback terms from the primary source; simultaneously download the IRS EO BMF and script the 1,000-org MX/SPF detection test.