Skip to main content
+1 332 241 7790

Industry

Logistics & Supply Chain.

We build route optimization, ETA prediction, demand forecasting, exception management, and last-mile systems for fleet-scale operators. Architecture is designed for real-time operations, not generic SaaS patterns.

Book a discovery callGet a scoped plan
DOT / FMCSA
Aware
C-TPAT
Supported
ELD compliance
Aligned
SOC 2 Type II
In flight

The landscape

Logistics fails at the gap between the optimization model and the dispatcher.

Logistics platforms usually fail between systems, not inside one model. Routing works in backtests but fails during live exceptions. Dispatcher tools fight the model instead of helping teams use it. ETA models miss driver and dwell-time behavior. WMS and routing stacks drift apart. Customer tracking is stale. Strong logistics delivery connects optimization, operations, and customer experience in one flow.

We scope around operational reality first. Real-time routing pipelines are built to tolerate high exception volume. Dispatcher interfaces are designed with dispatch teams, not in isolation. ETA models are calibrated on live telemetry and stop-level behavior. Customer tracking is built for near-real-time freshness. CORTEX leads optimization, FORGE leads operational tooling, and rollout happens with dispatch teams in the loop.

Where we ship

6 workloads, grounded in this sector.

Specific applications we’ve built and operated for logistics & supply chain buyers. Every example below is grounded in a real shipped engagement.

  • 01

    −18%

    miles per delivery

    Route optimization at fleet scale

    Real-time routing for fleet-scale operations with exception handling, driver-behavior reality, and integration with TMS / WMS. Dispatcher UIs co-built with the people who use them.

  • 02

    ETA prediction

    Telemetry-grounded ETA models with explicit calibration to driver behavior, traffic conditions, and stop dwell. Integration with customer-facing tracking and exception escalation.

  • 03

    Demand forecasting

    Multi-horizon demand forecasting for inventory, capacity, and labor planning. Integration with WMS and ERP for closed-loop replenishment.

  • 04

    Last-mile delivery apps

    Driver mobile apps, customer tracking, proof-of-delivery, exception capture, and the offline-first patterns last-mile actually requires.

  • 05

    Warehouse management

    WMS, slotting optimization, pick-path engineering, and integration with automation (AS/RS, conveyor, robotics) where the workload warrants it.

  • 06

    −12%

    fuel spend

    AI dispatch optimization

    Reinforcement-learning-driven dispatch combined with predictive ETAs. Migration of batch jobs to event-driven workers with documented rollback per workload.

Quick read

In plain terms: we map the compliance frame, ship the core workflow, and operate the system with named owners and measurable targets.

  • - Route optimization at fleet scale: shipped for production teams.
  • - ETA prediction: shipped for production teams.
  • - Demand forecasting: shipped for production teams.

How we engage

4 phases, named in the SOW.

Each phase has a deliverable, an owner, and an acceptance criterion specific to logistics & supply chain delivery.

  1. 01

    Operating reality assessment

    Discovery in dispatch operations, not in the boardroom. We sit with dispatchers, ride with drivers, audit TMS / WMS configurations, and identify the operational friction the project has to solve. Architecture decisions land against actual operations, not optimistic backtests.

  2. 02

    Real-time architecture with exception handling

    Streaming-first architecture for routing, ETA, and exception flows. Latency budgets calibrated to dispatch decision cadence, not engineering convenience. Exception handling designed in from architecture, not bolted on after launch.

  3. 03

    Co-built dispatcher tooling

    Dispatcher and driver UIs co-built with the people who use them. The model that ships is the model dispatch trusts; the UI that ships is the UI dispatch defends in the post-mortem when something breaks.

  4. 04

    Operating cadence

    Quarterly model recalibration against drift and seasonal shifts, monthly exception-pattern review, and the operational discipline logistics rhythms require. Many engagements continue under Managed Services through multiple peak seasons.

Practices in logistics & supply chain

How each practice plays in this sector.

The capabilities below are scoped to the constraints logistics & supply chain procurement actually enforces: compliance, audit, data residency, and vendor risk.

Selected work

Quantified outcomes, not adjectives.

All case studies

Common questions

Asked before the first call.

  1. 01

    Can you integrate with our existing TMS and WMS?

    Yes. Manhattan, Oracle TMS, BluJay, JDA, and other major WMS platforms are in our active portfolio. Integration is treated as primary scope, not a later phase. We define interface contracts, run dual-write windows on critical paths, and include fallback paths for partner outages.

  2. 02

    Do you do edge inference for vehicle workloads?

    Yes, when latency and connectivity requirements justify it. We deploy edge inference for in-cab assistance, driver-behavior monitoring, and routing support. We also advise when cloud plus QoS-aware sync is the better option.

  3. 03

    How do you handle driver-facing apps?

    Driver apps are offline-first by default, with explicit sync conflict handling. We design for battery constraints and in-cab accessibility. We also co-build with driver focus groups during design to match real usage conditions.

  4. 04

    Can you support multi-modal logistics?

    Yes. We have shipped programs across truck, rail, ocean, and air. Scope includes multi-modal optimization, network-flow planning, and operational tooling used by carriers and 3PL teams.

  5. 05

    What about ELD compliance and DOT regulations?

    We design with ELD requirements in mind and integrate hours-of-service compliance into routing and dispatch. We also implement audit-trail tooling required for DOT examinations. CITADEL co-pilots regulated-fleet engagements from kickoff.

  6. 06

    What does a logistics engagement cost?

    Operating assessment: 4–6 weeks, $50K–$120K. Routing / ETA program: 6–10 months, $500K–$1.5M. Dispatch platform with TMS / WMS integration: 9–14 months, $1M–$3M. Multi-modal optimization programs: $1.5M–$4M+. Managed Services: $40K–$150K monthly retainer.

Talk to us

Bring a logistics & supply chain problem. We’ll bring a senior engineer.

A senior engineer plus the relevant department lead joins the first call. No discovery gauntlet, no junior reps.

Book a discovery callRequest a proposal