AI search for logistics + supply-chain. From freight quotes to AI answers — be the cited recommendation.

1. Week 1. Hermes baseline across 9 engines: per-corridor citation map (your top 5 trade lanes vs your 3 closest competitors).
2. Week 2–3. Schema rollout: Organization + sameAs, Person nodes for ops leads with Incoterms + corridor expertise, Service nodes per trade lane with rate ranges.
3. Week 4–7. ContentOS ships 5 trade-lane comparison guides (verified transit times, customs notes, rate bands) — chunk-ready for AI extraction.
4. Week 8–10. Authority graph: Clutch case studies, trade-publication outreach (FreightWaves, JOC, RZD-Partner), client case studies with named-route metrics.
5. Week 11–12. Re-scan + report. See where AI engines now cite you for corridor queries and which lanes need a second round.

• No paid Google Ads, no LinkedIn ads, no display media. AI search lifts via citation graph, not bought impressions.
• No generic SEO blog content. AI engines discount it. ContentOS ships corridor-specific, factcheck-verified guides instead.
• No EDI/TMS integration work — that stays with your IT team. We work with whatever rate data you can expose in schema.

Logistics decisions are matrix problems. A shipper weighs price, transit time, customs clearance, fleet match, and seasonal capacity in one breath. Old SEO sites answered one slice per page. AI engines answer the whole matrix in one sentence. When your trade-lane data, operations-lead expertise, and live rate ranges all live in machine-readable schema, the engines can synthesise. When that data lives in marketing prose, the engines pass you over and cite the broker with the cleaner data layer.

Q: Do we need to expose live rates?

A: Helpful but not required. Static rate ranges in Service schema (low-mid-high per corridor, updated quarterly) lift citations meaningfully. Live API-fed rates lift more, but the ROI on the integration depends on your existing TMS.

Q: What about RFP-specific work?

A: AI-search citations drive top-of-funnel awareness; the RFP cycle stays with your sales team. We close the "shipper has never heard of you" gap. The actual quote, contract, and close are yours.

Q: Does this work for non-English corridors (RU, CN, AR)?

A: Yes. Hermes scans Yandex Neuro for RU corridors, scans across language-localised model surfaces, and ContentOS ships per-language guides. Most logistics brands ignore non-English AI surfaces; we treat them as primary in their corridors.

Q: How does this affect direct shipper enquiries vs broker traffic?

A: Both surface. AI engines name brokers when buyers ask "best freight forwarder", and they name carriers when buyers ask "best fleet for X". The trust-graph work lifts whichever role you play.