Golden Green Courier

What breaks today

• Passenger items, urgent parcels, returns, and documents run across separate flows.
• Many requests are handled as one-offs, not as windows on repeat corridors.
• Heavy reliance on cars/vans increases curbside pressure and variability.
• Data is scattered: SLA/POD, timestamps, and failure reasons are inconsistent.

A missing customer-facing layer

• No standard option during ticket purchase or check-in to book a corridor window with a clear quote.
• Price/time uncertainty until manual coordination is complete.
• Hard to procure repeatedly because rules and evidence are not standardized.

1) Corridor Windows (capacity-aware)

• Defined Airport ⇄ hub corridors with bookable time windows.
• If the nearest window is full → the system offers the next feasible slot.
• Each tier maps to a window policy: Scheduled / Same-Day Window / Sprint.

2) Evidence Layer (audit-friendly)

• POD at pickup and delivery: OTP/signature + timestamps.
• Exception reasons are tagged (not “stories”).
• Pilot outputs weekly KPI tables + final report.

3) Software Pricing (upfront + explainable)

• Inputs: parcel size/weight/volume + corridor distance/time + handover mode.
• Timing factor: peak/off-peak + urgency tier.
• Scheduled windows get a utilization discount; Sprint may include a scarcity premium.
• Output: quote + slot shown upfront and locked on confirmation.

Draft hub set (Vienna)

Pilot starts with Wien Mitte + Westbahnhof. Handelskai is added if north-corridor demand is validated.

Scope

• Scheduled corridor windows, capacity-managed slots.
• Two-way: Arrivals ⇄ Departures (luggage + small parcels + documents).
• Public transit backbone + last meters (pilot scope).
• Auditable POD + event logs.

Out of scope

• No restricted-zone operations (no airside handling).
• No bulky freight, hazardous goods, spill-risk liquids, controlled substances.
• SLAs are corridor-specific (no citywide guarantee).

Corridor visual

assets/img/vie-corridor-map.png

B2C (C1–C5)

• C1
  Arrival Luggage Delivery & Reunite

  Arrivals or recovered baggage → home/hotel with seal option + OTP/signature + timeline.

  Arrivals/recovered baggage → home/hotel (seal + OTP/POD).
  Details
• C2
  Pre-Flight Pickup & Airport Delivery (Pickup → Hold → Deliver)

  Pickup from hotel/home earlier in the day → optional hold → deliver to the airport at a chosen departure window (POD at both ends).

  Pickup → (optional hold) → airport window (POD both ends).
  Details
• C3
  Deadline-to-Flight Sprint

  Forgotten item → airport before deadline (priority only when reserving scarce slots).

  Forgotten item → airport deadline (scarcity premium if needed).
  Details
• C4
  Secure Document Relay (Sign & Return)

  Pickup/hand-carry important documents for signature/hand-over and return the signed set with full custody trail (ID/OTP + POD).

  Docs sign/hand-over + return (ID/OTP + POD).
  Details
• C5
  Return-to-Store / Return-to-Location

  Returns with proof-of-return to reduce passenger load during stay.

  Returns with proof-of-return (window-based).
  Details

B2B (B1–B6)

• B1
  Airport-Adjacent SMB Operator

  Near-corridor businesses with frequent small runs — windows + POD + repeatable rules (procurement-friendly).

  Near-corridor SMB runs (windows + POD + rules).
  Details
• B2
  E-commerce Seller in Umland

  Suburb clusters → Vienna same-day via corridor windows, without owning a fleet.

  Umland → Vienna windows (no fleet needed).
  Details
• B3
  Forwarder/Broker Runner (Low-Risk, Landside)

  Fast movement of documents/small samples/parts — explicitly no bonded zones; strict POD + timeline.

  Forwarder runners (landside, no bonded; strict POD).
  Details
• B4
  Field Service / Maintenance Parts (AOG-lite)

  Critical small parts/tools delivered in corridor tiers to reduce downtime; measurable exceptions.

  Critical parts/tools (AOG-lite; tiered windows).
  Details
• B5
  Medical/Lab Samples (Pilot-safe subset)

  Only an allowlisted, low-risk subset with simple SOP + serious POD; activated only if pilot rules allow.

  Allowlisted samples only (SOP + POD; pilot-approved).
  Details
• B6
  Retail Stock Transfers (Vienna ↔ Suburb)

  Light boxes moved between branches/mini-warehouses in booked windows — fewer ad-hoc staff trips.

  Retail transfers (light boxes; booked windows).
  Details

What exists

• MVP (backend + web) usable in real operations.
• 100+ logged executions (timestamps, routes, handovers).
• POD flows: OTP/signature + timestamps; return-document where needed.
• Exception tagging and resolution patterns available.

Example screenshot

assets/img/app-screenshot.png

What we ask (clear)

• Pilot permission + boundaries: confirm landside scope, allowed item classes, and pilot duration.
• Meeting points: agree 2–3 handover points and basic on-site rules.
• One POC + intros: a single coordination contact + introductions to ops / passenger services / retail / security (as needed).
• Co-design / mentoring: 2–3 working sessions to finalize KPIs, handover design, and post-pilot integration options.
• Demand seeding: 2–3 pilot-friendly tenant/retail/ops introductions for early B2B volume.

QR → website

assets/img/qr-ggcourier.png (generated on server)