Dial. Glance. Say it.

“We are still reviewing vendors (VSpark)”

Fair. The trial costs you nothing and produces the comparison data for that review. Run us while you decide.

“Our forwarders already send us reports”

Theirs is the carriers' homework self-graded. This is independent, measured from the boxes themselves.

“I need approvals to share shipment data”

NDA covers exactly that, and it is being re-sent now. List can be ready the day it signs.

“That is a logistics tool, not mine”

The tracking is logistics. The arrival-forecast feed is planning data, and that part lands on your desk.

“We are committed to Transporeon for 12 months”

Committed with a break clause. Use the year to collect the evidence that decides whether to use it.

“Transporeon already integrates with our FF systems”

And it can keep doing that. The RFI question is which feed is more accurate and earlier, which is exactly what a side-by-side shows.

“Too early for IT involvement”

That is exactly the answer I needed. Who tells me when it is the right stage?

“Every vendor claims door-to-door”

Agreed, most are lying about the road leg. I will tell you exactly where our data ends, which is rarer than it should be.

“My team handles vendor reviews”

They are, with Daniel and Adrian. This is the two-line version so the decision arriving on your desk has context.

“How did you get my name?”

Researching Tesco's intermodal setup, your name sits on the rail side. If that is wrong, point me right and I am gone.

“Transporeon covers us now”

On the ocean leg, partly. The CE pain you flagged was inland and multimodal, which is precisely where it is thinnest.

“K+N might see this as hostile”

They never see it. It is your internal benchmark of a service you pay for. Auditing a supplier is not hostility.

“Air spend is strategic, not panic”

Some is. The save-the-launch bookings are not, and they are the expensive ones. Worth separating the two.

“We went with another provider”

Genuinely useful to know, thank you. Who won, and what tipped it? That answer is worth more than a deal to me today.

“Why are you calling me then?”

Because clean redirects deserve thanks, and people who give them usually know the org better than the org chart does.

“We need a bigger evaluation than one lane”

Bigger evaluations need a business case. One lane, one month, one report IS the business case, then go as big as you like.

“I have not had time to look”

Totally fine. One name off the top of your head beats a search. Who would YOU call about ocean visibility?

“Our forwarders give us visibility”

They give you their version of it. Independent measurement is how you grade forwarders, not ask them to grade themselves.

“I told you, I am not the decision maker”

Exactly why this is for you, not the deal. Analysts run on data, this is a free dataset.

“Nexus alerts us already”

After the fact. The UK and Poland boxes were the proof: alerted at arrival is just informed of the damage.

“Nexus covers visibility now”

It moves the data. The gap analysis we did together showed it does not predict. That gap survived go-live or it did not, you tell me.

“Team just finished one rollout”

Which is why this is small on purpose: 5 users, focused scope, no integration. A pilot, not a programme.

“I cannot share vendor names”

Then tell me what it does badly. The gaps tell me whether to keep calling Unilever at all.

“We have a central tracking hub now”

Exactly why I am calling the top. The hub is plumbing; the question is whether its predictions are good enough to plan on.

“I am not the decision maker”

Perfect, I am not selling yet. I want the user's verdict, it is worth more than the buyer's.

“Send me something in writing”

Six emails are in your inbox. The snapshot is different: your lanes, your numbers, one page. Yes or no is enough.

“Unilever tooling still covers us”

For how much longer? Separation means the tooling walks away. Greenfield is the cheapest moment to choose well.

“We sell a competing product”

Which is why I am not selling a platform. I am selling the data layer that makes yours better than what you ship today.

“Talk to logistics, not me”

Logistics buys the feed. You decide whether it changes anything. I would rather design that with you first.

“Shippeo and Roambee cover us”

On land and finished goods. D&D dies at ports on flows they do not watch. That gap is the whole pitch.

“We have data lakes full already”

Full of carrier self-reporting. This is independent, predictive, and clean enough to model on. Different raw material.

“We said no third provider”

And I agreed. This is not a third platform, it is coverage for the flow none of the two see, delivered as data into what you have.

“We track carrier KPIs internally”

From data the carriers send you. Independent measurement is the difference between their report card and an audit.

“No budget at my level”

Not asking for budget, asking for container numbers. The demo costs nothing and the case builds itself upward.

“MRP dates come from the ERP”

Fed by carrier schedules. Correct the feed and the ERP gets smarter without touching the ERP.

“Wrong person, sorry”

No apology needed, you replied once which beats most. Who should I be annoying instead?

“Just send a presentation”

I could, it would join the others. Three container numbers gets you proof on your own boxes instead of claims on my slides.

“We get carrier notifications”

Notifications arrive after the fact. Predictions arrive while you can still do something. That gap is the pitch.

“Tender is not this year”

Better still. Data collected now is leverage then. The worst time to start measuring is the month before negotiations.

“Another tool to manage”

Zero tools. One email at 7am. If it stops earning its open, it stops arriving.

“You emailed me 11 times”

Ten too many, agreed. This call exists because the eleventh should have been an answer to your roads question. Here it is.

“Carrier data is enough for us”

It said the same thing through the Red Sea while transit doubled. The gap between plan and reality is exactly what you asked us about.

“Hendrik owns this, not me”

He does, and he is buried in S4. You carrying one new fact to him moves it further than my eighth email will.

“S4 takes all our bandwidth”

Which is why this needs none of it. Container numbers in, data out, IT never enters the room.

“We tried RTV, it failed”

It failed on missing transport orders. This does not use them. Different input, different outcome.

“We just went live with someone”

I know, January, Vision data. This call is not against them, it is for your December file. October is when numbers help you.

“Still no booking in your platform”

Correct, and September's session shows the workflow that works without it. If it does not convince you, we are done in 30 minutes.

“Call me back in September”

That is the plan. I am calling so September has a date on it instead of a vibe.

“P44 is the safe enterprise choice”

Safe and heavy. You asked me the difference in October: they need your transport data wired in, we need a container number. For Materials' setup that is the whole decision.

“I said I would reach out”

And I am not arguing. I am making sure the mental box says ocean, not trucks, so the right trigger reaches you.

“We are mid ERP migration, bad timing”

That is the argument for us: API-level, zero dependency on the ERP timeline, value before 2027.

“We would build this ourselves”

Everyone says that until they meet 100+ carrier formats. Buy the data, build the logic on top, that is the CoE move.

“We run SAP TM for this”

TM executes. It does not predict. The '23 internal verdict at Borealis said exactly that, and nothing in TM has changed it.

“Nothing changed since I said no”

One thing did: no transport orders or carrier contracts needed anymore. If that one thing does not matter, the file closes today.

“We built our own tracking already”

Against 3 carriers. We cover 100+. Feed ours through your front-end and your coverage story is complete overnight.

“Tracking is on our roadmap to build”

Building means maintaining 100+ carrier integrations forever. Embed ours and ship the feature this quarter instead.

“Our users have not asked for it”

They ask every time they open a carrier site after booking with you. The behaviour is the feature request.