Search “demand forecasting software” and most of what ranks is built for retail and supply chain, forecasting SKU-level demand by week, feeding a procurement system. None of that transfers cleanly to fleet and mobility operations, where the unit isn’t a product on a shelf, it’s a vehicle that needs to be in a specific zone at a specific hour, and the cost of guessing wrong shows up the same day, not next quarter.
Here’s what mobility demand forecasting actually requires that generic demand forecasting software doesn’t provide, how a forecast should connect to an operational decision instead of dead-ending as a chart, and how Myles, SWITCH’s AI agent for mobility and logistics (getswitch.io) approaches it.
Why mobility demand forecasting is a different problem
Generic demand forecasting software optimizes for a single axis, usually time. A retail forecast asks how many units next week. A fleet forecast has to answer two axes at once, where and when, because a correct total-demand number citywide is operationally useless if it doesn’t say which zones need vehicles at which hours. A forecasting tool built for retail and relabeled for mobility will get the aggregate right and the distribution wrong, which is the number that actually drives a rebalancing or staffing decision.
Mobility demand also moves on a faster and noisier signal set than retail. Weather, a nearby event, a transit disruption can shift demand within the hour, not the week, and a forecasting model trained on slower-moving retail patterns isn’t built to catch that.
Why a single number is the wrong output
A forecast that returns one number, “42 trips expected in this zone tomorrow,” presents a prediction as a fact. A better forecast returns a range with a confidence level attached, because the operational decision that follows, how many vehicles to reposition, how many staff to schedule, should weigh the cost of being wrong against the size of the range, rather than just reacting to the midpoint. This matters most exactly where it’s easiest to skip: a forecasting tool with no confidence signal looks identical to a good one in a sales demo and behaves very differently the first time real demand deviates from the model.
A forecast is only useful if it turns into a decision
The gap between a forecasting tool and an operationally useful one isn’t accuracy. It’s what happens after the number appears. A mobility demand forecast should feed rebalancing directly, generating the vehicle-relocation plan rather than just flagging that a zone will be short. For EV or driver-operated fleets, it should inform staffing and charging schedules, when crews or charging sessions need to happen, not just how many trips are expected. And for pre-launch or expansion planning, it should feed a fleet-sizing simulation of how a specific fleet size performs against it, before the vehicles are purchased. None of these should require a separate manual step to reach from the forecast.
How Myles approaches demand forecasting
Myles forecasts by zone and by hour, with a confidence range rather than a single point estimate, and connects that forecast directly to the operations layer. A rebalancing plan or a ground-team assignment follows from the same forecast, rather than a separate tool reinterpreting it. The Pro tier runs on a pre-trained forecasting model suited to standard fleet patterns. The Enterprise tier trains a custom model on the operator’s own history for higher-precision forecasting and connects into full simulation and orchestration. Both are grounded in the same operational data layer, roughly 350 million trips modeled monthly across 4,002 live feeds and close to 987 cities, rather than a generic retail-forecasting model relabeled for mobility.
Key takeaways
- Mobility demand forecasting needs both axes, where and when, not just a citywide total. Generic retail forecasting software optimizes for time alone.
- A forecast without a confidence range presents a prediction as a fact. Ask any vendor how their forecast communicates uncertainty, not just accuracy.
- A forecast only earns its cost if it connects to a decision, rebalancing, staffing, charging, or fleet sizing, without a manual translation step.
- Myles forecasts by zone and hour with confidence ranges, on a pre-trained model on Pro or a custom-trained one on Enterprise, both feeding directly into operations.
Want a demand forecast that turns into a rebalancing plan, not just a chart? Try Myles free for 14 days.
