What changed
FACT (Federal Register, 2026-06-25): nine regulators (OCC, Fed, FDIC, NCUA, CFPB, FHFA, CFTC, SEC, Treasury) published the FINAL joint rule establishing FDTA data standards to make financial regulatory data machine-readable and interoperable. This is the statutory trigger: each agency must now incorporate these standards into its own collections — for the SEC that includes municipal securities disclosures to the MSRB (inference from FDTA statute scope; the provided rule text confirms the joint standards, not the muni-specific rulemaking).
Why now
The joint standards are now FINAL, which starts the clock on agency-specific implementing rules and compliance phase-ins. The filer class most structurally unprepared is municipal issuers: ~50,000 cities, counties, school districts and authorities (inference) that produce PDF financial statements with tiny finance staffs and no XBRL capability whatsoever. Corporate filers went through this with EDGAR/XBRL 15 years ago and an incumbent stack exists for them; munis have nothing equivalent and their advisors are small firms, not Big 4. Building now, during the phase-in window, means owning the category before compliance dates hit.
Converging signals
Three signals meet at one point, which per the system's own scoring rule constitutes convergence: (1) the finalized joint data-standards rule (FACT, cited); (2) a defined compelled filer class — entities regulated by the nine agencies, with muni issuers as the underserved wedge (class defined by statute; muni sizing is inference); (3) a known destination portal (MSRB EMMA for munis; EDGAR/FFIEC/NCUA systems for the other agency surfaces — inference). Supporting: an FFIEC 101 PRA notice showing the adjacent regulatory-reporting apparatus and respondent burden already exists (cited).
Customer pain
HYPOTHESIS grounded in structure: a small-city finance director or a 5-person municipal advisory firm cannot produce a schema-valid structured-data filing. Today they outsource continuing-disclosure dissemination for hundreds to low-thousands of dollars a year; adding a machine-readable format requirement converts 'upload a PDF' into a technical validation problem they are staffed to fail at. No complaint threads are in evidence — none are needed for a compelled filer class per the scoring rules — but the pain is a deadline-backed format conversion the filer cannot opt out of once the SEC's muni-specific compliance dates land.
Who pays
Primary: municipal advisory firms and dissemination agents (there are ~400+ SEC-registered MA firms; registry is public — inference on count) who file on behalf of many issuers and can spread a per-filing fee across a book of clients. Secondary: issuers directly (finance directors) for the long tail. Tertiary expansion: small credit unions/community banks facing NCUA/FDIC structured-data collections. The MA-firm channel means one sale yields 20-200 filings/year of volume.
Solved today
Issuers pay dissemination agents (e.g., DAC) and municipal advisors to post PDFs to EMMA; larger issuers use investor-relations platforms like BondLink. Corporate-side structured-data filing is served by Workiva, DFIN ActiveDisclosure, DataTracks, Novaworks — priced and designed for SEC registrants, not for a school district with a $30k disclosure budget. Nobody currently converts muni AFRs to FDTA-standard structured data because the standard just became final.
Why current solutions are bad
The incumbent muni workflow ends at 'upload a PDF' — it has no conversion, tagging, or validation layer, which is exactly what FDTA adds. The incumbent corporate XBRL stack is 10-50x too expensive and procurement-heavy for munis and MA firms. The gap is a self-serve, per-filing-priced converter with validation against the official taxonomy — a shape incumbents historically ignore because the per-seat enterprise price they need doesn't exist in this market.
Proposed product
Web app: upload the audited financial statement (PDF/Excel), AI-assisted extraction maps line items to the FDTA/XBRL muni taxonomy (XBRL US already publishes an ACFR taxonomy — inference, verify), human-in-the-loop review screen shows every mapped tag with source-page provenance, deterministic validator checks schema conformance, output is the compliant structured filing plus an audit-trail report; optional push/submission to EMMA on the customer's behalf, mirroring the founder's shipped ELDT-to-TPR per-upload model. Charge per filing; subscription for MA firms with multi-issuer books.
MVP version
No EMMA integration in v1. MVP = converter + validator only: ingest a real published muni ACFR PDF, emit taxonomy-tagged structured output plus a validation report, delivered as a white-glove service behind a simple upload page. Use 10 real ACFRs from EMMA as demo corpus. This is 4-8 weeks of AI-assisted build for this founder, and it is sellable to MA firms as 'FDTA-readiness' even before compliance dates bind.
30-day build
1) Read the actual final rule + FDTA statute sections on munis; extract the real compliance-date mechanics (kill/confirm the timing risk below). 2) Pull the XBRL US ACFR taxonomy and build the extraction→tagging→validation pipeline against 10 real ACFRs. 3) Scrape the SEC's public municipal-advisor registry into a prospect list. 4) Publish 3 plain-English 'what FDTA means for muni issuers' explainers to start owning the search category — it is nearly empty today (hypothesis).
60-day build
1) White-glove convert filings for 3-5 MA firms free-to-cheap in exchange for taxonomy feedback and testimonials. 2) Harden the validator (the defensible core — correctness is the product). 3) Price test: $200-500/filing vs annual per-issuer subscription. 4) Talk to MSRB/EMMA about submission mechanics and to GFOA about the practitioner view (also de-risks the 'MSRB builds it free' kill argument).
90-day revenue plan
Convert the pilot MA firms to paid annual 'FDTA-readiness' engagements covering their issuer books (e.g., $2-5k/firm/year pre-compliance, converting to per-filing at mandate onset). 10 firms at $3k = $30k in 90-180 days — real revenue during the phase-in, with the compelled-volume ramp still ahead. This meets the 180-day bar only via the advisor channel, not compelled filers; that is the honest structure of the bet.
Distribution path
Direct outreach to the public SEC MA registry (a finite, listable, reachable buyer set — the founder's demonstrated-value sales style fits); GFOA/NFMA conference and newsletter ecosystem; SEO on 'FDTA compliance for municipalities' while competition is near zero; partnerships with dissemination agents who need a conversion layer but won't build one.
Pricing hypothesis
$200-500 per filing (input's own hypothesis, plausible vs the $1-5k/yr issuers already pay advisors — inference); MA-firm subscription $2-10k/yr for unlimited validation + per-filing submission fees. At even 500 issuers × 2 filings/yr × $300 = $300k ARR; the 9-agency surface (credit unions, small banks) is the expansion multiple.
Technical difficulty
Moderate and founder-shaped: PDF financial-statement extraction is genuinely hard to do at 100% accuracy, which is why human-in-the-loop review is core MVP design, not a crutch. Taxonomy mapping + schema validation is deterministic engineering. EMMA submission automation mirrors the ELDT/TPR portal work he has already shipped. AI-assisted build keeps this solo-feasible with paid contractor help for the taxonomy edge cases.
Legal / regulatory risk
Low-moderate: the tool prepares and transmits disclosures; the issuer certifies them. Must avoid giving municipal advice (MA registration trigger — needs a lawyer letter, ~$5-10k, affordable). Errors in a filed disclosure are reputationally serious — the validation/audit-trail layer is both the moat and the liability shield. Not a reason to kill; a reason to build the validator first.
Platform dependency
Depends on EMMA/agency portal specs, but a government portal cannot deplatform a filer's agent — per the scoring rules this is not platform risk. Real dependency: the final muni-specific taxonomy could shift between proposal and adoption, forcing rework (manageable; standards drift slowly).
Founder fit
Maximal — this is structurally identical to his shipped FMCSA ELDT product: a federal mandate compels a defined class to submit to a government portal, and he builds the submission layer and charges per transaction. Adds his public-records fluency (muni financial documents) and systems-operations background. The applicable lesson ('government-portal mandate opportunities fit this founder best', confidence 0.79) directly supports this, and the fresh evidence here is stronger than that prior.
Breakout potential
High: munis are the wedge, but the FDTA covers nine agencies' collections — credit unions (NCUA), small banks (FDIC/OCC call-report adjacencies, see FFIEC 101 citation), FHFA sellers/servicers. Each is a new compelled filer class on the same conversion-validation engine. Fifty-state muni replication is built in since EMMA is a single national portal.
Final recommendation
PURSUE — with the 30-day gate. This is the founder's exact proven shape (mandate → compelled filer class → portal → per-filing fee) at 100x the ELDT market size, caught at the moment the trigger rule went final and before a competitive category exists. It survives the kill attempts: buyers are reachable and finite (MA registry), spend already exists (issuers pay advisors/dissemination agents today), the wedge (self-serve per-filing pricing + muni-specific validator) is defensible against enterprise-priced incumbents, and no VC or procurement is required. The one honest weakness is mandate timing, so the recommendation is conditional: spend 30 days confirming the muni-specific compliance path from the actual rule text before committing the full build. Fund the build from capital; sell 'FDTA readiness' to MA firms for first revenue inside 180 days; be the default converter when compliance dates bind.
Next action
Read the actual final rule (federalregister.gov/documents/2026/06/25/2026-12787) end-to-end plus FDTA §5892 muni provisions; extract the concrete standards, the agency-implementation timeline, and any muni carve-outs; simultaneously pull the XBRL US ACFR taxonomy and run one real city's ACFR through a prototype extraction→tagging pass to prove the core conversion is feasible.