Dispatch and route optimisation software for logistics and last-mile delivery
We prove we're better, or we refund everything. And you keep the solution.
We measure it with an A/B experiment in your live operation, against what you use today, with the metric, method and duration agreed before we start.
- Tailored to your operation
- Integrated with your TMS, WMS and ERP
- Dedicated instance in the EU
Your operation changes by the minute. Your decisions have to keep up.
- 1.1
A rush order comes in or a vehicle breaks down, and you're replanning by hand.
What was decided in the morning no longer holds by mid-afternoon.
- 1.2
Nobody can prove how much a change improves things.
A before/after comparison can't separate the improvement from everything else that changed: volume, season, staff.
- 1.3
Switching systems sounds like a year-long migration.
What already works—your TMS, your WMS, your integrations—shouldn't have to be touched.
Built around your operation. Not the other way round.
We don't ask you to change how you work to fit a piece of software. We start from your operation and build the solution on top of it.
- Fleet
- YoursVehicles, capacities and shifts, exactly as you run them today.
- Zones and windows
- Your customers'With their priorities and constraints.
- Rules
- Your operation'sNot those of a generic template.
- Systems
- The ones you already haveTMS, WMS, ERP and online shop. No migration.
- Driver app
- Yours, extendedIf you already have one, we add what's needed. If not, you use ours.
- Success metric
- The one you chooseAgreed before the experiment.
- Instance
- Yours aloneIsolated, in the EU. We run it.
Three pieces, one solution, tailored to your operation.
We run it for you on an instance that is yours alone. You don't maintain any infrastructure.
- Piece 1 / 3
The decision engine
Decides in real time which driver handles which order and in what sequence, and measures how much it improves on your previous solution.
- Piece 2 / 3
The operations console
Your live operation: manual dispatch, overriding an assignment with a reason, escalation and an explanation of every decision.
- Piece 3 / 3
The driver app
Receive and accept jobs, mark pickup and delivery, share location and capture proof of delivery. Already have an app? We extend it.
Integrates with what you already have.
No forced migration.
- TMS
- WMS
- ERP
- Online shop
Four steps. The last one is our risk, not yours.
- Step 1
Meetings and requirements
We get to know your operation: fleet, shifts, zones, constraints and systems.
- Step 2
We build it to measure
The solution, adapted to your operation and integrated with your systems.
- Step 3
A/B experiment
In your live operation, against your current solution. Metric, method and duration agreed up front.
- Step 4
No improvement, full refund
Onboarding and licences. And you keep the solution.
A before/after proves nothing. An experiment does.
Between before and after, volume, weather, staff and customers all change. That's why we alternate your current solution (A) and Pontro (B) in the same operation, on the same days, and compare the metric we've agreed with you.
Example: time blocks within a single day are randomly split between A and B. The same conditions for both.
Before / after
- Different periods, different conditions
- The vendor chooses the baseline
- Impossible to isolate its effect from everything else
A/B experiment
- A and B in the same operation, on the same days
- Metric, method and duration in writing, before we start
- Results your team can audit
A model with a single incentive.
We send you a proposal after the first meeting: it depends on your operation.
- Onboarding
- A fixed fee for building your solution and integrating it with your systems.
- Licence per order delivered
- You pay for the orders the solution delivers. If your operation stands still, so do we.
- If we don't prove an improvement
- If the agreed experiment doesn't prove we're better than your current solution, we refund onboarding and licences, and you keep the solution.
We only win if you win.
Who's behind it, and where your data lives.
Founded by the engineers who built Glovo's dispatching system.
We know what it takes to make decisions every minute while the streets keep changing. Now we do it around your operation.
- Dedicated instance
- Isolated from every other customer.
- Data in the EU
- In our dedicated cloud, within the European Union.
- GDPR
- Processing compliant with the GDPR, by contract.
- Perpetual licence
- If our company disappears, the solution remains yours.
What people ask us before the first meeting.
How is the improvement measured?
With an A/B experiment in your live operation: your current solution and Pontro alternate in the same operation, on the same days. The metric, method and duration are agreed in writing before we start.
Which metrics do you use?
The ones that matter to your business, chosen with you: for example cost per order, on-time deliveries, kilometres per order or orders per driver hour. We set one primary metric before we start.
Do I have to replace my TMS, WMS or ERP?
No. We integrate with the systems you already have and with your online shop. We don't force you to migrate.
What if we already have a driver app?
We extend it with what's needed to receive jobs, mark pickup and delivery, share location and capture proof of delivery. If you don't have one, you use ours.
How long does it take?
It depends on your operation and your integrations. After the first meeting we give you a firm timeline to the start of the experiment.
Where is my data?
In your dedicated instance, in the EU and isolated from other customers, in line with the GDPR. And if Pontro were to disappear, you hold a perpetual licence to the solution.
What exactly is refunded if you don't prove the improvement?
The onboarding and every licence fee paid. And you keep the solution, with a perpetual licence.
Do you have real dispatching experience?
Yes. Founded by the engineers who built Glovo's dispatching system. Right now we are designing and implementing the dispatching system of a last-mile delivery company.
Let's talk.
A first conversation to understand your operation and tell you whether we can prove an improvement. If we can't, we'll tell you.