A Day on the Quoting Desk

The real cost of a quote

When your salesperson can't finish a quote without pulling your programmer off the nesting desk, two things happen at once. The quote slows down — and so does production.

That programmer was mid-sequence. Thinking about how parts will unload, which way the head needs to travel, whether those parts are going to hold on the skeleton or shift mid-cut. Now they've lost that thread to answer a bevelling question.

It's tempting to hand the big line-item quotes to the junior — but those are the ones that come back. Missing allowances, processes that don't match the machine, costings that looked right until someone senior checks. Same pattern in programming. The experience gap doesn't show up in the software. It shows up in the rework.

Sales needs technical data that lives in the nesting software or the programmer's head. Until that changes, every quote costs more than the margin shows.

The enquiry lands

Big customers send clean BOMs — spreadsheets with corresponding PDFs or DXFs. Straightforward enough.

Smaller customers are a different story. Hand sketches. PDFs with handwritten dimensions. Physical templates. Multi-page assembly drawings where every part has to be located in the assembly view and matched to a BOM line by line.

Assembly drawings are the quiet time killer. A complex assembly can cost you hours — and it's a constant risk-reward calculation. Do I keep at this, or smash out ten easy ones in that time?

That's hours of experience-dependent work — and it's one of the areas where better tooling is starting to make a real difference.

Building the quote

Most shops run bespoke quoting software with costing databases. For simple jobs — standard plate, square cuts — it works fine.

Where it breaks down: bevelling. Compound bevels, K-preps, variable root faces — these require material allowances that salespeople often miss. Or worse, they quote something the machine physically can't do. Counter-sinking and tapping are the same story — easy to overlook on a busy quote, and they blow out in both time and cost when they weren't factored in.

Complex jobs mean programmer interruptions. "Quick question" turns into a ten-minute conversation, and the programmer is pulled out of flow for the second time that morning.

Most nesting software packages include built-in quoting modules. Most shops ignore them entirely and quote from a separate system. That's paying for a tool and leaving half of it in the box. The integration cost was already paid — the benefit was never claimed.

The data to fix this already exists in most shops. It's just not connected to the people who need it at quoting time.

If this sounds familiar, let's talk →

The handoff to production

Customer sends the PO. Sales converts it to a work order. Programmer picks up the job and starts pulling files.

This is where the real work begins — and where the next round of friction starts.

Getting the DXFs ready

Every BOM line needs a DXF. Sounds like a solved problem. It isn't.

PDF-to-DXF conversion is good enough to look right on screen and wrong enough to cause problems on the machine. Scaling errors. Hidden lines that show up as cut paths. Arcs converted to splines that the nesting software can't process cleanly.

The programmer goes through every file manually: checks scale against the drawing, redraws holes, cleans up arcs, strips hidden layers. On a tight turnaround, a missing file or a bad conversion doesn't surface until it's already a problem.

This is one of the areas where tooling is genuinely catching up. Not perfect yet — but closer than most people realise.

Nesting

Auto-nesting has gotten good. The software can pack parts efficiently and generate reasonable cut paths. But auto-nest quality varies, and the software doesn't know what the experienced programmer knows.

Cut direction matters. So does how parts unload — whether the operator can clear the table between cycles, whether the skeleton stays intact long enough to finish the sheet. That knowledge comes from years of walking to the workshop floor and talking to operators.

The best nesting programs augment that knowledge. They don't replace it.

Cutting to dispatch

Program goes to the machine. Parts get cut. Most of the time, everything runs as expected.

The pain point is the feedback loop. Jobs complete or they don't, and sales doesn't always find out in time. The customer calls to ask where their material is. Sales goes to check. That's when someone mentions there was an issue on the floor — hours ago.

Not a technology problem. A communication problem. But it shows up at the worst possible time, in front of the customer.

Most of the fix here is process, not software. But knowing where to look is half the job.

Where does the time actually go?

• Interpreting ambiguous enquiry drawings — hours of work on complex assemblies
• Programmer interruptions during quoting — repeated, hard to quantify, easy to underestimate
• Manual DXF cleanup before nesting — every file, every job
• Rework from quoted bevels, counter-sinks, or tapping that don't match machine capability
• Reactive customer communication when the feedback loop breaks down

None of these are unusual. Every cutting shop deals with them. The question is whether you're measuring them — and whether there's a better way through any of them.