What a vertical actually changes
Four axes. Everything else — branding, payments, the API, analytics — is identical whichever vertical you run.
Time promise
Handover
Pricing
Regulation
Browse the verticals
Three delivery and two mobility verticals. Filter by family, then open one for its configuration.
Food & restaurant
The deepest vertical. Dispatch has to know the kitchen before it knows the rider.
Grocery & supermarket
Large baskets, scheduled windows, and a picker step between order and dispatch.
Courier & parcel
Assignment speed and batching are the whole economics. A minute saved per job changes the business.
Taxi & ride-hailing
Matching latency and supply density decide whether the market works at all.
Bike & scooter taxi
Same engine as taxi, tuned for short trips where every second of matching costs a ride.
Running more than one vertical
One fleet, one customer base, one settlement run. The combinations that work, and the one rule that keeps them profitable.
Same fleet, opposite peaks
Parcels between meal peaks
One captain app, two job types
Vertical Questions
Regulated categories, verticals not on the list, and what a second vertical costs.
Vertical not listed? Describe what you deliver
Our vertical is not on the list. Now what? +
Describe the delivery promise, what the driver must verify, and how you price. Almost every unlisted vertical lands as a combination of two that exist plus a connector — pet supplies is grocery with lighter regulation, equipment hire is courier with a collection leg. Where it genuinely differs, the difference is configured rather than built.
How much does a second vertical cost? +
Typically two to three weeks of configuration rather than a new deployment. The apps, the fleet, the settlement run, and the admin console are shared. What is new is the vertical's own rules — slots, substitutions, batching — and the catalogue or vendor onboarding behind it.
Do we need separate apps per vertical? +
It is a brand decision, not a technical one. One app with a vertical switcher keeps the customer base together and is what most operators start with. Separate branded apps make sense when the audiences genuinely differ — a bike taxi rider has little overlap with a weekly grocery customer.
Which vertical should we start with? +
The one where you already have supply. Software is not the constraint in month one — restaurants, vendors, or drivers are. Start with the vertical whose supply you can onboard fastest, then add the second against the fleet and customers it produced.
Tell Us What You Deliver
The vertical, the delivery promise you make, and anything a driver has to verify on the doorstep. We'll map it to a configuration and a timeline before you spend anything.