科研 Skill

硬件成本核算与采购

cost-and-sourcing

Prices a hardware product at multiple volumes with one-time vs per-unit cost, landed cost per country, and sourcing leads. Use to estimate unit cost before a pitch.

发布者 Codar安全审核通过v0.1.0更新于 2026-11-18

SKILL.md

Cost and sourcing

You work out what the product costs to make at each order size, and where every part and process comes from. Every number keeps its source. Talk to the user in their language.

The goal is not one magic number. It is a table that shows:

  • why one unit costs hundreds of dollars and ten thousand units cost tens;
  • which three or four lines drive the cost;
  • which numbers are verified and which are still estimates;
  • which quotes to ask for next.

Prerequisites

Run commands from inside this skill's own directory (the folder containing this SKILL.md), since script and reference paths below (such as scripts/foo.py) are written relative to it, not to the project root.

Inputs

  • hw/bom.csv: the canonical BOM (columns in CONVENTIONS.md §5). electronics-researcher fills in the price breaks.
  • hw/brief.md: target markets, launch quantities and target retail price.
  • hw/pcb/: board count, layers, size, sides, joint count and hidden-joint parts (QFN, BGA, LGA).
  • hw/mech/: enclosure parts, materials, finishes and inserts.
  • hw/power/: the battery, catalog or custom.
  • hw/compliance.md: certification costs (owned by compliance-planner; you read them and never re-estimate them).
  • hw/roadmap.md: which build stage (EVT/DVT/PVT) uses which process (owned by prototype-roadmap).

Outputs

  • hw/cost/manufacturing.json: the inputs of the cost model. Start from templates/manufacturing.example.json.
  • hw/cost/model.json, hw/cost/cost.md and hw/cost/cost.svg: written by scripts/cost_model.py. In cost.md the script rewrites only the block between <!-- cost_model:begin --> and <!-- cost_model:end -->. Write your analysis outside the markers, and it survives every re-run. The chart title states the conclusion against targets.unit_cost.
  • hw/cost/rfq.md: the quotes to request, built from templates/rfq.md.
  • hw/cost/sourcing.md: where to buy each part or process, with the authorized channel, MOQ, lead time and second source.

Procedure

  1. Read the BOM and check that it can be costed. Every line needs a full orderable MPN with its packaging suffix, a quantity, at least one price break and an evidence tag.

    • If prices are missing, ask electronics-researcher to fill them. Do not invent a price.
    • A part with no price stays in the model with a warning.
  2. Model the PCBA from the assembler's published tariff, not from a guess. Count three things per board:

    • solder joints (pins plus exposed pads);
    • unique part types (each one has a loading fee);
    • hidden-joint parts that need X-ray.

    Put them in the pcba block. The example template holds one quick-turn tariff as published on its date. Re-check it before use, and replace it with a real quote once Gerbers exist.

  3. Write every other cost as a line with a value per tier. Classify each line by how it behaves (section "Cost structure"): recurring, per order, or one-time (NRE).

    • Give every value as a [low, high] range unless it is a quote.
    • Tag every line verified: <source, date>, estimate: <basis> or assumption.
  4. Use the right process for each tier. The same part is made differently at 10 and at 10,000 units. For example, an enclosure goes SLA → urethane casting → rapid aluminum tool → hardened steel. Each process brings its own NRE (from_tier/to_tier). See references/cost-reference.md.

  5. Run the model:

    python3 scripts/cost_model.py --mfg hw/cost/manufacturing.json --out hw/cost --svg
    

    The script applies three rules:

    • Part attrition: the assembler's extra parts per feeder.
    • MOQ: below the MOQ you pay for the whole MOQ or for paid samples, whichever is cheaper.
    • Yield loss: scrapped units still cost their parts.

    It writes the tables, the top cost drivers per tier and the share of cost that rests on verified figures. Test the script with python3 scripts/test_cost_model.py.

  6. Add landed cost for each market in the brief. Use the method in references/landed-cost.md: duty and tax multiplier on CIF, courier versus formal import, FX as a dated assumption. Destination rules change often. Every rule carries a date and the word "verify".

  7. Read the result like an engineer and write cost.md around the script's tables, outside the generated-block markers. Put the brief's unit-cost goals in targets.unit_cost, so each tier reads met, not proven or not met. Use the landed recurring row for the cost of one more imported unit, and the incl. NRE row for the launch budget. Answer these questions:

    • At which order size does NRE stop dominating?
    • Which single part or process is the biggest lever? (A memory chip or a custom battery often outweighs everything else.)
    • What does the launch batch really cost per unit, with certifications spread over it?
    • What is the gap to the target retail price? A retail price usually needs to be about 3–5× the landed cost to leave room for the channel and the margin. Label this as a rule of thumb.
  8. Write sourcing.md. For each BOM line, list:

    • the authorized distributors that stock it;
    • the MOQ and reel size;
    • the lead time;
    • a second source;
    • anything long-lead to buy now.

    For each process (PCB, PCBA, molding, cell, metal parts, packaging, final assembly), list 2–4 established vendors from references/suppliers.md.

  9. Write rfq.md. List every estimate that moves the total by more than about 5%. For each one, say what to send, to whom, and which number the quote will close. Order the list by impact.

Cost structure

KindBehaves likeExamplesIn the model
Recurringpaid for every unitparts at the tier price; bare boards; PCBA per-joint and X-ray fees; molded parts; battery; magnets, membranes, cord; packaging; final assembly, programming and test labor; freightrecurring, BOM, pcba variable
Per order (batch)paid on every production order, spread over that orderPCBA setup, stencil, feeder loading, fixtures, handling; molding run setup and color change; plating lot charge; prototype board lotper_order, pcba batch
One-time (NRE)paid once per design revisionmold tools; stamping dies; photo-etch phototools; test and programming fixtures; custom cell tooling; certifications (radio, EMC, safety, Bluetooth qualification, IP rating, UN38.3); packaging dies; design servicesnre
Yield lossa percentage on recurringscrapped and reworked units; cosmetic rejects on clear parts (10–30% early)yield_loss_pct
Landeda multiplier on recurring plus freightduties, import taxes, broker feeslanded

Keep engineering salaries, marketing, warranty reserve and retail margin out of the unit cost. Say in the report that they are excluded.

Sourcing rules

  • Buy production parts only from authorized channels. These are the manufacturer, its franchised distributors (DigiKey, Mouser, Arrow, Avnet, Future, TME, Farnell/Newark, and LCSC for parts it is franchised for), or the EMS's own purchasing.
    • A broker or marketplace is a last resort, for prototypes, and only with traceability.
    • Counterfeit and remarked parts come from brokers.
  • Respect the reel. Prices at 1k and 10k assume full reels. Cut tape and small quantities cost more and carry an assembler surcharge. Check that the tier price you use matches the packaging suffix of the MPN.
  • Plan attrition. Assemblers consume extra parts per feeder. For 0201/0402 passives, order at least 20 extra, or 5%.
  • Buy long-lead parts early. Any part with a lead time over 12 weeks, or with stock below one production run, goes in sourcing.md under "buy now".
    • For prototypes, buy enough for EVT and DVT at once.
    • A part that is "early sampling" or NRND at the manufacturer is a design risk. Hand it back to specs-engineer. Do not hide it with a price.
  • Second-source passives by value, not by MPN. Approve 2–3 brands per value and package (for example Murata, Samsung, TDK, Yageo for MLCCs). Single-source an IC only when no pin-compatible alternative exists, and say so.
  • Consign or turnkey. For quick-turn turnkey assembly, check that the assembler's library stocks your exact parts. Consign the rest: ship them to the assembler, labelled, with spares.
  • Use established vendors only. Never recommend an unknown company found through a marketplace. Check that a vendor still operates (some well-known startups have closed). Verify each vendor's current status before recommending it.

Gate

Cost and sourcing pass when all of these are true:

  • Every BOM line has a price at every tier, or an explicit warning.
  • Every line in manufacturing.json has an evidence tag.
  • cost.md states the share of cost resting on verified figures at the launch tier.
  • rfq.md covers every estimate that moves the total by more than about 5%.
  • The total at the launch quantity, with certifications, is stated next to the target retail price.

Taste and pitfalls

  • Never present an estimate as a quote. "About $3–8 for final assembly at 1k (estimate, China box-build range)" is honest. "$5" is not.
  • Don't let one line hide inside a total. A single 4 Gbit NAND or a custom cell can be half of the recurring cost. Call it out by name, with its share.
  • A custom battery below its MOQ is expensive. At 100 units you either pay for 2,000 cells or for paid samples. The model shows it, and you say it.
  • Certifications are paid before the first sale, even for a "small" launch batch. Spread them over the launch batch and show that number. It is usually the uncomfortable one.
  • Tooling dominates at 1k. At 1,000 units, NRE is often about half the total. Do not quote the 10k recurring cost as "the cost".
  • Clear and cosmetic parts have high scrap. Budget it in yield_loss_pct or in the part price.
  • Use the tariff's real breakpoints. PCBA X-ray and fixture fees step with quantity. A smooth curve is wrong at 5 and at 100 units.
  • Date every price and every tax rule. Duties, de minimis thresholds and courier regimes change, sometimes within months.
  • Tables are aligned and readable. Right-align numbers, keep units in the header, and use one currency per table. Never show more than 3 significant figures for an estimate.

References

Read these when the step needs them:

FileRead when
references/cost-reference.mdyou need typical, dated figures for PCB, PCBA, molding, metal parts, batteries, final assembly, packaging and certification lines
references/landed-cost.mdyou compute landed cost or explain import taxes for a destination
references/suppliers.mdyou name vendors for a part or process
references/manufacturing-json.mdyou write or debug hw/cost/manufacturing.json
templates/rfq.mdyou write hw/cost/rfq.md
templates/manufacturing.example.json, templates/bom.example.csvyou start a new model; they are a complete fictional example that runs

示例提示词

帮我算一下这款产品在不同产量下的单台成本和采购渠道。

所属插件

电子电气与信息工程面向电气与电子工程研究:电力系统仿真(PSS/E、PSLF、PowerWorld、pandapower、PyPSA、OpenDSS、ANDES)与越限/稳定/短路处置,FPGA 时序收敛与跨时钟域检查,电路与 PCB 设计评审,硬件产品开发流程。

安装该插件会一并获得同领域的 63 个 Skill / MCP。

同插件的其他科研 Skill

常见问题

硬件成本核算与采购能做什么?

Prices a hardware product at multiple volumes with one-time vs per-unit cost, landed cost per country, and sourcing leads. Use to estimate unit cost before a pitch。

如何安装硬件成本核算与采购?

在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「硬件成本核算与采购」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。

硬件成本核算与采购需要哪些权限?

该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。

硬件成本核算与采购经过官方审核吗?

是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。