Routeworks Series A

Logistics startup pitch deck built on cost per delivery

A fleet buyer and a logistics investor will both accept exactly one number, and it is the cost of one drop. Routeworks is invented, and its eleven slides carry that number from the cover to the ask, proved on one matched Tuesday rather than on a demo.

Create a presentation with OneCraft11 slides, read in order

Every slide, in order

The whole deck as it renders, one slide after another. Read it the way the audience would.

ROUTEWORKS

SERIES A, 2027

2.1M deliveries routed a month

IN ONE LINE

Route planning for fleets of 10 to 200 vans. Thirteen percent fewer kilometres on the same drops, measured against the fleet’s own dispatcher over a matched six week period. 3.2 million dollars of ARR.

Cost per delivery, measured rather than promised

Ivan Kraljevic

Co-founder and Chief Executive

Slide 1 · cover · Put the deliveries routed and the saving on the cover, in that order.

THE JOB

Ninety stops, one morning

A dispatcher with twelve vans and ninety stops is solving a problem with more possible answers than there are atoms in the room. They do it every morning in about fifty minutes, using a wall map, a whiteboard and the knowledge of which driver hates which suburb. The answer they produce is usually good. It is almost never the best one, and the gap between good and best is the 13 percent of kilometres this product is sold on. Nothing about that is a criticism of the dispatcher. It is a problem shape people cannot hold in their heads and computers can.

01
The plan breaks by ten

A failed delivery, a road closure or a late load makes the morning plan wrong before the second drop. Redoing it by hand is not possible, so nobody does.

02
Nobody measures the miss

A fleet knows what it spent on fuel. Almost none of them know what the same drops would have cost on a better route, so the saving is invisible.

02

Slide 2 · intro · Why a dispatcher cannot do this by hand, written as an arithmetic problem rather than a criticism.

What Routeworks does

Five things, in the order they happen on a weekday.

Plans the morning

Ninety stops across twelve vans in under two minutes, with time windows and vehicle limits.

Replans on the road

A failed drop or a closed road triggers a fresh plan for the vans that are affected.

Talks to the driver

Next stop, window and access notes. No paper run sheet and no phone call to the office.

Tells the customer

A live window that narrows as the van gets closer, which is what cuts the failed drops.

Costs the day

Kilometres, hours and failed drops priced into one cost per delivery, every evening.

03

Slide 3 · pillars · Five things the product does, each one tied to a moment in the day rather than to a feature list.

Who buys Routeworks

Deb, fleet manager at a 46 van refrigerated distributor in Western Sydney. She has been sold routing software twice before.

Says

"Show me on my own run." She will not look at a demo with sample data. Every deal we have won started with her sending us one real day of stops.

Thinks

That the last system produced routes the drivers refused to run. She is not worried about the algorithm, she is worried about a mutiny at six in the morning.

Does

Arrives at five, plans by hand, fields driver calls until eleven, then spends the afternoon on compliance paperwork nobody else will touch.

Feels

Accountable for a fuel bill she can influence but cannot evidence. When the cost per delivery moves, she wants to be able to say exactly why.

04

Slide 4 · persona · The fleet manager who signs, in her own words, because she is the only person who can prove the saving.

Where Routeworks is

Figures to 31 December 2026 across 118 fleets and about 5,900 vans.

2.1M

Deliveries routed

In December 2026, up from 780,000 a month a year earlier. About 100,000 on a weekday.

13%

Fewer kilometres

Same drops, same fleet, measured against their own dispatcher over six matched weeks.

$3.2M

ARR

118 fleets at a median of 2,100 dollars a month, priced per van.

05

Slide 5 · metrics · Volume, saving and revenue in one row, with the saving stated as a matched comparison.

COST PER DELIVERY

Eight quarters

Q1 25
Q2 25
Q3 25
Q4 25
Q1 26
Q2 26
Q3 26
Q4 26
02468
Routed
Manual baseline

COST PER DELIVERY

$3.41

Blended across 118 fleets

SAVED PER DROP

82c

Against the manual baseline

SAVED IN DECEMBER

$1.7M

Across 2.1 million deliveries

MANUAL BASELINE

$4.23

Flat for eight quarters

06

Slide 6 · metrics · Cost per delivery over eight quarters against a flat manual baseline, since one line alone proves nothing.

One fleet, one Tuesday

Forty six vans, 1,180 drops, the same customer list. Run by the dispatcher one week and by Routeworks the next.

Measure
Dispatcher
Routed
Difference
Kilometres
4,910
4,270
640 fewer
Vans needed
46
42
4 fewer
Driver hours
392
361
31 fewer
Failed drops
58
34
24 fewer
Fuel
$1,830
$1,590
$240
Cost per delivery
$4.22
$3.67
55 cents
Planning time
50 min
2 min
48 min
Both weeks ran in October 2026, same season, same customers, same drivers. The fleet holds the raw data.

07

Slide 7 · comparison · One matched day, dispatcher against routed, so the 13 percent is a subtraction rather than a claim.

How a fleet buys

Four steps, median 31 days, and we never present sample data.

1

Send one day

The fleet sends a real day of stops as a spreadsheet. No integration, no account.

2

See the gap

We route it and put our plan beside theirs. Kilometres, vans and hours, nothing else.

3

Run a fortnight

Half the fleet routed, half on the dispatcher, same two weeks. The drivers decide the rest.

4

Price it per van

Priced on vans, not deliveries, so a quiet month does not punish the fleet for signing.

08

Slide 8 · process · How a fleet gets from a trial to a signature, since the sale is won on their own data.

Priced per van

Monthly, on the vans that ran that month. A van off the road for a week is not charged for that week.

Under 20 vans

Saves about 2,900 dollars a van a year

$58

per van a month

Morning plan and replanning

Driver app and customer window

Cost per delivery reporting

Spreadsheet import

Send us a day

20 to 80 vans

Saves about 3,500 dollars a van a year

$44

per van a month

Everything in the band below

Time windows and vehicle rules

Depot and multi shift planning

Order system integration

Send us a day

Over 80 vans

Saves about 4,100 dollars a van a year

$36

per van a month

Everything in the band below

Multi depot optimisation

Subcontractor allocation

Named engineer on rollout

Talk to us

09

Slide 9 · pricing · Per van pricing in bands, with the saving per van beside the price so the case makes itself.

The ask

Sized to 600 fleets and 12 million dollars of ARR without changing the per van price.

$10M

Series A, to 600 fleets and 22,000 vans routed daily

$3.50M

Integrations

Thirty five percent. Order and warehouse systems. The largest fleets will not import a spreadsheet forever.

$3.00M

Sales

Thirty percent. Twelve sellers, all of whom run the one day comparison themselves rather than handing it to an engineer.

$2.00M

Optimisation

Twenty percent. Six engineers on the solver, because a one percent gain is about 850,000 dollars a year to our customers.

$1.50M

Working capital

Fifteen percent. Fleets pay monthly in arrears and the rollout work is delivered before the first invoice.

10

Slide 10 · investment · Ten million in four lines, weighted to the integrations that decide whether a large fleet can even start.

Send us one real day of stops

A spreadsheet is enough. We route it and put our plan beside yours, on kilometres, vans and hours.

ivan@routeworks.example

11

Slide 11 · closing · Close by asking for the one thing that starts every deal, rather than for a meeting.

The structure

What each slide is doing, so you can reuse the order even with different content.

Slide 1cover
Put the deliveries routed and the saving on the cover, in that order.
Slide 2intro
Why a dispatcher cannot do this by hand, written as an arithmetic problem rather than a criticism.
Slide 3pillars
Five things the product does, each one tied to a moment in the day rather than to a feature list.
Slide 4persona
The fleet manager who signs, in her own words, because she is the only person who can prove the saving.
Slide 5metrics
Volume, saving and revenue in one row, with the saving stated as a matched comparison.
Slide 6metrics
Cost per delivery over eight quarters against a flat manual baseline, since one line alone proves nothing.
Slide 7comparison
One matched day, dispatcher against routed, so the 13 percent is a subtraction rather than a claim.
Slide 8process
How a fleet gets from a trial to a signature, since the sale is won on their own data.
Slide 9pricing
Per van pricing in bands, with the saving per van beside the price so the case makes itself.
Slide 10investment
Ten million in four lines, weighted to the integrations that decide whether a large fleet can even start.
Slide 11closing
Close by asking for the one thing that starts every deal, rather than for a meeting.

Slide by slide

Slide one puts deliveries routed and the saving on the cover. Slide two argues that ninety stops is a problem shape people cannot hold in their heads. Slide three is five things the product does across a weekday. Slide four is the fleet manager in four quadrants, including what she thinks of the last system. Slide five is volume, saving and revenue in one row. Slide six is cost per delivery over eight quarters with a manual baseline. Slide seven is one matched Tuesday in seven rows. Slide eight is how a fleet buys in four steps. Slide nine is per van pricing in three bands with the saving per van. Slide ten splits ten million four ways. Slide eleven asks for one real day of stops.

How to adapt this deck

A company selling to a single national carrier rather than to many mid size fleets replaces the pricing bands with a contract value slide and moves the integration line in the ask to the front, because the sale is one procurement process rather than many small ones. A product for owner drivers drops the persona slide and prices per driver, since there is no dispatcher to displace. A business selling into warehousing rather than delivery keeps the matched comparison and swaps cost per delivery for cost per line picked, which is the same discipline applied to a different unit.

What this audience asks for

The National Heavy Vehicle Regulator publishes the fatigue and work hour rules that constrain how a route can legally be built in Australia, and the federal infrastructure department publishes freight performance work that fleets use as a benchmark. Both matter here because a routing product that produces a plan a driver cannot legally run is worse than no plan at all. A deck that mentions time windows and vehicle limits as constraints, as this one does on the product slide, is speaking the language a fleet manager uses when they evaluate it.

What makes this deck work

The chart carries its own control line

Slide six plots cost per delivery falling from 4.23 to 3.41 dollars over eight quarters with a flat manual baseline running beside it at about 4.23. One line could be fuel prices. Two lines on the same axis make it the product, and nobody has to take that on trust.

One Tuesday, both ways, seven rows

Slide seven runs 46 vans and 1,180 drops through the dispatcher one week and the software the next, and reports kilometres, vans, hours, failed drops, fuel and planning time. The 55 cent saving per delivery is a subtraction anybody can check, and the fleet holds the raw data.

The sale is the proof, and it is on a slide

Slide nine says the fleet sends one real day of stops, the plans are compared, half the fleet runs routed for a fortnight, and only then is a price discussed. Describing the sale as a test the customer runs is more convincing than any accuracy claim.

Questions people ask

What goes in a logistics startup pitch deck?

The planning problem, what the software does during a day, who signs, the volume and saving, cost per delivery over time, a matched comparison, how a fleet buys, the pricing and the ask. This example uses eleven slides and one unit throughout.

Why is cost per delivery the right metric?

Because a fleet manager and a finance director will both agree to be measured on it, and it absorbs kilometres, hours and failed drops into one figure. Kilometres saved alone can be gamed by dropping stops, which is why this deck reports vans and hours beside it.

How do I prove a routing saving?

Run a matched comparison on the customer own data and publish every row. This example uses the same 46 vans and 1,180 drops on consecutive weeks and reports one row where the software is slower. A percentage with no method behind it is assumed to be a best case.

Should logistics software be priced per van or per delivery?

Per van in most cases, because a quiet month should not punish a fleet for signing. This deck charges per van on the vans that ran that month, in three bands from 58 to 36 dollars, and shows the annual saving per van beside each band.

What do fleet buyers object to?

Routes their drivers refuse to run. It is the reason a previous system failed in most fleets that have bought one before. The persona slide in this deck puts that objection in the buyer own words, and the sales process answers it by running half the fleet for a fortnight.

How many slides for a logistics Series A?

Ten to twelve. This one is eleven. Map screenshots are the usual filler and they all look the same. The matched day table is the slide that gets forwarded internally, which is the only real test of a slide in a business to business deck.

Build your own in about a minute

The button below opens the generator with this use case already described. Change the wording to match your own, generate, then edit anything you like.

Make one like this

Other presentation examples

Want the steps in the builder? Read Make a pitch presentation with AI, then Add charts, maps and diagrams to slides. For everything this generator can do, see the presentation maker.

Sources

Written and checked by the OneCraft team. Last checked .