Spare vs. Via:
The Transit Platform Built for Agency Control

When service needs shift, agencies need to adjust zones, service hours, vehicle capacity, and reporting on their own timeline. With Via, most of these changes route through vendor support tickets rather than agency staff. Agencies have reported zone changes taking four to eight weeks (sometimes with additional fees), routine settings like vehicle capacity requiring vendor involvement, and in-app driver messaging unavailable in some deployments — leaving staff to share PDFs through internal channels just to reach drivers.

This vendor-dependent model becomes a real constraint during pilots, when agencies need to iterate quickly on what they're learning from riders.

• Which configuration changes can agency staff make independently in-platform, and which require Via's involvement?
• What is the typical turnaround time and cost for a zone modification, a service-hour change, or a vehicle capacity update?
• Is in-app driver communication available across all service types and deployments?
• How does the configuration model scale as service rules and zones expand?

Via has built its reputation in microtransit. Paratransit is a newer, less proven area of the product, and agencies evaluating it have surfaced gaps that matter for ADA service delivery. Eligibility rules don't distinguish device types beyond a single wheelchair-accessible category. Roll calls aren't natively supported. Vehicle-on-the-road metrics have shown calculation errors. Rider accommodation information is stored in free-text notes rather than structured fields surfaced to drivers, creating compliance and service-quality risk on regulated trips.

Agencies have also reported difficulty pulling ADA-specific reporting metrics, and Via's paratransit capability is widely understood to have returned to product focus only after a period of losing paratransit contracts.

• Which ADA paratransit deployments are running on Via today at scale, and what are their on-time performance and compliance reporting outcomes?
• How are roll calls handled?
• How are rider accommodations stored and surfaced to drivers?
• Which ADA-specific metrics are available in standard reports, including excessive ride time?
• What is Via's data migration methodology for legacy paratransit eligibility records?

Via markets a unified platform across service types, but agencies running both microtransit and paratransit have reported that the same rider often ends up with two separate accounts. When customer service staff can't quickly locate an existing record, they create a new one, and duplicate accounts pile up over time. End-to-end itinerary visibility across multimodal connections is also reported as inconsistent across deployments, leaving agency staff and riders without a single view of someone's full trip history or eligibility.

• When a rider uses both microtransit and paratransit, is there a single rider record or two separate accounts?
• How does Via prevent duplicate account creation in call center workflows?
• Can rider eligibility, trip history, and accommodations be viewed across all service types in one record?
• Can riders see and book multimodal itineraries end-to-end in the rider app?

In March 2026, an independent short-seller research firm published a public report based on a review of more than 100 Via contracts. The report alleges that Via routinely books large implementation fees and up to 18 months of software charges upfront, with upfront fees ranging from 31% to 153% of first-year contract values, and that Via's revenue is driven primarily by driver hours, vehicle hours, and operational labor rather than software licensing.

The report also alleges that Via's main upsell path is for agencies to buy more vehicles and drivers rather than more software, that some top customers have been reassessing or downsizing their Via relationships, and that two transit agencies have recently replaced Via software. Separately, agencies have reported scope creep, added fees, and post-award renegotiation as recurring patterns once contracts are in place.

• What is the total cost of ownership over the contract term, including all implementation fees, software charges, and configuration costs?
• How do upfront implementation fees compare to first-year contract value?
• Are zone changes and scope additions billed as separate implementation fees?
• When Via has renegotiated contracts post-award, what triggered the renegotiation?
• Which agencies can speak to year-over-year pricing stability and contract retention?

Via often serves as both the software platform provider and the contracted service operator on the same engagement. Via's own proposal language describes a "single vendor" model that bundles the technology platform with vehicle sourcing, driver staffing, and operations management.

This creates a dynamic that doesn't exist with a software-only partner: the same vendor's revenue is tied to both the platform contract and the operational hours billed, which can shape how trip volume, fleet size, and use of third-party providers are managed over time.

• When Via is both the software platform and the service operator, who owns the efficiency target, and how is it measured independently?
• Can Via demonstrate cost-per-trip reductions year over year at comparable agencies?
• How does Via handle brokering trips to non-dedicated providers when doing so reduces direct Via revenue?
• What happens to the contract structure if an agency wants to bring in a different operator while keeping the platform?
• What share of Via's deployments depend on temporary federal grants or COVID-era funding?

Agencies across North America have reported a consistent pattern: strong pre-sales engagement, well-resourced implementation, and a sharp drop-off after go-live. Launch managers often disappear once implementation ends, with handoffs to ongoing account managers described as ineffective. Product features change without corresponding documentation updates, leaving staff unable to explain new behavior to riders or drivers, and ticket responses have been described as templated rather than diagnostic.

• Who is the named account manager after go-live, and what is their typical tenure?
• How is the handoff from implementation to ongoing support structured?
• How are product changes communicated to operations staff before they affect rider-facing or driver-facing behavior?
• What is the average ticket resolution time, and are response metrics published or shared with agencies?
• When Via has missed a contracted technology delivery milestone, what remediation process applies?

Via markets AI-powered continuous optimization, with manifest changes pushed instantly to drivers. Field reports from active deployments describe a different reality: optimization running primarily as an overnight batch process, with dispatchers spending the operating day manually regrouping trips, resolving unmatched requests, and patching the prior night's output.

Agencies have also reported a roughly 15-minute cooldown on mid-shift vehicle and driver swaps, group trips split across vehicles that need manual consolidation, forced rematch behavior contributing to avoidable no-shows, arrival geofencing blocking driver status updates in poor connectivity, and drivers viewing full daily manifests and completing trips out of sequence with no dispatcher-side control over the optimized order.

• Does optimization run continuously throughout the operating day, or as an overnight batch process with same-day manual intervention?
• Can a dispatcher swap a vehicle or driver mid-shift without creating a new shift?
• Can dispatchers preview optimization changes before they are applied?
• Can dispatchers enforce the optimized trip order on the driver app, or can drivers complete trips out of sequence?
• How does the driver app handle status updates when connectivity is poor?
• What reference customers can demonstrate the marketed continuous-optimization workflow in live operations?

Scale and reliability concerns surface consistently as agencies grow on Via or experience disruptions. One operator partner has reported Via struggling to keep up as trip counts recovered post-COVID, pointing to performance degradation at higher volumes. Agencies have also reported full revenue loss during outages with no way to reconcile data after the fact, and at least one debrief identified a major Via outage with no backup options as a reason for moving off the platform.

Procurement evaluations have flagged the absence of a documented failover or backup option as a risk factor during disruptions.

• What is Via's documented uptime SLA, and how is it measured?
• When an outage occurs, how is trip data reconciled, and how is revenue recovered?
• What is the failover architecture, and has it been tested at production scale?
• At what monthly trip volume has Via observed performance degradation, and how has it been addressed?
• Which agencies are running Via at the highest monthly trip volumes today, and what are their reference experiences?