What changed
FACT (per convergence input, signal 1729 — source text not provided to this reasoning pass): Microsoft is ending the free 365 Business Premium grant for nonprofits, forcing license restructuring and eligibility revalidation. FACT (general regulatory background, stable and verifiable): the IRS auto-revokes tax-exempt status after 3 consecutive missed 990-N/990 filings, and publishes both the Business Master File and a monthly Auto-Revocation list. HYPOTHESIS: these two obligations now hit the same staff-less entity class in the same quarter.
Why now
The grant termination is a dated, forced re-decision touching hundreds of thousands of orgs at once — the only moment this class must simultaneously handle licensing evidence (TechSoup validation) and compliance posture. After the transition quarter passes, the bundle collapses back to a commodity 990-N filing service, so the wedge is time-boxed.
Converging signals
(1) Microsoft 365 Business Premium nonprofit grant ending with revalidation required for remaining free tiers [from convergence input; underlying source URL not supplied]. (2) IRS 990-N annual obligation with automatic revocation after 3 misses — existential because revocation ends deductibility [regulatory fact, not in supplied evidence]. (3) IRS BMF/Pub 78/Auto-Revocation list publicly enumerate the entire target class with addresses and filing status — a free, legal outbound roster [regulatory fact].
Customer pain
HYPOTHESIS — no demand_evidence rows were supplied, so pain is inferred, not proven: volunteer-run nonprofits forget the 990-N (the monthly auto-revocation list's ongoing size, if confirmed, would prove a persistent failure rate), and now face a confusing Microsoft license decision (Business Basic loses Intune/Defender vs Premium) with no IT staff. Reinstatement after revocation costs a $275+ IRS user fee plus Form 1023 paperwork — the insurance framing that justifies a subscription.
Who pays
The volunteer treasurer/board president of a <$50k-revenue nonprofit — clearly identifiable and reachable via the IRS roster, but this is also the weakest link: these orgs are budget-poor and famously reluctant buyers. Willingness to pay is UNPROVEN (empty demand_evidence) and is the single thing the 100-email test must establish before any build.
Solved today
HYPOTHESIS (well-known market, but no evidence rows supplied): the IRS offers free direct 990-N e-filing (~10 minutes); commercial e-filers (Tax990, File 990, Aplos) charge ~$0-90/filing; TechSoup handles Microsoft validation for free. Nothing bundles the two, and none of the filers run outbound against the at-risk segment of the roster.
Why current solutions are bad
The free IRS path fails silently — no reminder system, and the org only discovers revocation when a donor's deduction bounces. Commercial filers are reactive (SEO-inbound at tax time), not proactive off the auto-revocation pipeline. The Microsoft transition has no dedicated helper at all for the micro segment; MSP attention starts at orgs 10x larger.
Proposed product
Annual 'Compliance File' subscription: (a) 990-N filed on time every year with reminders and confirmation receipt, (b) TechSoup/Microsoft eligibility revalidated annually + one license audit at the grant transition, (c) a one-page security-baseline checklist covering what Business Basic loses vs Premium. Concierge-first; automate the 990-N submission layer only after paying customers exist (this is the founder's proven ELDT pattern: mandate → forced filer → submission layer → per-transaction fee).
MVP version
No software. Pull the IRS BMF + latest Auto-Revocation list (public CSVs), filter to <$50k orgs with a 990-N due within 60 days or one missed year, email 100 with a combined '990-N + Microsoft grant transition' offer, fulfill manually via the IRS site and TechSoup portal. Landing page + Stripe. Total cost: domain, email tooling, a weekend.
30-day build
Run the roster-outreach test exactly as the convergence's testable prediction specifies (100 emails → target ≥3 paid). Verify the two load-bearing facts first: the Microsoft grant end date/revalidation requirement from Microsoft/TechSoup primary sources, and the monthly auto-revocation list size. Test annual pricing (~$99-149/yr) against the hypothesized $29-49/mo — monthly is likely mispriced for this buyer.
60-day build
If conversion ≥2-3%: scale outreach to 2-5k at-risk orgs (email + postcard to BMF addresses, since roster emails don't exist — expect address staleness), systematize fulfillment with checklists, investigate IRS-authorized e-file provider status or an existing 990-N API/partner so filing scales past ~50 customers.
90-day revenue plan
100-200 subscribers at ~$120/yr = $12-24k ARR plus one-off $99 'grant transition rescue' fees. If conversion is <1% on two pricing variants, kill — the roster is enormous but a sub-1% rate on a forced-deadline offer means willingness to pay isn't there.
Distribution path
The IRS roster IS the distribution: free, legal, complete enumeration of every prospect with filing status and address — no ad spend, no SEO war. Auto-revocation list = monthly feed of the most desperate prospects. Weakness: email addresses are not in the BMF, so it's postal mail + scraped/appended contacts, which raises cost-per-touch.
Pricing hypothesis
$99-149/yr subscription (filing + revalidation + checklist) with a $99 one-time 'Microsoft grant transition audit' as the wedge offer. Per-filing à la carte ($49) as fallback if subscription resistance is high.
Technical difficulty
Low. MVP is manual. Automation phase: 990-N e-filing at scale requires either IRS e-file provider authorization or partnering/white-labeling an existing filer's API — a known, bounded hurdle, not a research problem. TechSoup has no public automation surface; that step likely stays manual per-account.
Legal / regulatory risk
Moderate-low: filing federal tax forms on someone's behalf implies accuracy liability; need clear ToS, E&O insurance, and possibly paid-preparer considerations (990-N is an e-Postcard with no tax computation, which softens this). CAN-SPAM compliance for cold email. Not 'heavy compliance' — same shape as the ELDT product he already runs.
Platform dependency
Real but diversified: IRS could change 990-N access (stable for 15+ years), Microsoft/TechSoup could simplify revalidation away (would kill the wedge but not the filing core). The subscription survives on the IRS obligation alone; the Microsoft angle is the time-boxed door-opener.
Founder fit
VERY HIGH on pattern: this is exactly his proven ELDT shape — public mandate, enumerated forced filers, submission layer, per-transaction/subscription monetization — plus public-records fluency for the BMF work. The 0.80-confidence lesson that government-portal mandate opportunities fit him best applies directly. The one mismatch: ELDT buyers (CDL training providers) are businesses with revenue; these buyers are near-broke volunteers.
Breakout potential
Moderate: expand to state charitable-solicitation registrations (40+ states, genuinely painful, orgs already pay Harbor Compliance real money), board-minutes/registered-agent upkeep, and other grant-eligibility revalidations. The 'compliance file for entities too small to have staff' wedge generalizes.
Final recommendation
TEST, don't build. The structure is genuinely good for this founder (forced buyer, public roster, ELDT-shaped) and the test costs under $500 and two weeks, but with an empty demand_evidence array the willingness-to-pay of budget-poor micro-nonprofits is the unproven load-bearing assumption. Run the 100-email roster test with annual pricing; kill on <1% conversion, scale on ≥3%. Do not write software before the test converts.
Next action
Download the current IRS BMF and latest monthly Auto-Revocation list, confirm the Microsoft grant end date and revalidation requirement from Microsoft/TechSoup primary sources, then send the 100-org test campaign within 14 days.