What multiplier should I use beyond the hardware price?

This guide does not establish a universal multiplier. Obtain the known quotations, estimate the remaining work explicitly, and test how the result changes when those assumptions change.

Can I calculate payback by assuming one robot replaces one worker?

Only use labor savings that the intended workflow can support. Include remaining supervision, recovery and other costs, and distinguish redeployed staff time from cash savings.

How long should the POC take?

Set its scope and acceptance criteria with the supplier and integration team. The schedule depends on the task, equipment and work required; no single duration in this guide is presented as an industry norm.

How should unknown costs appear in the budget?

Mark them unknown, identify who will obtain the quote or measurement, and include an explicitly labeled scenario if you need to make an interim decision. Do not silently count them as zero.

Is SDK access included in a low public robot price?

It depends on the configuration. Unitree lists secondary development for G1 EDU separately from standard G1, with EDU priced through sales. Confirm the required interfaces and entitlements in writing.

Does buying from China change the worksheet?

The same work packages still need pricing, but destination-specific shipping, import, service and return arrangements can change the costs. Confirm them for the actual supplier and order.

Total Cost of Ownership: Deploying a Humanoid Robot in a Factory

A planning worksheet, not an industry cost benchmark. Fill the inputs with dated quotations, your own labor rates and pilot measurements.

Who this guide is for

This is for a buyer who needs to budget a defined humanoid application. The starting point is the task, required output, working environment and planning period—not a claim that every robot replaces a worker.

For a hardware overview, see How Much Does a Humanoid Robot Cost?, then obtain a current quote for the configuration you actually need. The worksheet below is an editorial planning tool. Its empty fields are deliberate: we have not established a representative industry dataset that would justify fixed integration percentages, support rates or deployment timelines.

Get the hardware scope right

Ask for a bill of materials showing the robot, hands, batteries, chargers, compute modules, accessories and software entitlements. Record the currency, quotation date, validity, delivery basis, taxes and freight separately. Do not assume a public launch price is a landed price or includes your required SDK tier.

For example, the Unitree G1 manufacturer comparison separates standard G1 from G1 EDU. Secondary development is marked for EDU, and its price requires contacting sales. A standard-model price is therefore not sufficient evidence for the hardware cost of an EDU-based research project.

Item to confirm	Your project input	Evidence
Exact robot model and configuration	Fill in	Dated quotation and configuration list
Hands, tooling and adapter flanges	Fill in	Included-parts list and drawings
Compute, SDK and software access	Fill in	License terms and interface documentation
Batteries, chargers and initial spares	Fill in	Part numbers, quantities and prices
Freight, insurance, taxes and import services	Fill in	Destination-specific cost breakdown
Installation and training included in the order	Fill in	Written scope and exclusions

Price alone does not establish factory suitability. A lower-priced platform may suit a research or demonstration task, while a more expensive one may still require significant integration. Compare task evidence alongside the quotation.

The cost buckets to fill

Integration and engineering

Break integration into work packages: tooling, cell layout, controls connections, perception, grasping, application software, safety assessment and acceptance testing. For each package, record who performs it, estimated hours or fixed fee, dependencies and what triggers additional work.

Internal engineering time is a project cost even when it does not appear on the supplier’s invoice. If a hand or gripper is an add-on, include its adapter, cables and integration effort as well as its purchase price. The hands and grippers catalog can help identify candidates; it does not establish that a particular combination is ready to operate.

Supervision, teleoperation and recovery

Record the work a person must do: operating the robot, resolving exceptions, resetting the cell, changing objects and collecting data. Some activities may overlap, so avoid charging the same person’s time twice.

Estimate these hours initially, then replace the estimates with pilot logs. The teleoperation and autonomy guide describes the evidence to request. A robot completing an autonomous motion does not establish that its whole workflow needs no human assistance.

Batteries, spares and consumables

Use runtime measured on the intended workload, not a catalog runtime alone, to plan charging and battery changes. Obtain part prices and replacement procedures for the components your use case is likely to wear. Record expected replacement intervals as assumptions until supported by service data.

Price the spare-parts list before placing the order. Include delivery time, storage needs and whether replacement requires a supplier technician. Do not assume that a whole-hand replacement costs the same across models.

Maintenance and support

Request a support quotation with the covered country, response process, labor, parts, exclusions and responsibility for return freight. Keep warranty coverage separate from preventive maintenance and application support; the same contract may not cover all three.

Use the quoted support fee or your estimated service hours and parts costs. This worksheet does not prescribe a percentage of hardware value. Our import playbook provides purchasing context for the terms to confirm.

Software, compute and data

List licenses, subscriptions, compute, data storage, annotation and application maintenance. Confirm what is included, what renews, and what remains usable if a subscription ends. Document where data is processed and who can access and retain it.

If the project involves training or adapting a model, use the VLA buyer’s primer to identify the required observation/action streams, model access and evaluation work. Do not assume that buying a robot includes the data, model weights or rights needed for your workflow.

Downtime and training

Budget operator and maintenance training, commissioning, scheduled maintenance and recovery work. Track lost production separately from cash expenses: its value depends on your process, and adding it indiscriminately can double-count costs already included elsewhere.

Do not assume supervision or downtime will fall automatically. Treat any expected improvement as a scenario to test, with an owner and a date for reviewing the evidence.

A worksheet for the first year and later operation

Choose a planning period and currency before filling this table. Use the same scope for competing proposals. “Unknown” means an input still needs a quotation or measurement; it does not mean zero.

Cost bucket	Calculation or entry	First-year input	Later-period input
Hardware and initial accessories	Sum of included purchase items	Fill in	Planned replacements or additions
Delivery and import costs	Freight + insurance + applicable charges	Fill in	Costs of later shipments
Integration and commissioning	Fixed fees + internal hours × loaded hourly cost	Fill in	Change-related work
Supervision and teleoperation	Required staff hours × loaded hourly cost	Fill in	Measured or explicitly assumed hours
Batteries, spares and service	Quoted purchases + service labor	Fill in	Expected replacements, with assumptions stated
Software, compute and data	Licenses + subscriptions + compute/data costs	Fill in	Renewals and ongoing work
Training	Staff time + external training fees	Fill in	Refresher and new-staff training
Contingency	Separately chosen allowance for named uncertainties	Fill in	Reassess for the period

For a cash-budget view, total the purchases and operating expenses that occur in the chosen period. Do not add accounting depreciation on top of the full purchase price in the same cash total. Keep the estimated production impact of downtime alongside that budget, with its calculation explained.

Build a base case and a less favorable case using your own assumptions. Vary the inputs that could change the decision—such as integration hours, interventions per shift or replacement frequency. These are project scenarios, not manufacturer promises or industry averages.

Set rollout milestones instead of a universal timeline

A calendar should come from the project plan, supplier availability and acceptance requirements. We have no sourced basis for prescribing the same POC length, number of rounds, validation period or order size to every factory.

Milestone	Evidence needed to proceed	Your planned date and cost
Task definition	Objects, environment, output and acceptance criteria agreed	Fill in
Feasibility demonstration	Task results and limits documented	Fill in
Pilot installation	Site, equipment, integration and operator preparation complete	Fill in
Validation	Agreed performance and recovery criteria tested over the required period	Fill in
Expansion decision	Economics and support arrangements updated using pilot evidence	Fill in

For each milestone, record what happens if the criterion is missed: further work, a narrower task, a different platform or a stop decision. A rental or service proposal should be compared on its actual fees, responsibilities and exit terms, not assumed to transfer every performance risk.

How to decide whether the budget is ready

A useful project budget identifies its missing inputs as clearly as its totals. Before committing, name the owner of each unresolved quote or assumption. Check whether the less favorable case still meets your project requirements and whether the pilot can collect the measurements needed for the next decision.

For a scoped inquiry, send the task, configuration, quantity, destination and known integration requirements through the RFQ form. Separate the supplier’s hardware quote from the application work and operational assumptions that still need agreement.