Freight / 3PL · Upsell Call
The Upsell Script for Freight / 3PL Customers: Turning a Check-In Into an Expansion Without Burning the Account
Your customer is a brokerage running roughly 4,200 loads a month out of four branches. They bought your track-and-trace product fourteen months ago, rolled it into Columbus and Dallas, and never got Atlanta or Laredo onboarded because the Branch Managers there were mid-peak and quietly refused to add a click. Check calls per load in Columbus went from 7.4 to 3.1. Tracking compliance went from 54% to 79%. Nobody in that building has said thank you, because nobody in freight says thank you — they say "what about Laredo."
Today you're calling the Director of Brokerage Operations for what she thinks is a quarterly check-in, and you're going to ask for more money. She has three defenses loaded before she picks up: the freight tech budget got eaten by the TMS integration in Q2, her coordinators are heading into produce season and can't absorb another rollout, and somewhere in the back of her mind she suspects she's paying for 62 seats and using 38. That third one is the dangerous one. If she says it before you do, you spend the rest of the call defending your own product instead of selling the next piece of it.
This playbook is built for that exact call. The whole thing is won in the prep: you open with her numbers — her check calls per load, her tracking compliance rate, her detention write-offs off the AR aging she shared in the last QBR — and you name the gap before you name the module. Lead with "we launched an accessorial product" and you get a polite ten minutes and a request for a one-pager. Lead with "you wrote off $23,800 in detention out of Columbus last quarter and I think I know why" and you get a real conversation.
The upsell call script
Say it in your own words. The structure is the part that matters.
- 1
0. Pre-Call Usage Audit — do not dial without these seven lines
Fill these in from your own systems before you touch the phone. If any line is blank, you're not ready. 1. **Adoption by branch.** "Columbus and Dallas live. Atlanta and Laredo never onboarded — 62 licensed seats, 38 weekly active." Name the dark corners by branch, not as a percentage. 2. **Depth.** Which parts do they actually use? "They're live on driver-app tracking and ELD integration. They have never once pulled the dwell report or turned on EDI 214 auto-emit." 3. **The outcome that's theirs, not your benchmark.** Check calls per load in Columbus: 7.4 down to 3.1. Loads covered per coordinator per day: 19 to 26. Tracking compliance: 54% to 79%. On-time delivery on tracked loads: 91.4% to 96.1%. 4. **The leak you're going to sell against.** From their own AR aging or QBR deck: "$41,300 in detention, TONU and layover written off across the two live branches last quarter. $23,800 of it Columbus." 5. **Commercials.** $96K annual, renewal March 1, signed by the VP of Operations — who last logged in six weeks ago. 8% discount on the original. Co-term implications if you add anything now. 6. **Support history.** One escalation three weeks ago: pings dropping on a reefer lane out of McAllen. Status: closed, root cause was a carrier's ELD provider. Know this before she brings it up. 7. **Champion status.** Is the Director of Brokerage Operations still in the seat? Did the VP of Ops get a COO title? Has a Director of Carrier Sales been hired since the original deal who now owns carrier onboarding? **The test:** could you say one thing about their account they'd be mildly surprised you knew? "Your Dallas team is still logging 4.4 check calls a load while Columbus is at 3.1" passes. "How's everyone finding the platform?" fails, and it fails in the specific way that turns you from partner into vendor.
- 2
1. The First 30 Seconds — frame it, don't ambush
"Thanks for the twenty. Two things I want to get through. First — I pulled your load-level usage for the last two quarters and there's a split between Columbus and Dallas I want you to sanity-check for me, because I think it means something about how you staffed the two desks. Second, depending on what you tell me, there's a piece of our platform I think fits a hole you've got, and if it turns out it doesn't fit, I'll say so and we'll stop. Fair?" That pre-commitment to walking away does more for you than five minutes of rapport. And it stops her from spending the call waiting for the pitch.
- 3
2. Anchor on the Result They Already Own — make her say it out loud
"When we kicked off, Columbus was at 7.4 check calls a load and coordinators were covering about 19 loads a day. Last month Columbus was at 3.1 check calls and 26 loads a day, and tracking compliance is sitting at 79% against 54% at signature. Does that match how it feels on the floor, or am I reading my own dashboard optimistically?" Then shut up. Her correction is worth more than your number. If she says "79% is soft, half of those are four-hour ELD pings, not real position updates" — write that down verbatim. That's the metric she defends internally, and it becomes line one of the business case she takes to the VP of Operations. **If she cannot confirm any result, stop selling.** "Then let's not talk about anything new today. Let's fix the fact that you're paying for something you can't put in a QBR deck." That's not a lost call. That's the only version of this call that protects a March 1 renewal.
- 4
3. Say the Underuse Out Loud Before She Does
"Here's the thing I'd push back on if I were sitting in your chair: you're paying for 62 seats and I've got 38 people in there weekly. Atlanta and Laredo never onboarded. Why on earth would you buy more before you've used what you've got? So let me tell you what I think those two branches are actually doing. They're not idle — Laredo covered about 850 loads last month and every one of those check calls happened, they just happened on a cell phone and got typed into the load notes afterward. That's not unused capacity, that's unrouted work. Now — the piece I want to talk about doesn't fix Atlanta and Laredo. Onboarding fixes Atlanta and Laredo, and that's a separate conversation I owe you either way. I want to be clean about which problem I'm solving." Reframe unused seats as unrouted work, then be honest about what the add-on does and doesn't touch. Conceding the onboarding gap buys you the right to sell the other thing.
- 5
4. Find the Seam — diagnostics that surface the gap
Do not name the module yet. Find where value leaks out after your product's job ends. - "When a driver sits four hours at a receiver — what happens next? Who touches that?" - "Your coordinator's got the arrival timestamp on screen. Where does it go when the carrier bills detention six days later?" - "What's the thing that generates the Monday morning fire drill on the Columbus desk?" - "Which shipper is asking you for on-time and dwell reporting you can't produce without somebody building it in Excel?" - "Last RFP you bid — what did they want on EDI 214 status messaging?" - **The highest-yield question on this call:** "When we scoped the original rollout, what did you deliberately leave out because it was too big a bite at the time?" That last one usually surfaces the exact thing you're about to sell. Most upsells were already scoped and cut in the first deal. You're not introducing something new — you're reopening a decision she already made once, with fourteen months of her own data on the table this time.
- 6
5. Build the Incremental Case in Her Arithmetic
Four numbers, in this order, and the price goes in the same breath as the value. **The unit:** "A disputed detention claim costs you two things — the $250 to $400 you eat because you can't prove arrival time, and the forty minutes a coordinator spends digging through load notes and text messages before giving up." **The volume, from her data:** "You wrote off $23,800 in detention, TONU and layover out of Columbus alone last quarter. That's from the aging you sent me in July, not from a benchmark." **The capture rate, deliberately conservative:** "I'm not going to tell you we win all of that. Say we capture half — geofenced arrival and departure timestamps, auto-attached to the load, in the accessorial packet before the carrier invoices you. Half is $11,900 a quarter out of one branch." **The net, price spoken first:** "It's $1,400 a month for Columbus. That's $4,200 against $11,900, call it 2.8 times. If you think half is generous — and you'd know better than me on that reefer lane — give me the number you believe and we'll rerun it right now." Handing her the pencil on the capture rate is what makes it a business case instead of a slide. And at $181 net revenue per load, she'll do the load-equivalent math in her head before you finish the sentence — that's fine, let her.
- 7
6. Cost the Implementation in Hours and Names
Budget is the stated objection. Bandwidth is the real one, and in freight it's usually true. "Here's the honest ask. One 90-minute session with whoever owns the Columbus desk to set geofence radii by receiver — your top 30 stops cover most of it. Then about two hours a week from that same person for three weeks while we tune the false arrivals out. No project team, no coordinator training day. The timestamps land in the same load record they already work out of — it's not a second screen and it's not another login. If it needs more than that, I've mis-scoped it and I'll come back and tell you." Put everything you can absorb on the table here — your CS team building the geofences, your services running the 214 mapping — not later as a concession when she pushes back on price.
- 8
7. The Ask — one branch, one quarter, co-termed
"Give me Columbus for one quarter. You define the success number — my suggestion is detention dollars recovered versus written off, but if you'd rather measure it on coordinator minutes per disputed claim, that's your call and we'll write it down today. If we don't hit it, we pull it out at the end of the quarter and there's nothing further. If we do hit it, we roll it to Dallas at renewal and co-term it to March 1, so you're managing one contract and one negotiation instead of two." Co-terming is the most underused unlock on this call. It turns a new purchase into an amendment, skips a second procurement cycle, and gives the VP of Operations a single signature line in March instead of an unplanned one in October.
- 9
8. Buying Committee Check — do this before you hang up, not in week six
"Last time this went through your VP of Operations and then finance signed off. Is that still the path, or has the threshold moved since the TMS rollout?" Follow-ups worth asking out loud: - "Does your Director of Logistics Technology need to sign off on anything that touches the TMS write-back now? Because if so I'd rather bring him in at the front." - "You've hired a Director of Carrier Sales since we signed — does carrier-side onboarding sit with him now?" - "Is there a bid threshold where procurement wants three quotes?" If a new COO landed or procurement policy changed after the original deal, you're running a fresh evaluation wearing an expansion costume. Better to know that on the phone.
- 10
9. The Recap Email — write it for the forward, not for your CRM
Same day. Seven lines, no attachments unless she asked: 1. The result she confirmed, in her words: "Columbus at 3.1 check calls per load, 26 loads per coordinator per day, tracking compliance 79% — with your caveat that the ELD-sourced pings are coarser than the app pings." 2. The gap she described: "$23,800 in detention and TONU written off in Columbus last quarter because arrival time is a coordinator's typed note, not a timestamp." 3. The value math with **her** capture assumption, not yours. 4. The price, in a sentence of its own. 5. The implementation ask in hours and named people. 6. Pilot scope, success metric, and the date you both decide. 7. Next step with a calendar date already sent. This email is the artifact your champion forwards to the VP of Operations. Write it for that reader.
- 11
10. Park Signals — walk away from the upsell, keep the account
Do not push through any of these. Book the value conversation instead: - An open escalation — a load that went dark, a ping outage on a live lane, a shipper-facing report that broke. - Your champion just moved: the Director of Brokerage Operations promoted to VP, or a Branch Manager who owned adoption walked out. - Renewal inside 60 days with the value question still unresolved. - A flat or declining weekly-active curve you can't explain. - A hiring freeze, a cost review, or a lost anchor shipper in the last quarter — in this industry that news travels fast and you should already know it. Pushing an incremental $17K over the top of any of these is how a renewable account becomes an at-risk one.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Thanks for the twenty, Dana. Two things. First — I pulled your load-level numbers for the last two quarters and there's a split between Columbus and Dallas I want you to sanity-check, because I think it says something about how the two desks are staffed. Second, depending on what you tell me, there's a piece of our platform that might fit a hole you've got. If it doesn't fit I'll say so and we'll stop early. Fair?
Buyer
Sure. Though I'll tell you up front, if this ends with a quote, my freight tech budget went to the TMS integration in Q2 and there's nothing behind it until March.
Rep
Noted, and we'll deal with that when we get there. Here's the split. Columbus is at 3.1 check calls per load, down from 7.4 when we started, and coordinators there are covering about 26 loads a day against 19 at kickoff. Dallas is still at 4.4 check calls and hasn't moved much since March. Tracking compliance across the two is 79%. Does that match what you're seeing, or am I reading my own dashboard optimistically?
Buyer
The 79% is soft and you know it. More than half of that is ELD integration pings that land every four hours. That's not visibility, that's a breadcrumb. When my shipper calls at two o'clock asking where the truck is, a ping from 11:40 doesn't help me.
Rep
That's fair and I'm going to write that down the way you said it, because that's the number you have to defend in a QBR and I've been quoting you the easy version. So the honest read is: coverage is up, ping density on the ELD-sourced loads isn't where you want it. Is that the thing that's still generating your Monday fire drill, or is something else louder?
Buyer
Honestly? The fire drill is money, not maps. We ate a pile of detention last quarter. Driver sits four hours at a receiver in Marion, carrier bills me $340, I've got a coordinator's note that says 'arrived approx 0900' and the shipper's dock log says 10:15. I can't fight that with a note, so I pay it and move on. And on a load netting $181, that hurts.
Rep
That's the number I came in with, actually. Off the aging you sent me in July — $41,300 written off across Columbus and Dallas last quarter in detention, TONU and layover. $23,800 of it Columbus. Before I go anywhere near a product: when we scoped the original rollout, was accessorial evidence something you deliberately left out because it was too big a bite?
Buyer
We cut it. My VP of Ops said get the check calls down first, prove it, then look at the rest. But I'll stop you there — even if you hand me a perfect timestamp, my two biggest shippers have detention terms that are basically 'we'll consider it.' Proof doesn't make them pay.
Rep
Then don't buy this to win detention arguments with shippers. Buy it for the other side of the ledger. Right now when a carrier bills you $340 you can't verify the arrival time, so you eat it. With geofenced arrival and departure timestamps attached to the load, you can decline the ones that are wrong and pass through the ones that are right with evidence attached. The recovery isn't from your shipper — it's from not paying claims you can't check.
Buyer
Alright, that's a different argument. But geofencing on what? My Laredo carriers are one-to-five truck operations that decline the app after pickup. If this only works on the fleets with ELD integration, you're solving the loads I was never worried about.
Rep
Correct, and I'm not going to tell you it covers everything. That's exactly why I want to run this on Columbus and not Laredo. Columbus is 79% compliant and runs most of its volume through your top carriers. Laredo has an onboarding problem, and that's a separate conversation I owe you either way — the module doesn't fix it. Columbus alone wrote off $23,800. If we capture half, that's $11,900 a quarter.
Buyer
Half is generous. Call it a third.
Rep
Take the pencil. A third is $7,900 a quarter. Price is $1,400 a month for Columbus, so $4,200 for the quarter. At your number it's still just under 2x, and that's before any coordinator time back on the disputes. Say it out loud so I'm not hiding it: $1,400 a month on top of what you're paying today.
Buyer
The money's not really the problem at that size. The problem is my people. It's September. Produce is running, Dallas is short two coordinators, and the last time we rolled something out I had a Branch Manager in Atlanta who just refused. Quietly. Never said no, never logged in. I'm not doing that again.
Rep
Then I'll shrink the ask to something you can say yes to without touching a coordinator. One 90-minute session with whoever owns the Columbus desk to set geofences on your top 30 receivers — my team builds them, they just confirm. Then about two hours a week from that one person for three weeks while we tune out false arrivals. No coordinator training, no new login, the timestamps land in the load record they already work in. And if produce season means we start October 14 instead of Monday, I'd rather have the date on the calendar than a good start.
Buyer
October 14 I could probably live with. What happens at the end of the quarter if the number's not there?
Rep
You pull it out and there's nothing further. You define the success metric today — I'd suggest detention dollars declined-with-evidence versus written off, but if you'd rather measure minutes per disputed claim, that's yours to pick. If it works, we roll it to Dallas at renewal and co-term to March 1, so your VP of Ops signs one thing in March instead of two things in two different quarters. Which brings me to the last question: is he still the approval path, or did that change after the TMS spend?
Buyer
He's still the signature, but anything that writes back into the TMS goes past our Director of Logistics Technology now. That's new since June, and he's not going to love a new data source.
Rep
Then let's bring him in at the front instead of week six. I'll send the recap today with your one-third capture number, the $1,400, the October 14 start and the exact API endpoints we write to — and I'll include a 20-minute slot next week for him and me to go through the write-back so he can shoot at it before you take it to your VP. Does Thursday morning work for that?
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “My freight tech budget is gone. It all went to the TMS integration in Q2 and there's nothing until the new fiscal year.” | Don't discount — it teaches them the original $96K was padded. Ask two questions instead: "Committed to what, and when does it reset?" and "Is there a line in that same budget that's underperforming?" Very often there's a legacy tracking subscription, a per-ping fee, or a contractor building the dwell report in Excel that this replaces. Then offer the mechanism, not the price cut: signed order form now, start date after their fiscal reset, co-termed to the March 1 renewal so it's one contract and one negotiation. Budget objections in brokerage are almost always timing and authority objections in a costume. |
| “We barely use what we have. Atlanta and Laredo never onboarded — you want me to buy more?” | Say it before they do, and never argue with it. "You're right, 62 seats and 38 weekly actives. Those two branches aren't idle though — Laredo covered 850 loads last month and every check call happened, it just happened on a cell phone and got typed in after." That reframes unused seats as unrouted work. Then be honest about scope: if the add-on doesn't fix the onboarding gap, say so out loud and commit to a separate onboarding plan with the Branch Managers. Conceding the point is what earns you the right to sell the other thing on the same call. |
| “Even with timestamped proof, my top two shippers won't pay detention. Their contract says 'at shipper's discretion.'” | Agree and switch sides of the ledger. Don't sell it as a way to win arguments with the shipper — sell it as a way to stop paying carrier claims you can't verify. "Today a carrier bills $340 and you can't check the arrival time, so you pay it. With geofenced arrival and departure on the load, you decline the ones that are wrong and pass through the ones that are right with evidence attached." Then add the second-order benefit: timestamped dwell data by receiver is the thing that changes the detention conversation in the next RFP cycle, not this month's invoice. |
| “My coordinators can't absorb another rollout. It's produce season and Dallas is short two people.” | This one is almost always true and arguing with it makes you the vendor who doesn't understand freight. Do three things: shrink the ask to a single named person and a number of hours, absorb everything you can (your team builds the geofences, your CSM runs the tuning), and move the start date past their known crunch — but leave with a calendar date, not a "circle back after peak." "October 14, one 90-minute session with whoever owns the Columbus desk, two hours a week for three weeks after that. No coordinator sees a new screen." |
| “This is only going to work on the carriers who already accept tracking. The one-to-five truck guys on my hard lanes will never take it, and I'm not losing capacity over an app.” | Never let it become capacity versus visibility — you lose that. Concede the coverage limit immediately, then pick the pilot branch where the mix is in your favour: "That's exactly why I want to run this on Columbus, not Laredo. Columbus is at 79% compliance and most of its volume runs through your top carriers." Then ask what percentage of total loads run on their top 50 carriers. It's usually the majority, and those are the ones already onboarded. Quote a realistic compliance number for their mix, never a round 98%. |
| “We're eight months from renewal. Bring it to me in March with everything else.” | Take the renewal date seriously but attack the cost of waiting with their own leak. "March is fine as a signature date. My problem with March is that between now and then you'll write off roughly another two quarters of detention out of Columbus at the rate you did last quarter." Offer the version that costs them nothing procedurally: pilot now on a quarter-length term with a defined kill switch, order form signed today, co-termed to March 1 so it lands inside the renewal they were going to negotiate anyway. If they still say March, book the follow-up for 60 days before renewal — not after — and bring the quarter's write-off number with you. |
Questions reps ask about this call
- What has to be in the usage audit before I run an upsell script for Freight / 3PL customers?
Seven things, all from your own systems: adoption by branch (not company-wide percentages — name which branches never onboarded), which features they've never touched, one outcome number that is theirs rather than your benchmark (check calls per load, loads covered per coordinator per day, tracking compliance rate), the leak you intend to sell against pulled from their AR aging or QBR deck, the commercials including renewal date and whether the original signer is still in the seat, any open escalation in the last 60 days, and your champion's current status. The test is simple: could you say one thing about their account they'd be mildly surprised you knew? Brokerage operators know you have the data. Asking "so how's the platform going?" tells them you didn't look.
- How do I handle 'we barely use what we bought' without losing the expansion?
Say it first. If the Director of Brokerage Operations raises it, you're defending; if you raise it, you're diagnosing. Then reframe unused seats as unrouted work rather than wasted spend — the branch that never onboarded is still making 6-10 check calls per load, just on a cell phone and into a load note afterward. Finally, be honest about whether the add-on actually fixes the adoption gap. Usually it doesn't. Saying "this doesn't solve Laredo, that's an onboarding problem and I owe you a plan for it" is what earns you credibility to sell the thing that does.
- What's the right pilot scope for an expansion at a brokerage?
One branch, one quarter, a success metric the customer defines on the call, and a pre-agreed decision date. Pick the branch where the carrier mix works in your favour — the one already at 75-80% tracking compliance running most volume through the top 50 carriers — not the hard-lane branch full of one-to-five truck operations that decline the ping. And co-term the add-on to the existing renewal date. Co-terming removes a second procurement cycle, keeps it as one negotiation, and makes the expansion feel like an amendment rather than an unplanned purchase mid-year.
- How do I price an add-on for a customer whose margin per load is already squeezed?
Put the price against a leak they can already see in their own numbers, and say the price out loud before they ask. Use the unit-volume-capture-net structure: what one instance costs (a $340 detention claim you can't verify), how often it happened from their data (their quarterly write-off figure), a deliberately conservative capture rate that you then hand them the pencil on, and the net against the monthly fee. Never quote a per-load fee to someone netting $181 a load without immediately converting it into recovered dollars or loads-per-head. And never discount when budget comes up — it tells them the original contract was overpriced and teaches them to wait for the discount on every future expansion.
- Who actually signs the expansion — my original champion?
Check, don't assume. The Director of Brokerage Operations or Branch Manager who championed the original rollout may not carry the authority for an add-on, and in freight the committee changes fast. Ask directly on the call: is the VP of Operations still the signature, has a procurement threshold appeared since the TMS spend, and does the Director of Logistics Technology now have to sign off on anything writing back into the TMS? A new COO or a new bid-threshold policy means you're running a fresh evaluation, not an expansion. Discovering that on the call costs you five minutes. Discovering it in week six costs you the quarter.
- When should I park the upsell entirely?
Park it if there's an open escalation — especially a load that went dark or a ping outage on a live lane — if your champion just changed roles, if renewal is inside 60 days with the value question unresolved, if weekly actives are flat or falling and you can't explain why, or if they've announced a cost review, a hiring freeze, or just lost an anchor shipper. In each case run a value-realization call instead: fix the thing they're paying for, get the result confirmed in their words, and come back. Pushing an incremental $17K over the top of any of those converts a renewable account into a churn risk.