# Claude for Manufacturing: Set Up a Quote Pilot Before Enabling ERP Changes

The new plugin can assemble a quote from plant records, but connector access, missing inputs and release approval determine whether the draft is useful.

By Paras Madan | 2026-11-13

Claude for Manufacturing launched on November 12 with 17 skills and four connectors for Team and Enterprise plans. It can help draft quotes, quality reports and supplier requests from existing records. Start with a reviewed quote workflow rather than treating the plugin as permission to change production systems.

The useful opportunity is reducing the work required to assemble a decision. A quotation still needs an estimator who can recognize an unsuitable comparison job, a missing drawing revision or a delivery assumption that the plant cannot meet.

## Check the systems before testing the prompt

Anthropic's [launch guide](https://claude.com/resources/articles/claude-for-manufacturing) lists Autodesk Fusion, Infor, Microsoft 365 and Oracle NetSuite. After installing the plugin, the documented setup prompt is “Set us up.” Claude checks connectors and identifies skills that cannot fully run yet. Systems without a connector can supply exports through Microsoft 365.

A successful connection is only the first check. Confirm that the account can see the right facility, jobs and current records. An export should carry a timestamp and scope so the reviewer can tell whether it describes today's inventory or last week's snapshot.

The [manufacturing product page](https://claude.com/solutions/manufacturing) keeps vendor software as the system of record and describes skills as starting points to adapt to local procedures. That is the right mental model for a pilot: improve how a person prepares the quote without creating a second, unofficial source of operational truth.

## A first quote should expose what it does not know

Use a synthetic request or an approved historical job before introducing a live customer commitment. Here is an example prompt to adapt, not a workflow tested for this article:

```text
Prepare a draft quote for 500 machined brackets using the supplied
customer request, drawing revision C and approved costing template.

First list missing requirements. Find comparable completed jobs and
explain why each is relevant. Separate sourced costs from assumptions.
For each material, setup and machining figure, include the source
record and its date. Do not infer a delivery commitment from stock alone.

Return a review packet: missing inputs, comparable jobs, cost calculation,
assumptions and a draft customer quote. Do not send it or change ERP records.
```

The expected output is a review packet, not a particular price. Suppose the customer request says 500 parts but omits the required finish. A useful draft should flag that omission before presenting a confident total. If an old job used a different alloy or tolerance, the comparison should make that difference visible rather than bury it inside an average.

**The missing-input list is part of the result.** Forcing Claude to produce a completed quote from incomplete records can turn the time saved on research into time spent finding hidden assumptions.

## Keep lookup and ERP changes separate

The Infor connector in Claude for Manufacturing supports record lookup. Infor's separate plugin can carry out approved changes. These should not be described as the same capability with a different label.

[Infor's own announcement](https://www.infor.com/news/infor-and-anthropic-announce-partnership) limits its offering to select Infor Velocity Suite customers, with a separate Claude license and administrator activation. Existing Infor entitlements still govern access, changes require user approval, and actions are recorded in Infor.

That means a Team or Enterprise subscription alone is not evidence that your plant can use every write workflow in the demo. Check eligibility and the specific user's rights before promising purchase-order creation or production rescheduling.

Claude's [connector controls](https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities) let organization owners set actions to Always allow, Needs approval or Blocked. For an initial quote pilot, block unnecessary writes and retain approval for anything you intentionally enable. Prompt wording is useful, but it should not be the only control preventing an external commitment.

## Measure review effort, not just drafting speed

Compare the pilot against the existing process on similar jobs. Record the time needed to gather evidence, correct the draft and approve the final quote separately. Count unsupported numbers, wrong revisions and missing requirements, rather than celebrating the first polished document.

A draft produced in two minutes is not a two-minute workflow if the estimator needs an hour to reconstruct its arithmetic. Source links are valuable only when they resolve to the correct record and support the number beside them.

This plugin does not operate manufacturing equipment. Keep equipment decisions with the responsible people and approved procedures, and use the first rollout to learn which information gaps repeatedly slow their work. The strongest outcome may be a cleaner handoff to the estimator, not a more autonomous quote generator.

I'm Paras. I work at the intersection of AI, engineering and distribution.

I help enterprise AI teams explain practical workflows and product limits without losing the technical detail customers need.

[Book a 30-minute call](https://cal.com/paras-madan/30min)