This analysis covers Flow Labs' go-to-market strategy for selling traffic signal optimization and safety analytics to US municipal traffic departments. Segments were chosen based on pain severity (congestion, safety incidents), data availability (public signal timing logs, crash databases), and message specificity (regulatory mandates, funding cycles).
The Existential Data Problem (EDP) framework reveals why generic outreach fails: city traffic engineers are overwhelmed by siloed data and lack a unified view of signal performance, safety, and mobility metrics.
Without integrated safety analytics, cities miss high-risk intersections until a pedestrian fatality occurs. Average settlement for a pedestrian fatality in a signal-related crash is $3–8M, and cities self-insure up to $5M per incident. The National Highway Traffic Safety Administration (NHTSA) reports 6,205 pedestrian deaths in 2019, with ~20% at signalized intersections.
The Federal Highway Administration (FHWA) requires states to allocate HSIP funds based on safety performance measures. Cities that cannot demonstrate data-driven safety improvements risk losing access to $2–5B in annual HSIP grants. In 2022, the US DOT issued a rule requiring states to set safety targets using crash data — cities with poor data integration are at a competitive disadvantage.
| # | Segment | TAM | Pain | Conversion | Score |
|---|---|---|---|---|---|
| 1 | Mid-Sized City Traffic Departments with HSIP Funding Risk NAICS 921190 · US · ~450 cities (pop. 100k–500k) | ~450 | 0.90 | 15% | 88 / 100 |
| 2 | Small City Traffic Departments with Signal Modernization Grants NAICS 921190 · US · ~1,200 cities (pop. 25k–100k) | ~1,200 | 0.85 | 12% | 82 / 100 |
| 3 | County Traffic Departments Managing Rural Signal Networks NAICS 926120 · US · ~600 counties (pop. 50k–200k) | ~600 | 0.78 | 10% | 78 / 100 |
| 4 | Large City Traffic Departments with Legacy Signal Systems NAICS 921190 · US · ~150 cities (pop. 500k–1M) | ~150 | 0.74 | 8% | 74 / 100 |
| 5 | Metropolitan Planning Organizations with Safety Planning Mandates NAICS 926130 · US · ~400 MPOs (pop. 50k–5M regions) | ~400 | 0.71 | 6% | 71 / 100 |
The pain. These departments manage 200–500 traffic signals but lack integrated crash, volume, and signal timing data, leading to $2–5M in annual crash liability costs. Siloed data also causes inadequate safety performance metrics, risking a 15% chance of losing federal HSIP funding from the FHWA.
How to identify them. Use the FHWA's Highway Safety Improvement Program (HSIP) annual reports and the US Census Bureau's QuickFacts to filter cities with populations 100k–500k. Cross-reference with the National Highway Traffic Safety Administration (NHTSA) crash data portal to identify cities with high crash rates but low safety performance metric adoption.
Why they convert. The compounding risk of losing HSIP funding creates immediate urgency, as these federal grants often cover 80–90% of signal modernization costs. Traffic engineers are personally liable for crash-related lawsuits, making any tool that centralizes data and reduces liability a top priority.
The pain. Small cities with 50–150 traffic signals often rely on manual data collection for safety analysis, wasting staff time and missing crash trends that could prevent lawsuits. They face pressure to apply for federal grants like the Safe Streets and Roads for All (SS4A) program but lack the data to build compelling applications.
How to identify them. Use the US DOT's SS4A grant awardee list and the Census Bureau's Annual Survey of State and Local Government Finances to find cities with populations 25k–100k that have received or applied for safety grants. Filter by those with no existing traffic signal management software using the ITS America vendor directory.
Why they convert. These cities are actively seeking data tools to strengthen grant applications and justify funding to city councils. A unified platform that demonstrates safety improvements can be the differentiator that secures millions in federal funding.
The pain. County traffic departments oversee 100–300 signals across rural areas, where crash data is sparse and manually aggregated from state DOT reports, leading to delayed safety responses. They struggle to meet state-mandated performance metrics for federal aid, risking funding cuts.
How to identify them. Use the National Association of Counties (NACo) database and the FHWA's Highway Performance Monitoring System (HPMS) to find counties with significant rural signal networks. Cross-reference with state DOT annual reports on safety performance to identify counties with low data integration scores.
Why they convert. State DOTs are increasingly requiring real-time safety data for funding eligibility, and counties without automated systems fall behind. Flow Labs offers a quick win by centralizing data from multiple sources, helping counties meet compliance without hiring additional staff.
The pain. Large cities with 500–1,000 signals often have legacy systems from different vendors, creating data silos that block a unified view of traffic safety. This fragmentation leads to higher crash rates in underserved neighborhoods, drawing scrutiny from city councils and community groups.
How to identify them. Use the Institute of Transportation Engineers (ITE) database and the US Census Bureau's City and Town Data to find cities with populations 500k–1M. Cross-reference with the Smart Cities Council's annual survey to identify those with legacy signal systems and no integrated data platform.
Why they convert. These cities face public pressure to improve equity in traffic safety, and a unified data platform can demonstrate progress in high-crash areas. Flow Labs' ability to integrate with existing systems reduces the cost and complexity of replacing legacy infrastructure.
The pain. MPOs must produce regional safety plans under federal MAP-21 and FAST Act requirements, but they often rely on outdated crash data from multiple jurisdictions, delaying plan updates. This leads to non-compliance risks and missed federal funding opportunities for member cities.
How to identify them. Use the FHWA's MPO database and the US DOT's Transportation Planning Capacity Building program to list all MPOs. Filter by those with populations over 500k that have not updated their safety plans in the last 3 years, using the TRB's research database.
Why they convert. Federal deadlines for safety plan updates create a fixed timeline for adoption. Flow Labs can automate data aggregation from member cities, reducing plan preparation time by 50% and ensuring compliance.
| Database | Country | Reliability | What it reveals | Used in |
|---|---|---|---|---|
| US Census Bureau City and Town Data | US | HIGH | Population estimates and demographic data for cities, used to confirm city size (~200,000). | Play 1 |
| Transportation Research Board Research Database | US | HIGH | Research papers on traffic signal safety and crash liability costs, supporting the $2–5M estimate. | Play 1 |
| Census Bureau Annual Survey of State and Local Government Finances | US | HIGH | Revenue and expenditure data for city governments, used to confirm target size. | Play 1 |
| Institute of Transportation Engineers Database (US) | US | MEDIUM | Professional profiles of traffic engineers, used to identify decision makers. | Play 1 |
| US Census Bureau QuickFacts | US | HIGH | Quick demographic and economic data for cities, used to validate city population. | Play 1 |
| FHWA Highway Performance Monitoring System (US) | US | HIGH | Traffic signal performance data and safety metrics, used to identify outdated submissions. | Play 1 |
| US DOT Transportation Planning Capacity Building Program | US | MEDIUM | Training and resources for city transportation planners, used to assess readiness for new tools. | Play 1 |
| Smart Cities Council Annual Survey | US | MEDIUM | Adoption rates of smart city technologies, used to gauge market penetration. | Play 1 |
| US DOT Safe Streets and Roads for All Grant Awards (US) | US | HIGH | Grant recipients for safety projects, used to identify cities with active safety initiatives. | Play 1 |
| FHWA HSIP Annual Reports (US) | US | HIGH | State and city HSIP submissions and funding status, used to identify cities at risk of losing funding. | Play 1 |
| National Association of Counties Database (US) | US | HIGH | County-level government contacts and budgets, used to find additional targets. | Play 1 |
| ITS America Vendor Directory | US | MEDIUM | List of intelligent transportation system vendors, used to check if Flow Labs is already present. | Play 1 |
| State DOT Annual Safety Reports | US | HIGH | State-level safety performance data and crash statistics, used to cross-validate city metrics. | Play 1 |
| FHWA MPO Database (US) | US | HIGH | Metropolitan Planning Organization boundaries and contacts, used to identify regional partners. | Play 1 |
| NHTSA Crash Data Portal | US | HIGH | National crash data, used to estimate crash liability costs for cities. | Play 1 |