This post walks through the inputs, the pricing rules behind them, the open data the tool depends on, and what a rider should still confirm by phone.

The inputs

The Tri-City Rideshare fare calculator asks for very little:

• From and To: a pickup and a destination
• Car type
• An Include 20% gratuity toggle
• An option to enter miles and minutes manually

The manual option is easy to miss, and it's useful. If you already know your route, or the automatic geocoder picks the wrong match for an address, you can type the distance and travel time yourself. The page says the estimate updates as you type, so you can try a few scenarios quickly.

The pricing model behind it

The calculator is built on a simple set of published rules. For a sedan:

The results panel lists every one of those components on its own line: distance, travel time, base fare, extra miles charge, extra time charge, subtotal, gratuity and estimated total. I like that. A single number with no breakdown makes people suspicious. A line-by-line breakdown lets them see where the money goes and which part of the trip is driving the cost.

Here is the logic in pseudocode:

base = 85
extra_miles = max(0, miles - 25) * 2
extra_time = ceil(max(0, minutes - 60) / 30) * 20
subtotal = base + extra_miles + extra_time
total = subtotal * 1.20 if gratuity else subtotal

(How a partial half hour is rounded is my assumption. The page states the rate as "$20 per 30 minutes," so call to confirm the exact rounding.)

The data underneath

Small businesses usually don't have a budget for commercial mapping APIs, and this tool doesn't use one. The page credits its sources openly:

• Map data: OpenStreetMap contributors
• Address search: Photon / Nominatim
• Routing: OSRM

That combination works fine for a fare estimate. It turns typed addresses into coordinates, gets a driving distance and duration, and feeds both into the pricing rules above.

What the estimate leaves out

The page includes a clear disclaimer: distance and time are automatic driving estimates and don't include live traffic, tolls or waiting time. It also labels the result as an "estimated fare – not a final quote" and asks riders to call (510) 677-3909 for a final price.

Anyone who has driven in the Bay Area will see why that matters. A route the router calls 45 minutes can take much longer at rush hour, and the time component of the fare would change with it. The tool gives you a baseline, not a guarantee.

Where the fixed packages fit

The calculator covers point-to-point Bay Area and airport rides. The company's reservation page also lists fixed packages that you wouldn't run through a per-mile formula:

• All Bay Area Airports (SFO, SJC, OAK): $85 + 20% gratuity within a 25-mile radius, home to airport or airport to home, up to 4 passengers with 3 medium-size bags. The page says this fare also works for any location within the Bay Area.
• 5 to 6 passengers: $110 within a 25-mile radius.
• 7-hour charters (sedan $375 for 4, SUV $475 for 7, van $575 for 7 to 11) and a 6-hour extended van at $675 for 11 to 14 people. After the 7th hour, sedan and SUV charters add $20 per half hour.

So the calculator handles the variable trips, and the reservation page handles the predictable ones. For anything that fits neither, there's a create-your-own-trip form where you describe the trip and request pricing.

Takeaways for builders

Whether or not you ever ride with this company, the calculator has a few lessons for anyone building a pricing tool for a small business:

1. Mirror the published policy exactly. The calculator uses the same $85 / 25 miles / 60 minutes rule printed elsewhere on the site, so customers don't see two different answers.
2. Show the breakdown. Separate lines for base, extra miles and extra time build more trust than a single total.
3. Offer a manual override. Geocoders make mistakes. Letting users enter miles and minutes keeps the tool useful when they do.
4. Say what you don't model. Traffic, tolls and waiting time are the usual causes of surprise charges, and the page names all three.
5. Point people to a human. The final step is a phone number.

If you're in Fremont, Union City or Newark and want to check a trip, run it through the calculator first and then call for the final quote.

Muhammad Waseem writes about local transportation and travel planning in the San Francisco Bay Area. More about Tri-City Rideshare LLC, at 33476 Alvarado-Niles Rd Suite # 07, Union City, CA 94587, (510) 677-3909, is at tricityrideshare.com.