Last-Mile Cost Baseline Director — Consulting

The mandate

The narrow problem is that cost per delivery is calculated differently by finance, city operations and product, preventing reliable zone decisions. Incentives, failed attempts and support costs are especially inconsistent.

The deliverable is one transaction-to-ledger cost model, eight-zone benchmark, variance tree, customer-promise sensitivity and a prioritised ninety-day action plan. Network redesign is outside scope.

Milestone one is due 2 October 2026 with reconciled definitions and four-zone baseline; milestone two on 30 October with all eight zones, sensitivity tests, action owners and executive decision pack.

The Unit Economics Council accepts when model totals reconcile to finance within one percent, three sampled weeks reproduce independently, each variance has an operational driver and the top ten actions have named owners and measurable tests.

The client supplies transaction, route, rider, incentive, support, refund and ledger data plus city-manager access. Finance assigns one controller to approve allocation logic within forty-eight hours.

Why this is external work

Each function's current metric supports a different management narrative. A neutral cost team can establish one baseline quickly without reopening the entire operating model. The need ends once calculations and actions are reproducible.

What you will own

• Define the cost object and reconcile every component to the general ledger.
• Build milestone-one zone baselines by distance, density, promise and time band.
• Attribute failed-attempt, cancellation, support and incentive costs consistently.
• Separate structural zone effects from controllable operating variance.
• Model promise-time, batching and rider-supply sensitivities.
• Rank actions by verified value, feasibility and customer risk.
• Transfer the milestone-two model, documentation and ninety-day pack to client owners.

Candidate qualifications

• 18–22 years in delivery operations, logistics analytics or operations finance.
• Direct construction of transaction-level cost models for high-volume networks.
• Evidence of ledger reconciliation and independent model reproduction.
• Experience connecting zone variance to actionable operating levers.
• Fluency in rider economics, batching, failed delivery and service trade-offs.
• Ability to complete a defensible baseline within eight weeks.

Non-negotiables

• No contingent fee tied to estimated savings.
• Reproducible calculation logic and client-owned model files.
• Bengaluru presence during both acceptance weeks.
• No customer or rider data removed from client systems.

1. 49 words maximum. Which last-mile cost baseline did you build, and what previously hidden component changed management action?
2. 49 words maximum. How would you reconcile transaction and ledger totals within the first three weeks?
3. 49 words maximum. Which route, rider and support fields are essential to explain zone variance?