# Derek Holt, VP of Carrier Operations at Apex Road Solutions — read of carrier-rate-confirmation-voice-agent, June 11 2026

> 11 years in freight brokerage, last four running a 22-person carrier team out of Memphis. We move about 400 loads a week, mostly flatbed and dry van. Currently on McLeod. Two kids in third grade, 40-minute commute each way, I listen to trucking podcasts until I want to throw my phone out the window.

## How I got here

A guy named Phil in the Freight Brokers Network Facebook group dropped the link with the comment "someone build this already." I clicked it mostly to see if someone had. That was my bar coming in: I wasn't searching, I was just curious whether it existed.

## What I clicked first

The hero line landed: "Lock In Carrier Rates Before Dispatch." That's not fluff. That's the actual problem, stated correctly. Every dispatcher I have knows the Friday 4:45 PM version of this: you negotiate a rate, carrier says they'll call back to confirm, and by Monday morning they've moved on to another load. "The window to lock in a rate is measured in minutes" -- I have said almost that exact sentence in a team meeting. That got me reading.

## Where I paused

The FAQ answer: "From rate negotiation to call placed: under 30 seconds. From call placed to TMS logged: under 2 minutes, with timestamps."

That's a real, falsifiable claim. I appreciate that. But what triggers the 30-second clock? Is it a webhook from my TMS on a status change? A button a dispatcher pushes? An API event? That's the entire question. A voice agent that auto-dials in 30 seconds is impressive. A voice agent that dials in 30 seconds after my dispatcher remembers to click something is just a faster phone. The page doesn't answer this anywhere.

## What I distrusted

"Carrier Preferred. Brief, professional call. They confirm and hang up. Carriers appreciate the speed over endless callback chains."

Says who? No data behind this at all. Some of my owner-ops would love getting a quick robot confirmation call. Some of my regulars are going to hear a synthetic voice and hang up before it finishes the rate number. Carriers are not a monolith. I'd want something like "we tested this with 200 carriers and 68% confirmed on first call" -- not a marketing assertion written like a product feature.

Also: Samsara and Verizon Connect are listed as TMS integrations. Those are ELD and fleet management platforms, not TMS. A broker running McLeod, Trimble, or Mercury Gate is going to read that list and wonder where they fall.

Then I hit the bottom of the page. "We don't have live customers on this idea yet." And tiers labeled "Adopt the build $99-$199." Wait. This isn't a product. This is an idea marketplace selling me a starter kit to go build this myself. I spent three minutes deciding whether to book a demo on something that doesn't have a single live customer yet. The entire page reads like a product launch, and then the last section reveals it's a concept you can license. That's a pretty significant bait-and-switch in terms of page intent.

## What would convince me

One live call recording. 90 seconds. Real carrier, real rate, real TMS field that auto-populated after the call. I don't need a testimonial. I don't need a case study PDF. I need to watch the thing happen once, end to end, and see that the TMS entry looks like something my billing team would accept.

If this is still in the pilot-seeking stage, lead with that in the hero. "We're building this for the first 3 freight brokers willing to co-develop it" is a better lede than a demo CTA that implies a production-ready product.

## What I'd ask in an email reply

1. What specifically triggers the 30-second call timer? Is it a webhook from the TMS, a manual dispatcher action, or something else? Because the answer changes the whole workflow.
2. Have you tested this with carriers who only accept load confirmation through their own portals or have DNC policies on unsolicited calls? What's the fallback?
3. Is this live somewhere, or are you looking for a first pilot customer? I want to know what I'm actually signing up for before I get on a call.

## Verdict: on-the-fence

The problem description is accurate and specific, which is rarer than it should be on pages like this. But the page positions itself as a product and then reveals itself as an idea looking for its first builder. Those are two very different conversations. If it's the latter, say so earlier and I might actually reply.

---
*Memo by skeptic persona, generated 2026-06-11. Studio breaks own self-grading loop.*