← Back to library

Price a custom manufacturing job with every cost traced

Anthropic's Claude for Manufacturing plugin, released November 12, 2026, includes a skill that builds a job-shop quote. It produces two documents, a sendable quote and an internal cost sheet, refuses to invent missing labor or margin rates, flags tolerances the shop has never held and keeps counteroffers as revisions of one quote. We explain how to use it.

  • OutcomeUse the quote-build skill from Anthropic's Claude for Manufacturing plugin to price a make-to-order job from the intake form, similar past jobs and cost history, citing the purchase order or work order behind each cost, spreading setup across every quantity break, keeping margin on a separate internal line and checking the promised date against shop load, with a person releasing the quote.
  • SetupAn afternoon+
  • LevelAdvanced
  • Creditanthropics
View original
Works with
ClaudeClaude CoworkClaude Code

Published Nov 15, 2026Updated Nov 15, 2026AI dry run on sample input: passed Nov 15, 2026Source verified Nov 15, 2026

When should you use it?

  • Your estimator is the bottleneck and quotes wait days for pricing
  • A manager asks where a price came from and nobody can rebuild it quickly
  • Customers counter on price and you lose track of which version they saw

Not for: Catalog or fixed-price products that never need a fresh cost buildup; Shops with no recorded labor, burden or margin rates; it will price only what it can trace; Sending quotes automatically; a person releases every version

What do you need, and what do you get?

You need

  • The intake form or RFQ details, with quantities, materials and drawing revision
  • Cost history: past work orders, recent purchase orders and standard costs, from your ERP or exports
  • Labor, burden and margin rates recorded during plugin setup
  • A planning export of current shop load, if you want the date checked

You get

  • A customer quote with prices per quantity break, lead time, terms and listed assumptions
  • An internal cost sheet citing the source of every cost, the comparable jobs and the margin
  • A list of lines it could not price and the missing input behind each
  • A date check against shop load, or a clear note that it was not checked
  • A revision record when the customer counters

How does it work, step by step?

  1. Install and onboardAdd Claude for Manufacturing from the Claude plugin directory and record your labor, burden and margin rates during setup.
  2. Connect the cost historyConnect your ERP or attach exports of closed work orders, purchase orders and the planning schedule.
  3. Ask for the quoteSay 'build the quote' with the intake form or RFQ attached.
  4. Review both documentsCheck the internal sheet for blocked lines, capability flags and the date check, then read the customer version on its own.
  5. Release and reviseSend the quote yourself. When the customer pushes back, ask for a revision so the change record stays with the original.

The prompt

Our adapted version, written to work in Claude, Claude Cowork and Claude Code. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt7 variables
Build a quote for {customer} for {part} at quantities {quantities}, using {intake_form} and our cost history in {cost_sources}.
Cite the source of every cost: the purchase order and date for material, the closed job or routing for hours, and our recorded rates for labor and burden. If a rate is missing, name it, list the lines it blocks and give no total.
Spread setup separately at each quantity, keep margin on its own line, and flag any tolerance we have not held before.
Check the requested date of {due_date} against {shop_load_file}.
Give me a customer quote with no hours, rates or margin in it, plus a separate internal cost sheet. Do not send anything.

The original skill is published by anthropics on GitHub (anthropics/claude-plugins-official). Open it there to install or import it; the prompt above is our own adaptation.

What can go wrong?

  • Typing a labor rate into the chat to get a number faster. The skill ignores ad hoc rates on purpose; record the rate in setup instead.
  • Quoting a tolerance tighter than the shop has proven. Read the capability flags before the price.
  • Skipping the planning export. Without it, the lead time is labeled as unchecked, and that label belongs in front of the customer conversation.
  • Anthropic labels the plugin a reference implementation it does not actively maintain, so rebuild a few recent quotes with it before relying on it.

Our take

In most small job shops, the quote lives in one estimator's head and a spreadsheet only they understand. That works until they are on vacation or a customer disputes a number months later. This skill's best idea is that a price is only useful if you can explain it, so every line points to a purchase order, a closed job or a standard cost, and the margin sits on its own line where the estimator can see their negotiating room. Its refusals are equally valuable. With no confirmed labor rate it will not invent one or sneak a ballpark through past prices, and it flags a tolerance the shop has never held before anyone commits to it. The split between a customer quote and an internal cost sheet is also sensible, since internal hours and margin should never leak into what the buyer receives. The setup is real work, and the plugin is labeled a reference implementation, so trial it on recent jobs. In our dry run on a fictional bracket order with three quantity breaks, it priced material from a dated purchase order, blocked totals until the burden rate was set and flagged the requested date as too early.

Where the time goes back: Estimators spend much of each quote hunting for the last price paid, the hours on a similar job and the current shop load. Having those pulled and cited leaves them to apply judgment, and a counteroffer becomes an edit rather than a rebuild.

FAQ

What happens if a rate is missing?
It builds everything the missing rate does not affect, names the rate and the lines it blocks, and gives no total or unit price until the rate is set.
Why two documents?
The customer sees prices, terms and assumptions. Hours, rates, sources and margin stay on the internal sheet the estimator keeps.
Who made it and what license does it use?
Anthropic published it in the anthropics/claude-plugins-official repository on GitHub under the Apache 2.0 license.

Source and credit

This playbook is based on work by anthropics. We summarize it and link to it and write our own adapted prompt.

Original
quote-build skill (anthropics/claude-plugins-official, Claude for Manufacturing)
Creator
anthropics
Published on
GitHub (anthropics/claude-plugins-official)
Original date
Nov 12, 2026
License
Apache-2.0
Originally for
Claude
AI dry run
Nov 15, 2026: passed. Dry-run tested by our AI test agent on sample input. No invented rate, costs cited, setup re-amortized, margin separate, date checked, customer quote clean.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Nov 15, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

The original is licensed under Apache-2.0 by anthropics. Modified: our adapted prompt and summary are our own wording; the original skill {"was unchanged at the source when we snapshotted it (live source later removed)" if src_removed(s) else "is unchanged at the source link"}.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Log a sales order after checking its paperwork matches

Give one spoken instruction and get the order logged, cross-checked against its paperwork, the commission tracked and a client email drafted.

Credit: Elvis Rigglet (@rassailor)

An afternoon+
Operations & AdminPrompt✓ AI dry run

Stress-test a business decision with an AI pre-mortem

Before committing to a price rise, launch or other big change, have an assistant assume the plan has already gone wrong, rank the likeliest causes with an early signal for each, work out how much loss you can absorb before the change stops paying, list the assumptions underneath with a cheap test for each, and then write the announcement against a scoring rubric it sets first.

Credit: Shubham Vora

Minutes
Operations & AdminRoutine✓ AI dry run

Get the plant report ready before the morning meeting

Schedule the morning-plant-pulse skill from Anthropic's Claude for Manufacturing plugin to combine the overnight exports from planning, production and maintenance, compute output against plan, OEE and its three parts, downtime ranked by minutes and by count and the cost of losses, then refresh one operations dashboard per site with 14- and 30-day trends, all without changing any business system.

Credit: anthropics

An afternoon+
Operations & AdminSkill✓ AI dry run

Join plant exports and ERP data, with mismatches explained

Use the data-consolidate skill from Anthropic's Claude for Manufacturing plugin to identify each export file, check that every source covers the same dates before joining, pull matching ERP and maintenance records, normalize part and order numbers with a log of every rule applied, sort every record that fails to match into a named class with a proposed fix, and apply nothing without your yes.

Credit: anthropics

An afternoon+
Operations & AdminSkill✓ AI dry run

Send suppliers an RFQ package that makes bids comparable

Use the supplier-quote-request skill from Anthropic's Claude for Manufacturing plugin to assemble a request for quotes with the drawing at its confirmed revision, a sourced demand picture, quality clauses, commercial terms and a required bid layout, list what is missing, draft one email per supplier for the buyer to send, then read the returned bids into one shape and compare them by quantity break.

Credit: anthropics

Under an hour