What changed
HYPOTHESIS (from convergence description, no source signals attached): Microsoft is ending the free 365 Business Premium nonprofit grant, forcing every affected nonprofit to re-engage with licensing/eligibility decisions on a 2026 deadline. FACT status unverified — the input contains zero signals and zero demand_evidence items, so the grant-change claim itself is uncited in this brief.
Why now
If the grant termination is real, it is a one-time wedge event with a hard deadline, and the IRS auto-revocation list publishes monthly, continuously minting urgent prospects. But 'why now' rests entirely on the unverified Microsoft change — verify before building.
Converging signals
Only one underlying signal is described (the Microsoft grant change); 'convergence' with Google/Canva/Slack nonprofit programs is inferred pattern-matching, not evidenced. This is a hypothesis-generated convergence, not a multi-signal one.
Customer pain
INFERENCE: losing the Microsoft grant means losing the org's entire email/identity stack — operationally existential for a staff-less nonprofit. Plausible but unproven: no r/nonprofit or TechSoup complaint threads were supplied as evidence. The system's own lesson (conf 0.85) says it is demand-blind, so absence of evidence here is weak absence — but per instructions it still scores low.
Who pays
The ED/treasurer/volunteer admin of a small US 501(c)(3) (<25 seats, below MSP coverage). Buyer is identifiable and enumerable via the IRS Business Master File (~1.8M orgs with addresses), but this segment is famously budget-starved; willingness to pay $15-39/mo for reminders is the single biggest open question.
Solved today
HYPOTHESIS: TechSoup/Percent validation emails, calendar reminders, MSPs for larger orgs, and simply reacting after something breaks. The volunteer tail below ~25 seats is likely unserved by MSPs (inference in the convergence, not evidenced).
Why current solutions are bad
Fragmented across platforms (Microsoft, Google, Canva, Slack each with separate revalidation), no unified deadline view, and the IRS auto-revocation list is obscure — orgs discover revocation only when a grant is denied. Unverified.
Proposed product
Micro-SaaS 'grant eligibility file': per-org dashboard tracking each platform grant's revalidation date, monthly IRS auto-revocation/Pub 78 monitoring by EIN, evidence vault for attestations, plus a one-time Microsoft Premium→Business Basic migration planner that flags lost security features (Intune/Defender).
MVP version
EIN-keyed monitor: ingest IRS BMF + monthly auto-revocation list (public downloads — squarely in founder's public-records strength), let an org enter its platform grants and dates, send email alerts. Plus a free 'check your EIN' lead-magnet page. 2-4 weeks of AI-assisted build.
30-day build
Week 1-2: verify the wedge — confirm the Microsoft grant change and read TechSoup/Percent comms (falsification check); scrape r/nonprofit and TechSoup forums for complaint volume. Week 2-4: build the EIN checker + run the prescribed outreach test (40 emails from BMF addresses cross-referenced with the auto-revocation list).
60-day build
If ≥4/40 respond (the convergence's own testable prediction): ship paid tier with multi-platform deadline tracking and migration planner; publish a free 'Microsoft nonprofit grant shutdown survival guide' targeting the deadline-driven search traffic.
90-day revenue plan
Convert free EIN-check users and guide readers to $15-39/mo; target 30-60 paying orgs (~$1-2k MRR) as proof, with the monthly revocation list as a perpetual outbound engine. Realistic first revenue day 60-90, within the founder's 180-day window.
Distribution path
Uniquely good: the entire prospect universe is a downloadable public file with addresses (IRS BMF/Pub 78), and the monthly auto-revocation list is a pre-qualified urgent-lead feed. Cold email + SEO on the migration deadline + r/nonprofit/TechSoup forum presence. No ad spend, no marketplace gatekeeper.
Pricing hypothesis
$15-39/mo per org, or a $99-199 one-time 'migration rescue' package for the Microsoft change (better matched to nonprofit budgeting than a subscription — test both).
Technical difficulty
Low. Public CSV/XML ingestion, cron checks, email alerts, small dashboard. No portal write-access needed (unlike ELDT, this is read/monitor-only — simpler but also less of a moat).
Legal / regulatory risk
Low. All data sources are public IRS files; no PII beyond org contacts; no representations to the IRS. Avoid implying legal/tax advice on eligibility.
Platform dependency
Moderate: the product's value tracks the platforms' grant programs, but it doesn't depend on their APIs or approval — it monitors public state. If platforms kill nonprofit grants entirely, the category shrinks, but the IRS-status-monitoring core survives.
Founder fit
High but not perfect. Matches the roster-enumerated public-records playbook and the founder's ELDT-proven skill of reading a mandate and finding who is forced to act. Two deviations from the proven ELDT shape: the 'regulator' is a platform, not the government, and there is no per-filing submission event to monetise — it's monitoring, not filing. Applied lesson (conf 0.80): true government-portal filing mandates fit best; this is adjacent, so 7 not 9.
Breakout potential
Moderate. Wedge → whole 'nonprofit ops compliance file' (state charitable-solicitation registrations, Form 990 deadlines — the latter IS a true forced-filer government mandate and a stronger long-term product than the platform-grant wedge). Expansion path is real and moves it closer to the founder's proven shape.
Final recommendation
CONDITIONAL GO — do not build yet. This is a well-shaped hypothesis (enumerable forced-ish buyers, public-records distribution, low build cost) with no evidence behind it. Spend 1-2 weeks on the convergence's own falsification tests: confirm the Microsoft grant change from a primary source, measure complaint volume on r/nonprofit/TechSoup, and run the 40-email outreach test. Build only if ≥10% respond wanting help; otherwise archive the pattern and reapply it to a true government filing mandate (e.g. Form 990/state charity registration).
Next action
Verify the Microsoft 365 nonprofit grant termination from a primary Microsoft source, then download the latest IRS auto-revocation list, cross-reference against orgs with visible platform-grant usage, and send the 40-email test batch.