Priced by rider count. Everything the engine does is in every plan.
We do not gate route optimisation, window prediction or customer notifications behind a higher tier - those are the point. The plans scale with the shape of your fleet.
- Real-time route optimisation
- Delivery-window prediction
- Customer tracking pages and SMS notifications
- Dispatcher board with live fleet view
- Standard onboarding, two-week calibration
- Everything in Starter
- Dynamic rider reallocation with reason logs
- Fleet analytics with cohort comparisons and exports
- Multi-client separation with per-client SLA and branding
- Priority support with same-shift response
- Everything in Growth
- Custom escalation flows into your ops tools
- Dedicated onboarding and quarterly ops review
- Custom rider app branding and per-client domains
- Named engineering contact for integration work
| Feature | Starter | Growth | Enterprise |
|---|---|---|---|
| Route engine | |||
| Real-time route optimisation | |||
| Corridor-level tuning | Standard | Standard | Custom |
| Automatic batching | |||
| Window model | |||
| Live window prediction | |||
| Confidence-band tuning | Default | Configurable | Per-client |
| SLA tier support | Basic | ||
| Reallocation | |||
| Dynamic rider reallocation | - | ||
| Reason logs and audit | - | ||
| Fairness guardrails | - | ||
| Tracking and notifications | |||
| Customer tracking pages | |||
| SMS and email notifications | |||
| WhatsApp channel | - | ||
| Webhook to your systems | - | ||
| Analytics | |||
| Dispatcher board | |||
| Fleet analytics | Basic | Full | Full + exports |
| Cohort comparisons | - | ||
| Access and roles | |||
| Fleet manager and dispatcher roles | |||
| Per-client admin role | - | ||
| Custom roles | - | - | |
| Support | |||
| Response time | Next business day | Same shift | Named contact |
| Onboarding | Standard | Standard | Dedicated |
| Quarterly ops review | - | - | |
Practical questions we get before every pilot.
How is the plan priced within a tier?
Each tier has a fixed monthly platform fee plus a small per-rider component. Volume commitments and multi-year agreements move the rider component down. Exact figures are shared on the working call once we understand the fleet shape.
What does onboarding actually look like?
A two-week calibration where the engine learns your corridor patterns and rider mix, running in shadow mode against a slice of live orders. From week three the engine takes reassignment decisions on the tier and clients you approve.
Do we need a specific rider app?
You can use ours or keep your existing rider app - the engine talks to it through a small integration layer. If you have no rider app, ours is included and can carry your brand from day one.
How does coverage-area setup work?
You define the service area on a map with corridor tags. The engine begins operating in shadow mode over that area, then flips to live on your say-so. Coverage can be extended in-place as the fleet grows.
Are contracts month-to-month?
Starter is month-to-month. Growth and Enterprise are annual by default with monthly billing - which is where the pricing steps down meaningfully. There is a written 60-day exit clause on both.
What happens to our data if we leave?
Your operational data - orders, riders, corridors, analytics - is exportable to CSV and standard formats at any point. After exit, data is retained for the retention window on the security page, then removed.
The right tier is a conversation, not a checkbox.
Tell us the fleet shape and we will tell you the tier that fits, honestly - including if a lower tier would work.