The Global Summit 2026 lineup is out, and it reads like a supply chain org chart. Mattel, Amazon Canada, and the Ports of Los Angeles and Long Beach are all sending C-suite. If you sell into logistics, cross-border, or fulfillment-adjacent software, this is the conference to watch. Not necessarily to attend. To mine.
Here's the thing most founders get wrong about conference season. They treat the agenda as a to-do list. It isn't. It's a signal map. Who's speaking tells you where budget is moving, what problems are getting executive airtime, and which vendors are about to get squeezed.
What the speaker list actually tells you
Three names matter here, and they matter for different reasons.
Mattel. A toy company at a supply chain summit is not an accident. Mattel has spent the last two years rebuilding its logistics footprint after the 2023-24 shipping disruptions. When a consumer brand sends a supply chain exec to a conference, they're usually shopping. Either for software, for 3PL partners, or for visibility tooling. If you sell inventory planning, demand forecasting, or supplier risk software, Mattel is a warm signal. The deeper read: toy sourcing is concentrated in a handful of manufacturing clusters, and Mattel's lead times are seasonal and unforgiving. A missed Q3 window doesn't get recovered in Q4. That makes their evaluation criteria unusually strict — they're not buying dashboards, they're buying the ability to re-plan mid-cycle when a port strike or a tariff line moves. Pitch accordingly.
Amazon Canada. Cross-border fulfillment is the subtext. Canada has been a quiet headache for US-based sellers since the de minimis changes and the CBSA modernization push. Amazon Canada sending an exec means they're either defending share or building new infrastructure. Either way, anyone selling into Canadian e-commerce fulfillment should be paying attention. Watch the regulatory layer here: CARM (CBSA Assessment and Revenue Management) shifts duty and tax liability earlier in the import process, which changes who carries the cash-flow burden. Sellers who built their Canada playbook on informal clearance and consolidated brokerage are now exposed. If your product touches customs data, landed-cost calculation, or cross-border returns, this is a live buying trigger, not a hypothetical one.
Ports of LA and Long Beach. These two ports handle roughly 30% of US containerized imports. When their leadership shows up, the conversation is usually about automation, dwell times, and the ongoing shift of cargo to East Coast and Gulf ports. If you sell into drayage, yard management, or port-adjacent SaaS, this is your room. The process detail worth knowing: both ports have been pushing toward data-sharing mandates and appointment systems, which forces every downstream trucking and warehousing operator to adopt software they may have avoided for years. That's a compliance-driven adoption curve, and compliance-driven buyers move faster than efficiency-driven ones.
The pattern across all three: these are not innovation buyers. They're risk buyers. Sell to the deadline, not the dream.
The three themes that will dominate the agenda
Conference agendas are predictable if you've read enough of them. This one will hit three notes.
Geopolitics and cross-border risk. Tariffs, Red Sea routing, Panama Canal drought restrictions. Every supply chain exec in 2026 has a war story about a route that stopped working. The interesting part isn't the story. It's what they've bought to prevent the next one. Watch for how these teams have restructured their supplier qualification processes — dual-sourcing used to be a resilience talking point, and now it's a procurement requirement written into contracts. The regulatory layer matters too: forced-labor import rules, carbon border adjustments, and country-of-origin documentation now sit inside the sourcing workflow, not beside it. When a Mattel or Port of Long Beach executive describes their risk stack, they're describing a compliance function that has quietly merged with operations.
E-commerce fulfillment economics. The last-mile math has changed. Amazon's regionalization push, Walmart's store-as-warehouse play, and the rise of micro-fulfillment centers have all reset what "good" looks like. Anyone selling into fulfillment ops needs to know which cost structures are now table stakes. The deeper shift is in inventory positioning: regionalized networks reward teams that can forecast at the node level, which turns demand planning from a finance exercise into an operational one. Vendors pitching fulfillment software should expect questions about integration with existing WMS and OMS layers, not feature lists.
AI transformation, again. Yes, it's on the agenda. No, it isn't new. What is new is that supply chain leaders have moved past pilots. The 2026 conversation is about which AI deployments survived procurement and which got quietly killed. That's the useful part. The survivors tend to share a profile: narrow scope, measurable throughput or cost impact, and a clear owner inside operations rather than innovation. The casualties were usually broad platforms with no defined success metric. For anyone selling into this space, the lesson is that supply chain buyers now evaluate AI the same way they evaluate any capital purchase — on payback period and adoption risk.
How to work this conference without attending
You don't need a $2,000 badge to get value from a conference. You need the speaker list, the agenda, and a working outbound setup. When the lineup skews toward supply chain operators — the people at Mattel, Amazon, and the Port of Long Beach who own sourcing, logistics, and trade compliance — the speaker roster itself becomes a map of where budget and attention are moving. That's the signal worth mining.
Here's the workflow we'd run:
- Pull the full speaker roster from the conference site. Names, titles, companies.
- Cross-reference against your ICP. Not everyone speaking is a buyer. Some are consultants, analysts, or vendors. Filter them out.
- For the ones who fit, find a second signal. A recent press release, a podcast appearance, a LinkedIn post about a specific problem. One signal is noise. Two is a pattern.
- Draft a short email that references the talk, not the conference. "Saw you're speaking on cross-border risk at Global Summit" is fine. "Saw you're speaking on cross-border risk and wondered if the CBSA modernization timeline is affecting your Q3 planning" is better.
- Send after the agenda drops, not after the conference ends. Pre-conference inboxes are quieter. Post-conference inboxes are a graveyard.
The regulatory layer is where this gets sharper. A port executive speaking on throughput is really speaking about drayage capacity, chassis availability, and the knock-on effects of tariff classifications shifting mid-quarter. An Amazon supply chain lead is managing inbound freight consolidation and customs brokerage relationships that change with every trade policy update. A Mattel sourcing executive is tracking duty rates and origin rules across multiple manufacturing regions. These aren't abstract themes — they're operational constraints with deadlines attached. If your product touches any of them, the talk title is a doorway into a live problem.
We've written before about extracting attendee lists before your competitors do. The same logic applies here. The speaker list is public. The agenda is public. The only thing that isn't public is whether you'll do anything with it.
What doesn't work
Two things, based on what we've seen founders try.
First, generic conference outreach. "Are you attending Global Summit?" is not a hook. It's a filter question that gets deleted. If you can't name the specific session or the specific problem, don't send the email. The reason this fails is structural, not stylistic: a filter question asks the recipient to do the qualifying work for you. Supply chain executives at Mattel, Amazon, and the Port of Long Beach are already triaging inbound against a fixed set of operational problems — port congestion, tariff exposure, supplier concentration, last-mile cost. An email that doesn't name one of those problems reads as noise, regardless of how well it's written. The fix is to anchor the message to something verifiable: a session title, a panel topic, a published agenda item. That specificity signals you did the work, which is the only currency you have before the conference starts.
Second, waiting for the post-conference recap. By the time the LinkedIn summaries land, every SDR in your category has already sent. The window is the two weeks before the agenda goes live and the two weeks after. Miss both and you're competing on price. There's a mechanical reason for this: agenda publication is the moment intent becomes legible. Before it, you're guessing at priorities. After it, you're reacting to a crowded inbox. The pre-agenda window lets you frame the problem before anyone else names it; the post-agenda window lets you reference a specific session while it's still fresh. Both require you to be watching the conference site, not your competitors' feeds.
One caveat: this only works if your ICP actually overlaps with supply chain. If you sell HR software to tech startups, Global Summit 2026 is not your conference. Don't force it. There's a better conference for your pipeline somewhere. Find that one.
What we'd do next
Pull the Global Summit 2026 speaker list today. Filter it against your ICP. Pick five names. Write five emails that reference a specific operational problem, not the event. Send them this week, before the agenda cycle peaks.
The reason to move now is structural, not tactical. Speaker lists go live months before agendas are finalized, which means the executives named on that page are still in the phase where their teams are drafting internal priorities — tariff exposure modeling, port diversification, supplier concentration risk, returns economics — and haven't yet committed budget or headcount to solving them. Once the agenda publishes, those same executives get inbound from every vendor attending, and your email becomes one of forty. The window between "listed" and "scheduled" is the only period where a cold email reads as informed rather than opportunistic.
When you filter, resist the urge to sort by title. A VP of logistics at a mid-market retailer is often a better fit than a Chief Supply Chain Officer at a Fortune 50, because the VP owns the problem end to end and can approve a pilot without procurement. Look for signals in the speaker bio itself: a recent port shift, a nearshoring announcement, a distribution center opening. Those are the operational problems worth referencing.
- Reference their problem, not their panel. "Saw you're speaking on resilience" is noise. "Saw you moved volume through Long Beach after the Panama restrictions" is a reason to reply.
- Keep the ask small. One question about how they're handling a specific constraint outperforms a demo request at this stage.
- Sequence, don't spray. Five researched emails beat fifty templated ones, and they protect your domain reputation while you're at it.
If you want to see how MiraReach handles the prospect scoring and drafting side of this, give MiraReach a try. It won't send anything without you pressing the button.
— Mira