The Objection You Can’t Answer With a Feature

You got the second call. Then a third. You ran a demo for Dana Okonjo, Renée Salcedo (CFO), and Paul Grissom (Director of IT). Twelve minutes into the debrief, this happened. Verbatim. 

Dana: “We ran a pilot with Ledgerlane last year. It got ETAs wrong often enough that three of our customers called Marty directly. Tell me why you’re different — and don’t tell me your model is better, because that’s what they said.” 

Renée: “Your one-pager says one point four million a year. My entire dispatch payroll is two point one million. So either you’re telling me I cut ten people, or the number’s fake. Which is it?” 

Paul: “Your agent sends email as ardentlogistics.com. Our security review will not allow a third party to send from our domain. That is not negotiable this quarter.” 

You promised a written response by Friday and a fifteen-minute call to walk them through it. 

Here is the only customer data you are permitted to use. It is from Cordray Freight, a Halyard customer of comparable size, measured over the first 90 days of production. It is on the logo wall, so you can name it. 

Measure	Before	After 90 days
Check calls placed by a human, per day	780	300
Automated status updates sent per day	0	610
Status accuracy vs. carrier ground truth (200 sampled/week) — single-stop loads	94.1% (human)	96.4% (agent)
Status accuracy vs. carrier ground truth — multi-stop loads	93.8% (human)	91.0% (agent)
Customer-reported wrong-ETA incidents per month	31	22
Dispatcher headcount	22	22
Average dispatcher overtime, hours/week	9.4	3.1
Median quote response time	41 min	12 min
Loads per month	11,600	12,900

Two more facts. Ardent’s mix is roughly 35% multi-stop loads. And Halyard’s agent can send from a Halyard-owned subdomain with SPF/DKIM delegation, or from a Halyard address with the customer’s name in the display field — both are available today; neither requires sending as ardentlogistics.com. 

Write the response. 

Constraints to consider 

• You cannot discount. You have no pricing authority on this deal and asking for it this week would signal weakness to a CFO who is already testing your numbers. 
• You cannot promise anything not in the product today. No roadmap commitments, no “we’re working on that.” 
• You may not claim accuracy beyond what the Cordray table shows. Every accuracy statement you make has to be traceable to a number in that table. 
• The security constraint is fixed this quarter. Paul is not going to lose that argument internally, and pushing him on it costs you Paul. 
• You must concede at least one of the three objections — genuinely, not rhetorically — and say what you are conceding and what it costs the deal. 

AI Usage Guidance 

We expect you to use AI tools. We evaluate how you use them — not whether you use them. Evidence of iteration, redirection, and critical evaluation scores higher than a polished output with no process documentation. 

The single highest-signal indicator: your video answer to the mandatory AI question. If you cannot name a specific moment where you redirected AI output, evaluators will assume you did not. 

Mandatory AI question for your video: Walk me through one moment where you disagreed with, pushed back on, or redirected what the AI gave you — and what you did instead. Name the specific moment. Explain what the AI produced that didn’t meet the bar, what you did differently, and why. 

Communication presence is part of this role. We assess rapport-building, objection handling, and ability to tailor messaging — delivery style matters here.