What changed
HYPOTHESIS (from signal 1729, not independently verified here): Microsoft is terminating the donated Business Premium grant for nonprofits, leaving a smaller free tier (up to 300 Business Basic licenses) that is conditioned on validated nonprofit status and periodic revalidation. Affected orgs must re-plan licensing within one budget cycle or absorb full commercial pricing.
Why now
The grant change is rolling out now per the source signal; the window where tens of thousands of nonprofits must make a licensing decision is a one-budget-cycle event. After that window, the acute transition pain decays into a smaller recurring revalidation-maintenance need. Acting inside the window is the whole opportunity.
Converging signals
Weak convergence — this brief is built on a single signal (1729) plus a pattern template (roster-enumerated compliance file) and a free government roster (IRS Exempt Organizations Business Master File). The signals and demand_evidence arrays supplied are EMPTY, so no independent corroborating signals are in evidence.
Customer pain
HYPOTHESIS: losing the grant means either paying full commercial M365 pricing or losing mail/identity infrastructure — operationally existential for a staff-less nonprofit. Plausible and consistent with how these orgs run, but the system supplied zero PAIN evidence (no complaints, no unanswered questions), so pain intensity and willingness to pay are unproven.
Who pays
Executive director or operations lead of a small US nonprofit (~$250k-$5M revenue) running M365 under the nonprofit grant with no MSP and no internal IT. The IRS BMF makes this class enumerable and segmentable by size — a real, free, complete prospect list. Reachability is good; willingness to pay is the open question, since small nonprofits are notoriously price-averse and Microsoft's validation flow is designed to be self-serve.
Solved today
HYPOTHESIS: managed nonprofits get this from their MSP as part of an existing contract; unmanaged ones rely on TechSoup guidance, Microsoft's own nonprofit-portal revalidation flow, and volunteer/board members muddling through. No evidence in the input either confirms or sizes this.
Why current solutions are bad
MSPs only serve managed clients and won't chase $50/mo accounts; TechSoup gives generic guidance, not org-specific license-count optimization against the new tiers or a maintained evidence file. The unmanaged tail has nobody whose job it is to notice a failed revalidation before mail stops working.
Proposed product
(1) $99 one-time 'license cliff audit': what you have, what you lose, cheapest compliant configuration, Intune/Defender gap substitutes. (2) $25-75/mo eligibility-file subscription: revalidation calendar and paperwork, license-count monitoring against the 300-license tier, annual board-ready compliance snapshot. The audit is the wedge; the subscription is the business.
MVP version
No software needed for first revenue: a checklist-driven audit template, a scraped/filtered IRS BMF prospect list, and a cold-email sequence. Automate later (BMF ingestion, tenant license-count checks via Graph API with delegated read-only consent, revalidation reminders).
30-day build
Verify the mandate facts on Microsoft's nonprofit program pages (revalidation cadence, exact tiering, grandfathering policy — the falsification condition). Pull the IRS BMF, filter to $250k-$5M revenue orgs, enrich ~200 with contact emails. Run the stated outreach test: 100 emails offering the $99 audit; target ≥5 paid/booked in 7 days.
60-day build
If the test converts: deliver audits manually, standardize the deliverable, convert audit buyers to the subscription, and build the Graph-API license-count monitor. If it converts at zero: kill or reposition as a white-label tool sold to small MSPs instead of direct to nonprofits.
90-day revenue plan
Realistic path: 20-40 audits ($2-4k one-time) plus 10-20 subscriptions ($250-1,500 MRR) by day 90, driven entirely by list-based outreach during the transition window. Modest but fast, with the BMF providing effectively unlimited further prospects.
Distribution path
Cold email from the IRS BMF segmented list (the roster IS the channel), plus TechSoup forums, NTEN community, and state nonprofit-association newsletters. No ad spend, no marketplace, no gatekeeper. Deliverability and nonprofit inbox neglect are the practical risks.
Pricing hypothesis
$99 one-time audit → $25-75/mo maintenance subscription → possible $499/yr 'board compliance package' upsell. Low enough for a director's credit card; no procurement.
Technical difficulty
Low. BMF parsing, email tooling, a checklist product, later a read-only Graph API monitor. Well inside solo AI-assisted capability in days-to-weeks.
Legal / regulatory risk
Low-moderate: CAN-SPAM compliance on cold outreach, care not to misrepresent affiliation with Microsoft or the IRS, and accuracy duty on eligibility advice (bad advice could cost a client their tenant). No licensure required.
Platform dependency
High and asymmetric: the entire premise depends on Microsoft's program rules. If Microsoft grandfathers existing grants, simplifies revalidation further, or reverses course, the product's reason to exist shrinks overnight. This is the biggest structural risk after unproven demand.
Founder fit
Good but not perfect. It matches his proven pattern — read a mandate, enumerate the obligated class from a government roster, monetize the compliance burden — and his public-records/complaint-mining strengths. But the 'regulator' here is a vendor, not a government portal, and there is no per-filing transaction to own; it's advice + monitoring, not a submission layer. Fit is a 7, not the 8-9 of true portal-filing plays (per the accumulated gov-portal lesson, confidence 0.80).
Breakout potential
Moderate. The 'roster-enumerated compliance file' pattern generalizes: the same BMF-driven motion works for other nonprofit compliance products (state charity registration renewals, Form 990 deadline monitoring), which ARE government filings and fit the founder's per-filing model better. This idea could be the beachhead for that portfolio.
Final recommendation
CONDITIONAL GO — but on the test, not the build. The $99-audit outreach test is cheap (<$500, <2 weeks), the prospect roster is free and complete, and the downside is bounded. Do not build the subscription product until (a) Microsoft's pages confirm no grandfathering and a real revalidation cadence, and (b) the 100-email test produces paid bookings. If the test hits ≥5, this is a fundable-by-himself niche with a natural expansion path into true government-filing products for the same list.
Next action
Verify the grant-termination terms and revalidation cadence on Microsoft's nonprofit program pages today, then pull the IRS BMF and launch the 100-email $99-audit test this week.