About
Built for the 22:00 shift change, not the Friday night out.
Rydlnk started from a specific observation in Provo: the same forty people leave the same industrial park at the same time every night, and each of them pays for that trip as though they were the only one making it.
Why this shape
E-hailing solved the unpredictable trip. Nobody solved the predictable one. A commute that repeats four or five times a week at a known time, along a known road, with known people, does not need real-time matching, surge pricing or a daily booking step — and paying for all three is why staff transport costs what it does.
So the unit here is a seat on a scheduled run, priced in advance. A seat belongs to whoever pays for it, which is what makes it possible for one vehicle to carry staff from three employers plus two people paying their own way, and for each of them to get a correct receipt.
What we chose not to build
No surge. No dynamic pricing of any kind — one employer's no-show must never change what another pays. No consumer marketplace. No attempt to serve trips that don't repeat: if your week is different every week, an e-hailing app genuinely suits you better and we'd rather say so.
How we make money
A platform fee per active employee per month, and the margin between the sum of seat prices and the real cost of running the vehicle. That margin lives entirely in fill rate — which is why pooling exists and why we carry the yield risk rather than passing it to you.
Where we operate
Provo. Five corridors out of East Bay and Springville, timed to shift changes. We'd rather run a few corridors densely than many corridors badly.
Who we're for
Employers with shift patterns and staff who live in clusters — manufacturing, warehousing, support centers. And the people on those shifts, whether or not their employer ever signs up.
The hard part
Tenant isolation. A pooled trip has one identifier and several owners. Getting that wrong once — showing one employer another's staff list — would end the product. It's enforced at the query layer, not in the interface.
Come and argue with the numbers.
Bring a week of shifts. We'll cluster them against real corridors and show you what next Monday would cost.