What changed
FACT (cited): FTA published a Federal Register notice (2026-03-26) seeking OMB approval to extend the National Transit Database information collection under 49 U.S.C. 5335 — confirming the statutory annual reporting mandate continues unchanged. INFERENCE (well-established): NTD data drives the §5307 urbanized and §5311 rural formula apportionments, so reporting errors directly distort each agency's federal funding. This is a standing mandate, not a new rule — the 'change' is continuation of a forced-filer regime, which is the founder's target shape.
Why now
The mandate recurs every year on each agency's fiscal-year cycle, so there is always a cohort inside a 4-month filing window with a hard deadline. NTD reporting requirements have also been expanding (monthly ridership modules, safety/S&S events, asset inventory), raising burden on agencies with no dedicated analyst. HYPOTHESIS: modern LLM-assisted data reconciliation makes a solo-buildable validation engine feasible where previously only consultants or enterprise ITS suites could do this.
Converging signals
Three signals meet at one point, which per the scoring rubric IS convergence for a mandate: (1) the statutory rule (49 U.S.C. 5335, reaffirmed in the cited PRA extension notice); (2) a defined filer class (all urbanized-area transit agencies plus rural/reduced reporters via states — INFERENCE: ~2,000-3,000 entities); (3) a single federal portal (FTA's NTD reporting system) with known validation behavior. A second cited FTA collection (§5310/§5311 program reporting) shows the same agencies carry additional adjacent filing burdens.
Customer pain
Small and mid-size agencies must reconcile AVL/farebox counts, vehicle revenue miles/hours, asset inventories, safety events, and audited financials into NTD forms annually. Errors trigger FTA validation flags, analyst back-and-forth, and — the real fear — misstated data that reduces the agency's formula apportionment. FACT-grade demand basis: the mandate itself (forced buyer, no opt-out, deadline). INFERENCE: agencies without a data analyst pay boutique consultants today; no complaint-thread or job-posting evidence was provided, but per the forced-filer rule that absence does not negate demand.
Who pays
Primary buyer = the filer: small/mid urbanized-area transit agencies (public bodies, but a $3-10k purchase typically sits under micro-purchase/small-purchase thresholds — a P-card or single quote, not an RFP). Secondary buyer: transit consultancies who prepare NTD reports for multiple agencies (white-label seats), and state DOTs who compile reduced-reporter data for §5311 subrecipients. Beneficiary and buyer are the same party here, which is clean.
Solved today
HYPOTHESIS (consistent with input): in-house spreadsheets by a finance or ops manager wearing five hats; boutique transit consultants (e.g., RLS & Associates type firms) billing thousands per report; or NTD modules bundled inside enterprise ITS/AVL suites (TransTrack Manager, Clever Devices ecosystems) that small agencies can't afford or don't own.
Why current solutions are bad
Spreadsheets produce validation flags and year-over-year anomalies FTA questions; consultants are expensive and don't transfer capability; enterprise ITS bundles require the whole platform purchase. Nobody sells a cheap, standalone, small-agency-first prep-and-check layer. The FTA portal validates only AT submission — after the data is assembled — not while the agency is building the numbers.
Proposed product
Web SaaS: agency uploads farebox/AVL exports, GTFS, and financial statements; the system maps them to NTD form fields, runs the published FTA validation rules plus year-over-year anomaly checks against the agency's own public NTD history (NTD data is openly published — free training/benchmark corpus), and outputs portal-ready values with an audit trail explaining every number. White-label multi-agency workspace for consultants and state DOTs.
MVP version
Cut AVL ingestion from v1 (messiest surface). MVP = validation-and-anomaly engine: import last year's public NTD profile + this year's draft numbers (CSV/manual entry), run the FTA validation checks and cross-form reconciliations pre-submission, produce a flag report with fixes. That alone replaces the scariest part of the consultant's job and is buildable solo in weeks.
30-day build
Build the validation-rule engine from the public NTD Reporting Policy Manual; load the public historical NTD dataset for benchmarking; get 5 discovery calls with small-agency NTD contacts (contact names are listed in the public NTD data itself — a ready-made prospect list).
60-day build
Pilot with 2-3 agencies whose fiscal year ends June 30 (report window opens immediately after); add financial-form reconciliation; approach 2 transit consultancies with a white-label offer priced per client agency.
90-day revenue plan
Convert pilots at $3-5k/yr founding-customer pricing; one consultant white-label deal covering 5+ agencies. Target: $15-30k ARR booked by day 120-150, timed to the October reporting crunch for June-30-FYE agencies.
Distribution path
The public NTD dataset lists every reporting agency and contact — direct outreach requires no list-building. Amplify via state transit associations, CTAA, and state RTAP programs (which exist specifically to help small/rural agencies with exactly this). Demonstrated-value sale: run a free retroactive validation on their published prior-year report and show the flags — fits the founder's demo-not-relationship selling style.
Pricing hypothesis
$3-10k/yr per agency by size (INFERENCE: below consultant fees, above trivial); consultant white-label at per-managed-agency seat pricing. Undercutting consultant spend with software is the wedge the rubric prescribes.
Technical difficulty
Moderate. Validation rules and form logic are published and deterministic — ideal for the founder's fast-prototyping style. Hard parts deferred: AVL/farebox vendor-format ingestion (long tail of formats) and audited-financial parsing. LLM-assisted mapping helps but outputs must be deterministic and auditable.
Legal / regulatory risk
Low. Public reporting regime, no licensure, no PII beyond business contact data, no platform owner who can deplatform a tool that prepares data for a government portal. Agency remains the submitter of record — product prepares and checks, avoiding any question of unauthorized portal automation.
Platform dependency
FTA controls the NTD portal and manual; annual rule tweaks require maintenance (that churn is actually retention). No API dependency in the MVP since the agency keys in final values.
Founder fit
Near-maximal. This is structurally identical to his shipped FMCSA ELDT business: federal mandate → defined filer class → government portal → paid tooling layer. Applies the stored lesson (confidence 0.79) that government-portal mandate opportunities fit this founder best. His industrial-operations background maps directly to transit ops data (miles, hours, assets, incidents).
Breakout potential
Expansion within the same buyer: PTASP safety plans, TAM plans, §5310/§5311 program reporting (second citation), DBE reports, FFR submissions — a compliance suite for small transit agencies. 50-state replication via state DOT reduced-reporter compilation. Ceiling is real but bounded: ~2,000-3,000 filers caps this at a strong lifestyle-to-small-firm business, not a venture outcome — which matches the founder's goal.
Final recommendation
PURSUE — this survived the kill attempt. Forced annual filers, money-linked accuracy (formula apportionment), a published deterministic rulebook to build against, a public prospect list with named contacts, consultant spend to undercut, and a near-perfect match to the founder's proven FMCSA pattern. The honest risks are market-thickness and sales timing, not demand existence. Validate the addressable band before building: confirm 10 small agencies that neither use an ITS suite nor file via a state compiler.
Next action
Pull the public NTD dataset, segment agencies by size and reporter type, and email/call 10 small-urbanized NTD contacts with June-30 fiscal year ends offering a free retroactive validation of their last published report — kill or confirm willingness-to-pay within 3 weeks, before writing product code.