Freight / 3PL · Discovery Call
Discovery Call Questions for Freight / 3PL: A 25-Minute Playbook for Brokerage Buyers
You've got 25 minutes with a Director of Brokerage Operations who cleared time on a Tuesday in the middle of produce season. Behind him, forty coordinators are making six to ten check calls a load, retyping ETAs into the TMS and then into two shipper portals, and chasing a dispatcher who keeps saying "he's rolling" without a city. He already knows your one-liner. He booked anyway. That means he has a problem he hasn't solved, and he's going to hand you the polite version of it in the first two minutes.
The polite version is "we've got a visibility gap." That's worth nothing. Underneath it is a mechanism — the small carriers on the hard lanes decline the ping, tracking compliance sits at 58%, and the loads that go dark are exactly the ones the shipper's plant calls about. Underneath that is the part he'll only say once you've proven you can hold the conversation without reaching for a screen share: the QBR deck with a 91% on-time delivery number he can't defend, because the proof behind it is a coordinator's typed note instead of a GPS ping, and the account doing 40 loads a week is up for rebid in March.
This playbook gets you to that third layer before minute 16. It assumes you will be pushed — on "every freight tech company promises visibility," on the TMS rollout that took 18 months and still isn't done, on carriers who won't take the app. Those are fair objections in this business and the answers are specific, not clever. Your only deliverable at minute 25 is a dated next step with a named ops lead on it. Everything else is note-taking.
The discovery call script
Say it in your own words. The structure is the part that matters.
- 1
Before you dial — write these six things on your notepad
Top of the page: the time budget. 0–2 frame, 2–16 diagnose, 16–20 path, 20–23 relevance, 23–25 close. Under that, the six numbers you want to leave with, written as blanks you have to fill in out loud: 1. Check calls per load today — ___ 2. Loads covered per coordinator per day — ___ 3. Tracking compliance rate (% of loads with automated location) — ___ 4. Net revenue per load, spot vs contract — ___ / ___ 5. On-time delivery % in the last shipper QBR — ___ 6. Last account lost to service, and its weekly volume — ___ You will not get all six. Three of them, in their words, with a "how do you know?" attached, is a good call. Also write the name of their TMS if you know it — McLeod, MercuryGate, Turvo, Aljex, Tai — because you'll need it in minute 17 and guessing wrong is expensive.
- 2
0:00–2:00 — The frame (do not re-pitch)
"Thanks for making the time — I know what week this is for you. When we talked Thursday, you said your coordinators are on the phone half the day and nobody's building lanes while that's happening. That's the thing I want to dig into. Fair warning on how I run these: I'm going to ask a lot of questions for the first fifteen minutes and I'm not going to show you anything. I'd rather tell you at minute twenty that this isn't a fit for how your brokerage runs than burn a demo slot on you and a couple of your ops leads. Still good for 25? And before I start — anything you want to make sure we get to, so I don't run us out of clock?" [If they say "honestly I just want pricing and how it plugs into McLeod" — that's a different call and now you know it. Say: "Got it, I'll leave us six minutes at the end for both. Can I get a bit of context first so the pricing conversation is about your load count and not a list price?"]
- 3
2:00–6:00 — Layer 1 to Layer 2: open the check-call thread
Pick ONE opener. Not five. "Walk me through how a load gets covered and tracked at your shop today — from tender hitting the board to POD. Start to finish, the way it actually happens, not the way the SOP says." Then shut up and let them talk for two minutes. Three follow-ups before you change subject: - "When you say the coordinator confirms pickup — is that a phone call to the driver, to dispatch, or is something pinging you automatically?" - "Walk me through the last load that went sideways. What actually happened, hour by hour?" - "Where does that update live? Does it land in the load record in [their TMS], or does someone retype it into the shipper's portal too?" What you're listening for: how many humans touch one load, how many systems the same data point gets typed into, and who invented the workaround. There is always a workaround. It's usually a spreadsheet called Coverage Board or a WhatsApp group with the top ten dispatchers in it.
- 4
Minute 6 — "So what do you guys actually do?" (the trap)
It comes at minute six every time. Thirty seconds, tied to what they just said, then hand the ball straight back. "Short version — we take the check-call sequence you just described, the pickup confirm, the in-transit, the ETA, the delivered, off your coordinators and put the status into the load record automatically so nobody's retyping it into the portal. But whether that's worth anything to you depends on something I don't know yet: on a normal week, what percentage of your loads have automated location on them versus a coordinator typing a note?" If they push a second time, give a clean 60 seconds — no logos, no funding, no "400 brokerages" — then: "Can I go back to the thing you said about the small carriers declining the ping? That's the part I'm not clear on." Almost everyone lets you.
- 5
8:00–12:00 — Layer 3: cost, and then 'how do you know?'
Now you make it a number. Ask one at a time. "Roughly how many check calls does a coordinator make per load right now — pickup, in transit, ETA, delivered, plus the chasing?" "And how many loads is one coordinator carrying a day?" "So call it [X] loads at [Y] calls — how much of their day is that, honestly? Half?" Then the beat most reps skip: "How do you know? Is that coming out of the TMS activity log, or is that what your branch managers tell you?" If the answer is "that's what it feels like" — write it down. That's a finding. It means the problem is invisible above their head and you're going to have to help them build the case for the COO. Say so: "Okay, so nobody's actually measured it. That's going to matter when you take this to your COO, and we should fix it before then, not after." Second cost thread, margin side: "What's net revenue per load looking like on contract versus spot right now compared to where it was two years ago?" "And the ops cost to cover one — has that moved at all?" Three seconds of silence after the answer. Count it. Don't fill it.
- 6
12:00–16:00 — Layer 4: the stake. Whose number is this?
This is the layer that makes the deal move. Nobody buys because check calls are annoying. They buy because a name is attached to a number. "Who's feeling this most day to day — is it the coordinators, or is it your branch managers?" "Whose number does it show up in when a load goes dark and the shipper finds out from their own plant before you call them?" "What was the on-time delivery percentage in your last QBR with your biggest account? And when they pushed on it, could you defend it with tracking data, or was it your coordinator's note?" "When's that account up for rebid?" Then the one that gets the truth: "What have you told your COO you'd have fixed by when?" And if they're vague: "If this looks exactly the same twelve months from now, what's the conversation you're having with leadership about headcount per hundred loads?" Three seconds of silence. Every time.
- 7
Second thread if the first one runs dry — dark loads and quiet accessorial leakage
If the check-call thread closes early, open one of these. Don't open both. Tracking compliance: "You said the one-to-five-truck carriers on the hard lanes won't take the app. What percentage of your loads run on your top fifty carriers versus everybody else?" → "And what happens on a load that goes dark — who notices, and how long before the shipper does?" Detention and TONU: "Last time a carrier billed you detention for four hours at a receiver — did you fight it or eat it?" → "What did you have as arrival proof?" → "How often does that happen in a month, and does anybody own that number?" That last one is gold, because the honest answer is usually "nobody owns it," which means it's leaking a few hundred dollars at a time with no line item. Write their exact words down.
- 8
16:00–20:00 — Qualify the path (never recite BANT)
Weave it in as a consequence of what they just said. One at a time. "If you decided this was worth doing, what actually happens next in your world? Does it go to your CIO, or can brokerage ops make this call?" "Have you tried to fix this before? What happened?" — Then dig. The graveyard of the last failed project is your real competitor. If the answer is "we bought a tracking tool and the data never flowed back into McLeod so the coordinators stopped looking at it," you now know exactly what you have to prove and exactly what will kill you. "What's forcing the timeline — a rebid, headcount, a shipper scorecard, peak?" If nothing's forcing it, you have a nice conversation. "Is this a line item that already exists in the ops budget, or would it have to get created?" "And if you just keep running it the way you're running it — what does that look like in six months?" On the TMS specifically, get precise now, because you'll need it before the demo: "Which TMS, which version, and is your integration API or flat file today? Does a status update land inside the load record where the coordinator already works, or does it live somewhere else?"
- 9
20:00–23:00 — Targeted relevance: 90 seconds, only what they raised
No tour. No map demo. Two things, both theirs. "Two things from what you told me, and then I want to talk about next steps. One — you said your coordinators are at seven or eight check calls a load and tracking compliance sits around sixty percent. The part that matters for you isn't the ninety-eight percent number a vendor puts on a slide, it's what happens on the other forty percent. So the honest version is: ELD integration covers your fleets, the driver app covers the ones who'll take it, and on the rest it's an automated voice call to the driver's cell that logs a location and a timestamp into the load record without a coordinator dialing. That last bucket is the one everybody skips in the pitch and it's the one you actually asked about. Two — you said you ate detention twice last month because you had no timestamped arrival. Every one of those pings writes an arrival and departure stamp against the load, which is what you'd need to hold the line with the receiver. That's it. I'm not going to walk you through screens today."
- 10
The playback (do this before you close, in their words)
"Let me make sure I've got it before we book anything. Coordinators are carrying about twenty-five loads a day and burning three-plus hours on check calls, and your words were 'nobody's building lanes while that's happening.' The reason it happens is the small carriers on your hard lanes decline the ping, so you're at roughly sixty percent tracking compliance and the forty percent that goes dark is the freight your top shipper cares about most. Last QBR your on-time delivery number was ninety-one and you couldn't defend it with anything but a typed note. And that account — forty loads a week — rebids in March. Did I miss anything, or get anything wrong?" The "or get anything wrong" is where the last hidden thing falls out. Wait for it.
- 11
23:00–25:00 — Close a specific, dated next step
Never "I'll send some information." That's a no with a smile on it. "Based on what you've described, the useful next thing is forty-five minutes with you and [the ops lead they named] — and if your CIO owns the McLeod integration, him too — where I show you exactly how a dark load on a one-truck carrier gets a timestamped location without your coordinator dialing. Not the general tour. Two things I'd ask you to bring: one week of load count by carrier, and the on-time number from that last QBR deck. That way we're arguing about your data, not my slide. I've got Tuesday at 2 or Thursday at 9. Which one?" Send the invite while you're still on the phone. Confirm out loud: who's on it, what you'll show, what they're pulling.
- 12
What goes in the CRM
Their words. Not your summary of their words. Good: "Coordinators at 25 loads/day, 7-8 check calls each. 'Half my floor is on the phone and nobody's calling carriers.' Tracking compliance ~60%, dark loads concentrated on 1-5 truck carriers running the Laredo lanes. QBR OTD 91%, couldn't defend it — 'the number came off a coordinator's note.' Top account 40 loads/wk, rebids March. Bought Trucker Tools two years ago, data never flowed into McLeod, coordinators stopped using it — that's the objection I have to beat." Bad: "Prospect has visibility challenges and tracking compliance issues." The first version writes your follow-up email, your business case for the COO, and your demo agenda. The second version writes nothing.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Thanks for the time — I know it's the second week of produce season. When we talked Thursday you said your coordinators are on the phone half the day and nobody's building lanes. That's what I want to dig into. I'm going to ask questions for about fifteen minutes and I'm not going to show you anything — I'd rather tell you this isn't a fit than burn a demo slot. Still good for 25?
Buyer
Twenty-five, yeah. I'll be straight with you though — you're the fourth visibility company in my calendar this year. Everybody's got a map. So if that's where this is going, we can save each other the time.
Rep
That's fair, and most of them are selling a map. So let me ask you what I'd ask them: today, how many check calls is one of your coordinators making per load?
Buyer
Depends. Six on a good one. Ten if it's a reefer going into a receiver that doesn't answer their phone. Pickup confirm, in transit, morning ETA, delivered, plus the four times you call a dispatcher who tells you 'he's rolling' and won't give you a city.
Rep
And how many loads is that coordinator carrying in a day?
Buyer
Twenty-five, twenty-eight. That's the whole problem in one sentence, isn't it. Look — what do you guys actually do? Give me the thirty seconds.
Rep
Thirty seconds: we take that sequence — pickup confirm, in transit, ETA, delivered — off the coordinator and write the status into the load record so nobody retypes it into the shipper portal. Whether that's worth anything to you depends on one thing I don't know yet. On a normal week, what percentage of your loads have an automated location on them versus a coordinator's typed note?
Buyer
Fifty-eight percent last month. And before you tell me you'll get it to ninety-eight — you won't. The guys covering my Laredo and my Fresno lanes are one and two truck operations. They decline the ping. They turn the app off after pickup. And I am not losing that capacity in July to win a visibility argument.
Rep
I'm not going to argue capacity versus visibility with you, you'd win. I want to understand the forty-two percent. Walk me through the last load that went dark on you. What actually happened?
Buyer
Two weeks ago. Dry van, Fresno to a DC in Dallas. Carrier picked, app went quiet, coordinator called dispatch twice, got 'he's rolling.' Truck showed up eleven hours late. First we heard about it was the shipper's transportation manager calling my branch manager, because his plant told him. That's the part that kills you — not the late load. The fact that they told us.
Rep
How often does that version happen — where they find out before you do?
Buyer
Couple times a month. Maybe more, honestly, I only hear about the ones that reach me.
Rep
How do you know it's a couple a month? Is that coming out of the TMS, or is that what filters up from the branches?
Buyer
…It's what filters up. We don't have a clean number on it. Which I know is a bad answer.
Rep
It's an honest answer, and it matters for a reason we should talk about. When you sat in the QBR with that Fresno shipper, what was the on-time delivery number on the slide?
Buyer
Ninety-one. They had us at eighty-seven. And I couldn't fight it, because my proof is a coordinator typing 'delivered 1400' into the load record and theirs is a gate log. You can't win that argument with a note.
Rep
So what happens with that account?
Buyer
They rebid in March. Forty loads a week with us. If I show up at that table with another note-based on-time number, I don't think we keep all of it. Our net revenue per load on that contract is already down near a hundred and eighty from three-forty a couple years ago, so losing volume there isn't something I can just backfill on spot.
Rep
Let me play that back and you tell me what I've got wrong. Coordinators at twenty-five loads a day, six to ten check calls each. Tracking compliance is fifty-eight percent and the forty-two that goes dark is your Laredo and Fresno small-carrier freight — which is exactly the freight your Fresno account cares about. QBR came in at ninety-one your side, eighty-seven theirs, and you couldn't defend it. Forty loads a week, rebid in March, at a hundred and eighty a load. Miss anything?
Buyer
No, that's it. And I'll tell you the other thing, since you asked properly — we bought a tracking product two years ago. The data never flowed back into McLeod. Coordinators had to open a second tab, so within a quarter they just stopped, and I paid for it for eighteen months. That's the reason I'm hard on this. Not the map.
Rep
That's the most useful thing you've said, because that's the thing I have to beat — not the competition, that. So next step: forty-five minutes with you, whoever runs your Fresno branch, and whoever owns the McLeod integration on your side. I show one thing — a dark load on a one-truck carrier getting a timestamped location into the load record with no second tab. Bring one week of load count by carrier and the on-time number from that QBR deck. Tuesday at 2, or Thursday at 9?
Buyer
Thursday. Bring the integration person on your side too, because if the answer is flat file at midnight, we're done in ten minutes.
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “Every freight tech company that walks in here promises visibility. I've heard this exact pitch four times this year.” | Agree, then get specific fast. "You're right, and most of them are selling a map. Ask them the two questions I'd ask: how many check calls per load are your coordinators making today, and how many loads went dark last month. I only move one of those two numbers and I'd rather tell you which." Then quote a before/after from a brokerage with a comparable carrier mix and load count. Vague visibility loses to a number every time. |
| “We spent 18 months fighting to get people onto the TMS and half of them still work out of spreadsheets. Another tool isn't going to stick.” | Say it out loud before they do: "If this is a second place your coordinators have to look, you're right and it'll die in a quarter — same as the last one." Then get concrete. Which TMS, which version, API or flat file, and does the status write into the load record where the coordinator already is. Ask what the last tool did that got people to abandon it. That answer is your demo agenda. |
| “Our carriers won't accept tracking. The one- and two-truck guys decline the ping and I'm not losing capacity over it in peak.” | Never let it become capacity versus visibility — you lose that. Talk multi-source: ELD integration for the fleets that have it, driver app for the ones who'll take it, and an automated call to the driver's cell that logs a location and timestamp for everyone else. Quote a realistic compliance rate for their carrier mix, not 98%. Then ask what percentage of loads run on their top 50 carriers — usually most of them, and those onboard first. |
| “What's this going to cost me per load? Margin per load is already down to nothing.” | Put it against ops cost they're already paying, not against savings. "Your coordinator's on 25 loads a day and three hours of that is the phone. I'd rather price this in loads per coordinator per day than in dollars." Then reframe the risk: "You said Fresno is 40 loads a week at $180. What does one rebid loss look like against a per-load fee?" One account beats one line item in every CFO conversation. |
| “Our shippers aren't asking for this. They're fine with the emails we send.” | "They're not asking you — they're asking whoever's bidding against you." Then ask a real question: what did the last three RFPs require for visibility and EDI 214 status messaging, and was it scored? Most enterprise shippers now score it in the bid. Position it as bid eligibility for the March rebid, not as a service upgrade nobody requested. |
| “Send me something and I'll look at it. We're heads-down on peak.” | Use the calendar, don't fight it. "Peak is the week I want you looking at check calls per load — January numbers make everybody look fine." Then shrink the ask: 20 minutes with them plus one branch manager, and ask them to pull one week of load volume by carrier beforehand so the conversation is about their data. Book the date on the call or you don't have one. |
| “We're mid-cycle with a provider. Come back at renewal.” | Two questions before you let go: what's the renewal date, and what does the current provider not do. It's almost always carrier onboarding, the data not flowing back into the TMS, or a shipper-facing portal nobody logs into. Then book the follow-up 60 days before renewal — not after — and show up with evidence against that one specific gap, not a general pitch. |
Questions reps ask about this call
- What are the best opening discovery call questions for a freight brokerage or 3PL prospect?
Open one thread, not five. "Walk me through how a load gets covered and tracked today — from tender hitting the board to POD, the way it actually happens." Then follow up three times on whatever they say before you change subject. Strong second-layer questions in this industry: "Is the pickup confirm a call to the driver or to dispatch?", "Does that update land in the load record in your TMS or does someone retype it into the shipper portal?", and "Walk me through the last load that went dark." Avoid stacking questions — a Director of Brokerage Operations will answer the easiest one and skip the rest.
- Which metrics should I try to quantify on a freight / 3PL discovery call?
Aim to leave with three of these six in the buyer's own words: check calls per load, loads covered per coordinator per day, tracking compliance rate, net revenue per load on spot versus contract, on-time pickup and delivery percentage from their last shipper QBR, and carrier fall-off rate. After every number, ask "how do you know?" If it comes out of the TMS, great. If it's what branch managers tell them, that's still a finding — the problem is invisible above their head and you'll have to help them build the case before the COO ever sees it.
- How do I handle a Director of Carrier Sales who says their small carriers won't accept tracking?
Don't argue. In July, capacity beats visibility every time and you will lose that exchange. Move to multi-source: ELD integration for the fleets that have it, a driver app for the carriers who'll take it, and an automated call to the driver's cell for everyone else. Then ask a real question — what percentage of loads run on their top 50 carriers? It's usually the majority, and those are the easy onboards. Quote a compliance number that's credible for a small-carrier mix. Promising 98% to someone sitting at 58% ends the call.
- The prospect asks 'so what do you guys actually do?' at minute six. What do I say?
Thirty seconds, tied to something they already told you, then hand the ball back with a question. For example: "We take the check-call sequence you described off your coordinators and write the status into the load record so nobody retypes it into the portal. Whether that's worth anything depends on one thing — what percentage of your loads have automated location today versus a typed note?" If they push a second time, give a clean 60 seconds with no logos or funding history, then say "can I go back to the thing about the carriers declining the ping?" Almost everyone lets you.
- Who should be on the call, and who else needs to be in the room before this moves?
Discovery usually starts with a Director of Brokerage Operations, a Branch Manager, or a VP of Operations. Before you close, ask "if you decided this was worth doing, what happens next in your world — does this go to your CIO or can brokerage ops make the call?" In most brokerages the CIO or Director of Logistics Technology owns the TMS integration and can veto on architecture alone, and the COO owns the net revenue per head conversation. Get both named on the call and invited to the next one, or you'll spend a month relaying answers.
- What's a good next step to close a 25-minute freight discovery call with?
Prescribe, don't offer. Something like: "Forty-five minutes with you, your Fresno branch manager, and whoever owns the McLeod integration — I show one thing, a dark load on a one-truck carrier getting a timestamped location into the load record with no second tab. Bring one week of load count by carrier and the on-time number from your last QBR." Then give two dated options and send the invite while you're still on the phone. "I'll follow up with some times" is a no with a smile on it.