Across 10,800 supplier email threads, the median supplier conversation takes about a month and 16+ messages to reach resolution — and sample requests take 40 days. Resolution time isn’t a pricing problem or a negotiation problem. It’s a communication-overhead problem that touches every topic a procurement team handles.
Methodology
Waystation analyzed more than 10,800 supplier email threads from mid-market food, beverage, and supplement companies in the $50M–$500M revenue range. A “thread” is a continuous exchange around a single topic until the question is resolved, the supplier declines, or the thread is abandoned for 30+ days.
Resolution times by topic (median)
| Topic | Median days | Median messages |
|---|---|---|
| Sample requests | 40 | 17 |
| Negotiation | 34 | 19 |
| Quality | 33 | 16 |
| Product specifications | 31 | 16 |
| Lead time | 30 | 18 |
| Logistics | 30 | 18 |
| Pricing | 29 | 16 |
| MOQ | 27 | 14 |
Key findings
- Sample qualification is the pacing item. Samples clear in 40 days at the median — slower than pricing, negotiation, or spec resolution. That’s because sample qualification happens before sourcing decisions, creating pre-commitment delays that block everything downstream.
- Negotiation threads carry the worst tail risk. The 90th percentile sits at 176 days.
- Logistics threads have the longest tail. 90th percentile of 236 days.
- 52% of supplier communications are single-message broadcasts with no reply. Supplier announcements, blast updates, and unanswered outreach fill more than half the volume.
- The longest observed thread contained 1,290 messages spanning years. A single institutional-memory artifact, impossible to carry in anyone’s head.
The bottleneck isn’t a topic — it’s overhead
The insight isn’t that one topic is slower than another. The insight is that every topic clusters around the same month-plus resolution window. The bottleneck is communication overhead across all topics, compounded by concurrent threads across multiple suppliers.
A procurement lead isn’t handling one 30-day thread at a time. They’re handling dozens simultaneously — each waiting on a supplier reply, each with context the lead has to reconstruct every time a reply arrives.
Why this is structurally hard
- Suppliers juggle dozens of customers; reply latency is bounded by their bandwidth, not yours.
- Each topic pulls in a different internal stakeholder (QA for quality, R&D for specs, procurement for pricing), adding internal round-trips.
- Thread context lives in inbox scroll, not in a structured record. Every reply restarts the “where were we” process.
- Abandoned threads aren’t flagged — they just stop. A procurement team rarely knows which of their open conversations have gone cold.
What to do with this benchmark
If a conversation you expect to close in a week is actually closing in a month, your team is absorbing that lag in every downstream process — from RFP cadence to launch timelines to emergency procurement premiums.
Source: Waystation AI analysis of more than 10,800 supplier email threads from mid-market food, beverage, and supplement companies ($50M–$500M revenue range). The full dataset is published at waystationai.com.
