An electronics enquiry is a programme, not a deal
The stages a generic CRM has never heard of
A typical CRM models a sale as a contact, an opportunity and a close date. An electronics manufacturing enquiry does not behave that way. It arrives as a bill of materials at a particular revision, with Gerbers, drawings and a quantity band. It is costed, which is real engineering work. It is quoted with a unit price at each volume and a separate non-recurring charge for stencils, fixtures and test jigs. Then it goes quiet while the customer validates a prototype, and only afterwards does it become a purchase order, often a blanket one released in monthly tranches.
Every one of those steps has its own failure mode, and none of them is captured by a single "expected close date". Modelling them separately is what makes the pipeline honest, because it lets you distinguish an RFQ stuck in your own costing queue from one stuck in a customer's validation lab. Those two problems have completely different fixes and are usually reported as the same thing.
The costing queue is the real bottleneck
For most contract manufacturers, quotation turnaround is set by the availability of one or two people who can price a BOM properly. When those people are busy, RFQs queue silently. The buyer does not see a queue; they see a supplier who has not replied. Putting a visible clock and an owner on each RFQ turns an invisible backlog into a managed one, and usually reveals that a handful of low-value RFQs are consuming the costing capacity that a significant programme is waiting for.