AI-Powered Quoting for
CNC Manufacturing
Our client is a 12-person machine shop where the owner was the sole estimator — every quote built manually on spreadsheets, every RFQ answered by one person. Slow quotes meant lost deals. We built an AI quoting pipeline that extracts geometry from CAD files, runs ML-driven cost estimation against historical job data, and delivers operator-reviewed quotes into the ERP — cutting turnaround from days to under 24 hours. The result: ~22% revenue growth in year one, one $62K deal won through AI-recommended tooling changes, and zero new hires.
- CAD geometry extraction — automated feature recognition from STEP and IGES files feeds dimensional data directly into the cost model
- ML cost estimation engine — trained on 3+ years of historical job data, material costs, machine time and tooling wear to predict quote prices
- Operator review dashboard — machinists validate AI-generated quotes, adjust tolerances and flag edge cases before anything reaches the customer
- ERP integration — approved quotes flow into the shop’s existing system as work orders with BOMs, routing sheets and material reservations
The Quoting Bottleneck
The client — a twelve-person shop running three-axis and five-axis mills, lathes and wire EDM — does good work. But the owner was the only person who could estimate jobs — reading drawings, mentally decomposing geometry into operations, checking material stock, guessing setup time, and typing a price into a spreadsheet attached to an email. Every quote took one to three days. During busy periods, RFQs sat unanswered for a week.
The math was brutal. Prospects who needed parts in two weeks would not wait three days for a quote. They would send the same drawing to five shops and go with whoever responded first. Alpine was losing deals not because their prices were wrong, but because their prices arrived too late. The owner knew this. He also knew he could not hire a second estimator at his scale — the overhead did not justify itself for a 12-person shop. He needed a system that could do 80% of the estimating work so he could focus on the 20% that required his judgment.
We scoped the project around that constraint: build a pipeline that ingests CAD files, extracts the geometry and features that drive cost, runs a trained model against historical job data, and presents a draft quote for human review. The owner stays in the loop on every quote — but instead of building each one from scratch, he reviews and adjusts a machine-generated estimate. The bottleneck shifts from creation to validation, and validation is fast.
AI Quoting Pipeline Architecture
The pipeline follows a five-stage flow: CAD file ingestion accepts customer drawings, AI geometry extraction decomposes parts into machinable features, ML cost model predicts price from historical data, operator review gives machinists final say, and ERP export turns approved quotes into work orders.
Solution Components
What We Learned
The estimator bottleneck is a revenue ceiling, not a staffing problem
Alpine’s owner thought he needed a second estimator. He did not. He needed to stop being the bottleneck. The real problem was not that quotes took too long to build — it was that every quote required the same person. When that person was on the shop floor, on vacation or handling an urgent customer call, the quoting queue stopped. We reframed the project around throughput: the goal was not to replace the estimator but to give him a draft he could review in five minutes instead of building from scratch in two hours. The ~22% revenue growth came not from better prices but from responding faster and quoting more jobs.
Historical job data is the real asset — most shops do not know they have it
Alpine had three years of completed job records in their ERP — material consumed, machine hours logged, setup times, scrap rates, actual vs. quoted prices. Nobody had ever treated this data as a training set. We spent the first two weeks of the project cleaning and structuring it: normalizing material grades, mapping machine codes to cycle-time categories, and linking quoted features to actual production outcomes. That structured dataset became the foundation for the ML cost model. The model is only as good as the historical data, and most shops are sitting on gold they have never mined. The data cleaning phase is not overhead — it is the project.
CAD parsing is the hardest engineering problem in the pipeline
Extracting machinable features from a STEP file is not a solved problem in the general case. Holes, pockets and planar surfaces are straightforward. But compound curves, draft angles, thin walls and features that require five-axis access push the parser into territory where heuristics break down. We built a feature-recognition layer that handles the common 80% of Alpine’s part geometries reliably and routes the remaining 20% to the operator with a low-confidence flag. The temptation is to chase 100% automation. The correct approach is to handle the common cases well and make the edge cases visible, not hidden.
Confidence scores change how operators interact with AI estimates
Early prototypes showed a single price. Operators either trusted it or did not. Adding a confidence interval and a per-feature breakdown changed the dynamic entirely. When the model says a quote is $4,200 with 92% confidence, the machinist glances and approves. When it says $4,200 with 68% confidence and flags the surface-finish estimation as uncertain, the machinist digs into that specific feature and adjusts. The confidence score turned the dashboard from a take-it-or-leave-it system into a collaborative tool. Operator override rates dropped from 40% in the first month to under 15% by month four — not because we forced compliance, but because the model got better and the operators learned where to trust it.
The $62K deal: AI as a competitive advantage, not just efficiency
One RFQ came in for a batch of aerospace brackets. The customer had spec’d three-axis machining. The AI cost model flagged that a five-axis approach would reduce cycle time by 35% because it eliminated two setups and improved tool access to undercut features. The operator confirmed the recommendation, and Alpine quoted the job at a price the customer could not match elsewhere — because competing shops were quoting the slower three-axis approach. Alpine won the $62K contract. This was not a quoting-speed win. It was an engineering-insight win that only happened because the AI could evaluate alternative manufacturing strategies faster than a human estimator scanning a drawing.
Related use cases: Fleet Driver Management & Compliance Platform • AI Data Automation — Vendor Onboarding & Retail Pricing
Who Needs This
AI-powered quoting automation fits any manufacturer where estimating is a bottleneck, historical job data exists but is not leveraged, and quote speed directly impacts win rate.
FAQ
A system that reads CAD files, extracts machinable features (holes, pockets, surfaces, tolerances), runs a machine-learning model trained on your historical job data to estimate cost, and presents a draft quote for operator review. The operator stays in the loop — the AI handles the repetitive estimation work so the estimator focuses on judgment calls and edge cases.
Accuracy depends on your historical data quality and part complexity. For the client, the model reached an operator override rate below 15% within four months, meaning 85% of AI-generated estimates were approved without modification. Every quote includes a confidence score so operators know exactly where the model is certain and where it needs human judgment. The model retrains monthly as new completed jobs feed back into the dataset.
The pipeline handles STEP (.stp/.step), IGES (.igs/.iges) and DXF files natively. STEP is the preferred format because it preserves full 3D geometry with tolerance annotations. 2D drawings in DXF or PDF are supported for simpler parts. Adding native SolidWorks (.sldprt) or Fusion 360 export support is an extension we have deployed for other clients.
A minimum of 18 months of completed job data with material costs, machine hours, setup times and actual vs. quoted prices. More is better. Alpine had three years, which gave the model enough variance across materials, complexities and batch sizes. The first phase of every engagement is data cleaning and structuring — normalizing material grades, mapping machine codes to cycle-time categories, and linking quoted features to actual production outcomes.
Yes. Every AI-generated quote passes through the operator review dashboard before reaching the customer. The machinist sees the feature breakdown, predicted machine time per operation, material cost, tooling recommendations and confidence score. They can adjust any parameter, override the price, or flag the job for full manual re-estimation. No quote leaves the shop without human approval.
The integration layer is API-driven, not vendor-locked. Alpine uses a standard manufacturing ERP, but the same pattern works with JobBOSS, E2 Shop System, ProShop, Epicor, Global Shop Solutions or any system that exposes work order and BOM APIs. Adapting to a new ERP means mapping the quote output schema to the target system’s import format — not rewriting the pipeline.
A typical deployment runs 10–14 weeks: two weeks for data cleaning and structuring, three weeks for the CAD parser and feature extraction, three weeks for the ML model training and validation, two weeks for the operator dashboard, and two weeks for ERP integration and end-to-end testing. The timeline depends on data quality, part complexity range and ERP integration depth.
Python for the ML pipeline and CAD parsing (using Open Cascade via pythonOCC for STEP/IGES geometry extraction), scikit-learn and XGBoost for the cost estimation model, FastAPI for the backend, a React-based operator dashboard, PostgreSQL for job history and quote audit logs, and REST APIs for ERP integration. The entire stack runs on standard cloud infrastructure with no GPU requirements for inference.
Yes. The quoting bottleneck is actually more painful at smaller shops (where the owner is the sole estimator) and at mid-size shops (30–80 people) where quoting volume outpaces the estimating team. Larger operations benefit from the analytics layer — tracking quote-to-win ratios, estimation accuracy and identifying where manual overrides reveal model gaps. The core architecture scales in both directions.
Need a Team That
Builds This?
This project was delivered by our AI & ML engineering team. If your shop is losing deals because quotes take too long, we’re happy to walk through the architecture.
Book a Technical Call