How the work actually happens
What happens when a distributor rep has to escalate a technical question to the principal?
The question leaves the building. A distributor sells other companies' products, so when a rep cannot answer a customer's spec from the data sheets in front of them, the next move is an email to a supplier's technical contact and a wait — a step a producer's own sales team does not have. It costs labour twice, it spends the customer's elapsed time rather than yours, and the answer that comes back is scoped to one supplier's line when the customer's question was scoped to yours.
The step producers do not have
A producer's rep who cannot answer a question walks to the lab, or emails a colleague whose name is on the data sheet. The document was written inside the same company. The escalation is internal, and the person on the other end is accountable to the same P&L.
A distributor's rep is doing something structurally different: screening documents their own company did not author, for a customer who is their own. When the sheet does not answer the question, the escalation crosses a company boundary. That changes three things at once — who controls the clock, what the answer covers, and who is accountable for it.
The load is principal count, not SKU count
SKU count is the number everyone quotes, and it is the wrong one. Ten thousand SKUs from one supplier is one document format, one naming convention, one technical contact, one escalation path. Twenty-five principals is twenty-five of each.
We surveyed the public websites of 78 US specialty chemical distributors in August 2026 — the shape of that population is the substance of this page, so here is exactly what we found:
- 52 of 78 are pure distributors and 16 are hybrids that also blend, toll or manufacture. Not one is a pure producer. Every company in the set carries at least some line it did not make.
- 19 of the 78 publish a principal count on their own site. The median is 25; the range runs from 10 to 100, with two at 100 or more. Those are the companies that chose to state a number — the rest carry principals too, they just do not count them publicly.
- At the sharp end of that distribution, one company in the set lists 25-plus principals across nine unrelated markets — coatings beside oilfield beside institutional cleaning — carried by exactly two named territory sales managers on its own contact page. That is the escalation problem stated numerically, on a public page, by the company itself.
Each principal is a separate document set in a separate format with separate names for the same properties, and a separate person to email when the sheet does not say. A rep answering a boiler-water inquiry may be reasoning across a hundred suppliers' data sheets, none of which their own company wrote.
Who is actually doing the technical work
Here the survey turns up something worth stating carefully. 47 of the 78 company websites name no laboratory, no application chemists and no R&D function anywhere we could find on the site. Twenty-one of the 78 explicitly advertise technical service, support or expertise — and 7 companies are in both groups: they promise technical service in as many words, and name nobody on the technical side to deliver it.
Be precise about what that is and is not. It is absence of evidence on a public website, not proof that no bench exists; a company can have chemists it never mentions. But the customer sees the same website we did, and more to the point: not one contact list across the 78 companies carries the job title "formulator." The named people are presidents, vice presidents and sales managers. Whatever the org chart says, the person who receives the inquiry and owns the answer is a salesperson.
That is not a criticism of the model. It is the model working as designed — distributors compete on line card, availability and service, not on bench capacity. It just means the escalation path is load-bearing, because it is the whole technical function for a large share of these companies.
What the escalation actually costs
Four costs, none of which shows up on an invoice:
- Labour, twice. Your rep writes the question. Someone at the principal reads it, checks it, and writes back. Two companies pay for one answer.
- Elapsed time you do not control. The clock is running on your customer's decision, and the person who can stop it works somewhere else and has their own queue.
- An answer scoped to one line. You asked one principal, so you learned about one principal's products. If three of your suppliers could have served the requirement, you now have to run the loop three times and reconcile three partial answers — or, more often, stop at the first one that works and never learn what else would have.
- A silent loss when the answer is "no." An inquiry answered incompletely is lost quietly. The customer never learns which qualifying products were never surfaced, and neither does the rep.
What nobody has measured — including us
This is the part most vendors fill with a statistic, so we want to be direct: there is no credible public benchmark for how often a distributor escalates a technical question to its principal, or how long the round trip takes. We have looked. Every circulating figure in this area traces back to a vendor whose product is worth more if the number is large, which is a reason to distrust it rather than to repeat it.
So GRADE offers no number here. What we can say is structural and checkable: the step exists, producers do not have it, the population above shows how many principals it spans, and the companies carrying the most principals per rep are the ones where it bites hardest.
If you want to know what it costs at your company, the honest answer is that you have to measure it, and the measurement is not hard: for one month, count the technical inquiries where somebody had to ask a supplier, and log the days between the customer's question and the customer's answer. Most distributors have never counted, which is itself the finding.
There is a second question worth asking in the same month, and it is the better one:
When you tell a customer "we don't have anything for that" — how often is that actually true?
Nobody can answer it from memory, because the cases where a qualifying product existed and nobody found it look exactly like the cases where nothing qualified. That is the gap escalation is covering for, and it is the reason we built a screen that has to say, for every product it rules out, in one sentence, why.
Every claim on this page, and how to check it
- The 78-company survey is our own research, compiled 2026-08-17 from these companies' public websites and contact pages. Every count on this page was re-derived from that dataset on the day this page was written, with the counting rule stated: "distributor" and "hybrid" from each company's own self-description; the principal count from companies that print one; the no-lab figure from the sites where our researcher recorded that no lab, no application chemists and no R&D function are named. That last one is a reading of a website, not an audit of a company — see the paragraph above, which says so on the page rather than in a footnote.
- "Not one is a pure producer" and "no contact carries the title formulator" are counts of zero across all 78 rows, not impressions.
- The two-reps-nine-markets company is described from its own published About and Contact pages. We have not named it, because a page about how hard someone's job is should not arrive with their name attached.
- "No credible public benchmark" is a statement about what we could not find, and it is the reason there is no productivity statistic anywhere on this page. If we ever publish one, it will come with the study.
- What we are not claiming: that the 78 companies are a representative sample of US chemical distribution. They are a call list built to a fit profile, and the profile selects for companies whose reps do the technical work. Read the numbers as a description of that population.
The other half of the problem
Screening a spec across a line card you did not write.
How a requirement becomes a typed filter, and why every elimination has to come back with a reason a rep can read to a customer.