Halverson routing and tracking evaluation

The deal is in discovery; the agreed next step is a warehouse-integration deep-dive on Thursday, October 15, at 2:00 p.m. Hamburg time. Integration feasibility is the first gate; Halverson wants to choose by mid-December, with TrackPoint ending March 31.

Easy to miss

• All three depots live by March is tight, not promised — Ben said one depot usually takes four to six weeks from signing, and three by end-March is possible but tight; confirm a credible rollout plan after the integration review.

Next steps

Open objections

• Driver adoption — show how the app works in practice and how printed route sheets can support a transition.
• FleetLoop price comparison — provide a line-by-line proposal; Ingrid will ask what FleetLoop’s “all included” quote covers, especially warehouse integration.

Promised but not verified

• Warehouse compatibility: Ben said he cannot confirm compatibility on this call; review the interface, required fields, write-back and security before describing it as supported.
• TrackPoint boxes: Ben will check compatibility after receiving the model number; do not promise the existing boxes can be retained until verified.
• Older-driver case-study experience: Mia said she would check; do not state that the reference fleet had older drivers until confirmed.
• Peer reference call: Mia will ask, with no promise of availability; do not offer a call as confirmed.
• Rollout timing: Ben said three depots live by end-March is possible but not something he would promise today; present it as conditional, not committed.

The buyer corrected the seller

• Mia ranked warehouse integration, driver adoption, then price; Ingrid corrected this: driver adoption and warehouse integration are equal priorities, with price third. Use that ordering in follow-up.

How the buyer reacted to the seller’s moves

• “My mum uses apps…” → Ingrid replied that Klaus, a Bremen driver of 31 years, does not want a phone in his cab; Ben’s concrete adoption plan and printable route sheets felt “more realistic.” Lead with practical rollout and fallback, not ease-of-use claims.
• Early discount offer → Ingrid said a discount before she understood the offer made the first price feel unreal; send transparent, line-by-line pricing without a discount headline.

People who were not on the call

• Marit Olsen, CFO: signs anything over €50,000; wants a one-page view of cost, savings and payback, and does not need to meet vendors. Ingrid said Marit will look first for hidden costs.
• Henrik, Hamburg dispatcher: built the spreadsheet and will judge whether routes match his; Ingrid said others will follow if he approves. Prepare an actual-route comparison for him.

Suggested next move

• Prepare a route-quality comparison for Henrik after integration feasibility is established — built from Ingrid’s view that Henrik’s approval will influence the other dispatchers and her offer to provide a sample week — ask Ingrid whether he can review the output.

Deal snapshot

The buyer’s path to a decision

• Integration deep-dive: Ben and Halverson IT; October 15 at 2:00 p.m. Hamburg time. Ingrid may join the first half-hour.
• Pricing workshop: after the technical review, if integration looks good; owner and date not set. Marit may join.
• Ingrid chooses the tool by mid-December; Marit signs if the price exceeds €50,000.

CRM note

Discovery completed with Ingrid (Head of Operations) and Halverson’s IT manager. Ingrid chooses the tool; CFO Marit Olsen signs above €50,000, and the target decision is mid-December. Next: Ben and IT to review the warehouse interface on October 15; Mia to send the line-item proposal and case study by October 9, with pricing workshop gated on integration feasibility.