Freight / 3PL · Demo Call
The Freight / 3PL Product Demo Script: Running a Demo for a Room Looking for Where It Breaks
The person who took this demo has already heard your pitch. They're a Director of Brokerage Operations or a VP of Operations who runs a floor of coordinators making six to ten check calls a load, and they said yes to seeing it because something in the first conversation landed — probably the number of hours their team spends on the phone chasing a dispatcher who says "he's rolling" and can't give a city. They are not on this call to learn what your product does. They are on it to find out where it breaks: whether it writes back into McLeod or whether it's another tab, what happens to the 1-5 truck carriers who decline the ping, and who on their team owns it after your implementation lead disappears.
That means the demo you rehearsed is a resource, not a script. Every interruption in a freight demo is either a buying question or a disqualification test — "what happens on a drop trailer where the driver's gone before we get the ping?" is not a derailment, it's the whole call. If you run the standard tour — here's the dashboard, here's the map with the little trucks on it — you will hear typing, and a Director of Carrier Sales who has sat through four visibility pitches this year will be answering email while you narrate. Nobody will say no. The deal will just go quiet.
This playbook gives you the pre-call work, the three workflow loops to run instead of a tour, cold answers on integration and failure modes, and the objections you will actually get from this room — carriers won't accept the app, we already bought a visibility tool and shelved it, come back after peak. Use their metrics out loud: check calls per load, tracking compliance rate, loads covered per coordinator per day, net revenue per load. Those are the numbers in their weekly deck, and a demo that moves one of them beats a demo that shows twelve features.
The demo call script
Say it in your own words. The structure is the part that matters.
- 1
Pre-call email: pin down the stack before you build anything
Send this 48 hours out, and don't run the demo until you have answers. "Looking forward to Thursday. So I don't waste twenty minutes showing you screens that don't apply to your setup — three quick things: 1. What TMS are you running, and which version? (McLeod LoadMaster, Aljex, MercuryGate, Turvo, Revenova, something homegrown?) Hosted or on-prem? 2. Are you already running any tracking — MacroPoint, Trucker Tools, project44, FourKites, direct ELD integrations — and roughly what percentage of loads get an automated location today? 3. Who's joining? If your TMS admin or IT lead is coming, I'll bring the architecture and port list so they're not sitting through a workflow demo. If you can pull one week of load volume before we talk — total loads, loads that went dark, and any detention you ate — I'll build the demo around that instead of my sample data." Why this matters: "they use McLeod" is not enough. McLeod LoadMaster 20.x on-prem with a custom PowerBroker integration is a completely different demo from a hosted Aljex instance out of the box.
- 2
Pre-call: figure out who's in the room and what each of them wants
Three people, three demos, one hour. Know which is which before you open your mouth. **Director of Brokerage Operations / VP of Operations** — invited you. Wants check calls per load down and loads covered per coordinator per day up. Show them the coordinator's morning. **Director of Carrier Sales** — protects capacity. Every question they ask is really "does this cost me carriers on the hard lanes?" Never make it visibility versus capacity in front of them. **CIO / Director of Logistics Technology** — wants to know what lands on their team and whether it survives the next TMS upgrade. Give them the integration method, the direction, the frequency, and what you don't touch. **COO** — net revenue per load, headcount per 100 loads, and the account they lost last year to service. Speak in loads-per-head, not features. **Branch Manager** — wants to know what changes for their eight coordinators on Monday morning and whether it adds a click. If you don't know who's dialing in, ask in the confirmation. Walking in blind and adjusting live is how you end up showing admin screens to a Director of Carrier Sales.
- 3
Pre-call: build the three screens, decide what you will not show
Load their world into the demo environment. Their lane names — Laredo to Memphis, not Origin A to Destination B. Their shipper names if they gave them. Reefer loads if they run food, flatbed if they run steel. If they won't share data, at minimum use real lanes, real equipment types, and load numbers that look like load numbers. Pre-build exactly the screens tied to what they complained about last call: - If they said "my coordinators make eight calls a load" — build the check-call automation view and the TMS write-back. - If they said "we can't defend on-time delivery percentage in the QBR" — build the shipper-facing status trail with timestamps. - If they said "we ate $40K in detention last year" — build the geofence arrival/departure timestamp record. Then write down what you are not showing. Reporting suite, admin console, user provisioning, the analytics module, the roadmap. Every feature you demo that they didn't ask for is one more thing they have to evaluate, question, and price in their head.
- 4
Opening: 90 seconds, set the contract not the agenda
"Before I share anything — last time you told me your coordinators are running six to ten touches per load, that tracking compliance sits somewhere around 60%, and the loads that go dark are almost always the ones on your top three accounts. And you said you lost a shipper last spring after three late deliveries where nobody called them first. That still the picture?" [Let them answer. Actually let them.] "Anything shifted since we spoke? New volume, budget moved, anyone new in the seat?" "Two things about how I'd like to run this. First — please interrupt me. If you're thinking 'that won't work with our carrier base,' say it right then. That's the useful part of this call, not the part after. Second — what's the one thing that, if this can't do it, we're done and you can have the other forty minutes back?" That last question sets your running order. If they say "if it doesn't write back into McLeod it's dead," you open with the write-back, not with the map.
- 5
Loop 1 — The 7am check-call round (Problem → Screen → Consequence → Check)
**Problem:** "Let's start at 6:45 Monday. Your coordinator's got 25 loads on the board. Fourteen pick up today. She starts dialing — driver doesn't answer, dispatch says he's rolling, she calls back at 8:15, gets him, types 'in transit near Little Rock' into the load record, then goes and pastes the same thing into the shipper's portal. That's roughly how it goes?" **Screen:** "Here's the same board. These eleven have an automated position — six off the ELD integration, five off the driver app. She's not calling any of them. These three are dark. That's where the phone gets picked up. And the automated ones — watch the load record here, this is your McLeod screen, not mine. The location, the arrival timestamp, the status all land in the load. She doesn't retype anything." **Consequence:** "So the check-call round goes from fourteen calls to three. She's not choosing which loads to chase, the board is choosing for her. And whatever your loads-per-coordinator-per-day number is today, the three hours she gets back is where that number moves." **Check:** "Is that how your coordinators actually work in the morning, or am I making that up? And who does the shipper portal pasting — is that her too, or does that sit with a different desk?"
- 6
Loop 2 — The load that goes dark (this is the loop that wins or loses the room)
Do not skip this and do not oversell it. The Director of Carrier Sales is waiting for you to claim 98%. **Problem:** "Your hard lanes run on small carriers. One to five trucks. They decline the app, or they accept it at pickup and kill location sharing an hour later. And those are the loads on the accounts that matter." **Screen:** "So here's the exception queue. This isn't a map — a map tells you what you already know. This is the list of loads with no position in the last two hours, ranked by which shipper it's for and how close it is to the delivery appointment. This one's a reefer into a DC with a 0600 appointment and nothing since 9pm. That's the call your coordinator should be making, and it's the only one on the list she has to make personally." **Consequence:** "You're not going to get to 100% tracking compliance and I'm not going to tell you that you will. What changes is that the gap is visible before the shipper finds it, not after. Right now the dark load and the tracked load look the same on the board at 6am." **Check:** "What's your tracking compliance rate today, honestly? And what percentage of your loads run on your top fifty carriers?" — that second question is the one that opens the onboarding conversation.
- 7
Loop 3 — Detention, TONU and the timestamp you can actually bill on
**Problem:** "Driver sits four hours at the receiver. Carrier bills you detention. You've got a coordinator's typed note saying 'arrived approx 10am' and the shipper's got their own gate log. You eat it. That's a few hundred dollars, nobody owns the line item, and it happens all month." **Screen:** "Here's the same load. Geofence arrival 09:52, departure 14:18. That's a system timestamp, not a note. It exports as a PDF trail you can attach to the invoice, and it's the same record whether you're arguing with the carrier or the shipper." **Consequence:** "Two things move. You stop absorbing detention you didn't cause, and your carriers stop fighting you on the ones you do pay — which matters for your fall-off rate on the lanes where you're already thin on capacity." **Check:** "Who currently decides whether you fight a detention bill or just pay it? Is that the coordinator or does it escalate?"
- 8
The integration answer — say the method, the direction, the frequency, and what you don't touch
Never say "we integrate with everything." Say this: "On McLeod LoadMaster we connect over their API. We read the load — stops, appointment windows, carrier, equipment — every fifteen minutes, and we write back three things: current position, arrival and departure timestamps at each stop, and status. Those land in the load record, not in a separate screen. Your coordinator never opens our UI unless she's working the exception queue. For shipper-facing status, we generate the EDI 214 off the same events. If you're already sending 214s through your VAN, we hand you the file and nothing else changes on that side. What we don't touch: we don't write rates, we don't write to your accounting, we don't create or modify loads. We read and we append status. If we go away tomorrow your TMS is exactly as it was. If you're on-prem on an older version, that's a different conversation — you'd need the gateway sitting inside your network, that's an afternoon with your sysadmin, and I'll get your IT lead the port list and the security doc before we go any further." That last paragraph — naming the constraint before they find it — buys you more credibility than any capability claim.
- 9
Who owns it once you're gone
"Ongoing, this is about two hours a month and it's not IT work. It's adding coordinators, changing which shippers get which alert thresholds, and adjusting geofence radius on a couple of receivers where the yard is big. Your ops coordinator or your TMS admin does it — whoever currently maintains your carrier packet templates is the right profile. The part that is real work is carrier onboarding, and I'm not going to soft-pedal it. Your top fifty carriers need to be connected — ELD integration where they've got it, app invite where they don't. That's a few weeks of somebody in carrier sales making the ask on the loads they're already tendering. It works best when it's a condition of the load tender, not a separate email campaign. On my side: [name] runs implementation, [name] is your CSM after go-live, and they overlap for the first month. If your admin leaves, the handover is about a two-hour session and I'll give you the doc."
- 10
What happens when it breaks — failure mode, not uptime percentage
"If we go down: your TMS keeps running, your loads keep moving, your coordinators keep working. What you lose is automated position updates and the exception queue for that window. When we come back, we backfill the positions we captured — the ELD feeds queue, so you don't lose the breadcrumb history, you lose the real-time view of it. What that means practically is your team falls back to the phone for a few hours, which is what they do today. It's a degradation, not a stoppage. Support: P1 is a phone number, someone answers, 24/7 — because freight doesn't stop at 6pm on Friday. P3 is email and it's next business day. I'm not going to pretend it's anything else. Escalation goes CSM, then [role], then [role]. Our last incident of any size was [date] — [one honest sentence about what happened and how long]. I'd rather tell you that now than have you find it later."
- 11
Time to value — three dates, not one
"Three dates, and I'd rather you hold me to all three than one vague go-live. **Live** — the integration is up and positions are landing in the load record for your connected carriers. That's typically [X] weeks from kickoff. **Useful** — one branch stops making the routine in-transit check calls. That's when your check-calls-per-load number actually moves. It happens once you've got your top carriers onboarded, so it trails go-live by a few weeks. **Fully rolled out** — all branches, all coordinators, the 214 feed running to your enterprise shippers. What I need from you: a load export for the lane and volume baseline, your user list, your top-fifty carrier list with MC numbers, and roughly four hours of your TMS admin's time during integration. Coordinator training is twenty minutes because the workflow is in a screen they already use. And we wouldn't cut over during peak. You said your volume spikes [when] — that's not the week to change anything."
- 12
Handling 'will it handle X' — the three honest answers
Slow down and get the specific first. "Will it handle drop trailers?" is unanswerable. "Tell me the actual case — is the tractor dropping and leaving, and you need dwell on the trailer? Or is it a live load where you need the driver's position?" Then one of three: **Yes, and here it is.** Go show it live. This is the strongest thing that happens on a demo. **Yes, but not how you'd expect.** "You don't get that in the load view — you get it in the exception queue, and it's two extra clicks. It's not elegant." Buyers forgive ugly. They do not forgive discovering ugly in month three. **No.** "No. We don't do that today and it's not on the roadmap this year." Then: "How often does that come up — is that every day or is that a quarter-end thing?" Half the time the deal-breaker is an edge case they raised because it popped into their head. Never say "we can build that." To a room that just spent eighteen months on a TMS rollout, that sentence sounds exactly like the last promise that slipped. And write it down out loud: "Let me note that — dwell reporting on drop trailers at customer-owned yards. I'll come back to you Thursday with a straight answer." Then do it Thursday.
- 13
Recovering the room when it goes quiet
You'll hear it: shorter answers, "mm-hm," a half-second delay, typing, "yeah no that makes sense" said flat. Stop. Do not push through and do not add features. In order of preference: "I've been talking a while — is this the part you care about, or should I jump somewhere else?" "Let me stop the tour. What's the thing you're worried about that I haven't touched yet?" "Do you want to drive? Tell me what to click." — almost nobody offers this and it works. "I think I'm showing you the wrong things. Can I stop, spend ten minutes understanding what actually matters on your floor, and come back next week with a demo built for that?" Losing twenty minutes of a demo to save the deal is a good trade.
- 14
Closing — gaps out loud, temperature, next date on the call
"Let me summarise where I think we are, including the parts that didn't land. Three things worked for you: the exception queue instead of a map, the write-back into the load record so it's not another screen, and the timestamped detention trail. Two open: whether your on-prem version supports the API without the gateway, and dwell on drop trailers at the customer yards. I'll have both answered by Thursday, in writing. Where does this sit for you now — worth pursuing, or is there something you've already heard that rules it out?" [Let them say no. A clean no beats four weeks of chasing.] "Who else needs to see this before it's real? If your CIO wants it, I'd run twenty minutes of architecture and security only — no workflow, no dashboard. And if your Director of Carrier Sales wants to pressure-test the onboarding, I'd do a separate session on just that." "Let's put the next one in now while we're both here — what does the week of the [date] look like?" Within 24 hours: the two open answers, the four screens that mattered (not the recording of the whole hour), the security doc if IT was on, and a short list of what you need from them. Nothing generic.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Before I share anything — last time you said your coordinators are running six to ten touches per load and tracking compliance sits around 60%. Still the picture, or has anything shifted?
Buyer
It's 61% as of last month and honestly that's flattered — a chunk of that is a ping at pickup and then nothing. And I'll tell you now, I've sat through this pitch four times this year. Everybody shows me a map with little trucks on it.
Rep
Then I'll skip the map entirely. Two questions instead. What's your check-calls-per-load number today, if you've measured it? And what's the one thing that, if this can't do it, we're done and you get your forty minutes back?
Buyer
We haven't measured it, which is part of the problem. The deal-breaker is McLeod. We spent eighteen months getting this floor onto LoadMaster and half of them still work out of Outlook. If this is another tab, my coordinators will just not use it and I'll be paying for shelfware. We already did that with a visibility tool two years ago.
Rep
Then let's start there and if it fails we stop. This is a LoadMaster load record — your screen, not mine. The position, the arrival timestamp at stop one, the status: all written back into the load. My interface exists for one thing only, and I'll show you that second. What version are you on, and is it hosted or on-prem?
Buyer
On-prem, and we're a version behind because the last upgrade broke two of our custom reports. So before you go further — does that mean my IT guy is installing something? Because I've got one IT guy and he's not doing this.
Rep
On-prem, yes — there's a gateway that sits inside your network. It's an afternoon with your sysadmin, once. I'll send him the port list and the security doc before we talk again so he can tell you if that's a problem rather than me telling you it isn't. On the version behind — I need to confirm the API surface on that release. I'm writing it down: API compatibility on your LoadMaster version. Straight answer Thursday.
Buyer
Fine. Second thing. My hard lanes — Laredo, west Texas, anything reefer out of the valley — those run on one and two truck carriers. They decline the app. My Director of Carrier Sales will walk out of this meeting if I tell her she's losing capacity over a tracking mandate. So what's your compliance number, really?
Rep
I'm not going to give you 98% because you'd be right not to believe it. Here's what I'd actually expect with your carrier mix: the fleets with ELDs connect once and stay connected, the mid-size guys take the app, and a chunk of your one-truck operators never will. What percentage of your total loads run on your top fifty carriers?
Buyer
Probably 70%. Maybe a bit more on contract volume.
Rep
Then that's the onboarding project, and it's a carrier sales conversation, not a technology one — connected as a condition of the tender on loads you're already giving them. The other 30% is where this screen matters. This isn't a map, it's the exception queue: loads with no position in two hours, ranked by shipper and by how close the appointment is. This one's a reefer into a DC with an 0600 appointment, nothing since 9pm. That's the only call your coordinator has to make personally.
Buyer
Okay. That's actually different from what the last three showed me. But what happens when you go down? Because when our last tool went down nobody told us, and we found out because a shipper called us about a load we thought was tracking.
Rep
If we go down, your TMS keeps running, loads keep moving, and your team falls back to the phone — which is what they do today anyway. You lose the real-time exception queue for that window. The ELD feeds queue on our side, so when we're back we backfill the breadcrumb history, you don't lose the timestamps. And on notification: P1 is a phone number, someone answers, any hour. I'd rather tell you our last incident and what it looked like than quote you an uptime figure.
Buyer
Look, all of this sounds reasonable but we're three weeks out from peak. My coordinators are covering 25 loads a day each and I'm not putting anything new in front of them in October.
Rep
Agreed — I wouldn't cut over during peak either, and I'd say the same thing if you were mid-close. But peak is exactly the week I'd want you counting. Would you have one branch manager log check calls on a single day during peak — just tally the touches per load? That's the number we'd be measuring against in January, and you'd have it from your worst week, not your easiest. Meanwhile I'll get you the API answer and the port list. Can we put twenty minutes in the week of the 12th with your IT guy, architecture only?
Buyer
Send me the security doc first. If he tears it apart there's no point in the meeting.
Rep
That's fair and it's the right order. Doc goes over today with the port list and the API question flagged. I'll hold two slots the week of the 12th and you tell me by Friday if he's happy — and if he isn't, tell me that too and I won't chase you through peak.
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.” | "You probably have, and most of them showed you a map. Let me ask you what they should have asked you: how many check calls per load are your coordinators making today, and how many loads went dark last month? If you don't know, that's the first thing worth fixing regardless of whether you buy from me. I'll show you exactly two numbers I move and what those looked like before and after at a brokerage your size — and if it's not those numbers, we're wasting each other's time." Vague visibility loses to a specific number every single time. |
| “We fought for eighteen months to get people onto our TMS and half of them still aren't fully on it. Another tool isn't going to stick.” | Agree out loud, then reframe: "You're right, and if this is another tab I'd tell you not to buy it. This should be fewer screens, not more." Then get concrete immediately — which TMS, which version, hosted or on-prem, API or flat file, and does the update land in the load record where the coordinator already works. Show the write-back in their TMS screen before you show anything in yours. If your product genuinely creates a second place to look, say so on the call. They'll find out anyway and you'd rather lose in week one than in month three. |
| “My carriers won't accept tracking. The one and two truck guys decline the ping and I'm not losing capacity over it.” | Never let this become capacity versus visibility — you lose that argument in front of a Director of Carrier Sales. "I'm not going to tell you 98% compliance, because with your carrier mix that's not true." Talk multi-source: ELD integration for the fleets that have it, driver app for the ones who'll take it, and be honest that some won't. Then ask: "What percentage of your loads run on your top fifty carriers?" It's usually most of them, and those are a carrier sales onboarding project — connected as a condition of the tender, not a separate campaign. |
| “What's this going to cost me per load? My margin per load is already thin.” | Price it against ops cost they already pay, not as a new line item. "If a coordinator covers 25 loads a day and three hours of her day is the phone, the question isn't dollars saved, it's what your loads-covered-per-coordinator number looks like when those three hours come back — and whether that changes your headcount per hundred loads." Then go the other way: "Tell me about the last account you lost to service. One shipper doing 40 loads a week at a couple hundred in margin is a several-hundred-thousand-dollar problem." That reframes a per-load fee fast. |
| “Our shippers aren't asking for this. They're happy with the emails we send.” | "They're not asking you — they're asking the broker bidding against you." Then get specific: "What did the last three RFPs require on visibility and EDI 214 status messaging? Was there a scored section?" Most enterprise shippers now score automated tracking in the bid packet. Position it as bid eligibility, not as a service upgrade — the VP of Sales on the shipper side cares about which RFPs they can respond to, not about coordinator hours. |
| “Send me something and I'll look at it. We're heads-down on peak right now.” | Don't fight the calendar, use it. "Peak is exactly when your coordinators are drowning — that's the week I'd want you measuring check calls per load, not January." Then make a small ask instead of a big one: have one branch manager tally touches per load for a single day during peak. Offer twenty minutes with them plus one ops lead after the spike, and put the date in the calendar on this call. Never leave with 'I'll follow up in a few weeks.' |
| “We're mid-cycle with a provider. Come back at renewal.” | "What's the renewal date, and what would have to be true for you to actually switch?" Then find the gap — with visibility providers it's usually one of three: carrier onboarding stalled, the data never flowed back into the TMS so coordinators still work off two screens, or the shipper-facing portal is bad and the QBR deck still gets built by hand. Book the follow-up 60 days before renewal, not after, and come back with evidence against that specific gap rather than a general pitch. |
| “We bought a visibility tool two years ago and it's shelfware. Why is this different?” | Ask what killed it before you answer — it's almost always one of three things and you need to know which. "Was it that carriers never got onboarded, that it never wrote back into the TMS, or that nobody owned it after the implementation team left?" Then answer only that one, concretely, and name who owns it this time on both sides. If the honest answer is that the same failure mode exists in your product, say it. A room that's already been burned will trust the vendor who names the risk over the one who claims immunity from it. |
Questions reps ask about this call
- How long should a freight or 3PL product demo actually run?
Plan for forty minutes of content in a sixty-minute slot and expect to use every spare minute on interruptions. The rule that matters more than length: three workflows covered completely beats twelve covered partially. For a brokerage audience the three are almost always the morning check-call round, the load that goes dark, and the timestamp trail for detention and TONU. If you're more than ninety seconds into uninterrupted talking, you've drifted into tour mode and you're losing the room.
- What should I show a Director of Carrier Sales versus a CIO on the same call?
Different demos, same hour. The Director of Carrier Sales is protecting capacity on the hard lanes and every question they ask really means 'does this cost me small carriers?' Show them the onboarding path — ELD integration for fleets that have it, app for the ones that'll take it, and an honest answer about the rest. The CIO or Director of Logistics Technology wants the integration method, the direction and frequency of the data flow, what you don't write to, and who gets paged. If both are on, offer the CIO a separate twenty-minute architecture-and-security session so you're not making the ops people sit through port lists.
- The buyer won't share load data before the demo. Should I still use sample data?
Use their vocabulary even if you can't use their records. Real lane pairs, real equipment types — reefer, dry van, flatbed — appointment windows, load numbers formatted like load numbers, receiver names that sound like receivers. Never demo with ACME Corp and Test Customer 1 to someone who told you last call that their pain is Laredo reefer capacity. Generic sample data reads as 'I didn't prepare,' and in a room that's already sat through four visibility pitches this year, that's enough to lose them in the first five minutes.
- What do I do when they interrupt mid-demo to say their carriers will never accept tracking?
Stop the demo and answer it — it's the most important thing said on the call. Do not claim a compliance rate you can't defend, and never frame it as capacity versus visibility. Say what's actually true about their carrier mix, then ask what percentage of their loads run on their top fifty carriers. It's usually most of them, which turns a philosophical fight into a finite onboarding project owned by carrier sales. Then show the exception queue, because the honest value is that the dark loads become visible as dark, not that they stop existing.
- How do I handle a brokerage that already bought a visibility tool and shelved it?
Diagnose before you differentiate. Ask which of three things killed it: carriers never got onboarded, the data never wrote back into the TMS so coordinators worked two screens, or nobody owned it after implementation. Answer only that one, and name the owner on both sides this time. If your product has the same weakness, say so out loud on the demo. Buyers who've been burned trust a vendor who names the risk far more than one who claims it can't happen to them.
- What should I send after a freight demo, and when?
Within 24 hours, and nothing generic. Send the answers to the two or three open items you wrote down on the call — API compatibility on their TMS version, dwell on drop trailers, whatever it was — plus the four screens that mattered rather than the full recording, plus the security and architecture doc if IT was on. Include a short list of what you need from them: load export for the baseline, user list, top-fifty carrier list. And the next meeting should already be in the calendar before you hung up. 'I'll follow up next week' is where freight demos go to die.