The Density Problem
A carpooling marketplace does not fail when nobody wants it. It fails when not enough people want it at the same time, on the same road, in the same direction.
Liquidity is not how many drivers exist. It is how many are going this way, this evening, from here.
Photograph from the tripda.com picture kitThe threshold nobody advertises
Density is the arithmetic that precedes every other question in intercity carpooling. Before trust systems, before price, before the app's user interface, there has to be a driver leaving city A for city B on a given afternoon, and a passenger who wants the same corridor at roughly the same hour. Miss that coincidence and the marketplace returns nothing — not a bad option, but a blank page.
This is a two-sided market in a very specific, unforgiving sense. Both sides must be present simultaneously, on the same spatial corridor, within a time window narrow enough to be useful. A hundred drivers offering seats on a Monday morning do nothing for the passenger who needs Friday evening. Platform designers call this the liquidity problem: the stock of available options must be deep enough, at any moment a user checks, that the product feels real rather than aspirational. Below that threshold, users try once, find nothing, and do not return — draining the very supply that might have served the next person.
The geometry makes it worse. Long-distance carpooling is not a single market; it is thousands of micro-markets, each defined by a pair of cities, a direction, and a time band. Paris to Lyon on a Friday afternoon is a separate liquidity pool from Lyon to Paris on Sunday evening, which is separate again from Lyon to Marseille on any given day. Average occupancy on a long-distance car journey sits close to one and a half people — which means most drivers are already out there, seats empty, but they are invisible to the platform unless they choose to list them. Aggregating that latent supply is the whole challenge.
Two in the front, three places behind them. The occupancy average, seen from the seat that is being counted.
Photograph from the tripda.com picture kitWhy corridors do and do not tip
A marketplace "tips" when supply and demand reinforce each other: more drivers attract more passengers, whose presence attracts more drivers. On a single dense corridor — Frankfurt to Berlin, São Paulo to Rio de Janeiro — that loop can close. The route is short enough that the time window is manageable, frequent enough that users check back, and travelled by enough people that the platform can hold real inventory on a Friday. BlaBlaCar built its core business on exactly these trunk routes in France before expanding elsewhere; the corridor density on Paris–Lyon, Paris–Bordeaux, and Paris–Toulouse gave it the liquidity to look like a working product before it reached thinner markets.
The failure mode is the long tail of routes. A medium-sized city paired with a smaller one two hundred kilometres away might generate a handful of trips per week. On a competitive platform, "a handful" means a passenger might search and find one seat, at the wrong time, or none at all. That experience is not neutral — it is actively destructive to the platform's credibility, because users calibrate their expectations from their first search.
Geography compounds the problem. Germany's long-distance coach market, liberalised in 2013, instantly provided an alternative at a fixed, advertised price on every major corridor. The coach is not a carpooling competitor in the trust-system sense; it is a liquidity competitor. It is always there. A shared car is there only when a driver happens to be going your way and bothered to list the seat. On corridors with a reliable coach or fast rail alternative, the density threshold the carpool platform must clear to win a user rises sharply, because the comparison is now a certain option versus a probabilistic one.
What critical mass actually requires
The number that matters is not registered users but active listings on a given corridor in a given week. A platform with two million registered accounts and thin corridor coverage is operationally thinner than one with two hundred thousand accounts concentrated on twenty routes. Rocket Internet's multi-market launch of Tripda in 2014 tested this at scale: deploying simultaneously across more than a dozen countries meant spreading user acquisition across dozens of corridor pools, most of which never accumulated enough volume to tip. The launch machine is built to find which corridors reach critical mass quickly; the ones that do not are a signal, not a problem to be solved by patience.
Density, in the end, is not a feature. It is a precondition. Everything else — the reputation system, the pricing model, the driver profile — only matters once there is someone on the other side of the corridor to see it.
Most of the cars on this stretch are carrying one person, and every one of them is the supply side of the market.
Photograph from the tripda.com picture kitA marketplace needs enough drivers on one corridor on one afternoon; below that threshold the product is simply empty.