Quote hit rate by customer and part family
Shows where the shop is competitive and where quoting effort is wasted.
A job shop might send dozens of quotes a month and hear back on a fraction of them. The estimator is already working on the next RFQ, so follow-up happens only for the big ones, and the rest quietly expire. Nobody records whether a quote was lost on price, lead time or a buyer who simply went with the incumbent.
We would start with your quote log, whether that lives in JobBOSS, E2, Paperless Parts or a spreadsheet, and measure how many quotes get any follow-up today. Then we would set a simple follow-up rhythm by quote size and customer, with drafted emails for inside sales to send and a short reason code recorded every time a quote closes.
Close out quotes past their validity date with a reason, and agree which statuses and fields the ERP or quoting tool will use going forward.
Larger or strategic quotes get a phone call from the estimator or owner; smaller ones get two drafted emails from inside sales at agreed intervals after sending.
Draft each follow-up from the quote itself, mentioning part number, quantity breaks and current lead time, so it reads as a useful check-in rather than a generic chase.
When a quote is won, lost or expires, inside sales records one of a short list of reasons, such as price, lead time, tooling cost or no response.
Look at hit rate by customer, part family and quote size each month, so the owner and estimator can decide where to quote harder and where to decline.
How we deliver this: AI automation for small business or fractional CTO leadership, scoped in writing and run over 90 days. See pricing or the sample scope.
Shows where the shop is competitive and where quoting effort is wasted.
The basic discipline this workflow is meant to fix.
Turns lost quotes into information about pricing and lead time.
For example, a 40-person CNC shop finds about 120 open quotes in its ERP, most of them months past validity. After closing those out, inside sales sends two drafted follow-ups for quotes under a set value, and the estimator calls on larger ones. Over the next quarter, recorded reasons show most losses are on lead time rather than price, which changes how the owner thinks about capacity. This is an illustrative scenario.
In the first 30 days we would export a year of quotes, measure follow-up and hit rate as they stand, clean the open list with your estimator, agree follow-up rules and reason codes, and draft the first templates for inside sales to test.
A short, specific follow-up that offers updated lead time or a quantity break is usually welcome, especially from a supplier they have not used yet. The rules would limit the number of touches, and buyers who say no or ask to stop are closed out. Most buyers prefer a clear answer over silence.
Not always. Many ERPs and quoting tools track quote status well enough if the fields are used consistently. A CRM such as HubSpot can help when inside sales manages many contacts and accounts, but we would only suggest adding one if the existing system cannot handle follow-up tasks and reasons.
Usually inside sales or a customer service rep, with the estimator handling technical questions and the owner calling on strategic accounts. The key is that one named person owns the open quote list and reviews it weekly, rather than leaving it to whoever has time.
Illustrative defaults for a manufacturer. Replace them with your numbers.
a month in staff time, before any lost sales
Illustration only, not a forecast or guarantee. Recovered staff time becomes a cash saving only if spending actually declines or the time goes into paid work. Tool costs are an assumption; we replace every number here with yours before recommending a scope.
Quote and estimate follow-up: full guide
In 30 minutes we look at one recurring workflow, what it costs you today and whether there is a credible case to improve it. If there is not, we will say so.
30 minutes with Phil or Martin. No technical brief, no pitch deck. Phil or Martin replies personally, usually within one business day.