Guides / Operating gaps
Every operation quotes differently. Most of a quoting tool is the same everywhere. The part that isn't is your pricing logic, and that has to be yours. Written by someone who quoted machined parts for a living.
Ask ten manufacturers how they quote and you get ten answers. One prices off bar consumption per thousand. One prices off nest utilization and pierce count. One prices off rack space and load weight. One is quoting a project with a tryout and a sampling run at the end of it, not a part at all. Nobody's wrong. They're just not doing the same arithmetic, which is exactly why generic quoting software so often gets bought and then quietly abandoned.
I owned and ran a machine shop for the better part of a decade before I built software for one. Quoting was the thing that ate the week, and it wasn't because estimating is hard. It was because everything around the estimate was manual, and because the logic that made our prices ours lived in one person's head and in a spreadsheet only he maintained.
Here's the honest shape of it, and it's the reason a tool like this doesn't have to cost what you think.
Most of a quoting tool is the same no matter what you make. Requests arrive and something has to catch them. Drawings and documents have to be read and the numbers pulled off them. Parts, customers and revisions have to be tracked. Quantities and quantity breaks. Versions, because the customer will change something. Approvals before it goes out. A record of what you sent and what happened to it. Search, so you can find last year's quote. Users and permissions. That machinery already exists, it's already built, it's already running in production, and you are not paying anyone to write it again.
The part that isn't the same is your pricing logic, and it is the entire reason the tool is worth having. Your material formulas. Your work centers and their rates. Your setup rules. Your minimums. Your outside processing vendors and their real lead times. The quality requirements that scale with the customer rather than the part. The judgment calls you make that nobody wrote down. That part gets built around how you actually do it, and it's sized to that. Never more than you need.
That's the trade in plain terms. The common machinery is already paid for. The specific part is what gets specced, and you spec it.
This is the part generic software gets wrong, so it's worth being concrete. A few examples of what "your pricing logic" actually means, depending on what comes through your door.
None of those are exotic. They're just different, and a tool that assumes one of them cannot serve the others without somebody fighting it every day.
Rather talk it through than read the rest? Email me. First call's on us. No cost, about 30 minutes, a straight conversation, not a demo.
A fab quote lives or dies on the sheet. Not on the finished weight of the part, which is the number the model hands you, but on how much material you actually have to buy to get that part out. Get the nest wrong and no amount of care on the labor side saves the job. What belongs in the quote:
Where fab quotes leak most often: material priced off part weight, last quarter's metal price honored this quarter without anyone deciding to, secondary labor under-quoted because each piece of it is small, and actuals that never make it back to the estimator, so the same part gets quoted off the same wrong number every time it comes back. And answering late. The first credible quote on a buyer's desk gets the attention.
Most laser quotes are built on two numbers: how long the head is moving, and a machine rate somebody picked a few years ago and nobody has revisited since. The first number is usually close to right. The second one is where the money goes missing.
An hourly rate that was set when the machine was new, before the current gas contract, before the last maintenance agreement, and before power prices moved, is not a rate. It's a habit. Because it multiplies every quote that touches that machine, it's the number that moves the most money in the building and the one nobody owns. Working out your own is tedious rather than hard, and the method is the same one in working out your wire EDM cost per hour, with the consumables swapped.
Waterjet is the one process where the same geometry, in the same material, at the same thickness, can honestly be quoted at wildly different prices, and both numbers can be right. Cut fast and the edge comes off rough, with visible striations toward the bottom and more taper. Slow the same cut down and the edge cleans up. The difference between the roughest usable finish and one you could hand a customer without apologizing is not a small percentage. It is a multiple.
Prints often say nothing about edge finish, so the estimator picks one in their head and the operator picks a possibly different one at the machine. When those two picks disagree, either you gave away hours you never quoted or you shipped an edge that comes back. Neither shows up as a quoting problem in the numbers. It shows up as a job that ran long, and it gets blamed on the floor. The fix is not clever software. It is making the choice explicit on the quote, so the number that went to the customer and the setting used at the machine are the same decision, written down once.
On laser and waterjet both, what you bought is a sheet or a plate, not the part's weight, and a part that nests well with the rest of the order costs less than the same part standing alone.
There are platforms that read a model and tell you how long the part takes to run. If that's what you're shopping for, buy one of those, and I mean that without any edge on it. Run time depends on your machines, your tooling, your fixturing and how your people actually run the job. On a laser or a waterjet it's your nozzle and gas, or your pump pressure, your abrasive and the edge you mean to deliver. A number that comes from somebody else's assumptions is a number nobody in your building will stand behind, and the first time it's wrong on a real order it stops getting trusted at all.
What I'll do instead is stop your estimator working out something you already know. In the build that's running in production today, when a part number comes up the tool goes and reads what that part actually took on the jobs that have already run it, operation by operation, out of the ERP. It matches on your part number even when the customer calls it something different. That isn't a prediction. It's your own history put in front of the person quoting, at the moment they need it, and it can't be wrong the way an estimate can be wrong.
The estimating judgment stays with your estimator. That's the part that wins or loses money and it should stay with a person who knows the work.
Requests land in a shared mailbox and that arrival is the trigger. The system reads what it can out of the request and the attached drawings: quantities, part numbers, descriptions, material, and the callouts for plating and heat treatment. It does the reading, the extracting and the typing so the estimator doesn't.
From there it's their call. They set the routing and the costing, the part that needs someone who knows the operation. Before a quote can go out, the system checks that every line actually carries the costs it's supposed to, so nothing slips out un-costed because somebody was moving fast at four thirty on a Friday.
Built around your trade, that check covers the lines that usually get dropped: deburr and hardware on a fab job, gas and handling on a laser job, abrasive and the edge quality on a waterjet job.
Alongside it sits a smaller automation that watches the inbox, builds the folder structure, and files the request, the drawings and the finished quote, working on top of the Microsoft 365 you already run. Quoting gets faster and nothing ends up lost in one person's inbox.
I'd rather lose your interest now than your trust later.
The two options most manufacturers get offered are a spreadsheet or a per-seat enterprise subscription with a hundred features they'll never touch. There's a middle, and it's the one I build.
A paid half-day first, $2,500, at your place or over video. AI reads, drafts, and remembers what your people know. It is not exact, and it does not run your systems. So we go through the jobs eating your week, including how your quoting runs today, and sort them: the reading, writing and know-how AI can genuinely help with, and the parts that need a tool built because the answer has to be right every time. Your people leave able to write skills themselves. A skill is your way of doing a job, written down so the AI follows it instead of guessing. Whether AI, a small build, or nothing at all is the honest answer, I'll say so. Written document within two working days. Then a Build that's priced up front, so you know the number before it starts, and it's scoped to the part that's yours rather than to a feature list. I host and run it on managed infrastructure that works on top of the systems you already use, and there's an ongoing care plan after that keeps it running: hosting, monitoring, fixes, and small adjustments as your work changes. Term and price by agreement.
No hourly meter and no per-seat license. And to say the affordability part plainly: the common machinery already exists and you're not funding it a second time. What gets built is the part that's specific to you, and the price follows that scope rather than a seat count that grows every time you hire.
Everything described above is deployed and running for a mid-size manufacturer: request intake and extraction, the history lookup that reads what a part actually ran, the completeness check before a quote can leave, and the auto-filing that keeps requests, drawings and finished quotes from getting lost. See how it's built.
See the quoting tool, screen by screen →Everything that touches your price. The common machinery is fixed because there's no value in re-deciding how a version history works. The rest is yours to spec: the formulas, the rates, the rules, the minimums, the vendors, the approvals, what the quote document looks like when it lands on your customer's desk. If your logic changes next year, it changes in the tool.
No. The build is scoped to what you need, so a simpler operation gets a smaller build. What decides whether this is worth doing isn't your headcount, it's how much of your week disappears into quoting and how much work you're not quoting because there aren't hours to do it.
It's built to work on top of what you already run. I've built and deployed standalone connectors to ERP and accounting systems so tools read and write without anyone re-keying. Which specifics apply to you is something I work out before quoting, and I'll give you a straight answer rather than a maybe.
No, and it shouldn't. Their judgment on routing and costing is the part that wins or loses money. The tool takes the reading, extracting and typing off their plate so they spend their hours on the call only they can make, and it checks the quote is complete before it goes out.
It changes what matters. Contract cutting lives on turnaround, on minimum charges, and on quoting the same way twice for a repeat customer. That's a smaller build than a full routing and costing system, and it should be priced like one.
Common, and it's one reason generic software struggles. The processes price differently enough that one set of logic can't serve them all honestly, so the tool carries each one without any of them being an afterthought.
Then your pricing logic is the asset, and it's the part worth writing down. The reason isn't the software. It's that the operation shouldn't depend on one person being available to price the work.
If you need the full enterprise feature set, do, and I'll tell you so on the first call. For a lot of operations the honest answer is that they need their own quoting done faster, not a platform, and they'd be paying a subscription forever for the ninety percent of it they never open.
Where this connects to everything else. A quote is only as good as what the last one really took, which is why those numbers often aren't trusted. When the quote turns into an order, the next gap is usually customer POs being keyed in by hand, and then vendor acknowledgements nobody is watching. If you quote whole machines rather than parts, that's a different estimating animal. Two specific corners have their own notes: working out your wire EDM cost per hour and what the quality requirement really costs in first article inspection and ballooning.
First call's free. About 30 minutes, a straight conversation about how your quoting actually runs today, from request to PO, not a demo. If a right-sized build is worth doing, I'll say so. If you're better off with something off the shelf, I'll say that too.