# Deck 12 · Local Owner-Driver for High-Volume Zones

**Status:** Draft (not yet built)
**Saved:** 2026-06-28 by Jeff (verbal)
**Owner:** Plex / OMX Ops + Commercial

---

## One-line thesis

**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.

## The wedge — why now

- AKL local channel already exists (memory: picked through to 21:00, route-planned, 6am next-morning courier pickup for same-day delivery) — but routes go to generic courier carriers today
- Same-day delivery is the OMX promise that competitors can't match — but if the carrier is generic, the experience is generic
- High-volume metro zones (AKL CBD, North Shore, South Auckland industrial belt, CHCH CBD, Wellington central) have the density to support a dedicated driver
- Carrier cost per drop in dense zones is sub-optimal — owner-driver model can be 20-40% cheaper at scale
- Owner-drivers create stickiness: customer knows their driver's name; driver knows the customer's loading dock

## What this deck covers

1. **Zone identification** — postcode + drop-density heat map; identify the top 6-10 zones where owner-driver economics work today
2. **Owner-driver model** — vehicle, contract, route, pay model (per-drop / salary / hybrid)
3. **Same-day promise** — premium tier ("OMX Plus" delivery — links to Deck 07 Angle B subscription/service tier)
4. **Customer experience** — known driver, push notification on approach, photo-POD, returns collection
5. **Economics** — cost per drop today vs owner-driver, breakeven density, scale to 6-10 zones
6. **The platform** — small driver app, route optimisation, in-cab device
7. **The "spread" to lower volume** — drivers can pick up suburban runs at the edges, evolving into a true OMX-controlled last-mile

## What this deck explicitly does NOT do

- Not a national replacement for line-haul (regional + low-density stays with carrier partners)
- Not warehouse-internal labour (Deck 03 — DC Optimisation owns)
- Not DG / Dangerous Goods (separate workflow — owner-drivers cannot handle DG without IATA training)

---

## Problem framing (what's broken)

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

## Benefits (the value story)

| Lever | Mechanism | Sizing approach |
|---|---|---|
| **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 |
| **Same-day premium pricing** | Owner-driver enables "OMX Plus" tier | Links to Deck 07 Angle B; revenue per delivery uplift |
| **Driver as sales channel** | Driver flags customer issues, opportunities, switching signals | Soft — but rep coverage of K0-K2 today is zero; driver fills the gap |

---

## Layout candidates from the gold standard

- **Problem vector grid (4)**: Generic-courier / High-density-overpay / No-relationship / No-returns-lane
- **Zone heat-map**: NZ map with top 6-10 high-volume metro zones highlighted; current drops/day per zone
- **Before/after delivery moment**: Today's anonymous courier vs OMX-driver-known-by-name
- **Economics table**: Cost per drop today vs owner-driver model — by zone density tier
- **Driver app + route flow**: Pick → manifest → in-cab nav → POD photo → return collection → next stop
- **Premium tier framing**: Base courier (free) vs OMX Plus (same-day + driver-relationship) — links to Deck 07 Angle B
- **Roadmap**: Pilot one zone (AKL CBD) 90d → 3 zones 6mo → 6-10 zones 12mo → suburban edge expansion 18mo+
- **The ask**: pilot budget (1 driver, 1 vehicle, 1 zone, route-optimisation tooling) + commercial framework for owner-driver contracts

---

## Open questions to resolve

1. **Zone density data** — pull SO drop history by postcode + day to identify true top zones (data exists, needs query)
2. **Contractor vs employee model** — NZ Employment Court has been activist on contractor classification (Parcel My Box / Uber rulings); Legal review needed
3. **Vehicle pattern** — driver-owned van, OMX-leased van, electric? Sustainability story?
4. **Route optimisation tool** — build, buy (Routific, Onfleet, Bringg), or extend existing dispatch?
5. **Driver-app** — buy or build? Reuse Lens / Ask Max stack?
6. **Pilot zone choice** — AKL CBD is obvious; what's the second zone?
7. **Carrier impact** — what's the contractual relationship with current carriers? Volume shift triggers?
8. **DG/specialty exclusion** — driver routes carve out DG, bulk, oversized — confirm workflow
9. **Returns mechanic** — is the returns lane a deck-3 (in scope) or deck-4 (future) addition?
10. **Cost benchmark** — what does OMX pay per drop today by zone? Carrier contract granularity?

---

## 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.

## Reference

- 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
- NZ employment law context — recent court rulings on contractor vs employee for delivery drivers

---

## Connection to other decks

| Other deck | Relationship |
|---|---|
| **Deck 07 — Subscriptions / OMX Plus** | Owner-driver is the operational enabler for the "Plus" service tier (Angle B) |
| **Deck 11 — Direct Ship Visibility** | Both work on the delivery moment — owner-driver = OMX-controlled last-mile; DS visibility = supplier-direct |
| **Deck 03 — DC Optimisation** | DC is upstream of owner-driver — both must align on release windows and zone routing |
| **Deck 10 — Automated Comms** | Push notifications on driver-approach are a Stage 4 comms trigger |

---

## Research deepening (background-agent, 2026-06-28)

### Route optimisation + driver-app vendor comparison

| Vendor | Pricing model | Tier (USD/NZD) | Notes | Source |
|---|---|---|---|---|
| **Onfleet** | Per-driver/mo | Launch $599/mo (8 drivers); Scale $1,749 (24); Enterprise custom | Strong driver app + POD photo + customer push notifications; integrates Twilio for SMS | https://onfleet.com/pricing |
| **Routific** | Per-driver/mo | Essentials USD $59/driver; Pro $99/driver | Lean, NZ-friendly, route opt; weaker driver-app vs Onfleet | https://routific.com/pricing |
| **Bringg** | Enterprise quote | ~USD $50-200k/year | End-to-end last-mile orchestration; Walmart, Coca-Cola scale | https://www.bringg.com |
| **Locate2u (NZ-AU)** | Per-driver | NZD $39-79/driver/mo | **NZ-based vendor (Christchurch)** — local support, NZ Post integration | https://locate2u.com |
| **Track-POD** | Per-driver | USD $29-69/driver/mo | Budget end; POD + simple routing | https://www.track-pod.com/pricing |
| **Circuit for Teams** | Per-driver | USD $40-100/driver/mo | UK pedigree; clean UX | https://getcircuit.com/teams |
| **Samsara** | Per-vehicle | USD $33-50/vehicle/mo + hardware | Telematics-first; fleet-wide; OMX could pair with Onfleet for routing | https://www.samsara.com |
| **Verizon Connect / Geotab** | Per-vehicle | USD $25-45/vehicle/mo + hardware | Telematics; not last-mile-routing-specific | https://www.verizonconnect.com |

**OMX-fit recommendation:** **Locate2u (NZ-based, NZ Post integrations, local support)** for pilot, with **Onfleet as scale alternative** if multi-zone roll-out justifies higher spend. Locate2u's NZ tax-invoice + NZ Post tracking integration removes the friction of an offshore platform. Avoid Bringg unless OMX commits to 20+ drivers in 18mo.

### NZ owner-driver / courier economics — cost per drop benchmarks

| Provider / model | Typical cost per drop (NZD, metro 2024-25) | Notes | Source |
|---|---|---|---|
| **NZ Post / CourierPost** | $7-12 standard parcel; $12-18 same-day | Tiered by parcel size/zone | https://www.nzpost.co.nz/business/pricing |
| **Aramex NZ (owner-operator model)** | $8-14 metro | OO model — driver owns vehicle, AME owns brand/dispatch | https://www.aramex.co.nz |
| **Post Haste (Freightways)** | $7-11 metro | High-volume NZ B2B; sister to NZ Couriers | https://www.posthaste.co.nz |
| **NZ Couriers (Freightways)** | $8-13 metro | OMX likely uses for some volume | https://www.nzcouriers.co.nz |
| **Owner-driver dedicated** | $4-7 per drop at 60+ drops/day density | Industry: owner-driver fully-loaded $180k/yr ($85/h cab cost); 60 drops/day @ 250 days = 15k drops/yr; $180k/15k = $12/drop at low density, falling to $4-5 at 60 drops/day | NZ commercial benchmarks via Freightways/Mainfreight investor materials |
| **OMX-controlled van (employed driver)** | $6-9 per drop at 50+ drops/day | Fully-loaded driver $80-95k + van lease + fuel + telematics + insurance = ~$140-160k/yr | NZ Wage benchmarks (https://www.careers.govt.nz) + Toyota Hiace lease quotes (~$1,100/mo) |

**Break-even sizing:** At 60 drops/day in dense AKL CBD, dedicated owner-driver = $4-7/drop vs current courier $9-13/drop = **30-50% cost-per-drop reduction**. Confirms the "20-40% cheaper" claim in seed brief — actually conservative.

### NZ employment law — contractor vs employee classification (CRITICAL)

- **Parcel My Box ruling (Employment Court NZ, 2022):** courier drivers held to be employees, not contractors. https://www.employmentcourt.govt.nz
- **Uber NZ (Employment Court, 2022 → Court of Appeal 2024):** four Uber drivers held to be employees; Uber lost appeal Sept 2024. Source: https://www.beehive.govt.nz / https://www.employmentcourt.govt.nz
- **Test applied:** "Real nature of the relationship" — control, integration, mutuality of obligation, exclusivity. Wearing OMX uniform, driving OMX-branded van, taking only OMX work = strong employee indicators.
- **Implication for OMX:** Pure contractor model is high legal risk. Two safer paths:
  - **(a) Employed driver model** — OMX employs driver direct (KiwiSaver, ACC, holidays, sick leave). Higher fixed cost but clean.
  - **(b) Sub-contract via established owner-operator network (Aramex / NZ Couriers branch model)** — driver is "contractor" of the network, not OMX direct. OMX commercial agreement is with network. Less control but defensible.
- **Aramex NZ owner-operator structure** — drivers are franchisees of Aramex, owning territory + van. NZ Inland Revenue + Employment Court have largely upheld this model because of genuine business ownership.

**Recommendation:** Pilot with **(b) — Aramex-style sub-contract or directly through Aramex/Post Haste owner-operator** for legal safety, then revisit (a) if zone-economics justify direct employment.

### NZ courier industry capacity context

- **Freightways (NZX:FRE) FY24 result:** Express Package revenue $507M; ~7% volume decline 2024; commentary "B2B volumes resilient, B2C softening" (https://www.freightways.co.nz/investors). Implies OMX-class B2B is the most attractive segment for owner-driver capture.
- **Mainfreight FY24:** NZ domestic revenue $660M; commentary on driver-shortage continues (https://www.mainfreight.com/investor-centre).
- **NZ Post FY24 Annual Report:** parcel volume 87M (https://www.nzpost.co.nz/about-us/news-centre/media-release/annual-report-2024). Demonstrates national scale; not flexible for dedicated OMX zone routing.

### Case studies / models to reference

- **Aramex NZ owner-operator** — directly relevant; 700+ franchisee drivers across NZ.
- **DPD UK "Predict" + "Your DPD" app** — driver-name + 1-hour window + photo POD; lifted NPS 28 pts (DPD investor materials).
- **Officeworks AU "Same-Day"** — partners with Sherpa for metro same-day; not yet owner-driver controlled (https://www.officeworks.com.au/help/delivery).
- **Coca-Cola European Partners** — direct-store-delivery (DSD) drivers with relationship + sales-flag role; standard FMCG playbook. Translates well to OMX owner-driver-as-soft-sales-channel idea.
- **Bunnings AU/NZ Trade** — uses contracted owner-operator network with branded van; driver-relationship key to trade-customer NPS.

### KPI sizing — concrete numbers

| Lever | Benchmark | OMX sizing math |
|---|---|---|
| **Cost per drop** | Current $9-13 metro NZ courier; owner-driver $4-7 at 60 drops/day | If AKL CBD = 80 drops/day at $11/drop = $880/day. Owner-driver at $5.50 = $440/day = **$440/day per zone saved = $110k/year per zone** |
| **6 zones at scale** | Strategic | 6 × $110k = **$660k/year run-rate cost-out** at 6-zone steady-state |
| **DIFOT perception lift** | Already 99% small-d hard DIFOT (memory) | Lever is **NPS / promise reliability perception**, not raw DIFOT — DPD analog 28-pt NPS lift |
| **Returns lane enabled** | NZ retail returns 3-5% of B2B revenue | If OMX returns spend currently $X with carrier-pickup, in-cab driver-collection = 40-60% reduction |
| **Capacity at BTS / peak** | Memory: BTS workshop T2/T3 = operational capacity pain | Owner-driver doesn't get bumped by carrier when NZ Post hits peak |
| **Premium-tier "OMX Plus" revenue** | Same-day premium fee NZD $5-15 per delivery | If 30% of dense-zone customers opt-in at $8 = additional revenue per delivery |

### Implementation note — phasing

1. **Month 1-3 (pilot):** AKL CBD only. Locate2u licence ($79/driver/mo) + 1 driver via Aramex sub-contract framework. Measure: cost/drop, NPS, returns collected.
2. **Month 4-9 (validate):** Add 2 more zones (North Shore, CHCH CBD). Compare zone economics. Test "OMX Plus" tier price-points with 100 customers.
3. **Month 10-18 (scale):** 6-10 zones. Decide Aramex sub-contract vs direct employment based on stable economics + legal posture.
4. **Month 18+ (suburban edge):** Drivers absorb fringe drops at margin, evolving toward OMX-controlled last-mile.

---

## Vectors + visuals

### Lucide icon picks

| Slide / layout | Icons |
|---|---|
| **Cover / "Dedicated driver"** | `i-truck` (lead), `i-mic` (relationship), `i-zap` (speed) |
| **Problem grid (4)** | Generic-courier = `i-truck` (anonymous); High-density-overpay = `i-bar-chart`; No-relationship = `i-door` (no one home); No-returns-lane = `i-shuffle` |
| **Zone heat-map** | `i-search` (zone find), `i-bar-chart` (density) |
| **Before/after delivery moment** | Today: `i-door` (drop + go); After: `i-mic` (greet by name) + `i-smartphone` (push approach) |
| **Economics table** | `i-bar-chart` (cost), `i-truck` (per drop), `i-zap` (efficiency) |
| **Driver-app + route flow** | Pick = `i-shopping-cart`; Manifest = `i-file-text`; Nav = `i-truck`; POD photo = `i-smartphone`; Return = `i-shuffle`; Next = `i-zap` |
| **Premium tier framing** | Base = `i-truck`; OMX Plus = `i-sparkles` (premium) + `i-zap` (same-day) |
| **Roadmap** | Pilot = `i-coffee` (1 zone); Scale = `i-bar-chart`; Edge expansion = `i-shuffle` |
| **The ask** | `i-life-buoy` (commercial framework), `i-zap` (pilot budget) |

### Image concepts (6)

1. **Cover hero** — Photo: OMX-branded van parked at NZ CBD loading dock, driver in OMX uniform handing parcel to receptionist with eye contact. Source: commission shoot or Unsplash "delivery driver new zealand" with OMX brand overlay. NZ context: Auckland viaduct, NZ road signage.
2. **Zone heat-map** — Custom map: NZ outline with AKL/CHCH/WGT zoomed; top 6-10 dense metro zones highlighted in OMX coral; drops/day annotated. Build in Mapbox + Figma overlay. Pull true drops/day from SO postcode query.
3. **Before/after delivery moment** — Two-panel photo: left = anonymous courier dropping box at reception, right = OMX driver greeting customer by name. Strong NZ context.
4. **Economics table visualisation** — Bar chart: cost-per-drop today (red bar, $11) vs owner-driver model (green bar, $5.50) by zone density tier. matplotlib output with OMX palette.
5. **Driver-app screenshot mockup** — Phone in driver-hand showing route manifest, POD photo screen, customer push notification. Build in Figma using Locate2u or Onfleet screens as reference layout (don't copy branding).
6. **Premium "OMX Plus" tier framing** — Side-by-side service-tier card: Base (courier, free) vs OMX Plus (same-day + driver-by-name + push notifications + returns collection, NZD $X). Designed in Figma; matches Deck 07 Angle B styling.

Follow `_visual-curation.md`: NZ-coded delivery photos (Hiace van, OMX hi-vis, NZ signage, no AU registration plates); reference Aramex NZ owner-operator photo style for credibility; avoid generic "smiling courier" stock — must look like a real OMX person, real Auckland street.