Via's Public Sector Dependence

Via’s government heavy mix makes the business look more like critical infrastructure software than typical startup SaaS. That helps retention because transit agencies and school districts renew systems that run daily routes, dispatch drivers, and rider apps, but it also means growth and contract timing are tied to public budgets, grant awards, and shifting transit policy. In 2025, government entities generated $406.4M of Via’s $434.3M revenue, and about $294.4M of contracted backlog remained at year end.

• The stability comes from how the product sits inside operations. Once an agency uses Via to assign vehicles, build driver shifts, and manage live trips, replacing it is disruptive. That is why public contracts can behave like sticky recurring revenue even when procurement is slow.
  2 sacra
• The risk comes from who controls the money. Federal transit funding still flows through annual appropriations and formula grants to states, urbanized areas, and agencies. Those funds supported about $20.5B for U.S. transit in FY 2025, and agency level allocations depend on government budget decisions rather than direct customer demand.
  3 dot 4 apta
• This pattern is common in B2G software. OpenGov sells budgeting and permitting software to local governments and faces the same long RFP cycles and budget freeze risk. The difference is that Via is tied more directly to transportation operating budgets, where service changes or delayed grants can affect software and managed service spend faster.
  5 sacra

Going forward, Via’s path is to keep turning public contracts into broader platform spend. More analytics, student transportation, paratransit, and white labeled rider apps can raise revenue per agency, while expansion beyond pure transit operations can make the company less exposed to any single budget line or policy swing.