OMX Innovation · Deck 12 · Local Owner-Driver for High-Volume Zones
Replace generic courier with a dedicated owner-driver in the dense metro zones where OMX already has the volume to support a route.
Owner-driver = lower cost per drop, faster delivery window, real customer relationship, local knowledge — and a competitive moat carriers can't replicate.
01 / 06
Why now

The wedge.

02 / 06
What this covers

What's in scope.

01
Zone identification
postcode + drop-density heat map; identify the top 6-10 zones where owner-driver economics work today
02
Owner-driver model
vehicle, contract, route, pay model (per-drop / salary / hybrid)
03
Same-day promise
premium tier ("OMX Plus" delivery — links to Deck 07 Angle B subscription/service tier)
04
Customer experience
known driver, push notification on approach, photo-POD, returns collection
05
Economics
cost per drop today vs owner-driver, breakeven density, scale to 6-10 zones
06
The platform
small driver app, route optimisation, in-cab device
03 / 06
The problem

What's broken.

01
Generic carrier UX
courier turns up, drops at reception, leaves; customer doesn't know who, when, or why
02
High cost per drop in dense zones
paying carrier markup for the density we already created
03
No driver-side relationship
customer doesn't see OMX in the delivery moment
04
Carrier capacity volatility
peak periods (BTS, holidays) = carriers de-prioritise OMX
05
No returns lane
carriers don't reverse-pickup; returns are a separate, expensive workflow
04 / 06
The benefits

The value story.

Lever
Mechanism
Sizing
Cost per drop
Owner-driver vs carrier in dense zones
20-40% cheaper at scale (industry: see Couriers Please, Aramex owner-operator model)
DIFOT lift
Dedicated driver = predictable window
Memory: small-d DIFOT already 99% small (reference_omx_difot_canonical_definitions) — gain is in the customer-experience-perception of "OMX delivers on time"
Customer NPS
Known driver = relationship
Industry: dedicated-driver delivery models lift NPS 15-30 points
Returns enablement
Driver collects on next visit
Removes $X reverse-logistics cost; sizing needs current returns spend
Capacity at peak
OMX-owned driver doesn't get bumped in BTS / holiday peaks
Strategic — BTS Review workshop T2/T3 themes were operational capacity pain
05 / 06
The ask + roadmap

What we need.

Now
Problem vector grid (4)
: Generic-courier / High-density-overpay / No-relationship / No-returns-lane
P2
Zone heat-map
: NZ map with top 6-10 high-volume metro zones highlighted; current drops/day per zone
P3
Before/after delivery moment
: Today's anonymous courier vs OMX-driver-known-by-name
P4
Economics table
: Cost per drop today vs owner-driver model — by zone density tier
P5
Driver app + route flow
: Pick → manifest → in-cab nav → POD photo → return collection → next stop
Audience
Primary: CFO + Chief Operating Officer. Cost per drop + DIFOT + premium-tier revenue. Secondary: Commercial Director — K0-K2 customer experience + driver-as-sales-channel insight. Tertiary: Customer Service — fewer "where's my order" calls when the driver is known.
References
  • Memory: AKL has two despatch channels — line-haul (7pm) + AKL-local (next-morning pickup) (reference_omx_akl_local_vs_linehaul_dispatch)
  • Memory: AKL release sequencing — regional 18:30, metro 20:30, zero buffer (reference_omx_release_sequencing_zero_buffer)
  • Memory: Carrier cutoffs — 6:30pm regional, 8:30pm metro (reference_omx_carrier_cutoffs_correct)
  • Memory: BTS Review workshop themes T2/T3 — operational capacity pain
  • Industry: NZ owner-operator courier models — Couriers Please, Aramex, Post Haste
06 / 06
← All decks