What changed
FACT (per convergence input, signal 1729): Microsoft is ending the 365 Business Premium nonprofit grant, forcing grantee orgs to migrate licenses by a grant end date. HYPOTHESIS: this creates a synchronized migration window plus a recurring annual-revalidation duty across hundreds of thousands of small US nonprofits.
Why now
A vendor-imposed effective date compresses the affected class into one window; lapse allegedly suspends tenant licenses (email/files/identity down), which is auto-enforced urgency. CAUTION (inference): the grant wind-down may roll out per-tenant at renewal dates, meaning the 'cliff' is smeared over 12 months and part of it may already be behind us — this must be verified before building, since it determines whether the wedge still exists.
Converging signals
Only one underlying signal (Microsoft grant termination) plus public-data enablers (IRS Pub 78/BMF roster, MX/DNS tenancy detection). The signals array supplied is EMPTY, so convergence strength cannot be independently confirmed from source text — treat the whole pattern as a single-signal hypothesis.
Customer pain
HYPOTHESIS: <50-seat nonprofits with no IT staff face losing email/files/identity if they miss revalidation or mishandle the forced migration, and Business Basic strips Intune/Defender leaving a security gap. No PAIN evidence (forum threads, complaints) was supplied — the testable prediction (100-org outreach) is the cheapest way to confirm awareness and anxiety.
Who pays
Executive director or operations manager of a small US 501(c)(3) (<$2M revenue, <50 seats) running on a Microsoft 365 nonprofit grant tenant. They already pay for bookkeeping and payroll services at comparable price points, so a $99-199/mo 'keep our Microsoft grant compliant' line item is plausible — but this willingness-to-pay claim is UNPROVEN (no HIRING/SPEND evidence supplied).
Solved today
HYPOTHESIS: larger nonprofits use MSPs (Tech Impact, RoundTable Technology, regional MSPs); TechSoup validates eligibility and sells discounted licenses; the smallest orgs rely on a volunteer or nobody, and discover problems when something breaks.
Why current solutions are bad
MSP minimums and hourly rates don't fit 5-25 seat orgs; TechSoup validates eligibility but (inference) does not proactively manage migration, seat right-sizing, or the post-Basic security gap. The long tail is plausibly unserved — but 'TechSoup partners already blanket the small end with free migration help' is the stated falsifier and has not been checked.
Proposed product
A productized subscription: (1) annual Microsoft nonprofit eligibility revalidation handled done-for-you; (2) one-time migration plan and execution off Business Premium; (3) quarterly license true-up/right-sizing report; (4) a curated cheap third-party security baseline (MFA enforcement, backup, endpoint AV) replacing lost Intune/Defender; (5) monitoring that alerts before any lapse. Backed by a prospecting engine that cross-references the IRS BMF against MX records pointing at outlook.com/protection.outlook.com to build a precise target list.
MVP version
No software product needed for first revenue: the MVP is the target list (IRS BMF filter + MX scan, ~2-3 days of scripting — squarely in founder's public-records/automation wheelhouse), a one-page offer, and a manual done-for-you service for the first 10-20 clients. Tooling (tenant checks, lapse monitoring) gets built only after paid demand exists.
30-day build
Days 1-5: verify the falsifiers — exact grant end mechanics and dates, whether revalidation is genuinely annual with license suspension on lapse, and what TechSoup/Microsoft provide for free. Days 5-10: build the IRS-x-MX list (target 2,000 orgs). Days 10-30: run the stated testable prediction — email 100-500 orgs, measure discovery-call rate and awareness. Kill threshold as specified: <5 calls per 100 emails in 7 days.
60-day build
If validated: close 5-10 founding clients at $99-149/mo (or a $500-1,000 one-time migration package with subscription attach), deliver manually, document the runbook, and collect testimonials from named nonprofits for social proof.
90-day revenue plan
20-40 subscribers = $2-6k MRR plus one-time migration fees. Realistic only if the outreach test hits; with zero demand evidence in hand today, this is a hypothesis, not a forecast.
Distribution path
Cold email/phone from the IRS-x-MX list (highly specific, verifiable claim: 'your Microsoft grant ends on X and here is what breaks'), plus r/nonprofit and TechSoup forum presence, plus referrals from bookkeepers/CPAs who serve small nonprofits. No ad spend required. Risk: nonprofit boards move slowly even under deadline pressure.
Pricing hypothesis
$99-199/mo flat, or $750 one-time migration + $99/mo compliance retainer. Anchors against MSP hourly rates and the cost of a single day of email downtime.
Technical difficulty
Low. List-building is scripting; the service is Microsoft 365 admin work; later automation (Graph API tenant checks, license monitoring) is well within solo AI-assisted capability.
Legal / regulatory risk
Low-moderate: no regulated data handling, but taking admin access to client tenants creates liability exposure — needs an MSA, insurance, and careful credential hygiene. Cold email must respect CAN-SPAM (trivial).
Platform dependency
HIGH and structural: the entire wedge exists at Microsoft's pleasure. If Microsoft auto-migrates tenants gracefully, extends the grant, or TechSoup adds free migration concierge, the one-time wedge evaporates — the recurring residue (revalidation + license management) is thinner.
Founder fit
Strong pattern match to his proven ELDT shape — an authority (here Microsoft, not government) imposes a recurring duty on an enumerable class, and the roster (IRS BMF) is public. Public-records cross-referencing, automation, and demonstrated-value selling all play to strengths. Two deviations from the proven shape: the 'regulator' is a private vendor (weaker/less durable mandate than federal law), and the deliverable is an ongoing service relationship rather than a per-transaction filing, which edges toward the trust-building sales he avoids.
Breakout potential
Moderate: the same roster-x-tenancy engine extends to Google for Nonprofits compliance, other SaaS nonprofit grants, and generic 'grant software compliance' — a portfolio of small recurring duties across one enumerable class. Not venture-scale; a $10-30k MRR lifestyle SaaS/service is the realistic ceiling.
Final recommendation
VALIDATE, do not build. This is a well-shaped hypothesis that matches the founder's proven forced-filer pattern, with an unusually cheap and precise test already specified. Spend one week verifying the grant-end mechanics and running the 100-email outreach test; commit only if the >=5-calls threshold is met and the migration window is genuinely still ahead for a large cohort.
Next action
Verify the exact Microsoft nonprofit grant termination timeline and revalidation/lapse mechanics from Microsoft's official documentation and TechSoup/r/nonprofit thread volume; simultaneously build the IRS BMF x outlook.com-MX target list and send the first 100-email test batch.