A founder decision from 2024: Fare 1 doesn't surge.
That's an unusual choice for a chauffeur platform in 2026. Every major ride-hail and most private-hire operators run some flavour of demand-based pricing — late-night premiums, peak-time multipliers, Friday-Saturday uplifts. We don't, and this article explains why.
What "surge" usually means
Surge pricing is a real-time multiplier applied to the base fare when demand exceeds supply. The classic Uber model: 1.5× during the rush, 2.4× on New Year's Eve, occasionally higher.
The argument for it is economic — surge balances the market, attracts drivers to busy areas, signals scarcity to riders who can afford to wait. The argument against it is reputational — customers don't experience surge as efficient market-clearing, they experience it as the company taking advantage of them when they have no choice.
We landed on the second view.
What we do instead
Three things, in priority order.
Supply commitments. Drivers commit to shifts in advance. We have a clearer picture of who's available on Friday night than a system that hopes drivers turn on the app. When supply is tight, that's a planning problem — we accept fewer bookings rather than charge more for the ones we accept.
Booking caps. During known high-demand windows (cruise turnaround Saturdays, Royal Ascot week, festival weekends), we sometimes cap how many bookings we'll accept for a slot. The cap is silent — customers either see availability or don't. We don't charge a premium for the slots we do offer.
Honest unavailability. When we can't dispatch, the booking form says so. No fallback to a 3× fare for the same trip. You get to choose: book a different time, a different vehicle, or a different operator.
The trade-offs
We're honest about what this costs us.
Revenue per ride is lower on peak windows. A surge model would extract more from customers willing to pay during scarcity. We don't extract that, so per-ride revenue is flatter across the week.
Some demand goes unserved. When we can't dispatch in a tight window, we lose the booking — a surge operator would have served it at a higher price. The customer who couldn't book Fare 1 either booked elsewhere or stayed home.
Capacity planning matters more. We have to forecast demand windows accurately because we can't price-discriminate our way out of mismatches. We invest more in shift planning, vehicle availability tracking, and pre-allocation.
The trade-off we don't make
We don't trade off price stability between booking and trip. Once you've quoted, the price holds — even if a route turns out to be busier than expected, even if traffic delays the driver. The price you saw at quote is the price you pay.
That's the entire point of the model. Trade-offs we accept on revenue, we don't accept on the customer's experience of the price.
What this means in practice
If you book a Heathrow run for 8am on a Tuesday, you pay the same as a Heathrow run for 8am on a Sunday. If you book a Southampton-to-Bath wedding chauffeur on a peak Saturday, you pay the same hourly rate as a midweek shopping trip. If you call dispatch on New Year's Eve at 11pm, you either get a quote at our published rates or you get "no driver available — try a different time."
There's no version of the booking form where the price multiplies based on what time you've selected.
Where to read more
The rate-sheet that holds across every booking lives at /pricing. The 16 fixed-fare routes are at /fixed-fare. For the philosophy that drove this decision more broadly, how fixed fares work walks through the upstream design choice.
Questions on a specific trip? Reach us at hello@fare1.co.uk.