All posts
Amay Aggarwal
Amay Aggarwal
Co-founder, Anglera

Quotes Aren't Slow Because of Your Workflow — They're Slow Because Your Reps Are Human Part-Number Matchers

Quote cycle time isn't a workflow problem. It's a SKU identification problem, and CPQ tools automate the easy half while reps still hand-match the hard part numbers.

Quotes Aren't Slow Because of Your Workflow — They're Slow Because Your Reps Are Human Part-Number Matchers

A 20-line quote shouldn't take half a day. It does, and the trade press keeps blaming the workflow — approvals, spreadsheets, disconnected systems. That's not where the hours go. The hours go into a human being staring at a customer's part description or a competitor's catalog number and trying to figure out which of your SKUs it actually means. Fix that, and the workflow problem mostly evaporates on its own.

The workflow theory doesn't survive contact with a stopwatch

Distribution Strategy Group has built a real case this year that quoting is a strategic liability, not an administrative afterthought. Its June piece on "The Hidden Cost of Inefficient Quoting in Distribution" cites a survey finding that 73% of distribution companies report friction and fragmentation among teams causing delays, and points to spreadsheets, disconnected systems, and sales-finance misalignment as the culprits. Its companion pieces on lost profit before the order is placed and moving beyond the spreadsheet make the same diagnosis from different angles: better tooling, tighter process, fewer handoffs.

All of that is true and none of it is the bottleneck. Ask any operations leader to time a rep building a quote and the pattern is consistent: on lines where the customer's part number matches the distributor's SKU cleanly, quoting is close to instant — industry writeups on quote automation put a clean, no-cross-reference line at roughly thirty seconds of rep effort. The half-day quotes are the ones where nothing lines up. The customer wrote a competitor's catalog number, or their own internal part ID, or a generic description off a spec sheet, and somebody has to translate that into an item your ERP recognizes before pricing or approvals even enter the picture. Manual quoting in distribution commonly runs five to nine business days in the best case, and three to four weeks on complex bids, with accuracy in the 70-80% range even after all that time — numbers that track the difficulty of the matching, not the number of approval steps in the workflow.

Where the hours actually go

Break a quote into its line types and the time distribution stops looking like a process problem:

Line typeWhat the rep has to doWhere the delay lives
Your own SKU, correctly statedLook up price and stockSeconds
Manufacturer part number, your catalogConfirm mapping, check availabilityUnder a minute
Competitor catalog numberIdentify the competitor's line, find your equivalent, verify spec matchMinutes to a phone call
Customer's internal part ID or free-text descriptionGuess intent, search multiple fields, ask engineering or a senior repMinutes to hours, sometimes escalated

CPQ software is built for the top two rows. It prices fast, applies approval logic, and formats a document the moment a SKU is confirmed. What it does not do is confirm the SKU. That's still a person, opening a second browser tab, searching a competitor's site, or picking up the phone to ask a colleague who's been there fifteen years and just knows. The parts-cross-reference industry that grew up around automotive aftermarket sales exists precisely because this translation step is hard and error-prone at scale — catalogs like TecDoc built a business on standardizing exactly this lookup, because a printed or static cross-reference is out of date the moment a manufacturer revises a line.

CPQ automates the last mile of a race run mostly on foot

This is the part the workflow narrative gets backwards. Configure-price-quote systems are last-mile automation: they assume you already know which item you're quoting. That assumption holds for maybe half a distributor's line volume — the SKUs customers already order by your part number. For the rest, CPQ sits idle while a rep does catalog detective work upstream of it, and no amount of approval-routing or spreadsheet elimination touches that first mile.

Distribution Strategy Group is right that the cost is real and that it shows up before the order is placed. Where the diagnosis goes astray is treating quoting as one undifferentiated process. It's two processes stapled together: identification, which is a data-matching problem, and configuration, which is a business-logic problem. Only the second one is what most "quoting transformation" initiatives actually automate.

The evidence on urgency backs this up from the buyer side too. Seventy-eight percent of B2B buyers say they purchase from whichever vendor responds first, and leads contacted within five minutes convert at multiples of the rate of leads contacted thirty minutes later. Every hour a rep spends untangling a part number is an hour a competitor's quote — sent by a rep who didn't have to guess — sits in the customer's inbox first.

What to automate first

If quote speed is the goal, sequence the work backwards from where the time actually goes. Start with the identification layer: normalized attributes and cross-reference mappings that let a messy input — a competitor number, a customer's internal code, a copy-pasted spec line — resolve to your SKU without a phone call. Only after that layer exists does a CPQ investment pay off at full speed, because now every line a rep touches starts pre-identified instead of half of them starting as a search problem.

This is the same measurement Anglera has been making across the Top Distributors 2026 index: distributors with the strongest Digital Readiness Index scores tend to be the ones whose catalog data — attributes, cross-references, competitor mappings — is clean enough that search and matching work without a human backstop. That's the layer we work on. Your PIM stores the data; Anglera does the work of getting cross-reference and attribute data clean and current enough that a messy part number resolves on its own, whatever CPQ or ERP sits downstream of it.

Amay Aggarwal

About the author

Amay AggarwalCo-founder, Anglera

Amay is a co-founder of Anglera, where he's building the AI pipeline that turns messy supplier catalogs into structured, AI-readable product data for distributors and answer engines. He built the catalog AI systems at Uber Eats on top of research from Stanford's AI lab.

See it on your own SKUs.

A 30-minute walkthrough on your categories and your supplier data.

Book a demo