01
Matching is a seconds-level problem
Supply and demand both move while you decide. A match made two seconds late is a cancelled trip and two unhappy users.
ThinkDebug
Practical deep dives on software architecture, AI systems, and scaling digital products - drawn from the work we ship.
Marketplaces and dispatch built for peak load.
We build marketplaces and dispatch systems: rider and driver apps, the matching and routing engine between them, and the pricing, payouts and operations tooling that keeps a two-sided market running.
On-demand is a real-time problem disguised as an app. The hard part is not the booking screen, it is matching supply to demand in seconds while both sides are moving, under load that changes by the minute and geography that changes by the block. A match made two seconds late is a cancelled trip.
It is also a two-sided market, which means every product decision has two audiences with opposed interests. Surge pricing that protects driver earnings is the same feature that annoys riders, and the software has to make that trade-off explicit rather than accidental.
The constraints that shape every build in this sector, and the ones teams usually meet too late.
Supply and demand both move while you decide. A match made two seconds late is a cancelled trip and two unhappy users.
Every pricing or allocation decision helps one side at the other's expense, and the product has to make that trade-off deliberately.
Rain, a match finishing or a holiday multiplies demand in one part of one city. Global capacity planning does not help.
Battery, data and background location behaviour matter more than visual polish, and they decide whether drivers stay logged in.
Late or unclear earnings are the most common reason supply leaves. Payouts have to be fast, explainable and reconcilable.
Continuous tracking is expensive to store, expensive to query, and carries real privacy obligations.
Swipe to read all 6
Each one is a system we have built before, not a capability we are willing to try.
Native-quality apps built for all-day use, weak connectivity and background location without draining a battery.
Real-time matching with routing, ETA and allocation rules you can tune per city.
Fare calculation, surge rules, split payments and driver payouts that reconcile.
Location ingestion, geofencing and trip history at a volume and cost that stays sustainable.
The internal tooling city teams need to intervene, refund and investigate quickly.
Utilisation, acceptance and earnings reporting that drives incentives rather than just describing them.
Engagements across sectors - the same team, the same standards.
Partnering with Thinkdebug to develop the Forever 52 mobile app has been a game-changer for us. They were always open to feedback, and it was clear they were as invested in our success as we were. What really sets them apart, though, is the amazing support we've received since the app launched. They’ve made sure the app continues to run smoothly and are always ready to fix any issues that come up.DMDhruv MehtaBusiness Head, Forever 52
Chosen for fit and long-term maintainability, never for novelty.
Send us the scope and we come back with an itemised estimate - no discovery fee, no obligation.
What we design and document against, from the first commit rather than the week before an audit.
Certification itself belongs to your entity and its assessor. What we provide is software built and documented so the assessment is about evidence rather than remediation.
Most of our work comes from clients we already shipped for. These are the reasons they give.
The dispatch engine gets the attention, because match time is what riders and drivers actually experience regardless of how the app looks.
Battery, data and background location are budgeted explicitly, because an app that drains a phone by lunchtime loses supply.
Load is local and spiky, so we model and rehearse the worst hour in the worst zone rather than an average across the fleet.
Earnings breakdowns are derived from a ledger, so a driver dispute has an answer and finance can reconcile it.
Retention, aggregation and indexing are designed up front, because raw tracking data becomes the largest bill and the largest privacy surface.
City teams get consoles to intervene and refund early, rather than filing tickets to engineering for every exception.
Let's start with you.
Your information stays private. We reply within 24 hours.
Still have a question we have not answered?
Ask an engineerWhat we build for mobility & on-demand, the work we have shipped, and what we have written about it.
