PYLON.
pylon.work

Case Study · [VERTICAL]

How [FLEET NAME] cut [METRICS: dispatch time 65%] across [METRICS: X] trucks.

[FLEET NAME] Fleet
[VERTICAL] Operation
[CITY, STATE] Headquartered
[X] trucks on Pylon
[X] months with Pylon

Dispatch time / load

[METRICS: 11 min → 4 min]
From load creation to truck assigned and driver notified.

Driver-idle minutes saved

[METRICS: 14 min/load]
Better load-to-truck match, less staging time, fewer wasted miles.

Annual savings

[METRICS: $XXX,XXX]
Net of Pylon subscription. Dispatcher hours + driver-idle reduction.

The situation

[FLEET NAME] is a [SIZE: e.g. 14-truck full-TL / 22-truck mixed flatbed and reefer / 8-truck hot-shot] operation in [CITY, STATE], operating since [YEAR]. By [YEAR], the fleet had grown to [X] trucks, dispatched out of one back-office desk by [DISPATCHER FIRST NAME], who has been with the company [X] years.

The dispatch board was a wall-mounted whiteboard, an Excel sheet, and three SMS threads. [DISPATCHER FIRST NAME] could hold the system in her head, but the system was hitting the limits of one human's attention.

The decision

[OWNER FIRST NAME] had been quoted [DOLLARS: $X,XXX] per month for an enterprise TMS (Trimble or McLeod) with a [DOLLARS: $X,XXX] implementation fee. The price was outside the budget, the implementation timeline was 4 to 6 months, and the dispatcher's day-to-day workflow would not survive that disruption.

"[QUOTE: 1 to 2 sentence direct quote about the moment they decided to try Pylon. Specific. Includes a number or a moment of friction.]"
[OWNER FULL NAME] · [TITLE], [FLEET NAME]

The Pylon onboarding was scheduled for a Monday morning. [DISPATCHER FIRST NAME] was running the new board on real loads by 1 p.m. that day. Drivers were notified by SMS that morning; no driver app was required. The whiteboard stayed up for three weeks as a parallel reference, and was finally taken down [X] weeks after go-live.

What changed in 90 days

[FLEET NAME] saw three measurable shifts:

1. Dispatch time per load collapsed. Average dispatch time went from [BEFORE: 11 minutes] to [AFTER: 4 minutes]. The AI suggestions surfaced the right load-to-truck match faster than the dispatcher could mentally calculate it, and the keyboard shortcut workflow took the click count from 12 to 1.

2. Driver-idle minutes dropped. Better load matching reduced average driver-staging time by [METRICS: 14 minutes/load]. Across [X] loads/year, that is [METRICS: X,XXX] driver-hours saved, or roughly [DOLLARS: $XXX,XXX] at the fleet's loaded driver cost.

3. The customer-facing tracking link replaced phone calls. Customer calls into the dispatch desk asking for status dropped roughly [METRICS: 60%]. The dispatcher's day got quieter. The customer experience got measurably faster.

"[QUOTE: 1 to 2 sentence operational quote from the dispatcher. About what their day looks like now versus before. Mentions the board or the SMS dispatch specifically.]"
[DISPATCHER FULL NAME] · Dispatcher, [FLEET NAME]

Year one

Twelve months after rollout, [FLEET NAME] had saved [METRICS: $XXX,XXX] in combined dispatcher hours and driver-idle reduction. Net of the [DOLLARS: $X,XXX] annual Pylon subscription, the fleet captured [METRICS: $XXX,XXX] in net savings, or roughly [METRICS: XXx] return on subscription cost.

[FLEET NAME] is now expanding to [X] additional trucks in [QUARTER YEAR] and has rolled Pylon out as the standard for the dispatch desk on a second yard in [CITY].