Fixed Fares vs Fare Bidding: Uber vs inDrive Models Explained

Two answers to "how much is this ride?" — and a harder question first

Founders often come to us convinced that the pricing model is their big idea. "We will be the inDrive of our city." "We will beat Uber with lower fares." Let me be honest: in the AI era, either model can be built quickly. A fare screen is not a business.

What decides whether your ride-hailing company survives is whether you can sell — pull drivers away from what they do today, persuade riders to try you and come back — and whether you can operate long enough for the numbers to work. The pricing model matters, but only as part of that. Choose it to fit your market, not to sound different in a pitch.

And do not rush to spend money on the app. If the business cannot survive its first months, the money you pay any developer, including us, creates nothing. With that said, here are the two models:

• Uber shows the rider a single price before they book. An algorithm sets it. The driver decides whether to accept.
• inDrive asks the rider to propose a price. Nearby drivers accept, decline or counter-offer, and the rider picks the offer they like.

Reality check before you spend a dollar

Answer these for your launch city before deciding anything.

How fixed (upfront) fares work

In the fixed-fare model the platform sets the price. Uber describes its upfront fares as calculated from the expected time and distance of the trip, local traffic, and how many riders and nearby drivers are using the app at that moment. In its India explainer, Uber says the fare shown is inclusive of the booking fee and tolls.

A fixed-fare engine usually combines a base fare per vehicle category, per-kilometre and per-minute rates on the predicted route, a dynamic multiplier (surge) when demand outstrips supply, fees and pass-throughs such as tolls, and adjustment rules that recalculate when the trip changes. The rider gets certainty; the driver gets a take-it-or-leave-it offer; the platform controls the balance of supply and demand.

How fare bidding works

inDrive's flow, as widely described in coverage of the company:

1. The rider enters pickup and drop-off and sees a recommended fare.
2. The rider proposes a price — the recommended one or a different amount.
3. Nearby drivers accept, decline or counter-offer, without the acceptance-rate penalties drivers often complain about elsewhere.
4. The rider sees the offers, with each driver's rating, vehicle and arrival time, and chooses one.

inDrive began in 2013 in Yakutsk, Russia, growing out of a social-media group where students and drivers negotiated fares. It is now headquartered in Mountain View, California and, according to its Wikipedia entry, operates in roughly 1,200 cities across 48 countries.

Bidding is rarely a free-for-all. The recommended fare is an anchor, and platforms limit how far an offer may stray from it. Without that guardrail, very low offers go unanswered and riders get frustrated.

Side-by-side comparison

Which markets suit which model?

Price sensitivity. Where a ride is a big share of daily income, riders want control. In wealthier cities where time matters more than a small saving, riders prefer one tap and a known price.

Cash and haggling culture. Across much of South Asia, Africa, Latin America and Central Asia, informal transport has always been negotiated. A bidding app digitises a habit people already have. Where cards dominate and the meter is the reference, negotiation feels like friction.

Driver supply. Bidding needs enough drivers to produce several offers quickly. With one driver nearby, the "auction" becomes a single take-it-or-leave-it counter. Fixed fares with surge are better at pulling supply into a short area. Either way, recruit drivers before you advertise to riders.

Trip type. Short, urgent trips (commutes, airport runs) reward speed and predictability. Longer, less frequent trips (intercity, moving goods) reward negotiation.

Driver economics and commission

inDrive markets itself on a low commission. Its Wikipedia entry cites Business Insider reporting that the company charges about 10% per ride. The Rideshare Guy describes inDrive's commission as capped at 10%, and TechCabal reported in November 2024 that drivers in Botswana pushed for higher fares after inDrive introduced a 10% commission there, following an introductory period. Rates vary by market and change over time, so treat 10% as a positioning figure, not a guarantee.

Uber uses a variable service fee. In an October 2025 announcement for Helsinki, Uber said its service fee would range from 3% to 35% per trip, with lower fees on less attractive trips, while keeping an overall average of 25% across the city.

What this means for you:

• A low commission is a supply tool — one of the clearest messages you can send drivers leaving an incumbent.
• A low commission limits your budget for promos, support and insurance. Model it before you announce a rate you cannot sustain.
• Driver autonomy has value of its own. Choosing trips and prices is a retention advantage you can design for.
• Bidding cuts both ways. The TechCabal report noted complaints that when a rider's opening offer is already low, there is little room to negotiate up. Minimum-offer guardrails protect drivers.

Rider trust

With fixed fares the risk is surge shock; with bidding it is uncertainty and effort. In either model: show the reasoning (label surge clearly; explain the recommended fare), honour the price and explain any change, make the driver visible (rating, vehicle, plate, photo), and treat safety — SOS, trip sharing, verification — the same way regardless of pricing.

The regulatory angle

Regulation is the factor founders most often underestimate. Many cities license ride-hailing under rules written for taxis, with published fares.

The clearest example is the Philippines. In January 2024 the Land Transportation Franchising and Regulatory Board (LTFRB) suspended inDrive's operations, citing the "haggling of fares" as a violation of the fare matrix for Transport Network Vehicle Services, which specifies flag-down, per-distance, per-minute and surge components. ABS-CBN reported that inDrive resumed operations in June 2024, about five months later, after complying with the regulator's fare system.

Before launching bidding, check whether your city prices ride-hailing under a fare matrix, whether "recommended fare plus negotiation" counts as compliant, whether motorbike taxis are legal at all, and whether consumer rules require the price before the trip starts. Five months without revenue is exactly the kind of event your runway must survive.

Hybrid approaches

• Fixed fare with "offer more" — riders add an amount at busy times to attract a driver faster.
• Bidding within a band — offers only within a range around the recommended fare, closer to regulated structures.
• Model by category — fixed for city rides and airports; bidding for intercity, cargo or moving.
• Model by market — different pricing modes per city, switched in the admin panel.
• Driver-set minimums — riders see only drivers whose floor fits their offer.

Technical differences that matter

Both models need real-time location, maps, dispatch, payments, ratings and an admin panel. Fixed fares need a pricing engine that estimates and recalculates fares, a demand/supply signal per zone for surge, and sequential or batched dispatch. Bidding needs a broadcast-and-collect loop over persistent connections such as WebSockets, timeouts and expiry for requests and offers, guardrails on offers, race-condition handling so two drivers cannot both win a trip, and abuse controls against repeated low offers or counter-then-cancel.

Bidding is not dramatically harder to build, but it is less forgiving of weak real-time infrastructure. That is why our custom ride-hailing builds use Go for the dispatch and offer backend, with WebSockets, PostgreSQL and Firebase Cloud Messaging, Flutter (GetX) for the rider and driver apps, and React or Next.js for the admin panel.

Insider tips for either model

• Every fare estimate costs money. Both models calculate a route before the rider books — and riders check prices they never book. As of October 2026, Google charges $5 per 1,000 Compute Routes Essentials requests and $2.83 per 1,000 Autocomplete requests after 10,000 free per SKU each month, per Google's pricing list. Self-hosted OSRM routing on OpenStreetMap data, MapLibre for display and a cheaper geocoder (Mapbox's Temporary Geocoding API is free up to 100,000 requests a month, per Mapbox pricing) can cut that sharply. Keep Google where it is clearly better.
• Use WhatsApp OTP where it is cheaper than SMS. Meta prices WhatsApp Business Platform messages per delivered message by category and country since 1 July 2025, per Meta's pricing page. Compare your country's authentication rate with your SMS gateway and keep SMS as a fallback.
• Test offers on a bad network. Run the bidding flow on a budget Android phone with weak mobile data before launch. If offers arrive late there, the model feels broken in real life.
• Insist on CI/CD, backups and monitoring. A real-time system that goes down at rush hour loses drivers' trust in a single evening.

Checklist: choosing your pricing model

• Written answers to every reality-check question above
• Confirmed how ride-hailing is licensed and priced in your launch city
• Known share of trips paid in cash versus card or wallet
• Negotiation is (or is not) a normal part of local transport today
• Enough drivers per zone to generate several offers within seconds
• Unit economics modelled at the commission you plan to announce
• Driver protection against very low offers decided
• Admin panel can switch pricing mode per zone or vehicle category
• Real-time offer flow tested on a weak mobile network
• Surge or offer-raising clearly explained to riders before booking

When Joldisoft is — and isn't — the right partner

We build ride-hailing apps for founders in emerging and global markets and see both models every week. Our advice: start with the model your riders already understand, keep the other as a configuration rather than a rewrite, and talk to your regulator before announcing a commission. Our Uber-style and inDrive-style products share one core, so you can begin with one mode and test the other in a single zone. White-label with configuration starts from $3,000; MVP and custom builds and ongoing maintenance are available when your model needs them.

We do not take every project. We are the right partner if you bring validated demand, drivers you have already lined up, a sales and marketing plan, an operations budget with runway, and a named person running the business. We are not if the pricing model is the whole plan, or if the build would use up the money you need to operate.

We want long-term partners whose businesses grow, not one-off projects. If that is you, bring your answers to the reality check and we will walk through the right model for your city.