---
title: "Forty RFQ Packets a Week, One Estimator: In 2026 You Hand Over the Quote, Not the Drawing Package"
description: "One estimator, 38 RFQ packets a week, half of them never quoted. What Claude Cowork and ChatGPT Work change about aerospace build-to-print quoting in 2026."
canonical: https://callsphere.ai/blog/forty-rfq-packets-a-week-one-estimator-in-2026-you-hand-over-the-quote
category: "Industry Solutions"
tags: ["aerospace suppliers", "build-to-print machining", "rfq quoting", "claude cowork", "itar compliance", "as9100"]
author: "CallSphere Team"
published: 2026-06-09T15:08:32.000Z
updated: 2026-07-25T23:21:41.835Z
---

# Forty RFQ Packets a Week, One Estimator: In 2026 You Hand Over the Quote, Not the Drawing Package

> One estimator, 38 RFQ packets a week, half of them never quoted. What Claude Cowork and ChatGPT Work change about aerospace build-to-print quoting in 2026.

## 7:15 a.m., and there are already nine packets in the portal queue

The estimator gets in before anyone else because that is the only quiet hour in the building. He opens Exostar for the Boeing-side packages, then the prime's own supplier portal for the Northrop work, then the sales inbox where second- and third-tier requests arrive as plain email with a zip file attached. Nine new request-for-quote packets since Friday. Each is a drawing in PDF, a bill of material, two pages of quality clauses, a note that the order will carry a DO-A7 rating under the Defense Priorities and Allocations System, and thirty-odd pages of terms nobody has read end to end since 2019.

By noon he will have priced two. Two more go out Thursday. The rest get no-quoted, and the no-quote is not a decision anybody made — the calendar made it. Every build-to-print owner knows that number and hates it: the bids you never sent.

Walk the job honestly and you see where the hours go. Read the notes block, find every specification callout: AMS 2759 for heat treat, AMS 2700 for passivation, MIL-DTL-5541 Type II Class 3 for the chem film. Check whether your outside processor's NADCAP accreditation actually covers that process at that class — not the one next to it on the scope sheet. Build a routing in Epicor Kinetic or JobBOSS² or E2 with setup hours, cycle times, in-process inspection and the AS9102 first article nobody ever costs properly. Email the metal house for a price on 15-5PH bar and wait a day. Email the anodizer. Then apply your burden rate. Two and a half hours on a simple machined detail; a day and a half on a small assembly with six purchased components and a torque-and-lockwire operation.

The distortion this creates is worse than the hours. You quote what is easy to quote: repeat part numbers get priced Tuesday, and the unfamiliar package with two special processes sits until it expires. Your mix drifts toward whatever your estimator can price fastest, which is not the same thing as whatever your shop makes money on.

The 2026 change worth an owner's attention is not that a chat window can read a drawing note. It is that you can now hand over the whole errand. **An agent that hands back finished work is software you give a goal to — "price this package by Thursday" — which then opens your files and systems, does the steps in order, and puts a finished quote packet on your desk, instead of answering one question at a time and waiting for you to think of the next one.**

## What actually changed: 12 January and 9 July 2026

Claude Cowork landed on 12 January 2026 and reached web and mobile in July. ChatGPT Work followed on 9 July 2026, running on GPT-5.6. Same idea from two directions: you state a goal, connect it to your files and applications, it works on its own for a stretch — sometimes hours — and hands back a finished artifact. Both were aimed squarely at people who do not write software, which in a machine shop means the estimator, the buyer, the quality manager and the contracts administrator.

The 2024 version could summarize a drawing note if you pasted it in. The 2026 version opens the drawing PDF, the spec list, your process capability sheet and your last four quotes for that customer, and produces the routing and the cost sheet in the format your ERP wants, plus a page of exceptions it wants you to look at. The practical proof is that the output is a document, not a paragraph.

```mermaid
flowchart TD
  A["RFQ packet lands in the supplier portal"] --> B["Agent reads drawing notes and spec callouts"]
  B --> C["Agent drafts routing in the ERP format"]
  C --> D{"Every process covered by a current NADCAP source?"}
  D -->|No| E["Agent flags the gap, drafts the outside-processor RFQ"]
  D -->|Yes| F["Agent pulls material price and builds the cost sheet"]
  E --> F
  F --> G["Estimator reviews, sets margin, releases the quote"]
```

## A Tuesday on the new way: goal in at 7:20, packet back at 11:40

The estimator does not open nine packets. He selects all nine and writes one instruction: price these against our standard burden, use current metal quotes if under fourteen days old, flag anything needing a process we are not approved for, and list every flowdown clause that differs from what we accepted last time from this customer. Then he goes to the production meeting.

By late morning there are nine draft packets. Each carries a routing he can read, a material line with the distributor and the date of the price, a first-article line with hours in it, and — the part that matters most — a short exceptions page. Package four: the note block calls for shot peen to AMS 2430 and your approved peening source lapsed in April. Package seven: the terms require source inspection at final where the last three orders from that customer did not, which changes inspection hours. Package nine: the drawing is one revision behind the revision named in the purchase order text.

That last one is the whole argument. A junior estimator misses it, you cut chips to revision H, and you find out at first article that the customer bought revision J — a corrective action and a no-charge rework on a job you underbid.

What the owner has to change is the harder half. You stop assigning tasks and start writing definitions of done. "Quote this" is not a goal; it is a wish. Write it down once: every spec callout with its approved source and accreditation date, material priced within fourteen days, first article hours included, exceptions listed separately, nothing sent to a customer without a human signature.

## The arithmetic: thirty-eight requests a week and the ones you never answered

Illustrative assumptions, not a case study. Substitute your own quote log from last quarter.

| **Assumption** | **Today** | **With the agent drafting** |
| --- | --- | --- |
| RFQ packets received per week | 38 | 38 |
| Packets actually quoted | 22 | 32 |
| Estimator hours per quote | 2.6 | 0.8 (review and price only) |
| Estimator hours per week | 57.2 | 25.6 |
| Loaded estimator cost at $52/hour | $2,974 | $1,331 |

The labor line saves about $1,643 a week, which is real and is not the point. The point is the ten extra packets. Assume a conservative 12% hit rate on those marginal bids — lower than your house average, because these are the unfamiliar ones — an $8,400 average job and a 26% gross margin. Ten extra quotes at 12% is 1.2 jobs, roughly $10,080 in revenue and about $2,621 in gross margin per week, against a seat cost in the low hundreds per month.

Prove it the way you prove a process change: keep an eight-week quote log with three columns — received, quoted, won — and compare it to the same eight weeks last year. The number you are testing is whether more bids left the building.

## The part that stops shops cold: ITAR, CUI and where the drawing is allowed to go

This is where an aerospace supplier is different from a sign shop, and it is not optional. If the drawing is technical data controlled under the International Traffic in Arms Regulations, putting it into a general-purpose service is an export the moment a foreign person can see it. If the contract carries DFARS 252.204-7012, the drawing is controlled unclassified information and has to sit somewhere that meets NIST SP 800-171 — and your CMMC Level 2 assessment will ask exactly where it sat.

Practical answer: start on commercial work. Quote the non-controlled packages first, get your definition of done stable, and keep controlled packages on the manual route until the vendor gives you a written answer about where the data is processed and stored, in a form your export compliance officer and your assessor accept. Anthropic's 2 July 2026 governance update — spend limits, alerts, per-user entitlements — matters here for the reason people miss: it records who was allowed to use what, which is what an assessor asks to see.

## Where you still need the estimator standing there

The margin call does not transfer. Whether you bid this customer at 24% or 31% is a relationship judgment: how they pay, whether they short-run you, whether this part opens a family of part numbers, whether the government fiscal year closing on 30 September means they need you badly in eight weeks.

Neither does capacity truth. The agent will happily produce a routing needing your Swiss lathe for eleven days in a window already committed. Your shop foreman knows what is really on the floor; the finite schedule in the ERP usually does not.

And neither do the ugly parts — thin-wall titanium with true position on a bore you can reach one way, or a weldment that warps at heat treat. That memory lives in your programmer and your material review board history. Feed it in as your own notes and the drafts improve; do not expect it off the drawing.

## Frequently asked questions

### Will it write into Epicor Kinetic or JobBOSS² directly, or do I re-key the routing?

Assume you export and import for now. The realistic 2026 setup is a routing and cost sheet laid out exactly like your ERP import, which one person checks and loads. Ask your ERP reseller what their agent connection looks like before you buy on the strength of a demo.

### What happens when the drawing is a scanned 1994 blueprint with hand-marked revisions?

It reads it better than it used to and still needs a human on the revision letter. Treat any hand-marked or scanned drawing as an automatic exception the estimator opens personally. That rule costs a few minutes and saves the rework job.

### Is it safe to let it email the quote to the customer?

No. Keep a human signature on anything that leaves the building with a price on it. A quote is an offer, and an offer with a wrong burden rate on a five-year agreement is an expensive typing error.

## Start Monday with the no-quote pile, not the live ones

Take the twelve packages you no-quoted last month — already dead, so they cost you nothing — and give the whole batch to the agent as one goal. Compare the drafts to what your estimator would have done. You will learn more in an afternoon than in three vendor demonstrations, without risking a live bid.

One more thing about quoting season: every extra bid generates phone calls. Buyers confirming you got the package, expediters chasing status the week before the government fiscal year closes, an AOG call at 6:40 p.m. that goes to voicemail. [CallSphere](https://callsphere.ai) builds AI voice and chat agents that answer the phone line and web chat around the clock, take the part number and need-by date, and put the message in front of the right person. It does not price your work — your estimator does that — but it makes sure the request reaches him.

---

Source: https://callsphere.ai/blog/forty-rfq-packets-a-week-one-estimator-in-2026-you-hand-over-the-quote