InsightsCategory: Guides
Estimating software for machining: what to check
Part 9 of 9 in the series Costing and quoting
Short answer
Judge estimating software for machining on seven points: drawing and model, your own machines and rates, traceable lines, quantity breaks, versions and revisions, export and integration, and your data. Test each one in the demo on a drawing you have already quoted. If every line traces back to a time, a rate and a quantity, the price holds up.
On this page
What should you compare estimating software on?
Comparing screens and licence prices is easy and tells you little. The question that matters is narrower: does the package price a drawing from your shop the way you would, and can you check the result. The table makes that question testable.
Subduxion makes Blake, so this guide is not neutral about Blake. It is neutral about the rest: no brand names, and every point applies to any package, a spreadsheet included.
| Point | What it comes down to | Ask in the demo |
|---|---|---|
| Drawing and model | STEP model and PDF drawing together, with the drawing's requirements. | Which values come from the drawing, and how do I correct one? |
| Your machines and rates | Envelope, axes and an hourly rate per machine. | Can you enter one of my machines and show which limit decides? |
| Traceable lines | Time, rate and quantity on every line, so a colleague can check it. | Where does this figure come from, and who confirmed it? |
| Quantity breaks | A price per part at each quantity, setup and programming spread over the batch. | What does the price per part do between 1 and 50 off, and why? |
| Versions and revisions | A new revision or repeat order builds on the last estimate. | What happens to the estimate at a new drawing revision? |
| Export and integration | The quote reaches the customer and your ERP without retyping. | What format does the quote leave in, and what can my ERP read? |
| Your data | Your drawings and rates stay yours, and you know where they are held. | Who can see my drawings, and can I take my data with me? |
What kinds of estimating software are there?
Machining shops run into five kinds, and the main difference is where the estimate starts.
A shop with steady repeat work and fixed routings prices well from its ERP. A shop that gets new drawings every week starts at the part. The instant-quote portal starts at the wrong end: at the buyer's upload, with machines, rates and setups that count only as far as the portal knows them. Take such a price as your own and a part that needs a third setup is priced like a part with two, and that difference comes out of your margin. Where a spreadsheet works and where it strains is covered in Excel estimating: where it works, where it strains.
Alongside those five sits a kind on your customer's side: should-cost software for purchasing and engineering. A buyer uses it to work out bottom-up what a part ought to cost, from material, operations, machines and rates. US federal acquisition rules define a should-cost review as a cost analysis that will not take a supplier's past costs as proof of efficiency, and so examines its workforce, methods, materials and equipment directly. With such a model, the buyer can ask at every line of your quote where your time or rate differs.
| Kind | Where the estimate starts | What to ask |
|---|---|---|
| Spreadsheet | With your own formulas and a copy of the last estimate | Who can read the file after its author leaves |
| Estimating in the ERP | With an item, its bill of materials and routing | Who creates that routing for a new part |
| CAD or CAM add-on | With the model or the program | Whether there is a price before anyone programs |
| Instant-quote portal | With an upload from the customer | How far your machines, rates and setups carry through |
| Workspace around the part | With model, drawing, requirements and revision together | How you confirm or correct a proposal |
Does the package work from your drawing and your model?
A request comes in as a STEP model with a PDF drawing. The model carries the shape, the drawing the requirements: tolerances, surface roughness, material, finishing and the threaded holes. A 2016 US report for NIST describes the same practice: many smaller suppliers still get either a fully dimensioned 2D drawing, or a 3D model with the requirements on a separate 2D drawing.
A package that reads only the model is pricing half the request. Even together, model and drawing do not fix the route. Subduxion describes how two capable shops can turn the same drawing into two different plans, both valid, since each has its own machines, tooling and way of setting up. Route, setup time and margin should therefore come from your shop, not from an average inside the package.
In the demo the test is simple: which values come from the drawing, and how do you correct one? A proposal you confirm is a different thing from a value that vanishes into a formula.
Can it price with your own machines and rates?
A cost based on an average set of machines is somebody else's cost. Good estimating software works with your machines: envelope, axes and an hourly rate for each. A 5-axis operation then lands on the 5-axis machine, at that machine's rate.
Fitting the envelope does not make a machine suitable. Each operation also has to be reachable, there has to be tooling for it, the setup has to hold the workpiece and the dimension has to stay within tolerance. That is why Subduxion describes machine selection as a reasoning problem rather than a database lookup.
In the demo, enter a machine from your own floor and see which limit decides: the X travel, the fourth axis or the rate. Building that rate is covered in How do you calculate a machine hour rate?.
Can you check every line?
Two cost engineers pricing the same part often arrive at two prices. That is no disaster if you can see where they part ways. For that you need a cost build-up: material, machining, finishing, setup and programming as separate lines. Each line then carries its line inputs: the time, the rate and the quantity it calculates with.
Ask where each figure comes from. Provenance means the drawing, your catalogue or a colleague, plus who confirmed it. A calculated time should read as an estimate until a measured time stands beside it. Why that label matters is covered in Four cycle times for the same part.
In the same demo, have a quantity break priced at 1, 10 and 50 off. Setup and programming time fall once per batch, while cycle time counts per part. A package showing a lower price per part at 50 should show how much of that comes from the one-off time.
What happens at a new revision or a repeat order?
A customer sends revision C of a drawing you quoted at revision B. One dimension has changed and a hole has been added. In a good package the revision B estimate still sits beside the new one, and you can see which lines the change moves.
A repeat order works the same way: you want last time's cost, quantity and rate. Every quote version that went out should be kept with its estimate and drawing revision. In the demo, ask for the previous version of a quote, not the latest.
How does the quote get into your ERP?
CAD holds the geometry, CAM the machining strategy and the ERP the orders, material and cost. Subduxion's research on the data gap describes how each of those systems holds only part of the picture, and how connecting them still does not explain why a manufacturing engineer chose one route over another. Estimating software sits in between; the question is how the quote gets out without retyping.
Ask two things: your ERP supplier which import it supports, and the software supplier which export it provides, in what format and with which fields. An export to CSV and JSON that your ERP can read is in use sooner than a link still to be built.
Ask about your data in the same conversation: where your drawings and rates are held, who can see them and how you take them with you if you switch. An export you can read yourself is also your way out.
Which promises deserve a closer test?
Subduxion's research separates two steps: finding a hole in the model, and working out what that hole demands of the operation. The second is the hard one. So test above all what the package does after recognition: whether it prices with your own machines and rates, and keeps a correction on record with its reason.
Milling and wire EDM remove material in physically different ways: one with a cutting tool, the other with electrical discharges. Subduxion argues that a single model cannot cover every process in the same way. So ask per process what the package calculates, and how.
In Blake
You upload STEP and PDF files; Blake pairs model and drawing per part by file name and sets out the drawing's material, tolerances, roughness, finishing and threads as proposals you confirm or correct. The estimate for milling, turning, mill-turn, drilling and tapping comes in separate lines for material, machining, finishing, setup and programming, priced at your own hourly rate per machine and labelled as an estimate. At every quantity break the one-off setup and programming time sits beside the time per part, so you see how much of the price per part at 50 off comes from that one-off time. For each machine in your registry Blake checks envelope and axes and shows the limit that decides. Correct a line and Blake records who did it, when and why. When a part comes back, Blake sets it beside its last priced calculation, and every quote version goes out as a PDF, with CSV and JSON for your ERP or spreadsheet.
Frequently asked questions
What should I ask in an estimating software demo?
Have the supplier price a drawing you have already quoted, and ask for the time, rate and source behind every line. Then have a revision and a quantity break priced, ask what format the quote leaves in, and set the result beside your estimate.
How is an instant machining quote different from an estimate?
An instant quote is a price that a quoting portal shows straight after an upload, usually to the buyer. An estimate is what you build as the supplier, with your own machines, rates and setups, in lines a colleague can check.
What is the difference between should-cost software and shop estimating software?
Your customer's purchasing or engineering team uses should-cost software to work out what a part ought to cost. As the supplier, you use estimating software to build your own price. Traceable lines show where your time or rate differs from their model.
Does estimating software work with my ERP?
That depends on what your ERP can read in. Ask your ERP supplier which import it supports and the software supplier which export it provides. Blake issues a quote version as a PDF, with CSV and JSON for your ERP or spreadsheet.
Can we share drawings under an NDA?
Yes. We agree confidentiality terms first; only then do you share drawings. The demo uses our own example part.
Can software decide the route and the price for me?
No. Software calculates and proposes; the manufacturing engineer chooses the route and the cost engineer or owner sets the price. Good estimating software shows the inputs on every line, so you confirm or correct a proposal and the decision stays on record with its reason.
Sources
- Subduxion Research, The manufacturing data gap between CAD, CAM, ERP and the shop floor, September 2026 (opens in a new tab)
- Subduxion Research, Why machine selection is a reasoning problem, not a database lookup, September 2026 (opens in a new tab)
- Subduxion Research, Why one AI model cannot understand milling, EDM and sheet metal the same way, September 2026 (opens in a new tab)
- Fischer, Rosche and Trainer for NIST, Investigating the Impact of Standards-Based Interoperability for Design to Manufacturing and Quality in the Supply Chain, NIST GCR 15-1009, December 2016 (opens in a new tab)
- Subduxion Research, The answer depends on the factory, August 2026 (opens in a new tab)
- Subduxion Research, Why manufacturing AI cannot understand a part from STEP alone, September 2026 (opens in a new tab)
- Acquisition.gov, Federal Acquisition Regulation 15.407-4, Should-cost review, March 2026 (opens in a new tab)