What changed
Wisconsin local governments have now received $160 million in opioid settlement funds (FACT: Wisconsin Watch headline). Under the national settlement structure, recipients must restrict spending to approved abatement uses and account for it (inference from national settlement terms, flagged as such in the source signal). Multiple states are simultaneously showing distress signals: Kentucky localities have spent only 10% of their money, and Indiana communities 'struggle to spend opioid settlement funds properly' (FACT: cited articles).
Why now
The money has landed and payouts continue for ~15 more years, but the accountability wave is just starting: Kentucky launched a public spend-tracking dashboard (FACT), journalists (Wisconsin Watch, WTHR, KyCEP) are auditing local spending, and Louisiana is calling for more oversight (FACT). Counties are moving from 'receive the check' to 'prove we spent it correctly' — that transition is when they buy tooling. No stated deadline, but annual reporting cycles and press scrutiny create recurring forcing events.
Converging signals
(1) $160M already disbursed to WI local governments — funded mandate, money exists whether or not tooling does; (2) documented spending dysfunction in comparable states (KY 10% spent, IN improper-spend investigation) proving counties lack management capacity; (3) state-built transparency dashboards (KY) signaling that public reporting expectations are rising — counties will be asked to feed data upward. Rule + filer class + reporting obligation meeting at one point.
Customer pain
A county of 20,000 people suddenly stewards hundreds of thousands of settlement dollars with DOJ-settlement strings attached, no dedicated staff, and Excel as the system of record. Fear vector: a Wisconsin Watch-style story naming YOUR county for improper or unspent funds, or a clawback/audit finding. The KY and IN stories are exactly this pain occurring in public (FACT for those states; extension to WI counties is hypothesis).
Who pays
County finance directors and health/human-services directors administering the local share of the $160M. At $2-5k/yr this sits under most counties' discretionary purchasing thresholds — no RFP required (hypothesis; thresholds vary by county). Secondary buyers: municipalities with direct allocations, and the consultants advising them.
Solved today
Excel spreadsheets plus general-ledger fund codes in legacy county ERPs (Tyler/other), occasional consultants billing hourly or a percentage, free technical-assistance guidance from nonprofits and state associations. None of these tag expenditures against the settlement's approved-use schedule or generate the report automatically (inference — needs validation call).
Why current solutions are bad
General ledgers track that money moved, not whether the use was settlement-approved; the approved-use crosswalk lives in a PDF exhibit nobody operationalizes. Result is exactly what the evidence shows: money sits unspent because staff fear misspending it (KY 10% figure supports this hypothesis), or gets spent improperly and surfaces in an investigation (WTHR).
Proposed product
OpioidLedger: single-purpose web app per county — import expenditures (CSV from any ERP), tag each to the settlement's approved-use categories, track allocation vs. remaining balance per strategy, flag questionable uses, and one-click generate the annual report in the state's required format plus a public-transparency page the county can link to preempt press scrutiny.
MVP version
Approved-use taxonomy encoded from the national settlement exhibit + WI-specific requirements; CSV import; tagging UI; balance dashboard; PDF/XLSX report export matching the WI DOJ/settlement-administrator format. No ERP integrations, no SSO, no procurement-grade features. 4-6 weeks solo with AI-assisted build — well within founder's demonstrated capability.
30-day build
VALIDATE BEFORE BUILDING: obtain Wisconsin's actual reporting requirements (WI DOJ settlement docs, the intergovernmental agreement governing the 30/70 state-local split, the real annual report form) — the paperwork burden is currently INFERENCE and is the make-or-break fact. Call 5 county finance/health directors (public officials, reachable by phone) and ask how they track it today and what they'd pay. Build MVP only if ≥2 say the report is painful.
60-day build
Ship MVP loaded with each pilot county's own published allocation (amounts are public record — demo with THEIR data, founder's demonstrated-value sales style). Convert 3-5 pilots at founder-friendly pricing ($1.5-2k yr one). Present or exhibit via Wisconsin Counties Association channels.
90-day revenue plan
Target 5-10 WI counties at $2-3k = $10-30k ARR. Then replicate: the settlement structure is national, so the same product re-skinned for the next state (pick one with active press scrutiny — Kentucky, Indiana, Louisiana per the evidence) is weeks of work, not months. Realistic first revenue day 90-150 given county budget calendars.
Distribution path
Direct outreach to a named, public, finite buyer list (all 72 counties publish contacts); Wisconsin Counties Association and county human-services association meetings; ride the press cycle — every Wisconsin Watch follow-up story is a sales trigger email; offer the public-transparency page free as the wedge, charge for the internal tracking/reporting layer.
Pricing hypothesis
$2-5k/county/yr subscription, sized to sit under discretionary purchase thresholds and under any consultant alternative. 72 WI counties = ~$150-350k ARR ceiling in-state; national local-government count puts the replicated ceiling in the tens of millions (inference).
Technical difficulty
Low. CRUD app + taxonomy + report generator. Hardest part is encoding the approved-use schedule and each state's report format correctly — domain work, not engineering, and it IS the moat.
Legal / regulatory risk
Low. Founder handles no controlled substances, no PHI, no funds — just expenditure records. Compliance knowledge is the product, not a license requirement. Main risk is giving wrong approved-use guidance; mitigate with 'tool not legal advice' framing and citing the exhibit text verbatim.
Platform dependency
None. No app store, no platform owner, no government portal gatekeeper who can revoke access (reports are documents submitted by the county, not API submissions).
Founder fit
Very high on the thesis (public money → compelled documentation → software layer, per the accumulated lesson at 0.79 confidence), with one honest deviation: this is fund-management SaaS with reporting output, not per-transaction portal submission like his ELDT app — subscription rather than per-filing monetization. His public-records skill directly powers the sales motion (demo with the county's own published allocation data), and his operational credibility plays well with county officials.
Breakout potential
High for a solo operator: ~$50B national pool over ~18 years (inference), thousands of local-government recipients, 50 near-identical replications, and adjacent expansion into other restricted-fund tracking (ARPA tails, future settlements — e.g., social media or PFAS settlements will reuse this exact structure).
Final recommendation
PURSUE, gated on one week of validation. The shape matches the founder's primary thesis (funded mandate, defined filer class, documentation burden, finite reachable buyer list), the build is trivially solo-feasible, and replication economics are excellent. But the single load-bearing assumption — that WI counties face a real, painful, recurring reporting obligation — is inference. Verify it with the WI DOJ settlement documents and 5 county phone calls before building. If the burden is real, this is a top-decile fit; if the report is trivial or state-provided tooling exists, kill it in week one at near-zero cost.
Next action
Pull the Wisconsin DOJ opioid settlement intergovernmental agreement and the actual county annual-report form/requirements (public records — founder's strength), and book calls with finance or health directors in 5 mid-size WI counties this week to ask: 'How do you track settlement expenditures against approved uses today, and what does your annual report take to produce?'