03 · Orchestrate

Per-ride decisioning across owned, contracted, on-demand.

Real orchestration. Not export-to-a-second-provider. Every ride is decided against cost, SLA, live capacity, and vehicle requirement in one dispatch loop.

Request a Demo Read the case study

Most "multi-carrier" features in the category are export buttons to a second provider. A dispatcher still decides who goes where. Mycelium runs per-carrier cost models, per-carrier tracking feeds, per-carrier SLA logic, and reconciles after the shift — fast enough to decide each ride on its own.

01

The decision is per ride.

The operator decides per ride. Manually, or by rule. Rules can compose any of these factors.

  • Geographic area and carrier service zone
  • Fleet characteristics (capacity, accessibility, dimension)
  • Day and time / shift windows
  • Per-carrier cost rules and rate cards
  • SLA requirement of the specific ride
  • Live capacity across owned, contracted, on-demand
See the pricing engine →
02

Three carrier shapes, one operating model.

Owned fleet is the trunk — predictable, repeating, lowest marginal cost. Contracted carriers are the spike — recurring peaks and regional coverage. On-demand is the exception — spillover, standby, last-minute VIPs. Split is per region, per shift, per service tier — operator-set, decided per ride.

Pattern library

Three carrier shapes. One decisioning layer.

The same demand profile split across roles. Owned fleet covers the trunk. Contracted carriers absorb the spikes. On-demand catches exceptions.

TRUNK
Owned fleet. Predictable. Repeating.
Fixed shuttle lines. Recurring delivery runs. Base-load demand.
0006121824
SPIKE
Contracted carriers. Recurring peaks.
Morning + evening commute peaks. Regional coverage where owned fleet runs thin.
0006121824
EXCEPTION
On-demand. Spillover and standby.
Flight delays. Vehicle breakdowns. Last-minute VIP rides.
0006121824
03

Post-shift reconciliation, not a spreadsheet hand-off.

Every completed ride is matched against plan, cost, SLA, and carrier invoice. Operator sees unified margin by carrier, SLA compliance by carrier, and the exceptions feed. The dispatcher does not open three portals.

See operations visibility →
Verticals

Where it compounds.

Own what you want to own. Rent what you want to rent. One operational view either way.

Corporate Commute

Own the trunk, rent the spike, overlay on-demand.

Crew Transport

Own shuttle plus contracted carriers plus on-demand standby.

Last-Mile Delivery

Owned fleet by branch, contracted by region, on-demand for exceptions.

On-Demand Rides

Owned, contracted, partner network — one dispatch loop.

Non-Emergency Medical

Multi-provider dispatch against mobility type and payer.
Observed

What the numbers look like in production.

25 %
Crew transport ride cost reduction · 3-4 dispatchers replaced, ~3,000 rides/mo at peak
3 sources
Owned, contracted, on-demand, one loop
Per-ride
Decisioning, not pre-allocated by morning plan
Post-shift
Reconciliation across every carrier

Send us your three-carrier nightmare.

Owned shuttle, contracted courier, on-demand backup — we'll model the decision loop in a 30-minute call.

Request a Demo Read the three production deployments