What changed
HYPOTHESIS (unverified — no signal text or demand_evidence was provided in this input): Microsoft is ending the free Business Premium nonprofit grant, falling back to capped free Business Basic, forcing small nonprofits to re-tier licenses, revalidate charitable eligibility, and absorb loss of Intune/Defender. Signal 1729 is referenced but its content was not supplied, so even the grant termination itself must be treated as inference here.
Why now
IF the grant termination is real, the wind-down window creates a hard deadline: act or receive surprise license bills and lose security tooling. Deadlines convert procrastinating micro-nonprofits into buyers. But 'MSP threads full of migration confusion' is asserted, not evidenced — zero demand_evidence items were provided.
Converging signals
Claimed convergence: (1) Microsoft grant termination announcement, (2) publicly enumerated obligated class via IRS Pub 78/BMF downloadable files with NTEE/size filters, (3) founder's proven roster-enumerated-compliance-file playbook. Only (2) is independently verifiable public infrastructure; (1) and the confusion volume are unverified inference in this input.
Customer pain
HYPOTHESIS: a 3-person nonprofit with donated Business Premium faces forced migration, potential surprise billing, loss of MFA/device management, and an eligibility revalidation it doesn't understand. No PAIN evidence items were provided to confirm anyone is actually complaining.
Who pays
Executive director or treasurer of small US 501(c)(3)s (<$1M revenue, no IT staff) currently on donated M365. Reachable: the IRS BMF enumerates them with EINs and addresses; emails require enrichment. Willingness to pay is UNPROVEN — this segment is notoriously price-sensitive and accustomed to free (TechSoup, donated licenses).
Solved today
HYPOTHESIS: TechSoup (Microsoft's official nonprofit validation partner) handles eligibility validation at nominal/no cost; nonprofit-focused MSPs (Tech Impact, RoundTable Technology, local IT shops) handle migrations; many nonprofits will simply accept free Business Basic and do nothing.
Why current solutions are bad
MSPs ignore sub-10-seat orgs (uneconomic); TechSoup validates eligibility but does not do license-tier optimization or replace the lost security stack; DIY nonprofits will misconfigure or overpay. This gap is plausible but asserted, not evidenced.
Proposed product
Productized service: flat-fee 'grant-loss migration' (license audit, Premium→Basic/discounted-tier optimization, security-gap report with low-cost Intune/Defender substitutes) converting into an annual 'licensing evidence file' subscription (eligibility revalidation, renewal-date monitoring, annual license re-optimization).
MVP version
No software MVP needed initially: an IRS BMF-filtered outreach list, a scripted license-audit checklist, a templated migration runbook, and a 2-page 'eligibility file' deliverable. Automate later (BMF ingestion, renewal reminders, license-price diffing) only after paid engagements prove demand.
30-day build
Verify the grant termination and revalidation cadence directly from Microsoft nonprofit eligibility docs (currently INFERENCE). Scrape/filter IRS BMF by NTEE and revenue. Run the stated falsification test: email 200 nonprofits a flat-fee offer; threshold >=10 calls and >=2 paid. Simultaneously check TechSoup forums for organic complaint volume and whether TechSoup/MSPs bundle this free.
60-day build
If test passes: deliver first 5-10 migrations at $500-1,500 flat, systematize the runbook, attach the $300-600/yr eligibility-file subscription at delivery, and build the renewal-monitoring automation.
90-day revenue plan
Scale outreach to 2,000+ BMF-filtered orgs; add referral channel via nonprofit bookkeepers/fractional CFOs who already bill these orgs. Target ~$10-20k cumulative from flat fees plus a base of annual subscriptions.
Distribution path
Cold email/direct mail from the IRS BMF enumeration (founder's proven public-records strength), plus nonprofit bookkeeper/accountant referrals. No ad spend, no marketplace. Weakness: email deliverability and the segment's low trust of cold vendors.
Pricing hypothesis
$500-1,500 flat migration (sized to org seat count) + $300-600/yr eligibility-and-optimization file. Deliberately below MSP minimums, above DIY-free.
Technical difficulty
Low. BMF parsing, checklists, M365 admin work, templated reports. The 'product' is packaging and repeatable delivery, not hard engineering.
Legal / regulatory risk
Low. No regulated data; acting as admin-on-behalf requires clean scoped-access hygiene and E&O-style care with client tenants. Not a government filing — no unauthorized-practice concerns.
Platform dependency
HIGH and the core structural weakness: the entire opportunity exists at Microsoft's pleasure. Microsoft reversing/extending the grant, or TechSoup bundling migration help free, deletes the wedge overnight.
Founder fit
Moderate-good, not the VERY-HIGH government-portal shape. It matches the roster-enumerated-compliance-file pattern (obligated class enumerated in public records, per-engagement monetization) and his public-records + automation strengths. But the 'regulator' is a private vendor, not a federal mandate — no statutory forced buyer, no filing portal to automate against, and the applicable lesson (gov-portal mandates score 8-9 founder-fit, conf 0.80) does NOT fully transfer.
Breakout potential
Moderate: the eligibility-file wrapper generalizes to other donated-software programs (Google for Nonprofits, Canva, Slack) — a 'nonprofit software-grant compliance file' covering all vendors. That expansion is the more interesting business than the one-time M365 wave.
Final recommendation
HOLD — do not build. Run the zero-build validation first: (a) verify grant termination + revalidation cadence in Microsoft's own docs, (b) confirm TechSoup isn't bundling this free, (c) execute the 200-email BMF test. Proceed only if >=2 paid engagements land; otherwise archive. The idea is cheap to test precisely because the MVP is a service, so the test IS the next action.
Next action
Fetch Microsoft's nonprofit eligibility/grant-change documentation and TechSoup forum threads to convert the core claims from inference to fact, then pull the IRS BMF, filter 200 targets, and send the flat-fee offer this week.