What changed
FACT (from input hypothesis text only — no source signals were provided): Microsoft announced the end of the free Microsoft 365 Business Premium nonprofit grant, replacing it with up to 300 free Business Basic seats plus discounted paid paths. HYPOTHESIS: this creates an enumerable class of nonprofit tenants that will silently lose Premium-only security features (Intune, Defender, conditional access) at renewal.
Why now
HYPOTHESIS: a lead window exists between announcement and each tenant's renewal date, and MSPs are currently confused (input cites an r/msp thread but did not include it as evidence). CAUTION: the announcement date is not in the input and must be verified — if the change began taking effect at renewals during 2025, many renewal cohorts have ALREADY crossed the cliff by mid-2026 and the pre-finalization window is partly or wholly closed. This single fact determines whether the pattern applies at all; verify before building.
Converging signals
Input provided zero signals and zero demand_evidence items. The convergence rests entirely on one licensing-change hypothesis (signal 1729, not included) plus the general 'Pre-Finalization Category Capture' pattern. Treat every demand claim below as unproven.
Customer pain
HYPOTHESIS: MSPs holding dozens of nonprofit tenants must re-quote licensing, explain silent security downgrades, and justify new annual spend to boards — manual per-tenant analysis via the M365 admin center is slow and error-prone. INFERENCE: nonprofits themselves don't know Business Basic drops Intune/Defender until something breaks or an insurer/auditor asks.
Who pays
Primary: MSP owners/service managers (reachable in r/msp, MSP Facebook/Discord groups, TechSoup partner community) who resell the analysis as billable advisory work. Secondary: larger nonprofits' internal IT. The MSP is the right buyer: one purchase covers many tenants and they already bill for exactly this work.
Solved today
Manually: exporting license assignments per tenant, cross-referencing feature matrices, building spreadsheets. Some RMM/SaaS-management suites (Augmentt, ScalePad, CIPP) do general license optimization; UNVERIFIED whether any ships a nonprofit-grant-specific cliff report — this must be checked in the kill test.
Why current solutions are bad
Generic license optimizers show seat waste, not 'this specific grant disappears on your renewal date and these 14 users lose device compliance enforcement.' The event-specific framing (dates, feature-loss deltas, board-ready cost options) is the gap — if it is still open.
Proposed product
Multi-tenant web app: MSP consents a read-only Graph app (delegated or GDAP), scanner pulls license SKUs, service plans, Intune enrollment, CA policies per nonprofit tenant, and emits a branded PDF 'Grant Cliff Report': feature-loss table per user, renewal-date countdown, three costed licensing paths, minimum-cost recommended mix. Per-report or per-tenant pricing; white-labeled so the MSP resells it.
MVP version
Single-tenant version: Graph API read of subscribedSkus + user license assignments + CA policies, hardcoded grant-transition rules, PDF output. 2-3 weeks solo with AI assistance. No Intune write scopes, no store listing needed.
30-day build
Week 1: verify the announcement timeline and remaining renewal-cohort window (kill condition #1); test CIPP/Augmentt/ScalePad for an existing equivalent report (kill condition #2). Weeks 2-3: build MVP scanner. Week 4: run the input's own testable prediction — offer 10 free scans in r/msp and one MSP community; the hypothesis specifies ≥10 volunteers in 7 days as the pass bar.
60-day build
Convert free-scan MSPs to paid multi-tenant accounts; add white-label PDF, GDAP bulk-tenant onboarding, and a renewal-date alert feed. Publish one 'state of the nonprofit grant cliff' data post from anonymized scan aggregates to own the vocabulary.
90-day revenue plan
Target 10-20 paying MSPs at $99-199/mo (unlimited nonprofit tenants) or $49/report — $1.5k-3k MRR is the realistic 90-day bar. Baseline fallback: even absent the cliff, the same scanner is a generic nonprofit-license-optimization report MSPs already bill for.
Distribution path
r/msp, MSP Discords/Facebook groups, TechSoup forums, cold outreach to MSPs advertising nonprofit specialization. Demonstrated-value motion (free scan → paid) matches founder's selling style. No ad spend required.
Pricing hypothesis
$49 per tenant report or $99-199/mo per MSP unlimited; white-label upcharge. MSP resells the report at $500-1,500 as advisory work, so pricing is far below buyer's realized value.
Technical difficulty
Low-moderate: Graph API reads, license-SKU feature mapping (tedious but static), PDF generation, multi-tenant OAuth consent. Well within solo + AI-assisted range. Main friction is GDAP/consent UX for MSPs.
Legal / regulatory risk
Low. Read-only tenant data under explicit MSP consent; standard DPA needed since nonprofit user data transits the tool. No regulated data categories required.
Platform dependency
High and double-edged: entirely dependent on Microsoft Graph API terms AND on Microsoft's licensing decisions. Microsoft softening the transition, extending the grant, or publishing its own migration report kills the event framing (the baseline optimizer survives).
Founder fit
Good but not his proven best shape. It rhymes with the ELDT play — a rule change creates an obligated class, build the tool, charge per unit — but the 'rule' is a vendor licensing change, not a government mandate, so there is no forced filing, no portal, no statutory deadline; the nonprofit can simply eat the downgrade. Fits his micro-SaaS/report-product/complaint-mining strengths and demonstrated-value sales motion. The high-confidence lesson that government-portal mandates fit best applies and caps founder_fit below the 8-9 tier.
Breakout potential
Moderate: wedge into a general MSP nonprofit-vertical toolkit (grant eligibility monitoring, TechSoup validation tracking, license optimization across Google/Microsoft nonprofit programs). The event is one-time; the vertical is durable.
Final recommendation
CONDITIONAL GO — but gate all build spend behind two cheap kill tests (≤1 week, ~$0): (1) confirm the transition timeline still leaves a meaningful renewal-cohort window, (2) confirm no incumbent MSP tool ships this report. If both pass, run the free-scan demand test the hypothesis itself specifies before charging. If either fails, keep the Graph scanner skeleton and re-aim it at the next enumerable licensing event.
Next action
Spend one day verifying the Microsoft announcement (official Microsoft Nonprofits blog/message center) and the renewal-cohort math, and search CIPP/Augmentt/ScalePad docs for an existing nonprofit-grant report. Only then post the free 'grant cliff report' offer in r/msp to test the ≥10-signup prediction.