What changed
FACT (per signal 1729 as quoted in the convergence input; no source URL was provided to verify): Microsoft is ending the free Business Premium nonprofit grant, with a fallback of up to 300 free Business Basic licenses 'depending on size'. Every affected nonprofit must act in the same window or lose licenses/security features.
Why now
The termination forces a one-time migration/revalidation event across the whole obligated class simultaneously. HYPOTHESIS: this window converts a cold outreach into a warm, deadline-driven conversation and is the only cheap wedge into a recurring subscription; six months after the deadline the wedge closes.
Converging signals
Only one hard signal (the grant change) plus two structural inferences: (1) the obligated class is enumerable via the public IRS Exempt Organizations BMF cross-referenced with domain MX records to isolate Microsoft-hosted orgs; (2) the sub-25-seat nonprofit tail is below MSP minimums. The signals array and demand_evidence array in this input are EMPTY, so convergence is thin and demand is unproven — scored accordingly.
Customer pain
HYPOTHESIS: losing Business Premium breaks Intune/Defender/desktop-Office workflows; mis-handling revalidation or the Basic-cap assignment risks email outage — existential for a small org. No complaint or forum evidence was supplied to confirm nonprofits perceive this as acute.
Who pays
Executive director or ops/admin lead of a US 501(c)(3) with roughly 3–25 staff, currently on donated Microsoft 365, no internal IT. Reachable directly by email because the class is enumerable (IRS BMF → domain → MX lookup). HYPOTHESIS until the outreach test runs.
Solved today
TechSoup for validation/discounted licenses; a local MSP if they can afford $1–2k/mo minimums; otherwise the ED does it themselves or ignores it until something breaks.
Why current solutions are bad
MSP pricing excludes the sub-25-seat tail; TechSoup validates eligibility but (HYPOTHESIS — must verify, this is a named falsifier) does not manage revalidation cadence, license right-sizing under the 300-Basic cap, or replacement security stack as an ongoing service.
Proposed product
'License compliance file' subscription: maintains eligibility documentation, calendars and executes annual/periodic revalidation, right-sizes license assignments under the free cap, and layers a budget security stack (e.g. Defender for Business add-on or third-party MFA/backup) replacing lost Premium features. Deliverable is a standing compliance file + quarterly attestation the board can see.
MVP version
No software needed to start: a runbook + spreadsheet delivered as productized service to first 10 clients, plus the lead-gen pipeline (IRS BMF pull, MX resolution, merge). Automate the audit (Graph API license/security posture report) only after paying customers exist.
30-day build
1) Verify Microsoft's published grant-change terms and actual revalidation cadence — this is the load-bearing fact and currently UNVERIFIED. 2) Build the BMF→MX pipeline, pull 200 Microsoft-hosted nonprofits. 3) Run the stated outreach test (≥5% response, ≥3 paid onboardings within 7 days of send). Kill or continue on results.
60-day build
Onboard first 10 clients at founder-led service level; write the Graph API posture-report script; document the revalidation calendar per org; collect testimonials from EDs.
90-day revenue plan
Target 20–30 orgs at ~$75/mo average ($1.5–2.2k MRR) plus one-time $250–500 migration/onboarding fees during the deadline window. Modest but recurring; founder has runway to ramp.
Distribution path
Direct email to the enumerated list (the core edge — nobody else is assembling BMF+MX-filtered lists), plus state nonprofit associations, CPA firms serving nonprofits as referrers, and content targeting 'Microsoft nonprofit grant ending' searches.
Pricing hypothesis
$50–150/mo per org tiered by seat count; one-time migration fee. HYPOTHESIS: orgs accustomed to $0 software may balk — willingness-to-pay is the single biggest untested assumption and the outreach test must include a real price.
Technical difficulty
Low-moderate: IRS BMF parsing, bulk MX lookups, Microsoft Graph API reporting, email outreach automation — all squarely inside founder's demonstrated public-records and automation skills.
Legal / regulatory risk
Low. CAN-SPAM-compliant B2B outreach; no regulated data. Must avoid implying Microsoft affiliation in outreach and product naming.
Platform dependency
HIGH and structural: Microsoft defines the program and could make the fallback fully automatic (named falsifier), extend deadlines, or restore grants — any of which dissolves the recurring service. Also churn risk to Google Workspace for Nonprofits, which remains free.
Founder fit
Good but not his best pattern. It rhymes with the ELDT edge (enumerable obligated class, recurring filing, per-org monetization, public-records lead gen) — the applicable lesson (confidence 0.80) favors mandate-shaped plays. But the 'regulator' here is a private vendor with no statutory force and a free competitor exit, so the forced-buyer structure is materially weaker than a government portal mandate. Fit 6–7, not 8–9.
Breakout potential
Moderate: the same BMF+MX enumeration engine generalizes to every vendor nonprofit-grant program (Google, Canva, Slack, Salesforce) — 'grant-stack compliance for small nonprofits' is the expansion thesis, reducing single-vendor dependency over time.
Final recommendation
CONDITIONAL GO — do not build yet. Spend week 1 verifying the two falsifiers (Microsoft's actual revalidation cadence; whether TechSoup bundles this) and week 2 running the 200-org priced outreach test. Total cost is a few hundred dollars and two weeks. Proceed to the productized service only if ≥3 orgs commit at a real price; otherwise archive with the outreach data as calibration.
Next action
Fetch and archive Microsoft's official grant-change announcement and revalidation terms (the core FACT is currently cited without a URL), then build the IRS BMF → MX-record matcher and generate the 200-org test list.