What changed
HYPOTHESIS (no signals supplied in input): Microsoft is terminating/restructuring its donated Microsoft 365 Business Premium nonprofit grant, forcing affected orgs to revalidate via TechSoup, downgrade to a ≤300-seat Business Basic fallback, or pay commercial rates. The convergence description references 'signal 1729' but the signals array is empty, so the underlying event is UNVERIFIED in this input.
Why now
IF the grant termination is real, it is a synchronized deadline event across the entire obligated class this cycle — every affected nonprofit must act at roughly the same time, which is the best possible moment to reach them. This urgency claim is inherited from the hypothesis, not from supplied evidence.
Converging signals
None supplied. The input contains zero signals and zero demand_evidence items. Everything below the pattern level (roster-enumerated compliance file) is inference layered on inference. The applicable lesson ('engine is capability-rich but demand-blind', conf 0.85) suggests low demand scores may partly reflect ingestion gaps rather than absent demand — but per instructions I must score from supplied evidence, and there is none.
Customer pain
HYPOTHESIS: a staff-less nonprofit that loses Business Premium loses Intune/Defender/email security or absorbs a full-price licensing bill — budget-existential at sub-$1M revenue. Plausible and specific, but not one complaint, forum thread, or job posting was provided to prove anyone is experiencing or articulating this pain.
Who pays
Executive directors / lone 'accidental techies' at US 501(c)(3)s under ~$1M revenue holding Microsoft nonprofit grants. Identifiable and reachable via the IRS Exempt Organizations Business Master File (public, with addresses and revenue bands) — the roster is real and free. Whether they will PAY (vs. lean on TechSoup forums and free peer advice) is the central unproven assumption; this segment is notoriously price-sensitive.
Solved today
INFERENCE: larger nonprofits use nonprofit-focused MSPs (Tech Impact, RoundTable Technology); small ones rely on TechSoup validation flows, TechSoup/r/nonprofit forums, and ad-hoc volunteer IT. Nobody is paid to maintain a recurring eligibility calendar for a $250k-revenue org because the economics don't support human service delivery — which is either an opportunity for software or evidence there's no budget at all.
Why current solutions are bad
Free community answers are generic, one-off, and arrive after the deadline panic; MSPs won't touch sub-$1M orgs profitably. A software 'eligibility file' could serve the long tail at a price MSPs can't. But 'unserved' can equally mean 'unmonetizable' — the kill test must distinguish these.
Proposed product
Subscription eligibility file per org: revalidation calendar (TechSoup/Microsoft/Google/Canva grant programs), license census vs. entitlement, migration plan off the expiring grant with cost comparison (Basic fallback vs. discounted Premium vs. Google Workspace for Nonprofits), and a security-gap checklist for what's lost in downgrade. Onboarding pre-filled from IRS BMF/990 data.
MVP version
No product yet — a validation asset first: a free personalized 'Microsoft grant exposure report' generated per org from IRS BMF + a 5-question intake, emailed to 100 targeted nonprofits. The paid MVP (if validated) is a simple portal: org profile, deadline calendar with email nudges, migration decision tree, and a printable board-ready one-pager. 2-4 weeks of AI-assisted build; no government portal integration required.
30-day build
Week 1: verify the grant-termination facts directly (Microsoft nonprofit hub, TechSoup announcements) and measure thread volume on r/nonprofit + TechSoup forums — this is the missing demand evidence. Weeks 2-4: run the stated testable prediction — email 100 IRS-BMF-filtered nonprofits + one r/nonprofit post; target ≥5 discovery calls. Kill threshold: <3 calls or Microsoft confirms auto-migration with no action required.
60-day build
If validated: build the paid portal, convert discovery calls into 5-10 founding subscribers at $25-49/mo or a $199 one-time 'migration file', partner-post through nonprofit newsletters (Nonprofit AF, NTEN community) rather than ads.
90-day revenue plan
Target: 20-40 paying orgs (~$500-2,000 MRR) plus one-time migration-file sales riding the deadline. Modest ceiling unless expanded across grant programs (Google, Canva, Adobe, Slack nonprofit tiers) into a general 'nonprofit software-grant compliance calendar'.
Distribution path
Direct: cold email/postal from IRS BMF revenue-filtered roster (legally public data — a genuine, unusual targeting edge). Community: r/nonprofit, TechSoup forums, NTEN, state nonprofit associations. No ad spend, no app-store gatekeeper, no platform approval. The roster-based targeting is the strongest structural asset in this idea.
Pricing hypothesis
$25-49/mo subscription or $199 one-time migration file; possibly $99/yr maintenance tier after the migration wave. Must stay under the 'ask the board' threshold. Risk: post-migration churn makes this a one-cycle product unless the multi-program calendar creates recurring value.
Technical difficulty
Low. IRS BMF/990 ingestion is a solved public-data problem squarely in the founder's wheelhouse; the product is CRUD + calendaring + templated decision logic. No API integration with Microsoft required for v1 (attestation-based license census). 3/10 difficulty.
Legal / regulatory risk
Low. Public IRS data, no PII beyond business contacts, no regulated advice (licensing guidance, not legal/tax opinion). CAN-SPAM compliance on cold outreach. Avoid implying Microsoft/TechSoup affiliation — trademark care in naming.
Platform dependency
Moderate and asymmetric: Microsoft controls the grant program's rules. The falsification case in the input is real — if Microsoft auto-migrates everyone to Business Basic with zero action required, the recurring-evidence burden evaporates and the product collapses to a one-time explainer. This is checkable in week 1 and must be checked before any build.
Founder fit
Good but not perfect fit. Matches the proven ELDT pattern structurally (roster of obligated parties + compliance event + per-org monetization) and uses his public-records strength directly. BUT the 'quasi-regulator' is a private vendor, not a government portal: no federal mandate, no statutory deadline, no forced filing into a government system — so it lacks the forced-buyer teeth that made ELDT work (government-portal lesson, conf 0.80, applies only by analogy). 6-7/10, below a true mandate play.
Breakout potential
Moderate: 1.8M+ orgs in the IRS exempt-org file; a multi-vendor grant-compliance calendar could become the 'renewal brain' for small-nonprofit software stacks, expandable into state charity-registration renewals (which ARE government filings — a stronger adjacent wedge worth noting).
Final recommendation
DO NOT BUILD YET — run the cheap two-week validation exactly as the testable prediction specifies. The pattern is sound, the roster-targeting edge is real, technical risk is trivial, and the founder can fund the ramp; but with empty demand evidence and a live falsification scenario, the only rational next step is the $0-cost outreach test plus verifying Microsoft's actual migration mechanics. Promote to BUILD only on ≥5 discovery calls AND confirmation that grantees must take recurring action.
Next action
Today: (1) pull Microsoft's official nonprofit-grant transition announcement and TechSoup's guidance to confirm whether affected orgs must act or are auto-migrated; (2) count r/nonprofit + TechSoup forum threads on the change in the last 60 days; (3) build the 100-org IRS BMF target list (revenue <$1M, likely M365 grant holders) and send the outreach email with a free 'grant exposure report' hook.