Since 2013 bolt has pursued its vision of “a world where cities are built for people, not cars” by making mobility safer, more affordable and more sustainable, with ride-hailing as its core strength and primary revenue engine. Bolt is now carrying that vision into its next era, partnering with Pony.ai and Stellantis to integrate autonomous driving into its network, with an ambition of roughly 100,000 autonomous vehicles (AV) by 2035.
On the other side of the ledger, Bolt is approaching a likely IPO, which puts a premium on protecting margin and growing revenue. Although Bolt Food and Bolt Drive together contribute roughly 18% of revenue, both hold smaller market positions and face steeper competition in their categories, so the next phase of growth should come from deepening penetration in existing ride-hailing geographies, since new market entry is capital intensive and slow to pay back.
Looking ahead, autonomous vehicles will ease the supply constraint that makes scheduled rides hard to fulfil today, while in the present Bolt needs capital-light revenue ahead of its IPO. Present need and future direction point the same way, making this the moment to check the viability of pre-scheduled rides, given the size of that pre-scheduled ride market worldwide.
A scheduled ride can be fulfilled in two ways:
Demand for the promise is set by two axes i.e stakes x perceived reliability:
The opportunity ****is that both channels run on infrastructure Bolt already owns. This creates two monetisable products with no new supply acquisition, no new market entry, and minimal incremental capex and a capital-efficient revenue stream aligned with Bolt's pre-IPO margin objectives.
| Step | What this means | Conservative | Base | Stretch |
|---|---|---|---|---|
| Driving GMV (2024) | Total fares riders paid before Bolt's cut. Bolt reports ~€1.6B(2024) revenue at a ~22% blended take, implying ~€7.3B in gross fares | ~€7.3B | ~€7.3B | ~€7.3B |
| Scheduled capture at maturity | Share of trips that become scheduled once the feature matures (Uber runs ~7%; Bolt assumed lower where Uber is entrenched) | 3% → €219M | 5% → €365M | 7% → €511M |
| Fare-skew adjustment | Scheduled trips skew toward airports and long rides, so their average fare is higher; scheduled GMV scales up accordingly | 1.3x → €285M | 1.6x → €584M | 1.9x → €971M |
| Scheduled take rate | Bolt's cut on scheduled fares, higher than on-demand because riders pay a certainty premium; driver pay unchanged | 30% | 32% | 35% |
| Net revenue to Bolt | Skew-adjusted scheduled GMV × scheduled take rate | ~€86M | ~€187M | ~€340M |
| Incremental revenue (net-new) | ~Half of scheduled rides would not have happened on Bolt otherwise (Uber benchmark); this half is genuinely new revenue | (~€86M/2) = ~€43M | ~€93M | ~€170M |
| Upsell margin uplift | The other half are rides Bolt already had, moved to scheduled; only the extra 10–15% take on them is new money | ~10% of (€86M / 2) = ~€4M | ~€14M | ~€26M |
| Total revenue impact at maturity | New revenue + upsell uplift, if scheduling ran in every Bolt city | ~€54M | ~€107M | ~€196M |
The opportunity is sizeable: even the conservative case (~€54M) is meaningful revenue for a feature that rides on existing infrastructure, which makes scheduling worth serious consideration. The TAM is a ceiling: it assumes every Bolt city can serve scheduling flawlessly, with no marketplace, regulatory, or execution friction. The constraints below determine how much of the ceiling survives.
| Area | Constraint | Decision implication | 2x2 axis (next section) |
|---|---|---|---|
| Marketplace | Scheduled rides pull drivers from the on demand pool at peak | Count only net lift: incremental minus on demand degradation | Liquidity axis |
| A locked price transfers surge risk to Bolt | The certainty fee must fund the surge gap Bolt absorbs | Reliability premium axis | |
| Booking ahead fights a spontaneous on demand habit | Adoption pattern is a pilot question: measure whether scheduling stays occasion-led or spreads into everyday trips | Reliability premium axis | |
| Scheduled demand clusters into the same peak windows as on demand rides | Higher complexity for forecast and stage | Liquidity axis | |
| Rider needs | Riders read "scheduled" as a hard guarantee regardless of terms | Backup mechanism in case of no show. Penalise driver in case of no show | - |
| Failure is asymmetric: a 5am no show damages the Bolt brand and compounds | Fulfilment rate should be a guardrail with a kill threshold | - | |
| Rider no shows strand committed drivers | Grace period plus late cancel fee paid to the driver | - | |
| Driver needs | Flexibility is the top reason drivers join | Acceptance stays optional, never forced assignment | Liquidity axis |
| Far ahead requests have little planning value to drivers | Surface scheduled jobs as near term earnings, not calendar slots | Liquidity axis | |
| A surge fare at pickup hour tempts committed drivers to ghost | Match surge at dispatch and penalise repeat cancellers | Liquidity axis | |
| Location | A liquidity floor decides if a guarantee is even possible | Binary gate before any city is scored | Liquidity axis |
| Willingness to pay premium depends on alternatives (public transport etc.) | Score alternatives for different locations and time | Reliability premium axis | |
| Regulation | Pre booked hire is a separate license class in several markets | Regulatory gate sits at step zero | Eligibility check |
| Execution | Going with only late dispatch without a funded guarantee is a proven failure (Uber v1) | Two models i.e driver assigned and late dispatch is the way to go | - |
| Cost to enter | Build spans dispatch, forecasting, ops tooling and support load | Net lift must clear build and run cost | Eligibility check |
| Capability | Uber has years of Reserve dispatch maturity; partners may be needed (flight data, corporate channels, fleet supply) | Enter Bolt led liquid cities first; partner where the gap binds | Liquidity axis |