Same fleet. Same drivers. Less time, less fuel, less CO2.
An Afdal productLaffa optimizes the cost, the time and the fuel of your vehicle routing, while respecting every constraint that matters: delivery time windows, vehicle capacity, fleet size, stop priorities and multiple depots. One optimization engine, delivered on three surfaces.
Every person who touches a delivery gets the tool that fits them, and all three are served by the same optimization engine, so the plan on the dispatcher's screen is the route in the driver's hand.
For the dispatcher
For the driver
POST /v1/optimize
{
"deliveries": [ {lat, lng, window} ],
"vehicles": 12,
"objective": "cost"
}
200 OK K ranked routes + KPIs
# back in seconds, capacity, time windows,
# priority & multi-depot, all in one callFor your IT team
POST
/v1/optimize returns ranked routes and KPIs in secondsNothing about your fleet changes. The order in which it drives does, and that single change moves every operating number you track.
Working hours on the road
Fuel and running cost
Kilometres driven
CO2 emissions
Freed capacity for additional deliveries
Measured on live client operations: 19% efficiency gain and 14% cost reduction. The ranges are honest, because the gain depends on how much slack today's manual plan carries. Tight, repetitive rounds land at the low end. Many stops, many vehicles or shifting demand land at the high end.
Real screens from the running app, shown here in the language you picked above, exactly as the driver sees them.
Every stop ordered automatically, each with an arrival time you can give the client, and the whole round on one map.
Play the whole round back stop by stop, in 3D, before the vehicle leaves the depot.
Turn-by-turn to the next stop, with no dispatcher in the loop, and the client one tap away on WhatsApp or a call.
The percentages are what get a manager's attention. These six capabilities are what make operations teams keep using Laffa after the first month.
Every stop gets a realistic arrival time and every round gets a defensible order, so trucks are loaded in the sequence they will be unloaded and your customer desk can tell a client when the driver will actually arrive, instead of "sometime today". Cleaner loading, fewer "where is my order?" calls, and real traceability for the client.
The route lives in the plan, not in one driver's head. A stand-in (or a new hire who has never worked the zone) follows the same optimized sequence turn by turn, so sick days, holidays and turnover stop being operational emergencies. Zone expertise stops being a single point of failure.
Move a depot and see the cost before you sign the lease. Model driver vacation schedules, truck maintenance windows, a seasonal peak, a new client zone or a vehicle off the road, and the engine re-plans and prices each scenario in minutes: depot siting, vacation planning, maintenance windows and fleet sizing, all decided on evidence.
For any request you know, before you quote, exactly how many drivers and how many kilometres it takes to serve it. Quoting stops being a guess and becomes arithmetic, and you walk into the negotiation with a number you can defend line by line.
Kilometres per vehicle, hours per driver, fuel consumed, CO2 emitted and stops served, recorded per route and exportable. The same export answers your client's service-level question, your finance team's cost question and your ESG report, with no spreadsheets rebuilt by hand.
A driver already carries enough: orders, invoices, cash, customers. With Laffa he no longer has to work out the route himself while driving. The sequence is decided, the navigation is turn by turn, and his attention is free for the parts of the job that actually need a human.
Laffa is not a template or a rule of thumb. It is a research-grade optimization engine, wrapped in tools an operations team can actually run.
Capacity, time windows, priorities, multi-depot and driver shifts, modelled rather than ignored
A digital twin stress-tests every candidate plan against the day that actually happens
Several strong plans ranked side by side, so you pick the trade-off you can live with
Fair objections deserve honest answers. Here are ours.
Q“Our drivers know the zone and the roads better than any software.”
AThey almost certainly do, and Laffa uses that knowledge rather than replacing it. But knowing the network is not the same as knowing the optimal order to visit it. With just 15 stops there are more possible sequences than there are seconds in the age of the universe; no human, however expert, can examine them all. The engine can. And there is a second answer, simpler than the first: that driver will one day be sick, on holiday, or gone, and the knowledge leaves with them.
Q“We don't have the data for this.”
AYou don't need a data project to start. The mobile app takes stops the way you already receive them: an address typed by hand, a pin dropped on the map, a Google location, or the location a client sends you over WhatsApp, dropped straight into the app. No TMS export, no clean database, no IT ticket. Integration through the API comes later, if and when you want it.
Q“Our days never go to plan. A client cancels, another calls at the last minute, a new stop appears.”
AThat is exactly what the mobile app is built for. Stops can be added, removed or paused mid-round, and the tour is recomputed on the updated data in seconds, so a cancellation or a late call becomes a small correction instead of a ruined afternoon. It is also a full navigator that adapts live: if the driver misses a turn or takes a different road, the route re-plans around him rather than telling him to turn back.
Q“Do you use real-time traffic data?”
AYes and no, and the honest answer is the more useful one. Real-time traffic describes the road now, but a round that starts at 07:00 and ends at 14:00 will not be driven under "now". So we built something better suited to a full working day: a historical street-speed model. For Lebanon alone, a cleaned dataset of over 6 million routing queries gives us an estimated speed for each street at each time of day, far more predictive than posted limits and matched to how your drivers really drive.
Ask your Afdal contact for a pilot on one week of your own delivery data. You will see your numbers, not ours.
The full Laffa story, the numbers, the three surfaces, and how our clients use them, in one PDF.
Or get the trilingual edition (EN/AR/FR) →Read Laffa's Privacy Policy, Terms of Service, and account-deletion instructions.
View policies