Check a customer RFQ for what you can make before sales quotes it
Give Claude the RFQ package. It lists every part and requirement, checks each against what your shop can make, and writes the questions for the customer before anyone puts a price on it.
FullEngineeringWhen you need it
Set it up4 steps
Open the Claude desktop app and sign in with the Claude account you use for work. On a personal Free, Pro or Max plan, chats can be used for training unless you switch off SettingsPrivacyHelp improve Claude.
No account yet? Ask your manager.
Where things are in Claude
- CustomizeConnectors In Claude's left sidebar: connect your email and files.
- /schedule Type it in a new Cowork task to run a prompt on a schedule.
- Scheduled In Claude's left sidebar: what runs, to pause or change it.
- Write a "What we can make" document in your Engineering folder: your processes and machines with their sizes and limits, the materials you work, the tolerances you hold in series production, what you send out (heat treatment, plating), your test equipment and certificates. Claude checks every RFQ against it.
- Connect Google Drive under CustomizeConnectors. Keep this workflow's files in one Drive folder called Engineering.
- When an RFQ comes in, save the whole package in an RFQs folder inside your Engineering folder: the letter, part list, drawings and specifications. Open Cowork, paste the prompt and name the package.
- Confirm every [CHECK] yourself, then hand the review to sales with your answers. The questions go to the customer from you or sales.
Set this up on your computer: the Claude desktop app runs it.
The prompt
- Check the customer RFQ named below, in the RFQs folder inside my Engineering folder, before sales quotes it. Judge it against the "What we can make" document in my Engineering folder.
- 1. List every part in the RFQ: part number, revision, material, yearly volume and lot size, as the RFQ gives them.
- 2. For each part, the requirements that decide whether we can make it: size and weight, the tightest tolerances and every characteristic marked special or critical, the material and its certificate, heat or surface treatment, tests, and the documents asked for (sample approval, material data, inspection reports). Name the drawing or clause each one comes from.
- 3. Mark each part "we can make it", "we can make it with an outside process" (name the process), "we cannot" (say why) or [CHECK: what an engineer must confirm]. Anything the "What we can make" document does not cover is [CHECK], never yes.
- 4. What sales needs before quoting: new tooling, fixtures or gauges, outside processes, tests we cannot run, and anything that would make the lead time longer than usual. Name no prices.
- 5. Questions for the customer: everything missing, unclear, or different between the RFQ letter, the drawings and the specifications, numbered, each with the document it concerns.
- Write it as a Google Doc in the same folder. Use only what the package and our document say. Never invent a capability, a tolerance or a lead time.
If your company keeps technical drawings out of AISafe version
Reads the RFQ letter, the part list and the specification text, never the drawings. Every dimension and tolerance check is left as a [SEE DRAWING] line for the engineer.
What you get
One review per RFQ: each part marked can make, can make with an outside process, cannot or to check, what sales needs before quoting, and the questions for the customer.
Learn how
Get this workflow for your team
Two minutes each: everyone gets a plan of ready workflows like this one, inside your company's rules.
Your manager sees progress and hours. Never what Claude reads or writes.
FirstPrompt's workflow library adapts parts of Anthropic's knowledge-work-plugins (Apache-2.0), rewritten by FirstPrompt. Source and licence