The first morning Qued spent inside a reefer carrier’s office, the senior scheduler had been live in the portals since 6:30. One of her produce shippers drops slots at dawn, and whoever’s late gets the 4 p.m. dock nobody wants. Qued President Tom Curee sat behind her with a coffee, a notebook, and instructions to touch nothing. She’d have preferred he wasn’t there at all.
Fair enough. The last vendor preferred a conference room, and she’d spent a year cleaning up after what they installed. Curee put in 20 years at 3PLs and carriers before helping build Qued, and he’s griped about that pattern on plenty of podcasts. Complaining fixes nothing. Sitting in the chair next to the problem occasionally does.
The industry term for what he was doing that morning is a logistics SaaS implementation methodology. In the room it looked like a guy staying out of the way and writing things down. Every scheduling build Qued has shipped since traces back to a morning like that one.
The Install-and-Train Trap
Her company had bought scheduling software once already. It demoed beautifully, handled the easy portals, and fell apart the first week a shipper wanted produce prioritized over paper, which is most weeks in reefer. Scheduling stopped being admin work years ago, and that tool was built like nobody had mentioned it.
Nobody should be surprised. PwC found 89% of operations leaders saying their tech spend hasn’t fully delivered while 85% of that same group believe they’re ahead of everyone else, and the broader research puts roughly 70% of these projects short of their own targets. An Arkansas fleet owner with 150 trucks told a reporter he pays for his TMS’s detention module and “our dispatchers are still doing 99% of the work.”
Nothing about that model is broken. It works exactly as designed. The design just never included her.
Why Qued Gets On-Site Before Building
When the conversation with the carrier got serious, they offered the usual: a requirements doc, a couple of calls, a tour if anyone wanted one. Qued asked for mornings with their most experienced scheduler instead, the skeptic rather than the enthusiast. An eager beta tester forgives a product anything. A 20-year veteran will say the new screen added three clicks to something she does 200 times a day, and she’ll be right.
The reasoning is simple and a little embarrassing for the whole category. Nobody can accurately describe their own workflow out loud. The real one lives in muscle memory and in whatever’s scribbled on the monitor bezel, and no discovery call has ever pulled it out.
So the team skipped the conference room and pulled up a chair.
What Qued Looks For on the Floor
Curee’s notes from that first morning: 14 browser tabs, a password reset at 8:04 because one portal locks accounts every 90 days, and a sticky note reading check back at midnight, Thursdays that went into the build file as a photograph. Also a workaround for one receiver so old that everyone in the room assumed it was official process. It wasn’t. Nobody could say where it started.
None of this is small. Detention hits about 1-in-10 stops and pulls a billion-plus a year out of truckload driver pay, and ATRI put the industry’s total detention bill north of $15 billion. Appointments are where that money leaks first.
The other thing worth watching is what arrives already broken. Late tenders, bad ASNs, windows that pretend a live unload takes 40 minutes. Most of it snaps upstream, a handoff or two before her desk, and she inherits it daily.
The Conversations That Reshape the Build
Around 10 she rejected an appointment the old tool would’ve called perfect: right dock, right window, instant confirmation. Curee asked why. That receiver’s afternoon crew won’t touch produce after 2, she said, whatever the portal claims, and she’d learned it the hard way twice. The rule lived in exactly one place, which was her head.
Working this way has a formal name. Contextual inquiry goes back to the early ’80s, when researchers used it to rebuild software for customer service reps. Forty years on, freight tech still mostly builds for CSRs from a distance, which tells you plenty.
Qued has made a habit of it. Voice scheduling came together the same way at Diel-Jerue: recorded calls, working sessions with actual users, a product shaped around how facilities really answer the phone. Live in under 90 days, across some 7,000 appointments a month.
How the Build Changes After a Visit
Her 2:00 produce rule is a line of logic in the platform now. So is the midnight Thursday drop, which the system watches so nobody has to set an alarm. Her team stayed inside McLeod the whole time, because that’s where they already worked, and the receiver that only answers email gets handled by email without her touching it.
This is the stretch of a logistics SaaS implementation methodology that either exists or doesn’t. NT Logistics said their own operational knowledge is what let Qued fit the platform to real conditions, and their numbers came in at 95.5% of appointments confirmed without a human touch, 98% at the ideal delivery time.
Axle still describes the work as “an ongoing process of discovery,” and go-lives run in days, since the homework already happened.
Building Around the Work, Not Over It
Adoption never came up at that carrier, because there was nothing to adopt. The tool did the job the way the job already worked. Joe Schulz at Schulz Logistics got at the same idea: his people’s time is worth more than clicking through scheduling sites juggling 32 logins, and his crew cut scheduling effort 95% and bad appointments by more than 80%.
The pattern holds well outside Qued’s customer list. Facilities that shift to structured, low-friction scheduling see dwell fall 30 to 50% inside 90 days, and GIX condensed the whole experience into “we save 22 hours per week, per person.” Those hours went back into carriers and customers instead of portals.
At last check the sticky note was gone. That scheduler’s mornings are exceptions now, a short list of judgment calls, and the question Curee puts to every operator sits under all of it: are you buying more technology, or building a better operation?
What Should a Real Scheduling Implementation Look Like?
It looks like somebody from the vendor sitting behind the chair, watching the job that consumes a scheduler’s morning, and asking dumb questions until the smart answers show up. The workflow gets mapped first, and the software gets shaped to it, which is the whole reason go-live takes days. The category’s default, meanwhile, is still install-and-train with better fonts.
Qued exists because appointments deserve that kind of attention. They’re all we do, an inch wide and a mile deep. We automate pickup and delivery scheduling across portals, email, and AI voice calls, inside the TMS your team already lives in, shaped around workflows we stood next to instead of imagined.
If a scheduling decision’s on your desk this year, don’t settle for the canned pitch. Book a demo that runs on your freight. If we can’t win your biggest skeptic over, don’t buy it. We’d rather hear it at your dock than read it in the churn data.
