AI on the Plant Floor

AI in Manufacturing: Real Examples of How Shops Use ChatGPT and Claude

AI in manufacturing today looks like paperwork, not robots: shops use tools like ChatGPT and Claude to draft quotes and estimates, search maintenance manuals, write quality documentation, communicate schedule changes, capture retiring veterans' know-how, and answer customer emails. This page walks through each example with copy-paste prompts.

1-on-1 with Pete Enestrom, on your actual work

Pete Enestrom

Written by Pete Enestrom

Yale & Columbia, ex-Microsoft & Intel — 1-on-1 AI coaching for executives

Pete Enestrom — executive AI coach and Zaigo co-founder

Your coach’s background

YaleCOLUMBIAUNIVERSITYMicrosoft

If you own or run a manufacturing business and you keep hearing that AI is coming for your industry, here is the honest version: the AI in manufacturing examples worth your attention right now are not robot arms or sensor networks. They are text jobs. A plant runs on paper-shaped work—RFQs, quotes, maintenance logs, work instructions, quality reports, schedule emails—and the new generation of AI tools is very good at exactly that kind of work.

This page is about what shops are actually doing with tools like ChatGPT and Claude today. No invented case studies, no company names I can't verify, no percentages from a consulting deck. These are composite examples from the kind of 20-to-200-person manufacturers I coach—places where the owner still walks the floor and the office is three people wearing six hats.

The goal here is fluency, not a project. By the end you'll know what these tools can and can't do on the office side of a plant, you'll have six prompts you can run this week on a free plan, and you'll have a sane way to pick your first task. That is the whole assignment.

How is AI used in manufacturing today?

AI in factories comes in two very different kinds, and confusing them is where most owners get stuck. The first kind is industrial AI: vision systems that inspect parts, sensors that predict when a spindle bearing will fail, software that optimizes the production schedule. That kind is real, but it requires data infrastructure, integration work, and serious capital, and it is not what this page is about. The second kind is language AI—ChatGPT, Claude, and similar tools—which lives in a browser tab, costs nothing to try, and works on the text your plant already produces every day.

The artificial intelligence use cases in manufacturing that a small or mid-size shop can run this week all share the same shape. A person pastes in real material—an RFQ email, a section of a machine manual, rough notes from the floor—and asks for a draft, a summary, or a list of questions. The tool does the typing and the reading. The person keeps the judgment: the price on the quote, the root-cause call, the date you promise a customer. That division of labor runs through every example below.

  • Quoting and estimating: turning messy RFQ emails into a clean spec list and a draft reply
  • Maintenance: searching manuals in plain English and turning technician notes into log entries
  • Quality: drafting nonconformance reports and work instructions from rough notes
  • Scheduling: communicating a schedule change to the floor and to the customer at once
  • Knowledge: capturing what a retiring veteran knows before it walks out the door
  • Customers: answering order-status emails quickly, clearly, and without corporate speak

What are shops doing with ChatGPT and Claude today?

Six examples, one for each paperwork job that fills a plant office's week. Copy the prompts verbatim, replace the [brackets] with your own material, and adjust the last line to taste. The prompt is the easy part—the context you paste in is what makes the output worth reading.

Quoting and estimating, minus the email archaeologyPrompt

I run a [type of shop: CNC machining / fabrication / injection molding] shop. Below is an RFQ email from a customer: [paste the email and any spec text]. Do three things: list every requirement and specification you can find in it, list the questions I need answered before I can quote, and draft a reply asking those questions in a plain, professional tone. Do not invent specifications—if anything is unclear, put it in the questions list.

The “do not invent” sentence is doing the safety work. Quoting is judgment; digging requirements out of a messy email is typing. Let the tool do the typing.

The machine manual, in plain EnglishPrompt

Below is the troubleshooting section of our [machine make and model] manual: [paste]. Our machine started [describe the symptom: e.g., the ram hesitates at the top of the stroke]. Based only on the manual text I pasted, list the likely causes in the order a technician should check them, and quote the manual line that supports each one. If the manual doesn't cover this symptom, say so.

“Based only on what I pasted” keeps the tool honest. The same prompt works in reverse: paste a technician's rough shift notes and ask for a clean, dated maintenance log entry.

Quality documentation from rough notesPrompt

Here are my rough notes from a quality issue on the floor: [paste notes—what the part was, what went wrong, where it was caught]. Turn them into a nonconformance report with sections for description of the issue, where it was found, suspected root cause, containment action taken, and open questions for the team. Use plain language a customer auditor could read. Flag anything ambiguous in my notes instead of guessing.

The structure of a nonconformance report is standard; the facts are yours. The tool supplies the structure, you supply the facts, and the “flag instead of guess” instruction keeps it that way.

Telling the floor and the customer about a schedule changePrompt

We have to push the [job or part number] order from [old date] to [new date] because [one-line reason: material delay / machine down]. Draft two messages: a short internal note to the floor leads explaining what moves and what it affects, and a customer email that states the new date in the first sentence, gives the honest reason in one sentence, and apologizes without groveling. Both under 120 words. No phrases like “we regret any inconvenience.”

Two audiences, one delay. The internal note and the customer email are different jobs—ask for both at once and edit each in a minute instead of writing both from a blank screen.

Capturing a retiring veteran's knowledgePrompt

Our senior [role: toolmaker / setup machinist / maintenance lead] retires in [timeframe]. I'm going to paste my rough notes from watching him set up [machine or job]: [paste]. Before you write anything, ask me up to eight questions about steps he does automatically that I probably didn't write down. Then turn my answers into a numbered setup procedure a newer machinist could follow, ending with a checklist of the things he checks by feel or sound.

“Ask me questions first” is the highest-leverage sentence on this page. The tool is genuinely good at finding the gaps in what you thought you'd written down.

The “where is my order?” emailPrompt

A customer emailed asking where their order is. Their email: [paste]. The real status: [one or two lines—where the job actually is and when it ships]. Draft a reply that answers the status question in the first sentence, explains any delay honestly in one sentence, and gives a specific date or a specific time for the next update. Under 100 words, warm and direct, no corporate phrases.

Answer first, explain second. Customers forgive a delay much faster than they forgive a vague reply.

What do these AI in manufacturing examples have in common?

None of the examples above touches a machine. Every one of them lives on the office side of the plant, and every one follows the same pattern: a person pastes material the shop already has, the tool returns a draft or a list of questions, and a person checks it before anything leaves the building. The judgment in each example—the price, the root cause, the promised date—stays with the person who owns it. That is not a limitation of the technology; it is the correct way to use the technology.

Notice also what how to use AI in manufacturing does not require: no integration with your ERP, no software purchase, no IT project, no consultant to learn. Every prompt on this page runs on the free plans at chatgpt.com or claude.ai, from the browser already on the office computer. The barrier is not budget or infrastructure. The barrier is that somebody has to sit down for twenty minutes with a real RFQ and try it—which is exactly what the checklist below is for.

Where does AI in factories fall short?

Accuracy first. ChatGPT and Claude write with the same calm fluency when they are wrong as when they are right, and in a manufacturing context the wrongness has teeth: an invented torque spec, a plausible tolerance, a regulation that doesn't exist. The habit that keeps you safe is already in the prompts above—paste the source document and say “based only on this.” Never let the tool supply a number, a spec, or a standard from memory, and verify anything you plan to repeat to a customer or an auditor.

Confidentiality second. Treat anything you paste as shared with an outside vendor. Customer drawings, defense or export-controlled work, anything under NDA, and personal information about employees are all out—unless your company has a written policy and a business plan that explicitly allow it. Many shops I talk to have no written rule at all, and that gap is worth closing before the tools spread on their own; this site publishes a plain-English AI usage policy template you can adapt in an afternoon. When in doubt, strip the part numbers and names and ask the structural question instead.

Finally, the tool has never seen your floor. It knows the generic version of a press brake, a nonconformance report, a setup sheet—it does not know your machines, your customers, or the sound your good machinist listens for. That gap is permanent, and it is the reason the examples above all end with a person checking the work.

What makes a good first AI task in a factory office?

Pick the first task the way you'd pick a first job for a new office hire. Six tests—if a task passes all six, it's a good candidate for this week.

  • It happens every week—quoting emails, status replies, log entries—not once a quarter
  • The input is text you already have: an email thread, a manual section, rough notes
  • You can check the output in under two minutes because you know the right answer
  • A wrong draft costs nothing, because a person reads everything before it leaves
  • The material contains no controlled, NDA-covered, or personal information
  • One specific person owns trying it—“the company should look into AI” is how nothing happens

What changes when someone teaches you?

Everything on this page is yours to run this week, alone, at no cost—and for a lot of owners, self-teaching is the right plan for a while. The pattern I see in coaching is consistent: month one is delight, month two is a plateau. The generic prompts work, and the open questions become specific to your shop—which of your workflows to rebuild first, how to get the quoting team and the floor leads using the tools under the same rules, and how to capture a thirty-year veteran's knowledge while he's still answering questions.

That is the point where a human teacher—not an AI coach bot, not another webinar—earns the fee. In a 1-on-1 session we open your actual RFQs, manuals, and customer emails, find the hours these tools can genuinely hand back to your people, and build the prompts and habits around your shop, your customers, and your risk tolerance. This page is the map. Coaching is walking it together on your floor.

1-on-1 coaching

Bring these to your team.

Examples show what's possible. A working session makes them yours—on your operations, with your people.

Format1-on-1Sessions
LocationNYCor Remote
Duration2-4 hrsFocused
ResultClarityWalk away ready
Pete Enestrom in a 1-on-1 coaching session

Your coach

Coached by Pete Enestrom

Yale and Columbia grad, former Microsoft and Intel, and a venture-backed exited founder. Pete has spent the last four and a half years going deep on every major AI tool, and he teaches the way operators learn: on your real work, at your pace, with nothing assumed.

YaleCOLUMBIAUNIVERSITYMicrosoft
Pete Enestrom's signature

Common questions

Straight answers, the way I'd give them across a table.

Keep reading

Beyond coaching

When the workflow needs to be encoded, not just learned — that's what our team at Zaigo builds.