Tandrel
Customer outcomes

Operational proof, with the system and human decision visible.

Verified and anonymized outcomes. No customer logo or legal identity is disclosed.

Talk through your workflow See the product

Reporting window · January 1, 2025 – June 1, 2026

312 active workspaces
2,840 active monthly users
1,104 workflows mapped
4,210 Living SOPs reviewed
82,000+ handoffs tracked
1,412 bottleneck suggestions generated
6,100 Weekly Ops Reviews completed

Verified customer case

A Tier 1 specialized logistics provider

Scale

140 FTEs, 22 Operations Leads, 4 Regional Hubs

Window

October 2024 – May 2026

Modules

Workflow Map, Handoff Tracker, Bottleneck Radar

Previous workflow

Slack threads, shared Google Sheets, and definitions of done held by three senior dispatchers

Source records

CargoWise webhook data and internal SQL records

Methodology

Handoff Tracker timestamps compared with CargoWise arrival stamps

Handoff latency reduced from 4.2 hours to 1.1 hours; missing-documentation errors reduced from 18% to 4%.

“The friction wasn't a lack of effort; it was a lack of visibility into the handoff. We stopped arguing about who dropped the ball because the system made the transfer explicit.”
Elena Vance, VP of Operations

Human authority remained explicit: Operations Leads reviewed Tandrel's surfaced issues and approved any resulting state change.

Approved agency client-onboarding story

A human-reviewed improvement loop

  1. 1Signed CRM contract triggers Tandrel webhook
  2. 2Tandrel structures a 14-step onboarding workflow
  3. 3Bottleneck Radar surfaces three 48-hour waits caused by missing client assets
  4. 4Ops Lead reviews the alert and edits the SOP to add a 24-hour asset reminder
  5. 5Onboarding cycle time falls from 11 days to 6 days

Source: internal timestamp audit. The Ops Lead—not Tandrel—reviews the alert and authorizes the SOP edit.