Ready to Work Together?
Let's discuss how our expertise can help transform your business.
Jordan Saunders
·
Jul 29, 2026
Most custom manufacturers have tried quoting software at some point. Most of them were back in Excel within a year.
That is usually where the story stalls. The software failed, so the conclusion becomes the problem cannot be solved, and the shop settles back into the spreadsheet and the two-week quote turnaround. I want to make the case that the software failed for a specific, fixable reason, and it is not the reason anyone thinks.
Quoting software — the whole CPQ category — is built on one assumption: that your product already exists. There is a catalog. There are options. Configure, price, quote. Pick the model, pick the finish, the price book does the rest.
That works beautifully if you sell configurations. If you build to order, it collapses on contact, because in a custom shop the product does not exist until the quote invents it. Every RFQ is a small act of design. There is no price book to look it up in, because the thing has never been priced.
So the estimator is not configuring. They are doing something much harder. They are reading a drawing, remembering the job from 2022 that was almost like this one but in stainless, recalling that it blew through its machining estimate because of one tolerance callout, and adjusting. That is not catalog work. That is judgment running on top of history.
And that is exactly why Excel survives every software rollout. The spreadsheet is not the problem. The spreadsheet is the only tool flexible enough to hold judgment. It bends to whatever the estimator knows. The enterprise tool demanded the shop fit its model, the spreadsheet fit the estimator, and the estimator won. Of course they did.
But look at what winning cost. All of that pricing knowledge — the actuals versus the estimates, the jobs that went sideways and why, the margins that hold for which customers — lives in one or two heads and a folder of files only they can navigate. Ask yourself how old your head estimator is. In most shops I talk to, the honest answer to what happens to our pricing when that person retires is a long pause.
The hard part of custom quoting was never arithmetic. It was messy similarity — looking at a new RFQ and finding the old jobs that rhyme with it, even when the drawings, the descriptions, and the file names have nothing obviously in common. Software could never do that. It can now. Reading an inbound RFQ, searching your own job history for the closest matches, pulling what those jobs actually cost rather than what you estimated, and assembling a draft quote is squarely inside what AI does well today.
Notice what that is not. It is not a configurator, because there is no catalog to configure from. The catalog is your history. And it is not a robot sending prices to customers. The estimator opens a draft with the comparable jobs and the real costs already on the table, corrects it, applies the judgment that is genuinely theirs, and sends it. The digging is gone. The judgment stays human.
We built exactly this for manufacturing and field services teams — if that sounds like your shop, it is worth a look at the AI Quoting Accelerator.
But get past that and something changes that is bigger than speed. The quote that took two weeks goes out in two days, yes, and the shop that answers first usually wins. The deeper win is that your pricing knowledge stops being a person and becomes an asset. The next estimator inherits a system instead of a folder. The retirement stops being a cliff.
Pull your last twenty quotes. For each one, answer three questions.
If the answers are weeks, most of them, and no — the spreadsheet is not your problem. It is your single point of failure, wearing a familiar face.
What happens to your pricing the day your estimator retires? If you do not like the answer, that is the project.
Author at NextLink Labs
AI collapsed the cost of building software. The case for always buying SaaS no longer holds — here's how to figure out which tools to keep renting and which to own.
Jordan Saunders
·
Jul 22, 2026
Buying a runtime governance tool is the easy 20 percent. Here's what the other 80 looks like — and why without it, the tool makes things worse, not better.
Jordan Saunders
·
Jul 15, 2026
Your senior people aren't slow — they're doing archaeology. Here's why retrieval is where AI should go first in your business, and what that actually looks like in practice.
Jordan Saunders
·
Jul 8, 2026
Let's discuss how our expertise can help transform your business.