Skip to content
Physical AI

Robot Data Collection Cost: Pricing 1,000 Demonstrations

Robot data collection cost is the total spend required to produce a usable demonstration dataset, and it lands between roughly $2 and $150 per usable demonstration depending on the task. This guide prices a fixed deliverable of 1,000 demonstrations three ways. It breaks a quote into the seven cost lines sitting underneath it, and shows […]

Robot Data Collection Cost: Pricing Demonstrations

Robot data collection cost is the total spend required to produce a usable demonstration dataset, and it lands between roughly $2 and $150 per usable demonstration depending on the task. This guide prices a fixed deliverable of 1,000 demonstrations three ways. It breaks a quote into the seven cost lines sitting underneath it, and shows why a first program costs about twice what the second one does. You also get the arithmetic that decides whether the spend turns into policy performance.

Most cost guides answer with an hourly rate. An hourly rate tells you almost nothing, because two teams paying the same rate for the same task can end up 5× apart on cost per usable demonstration. The gap sits in throughput, acceptance rate and the one-time engineering that never appears on a collection quote.

The model below uses 1,000 demonstrations as the unit because it is a realistic first commercial program: large enough to train a single-task policy that generalizes, small enough to fund before the results are proven.

What Does Robot Data Collection Cost per Demonstration?

Cost per usable demonstration is the number to quote and the number to negotiate. It combines three variables that vendors usually report separately: the all-in operator hour, how many demonstrations that hour produces and what share of them survive quality review.

Written out, the formula changes how a quote reads:

Cost per usable demonstration = all-in hourly rate ÷ (recorded demonstrations per hour × acceptance rate)

  • Single-arm pick, place and sorting: 10–15 recorded demos per operator hour, 85–92% acceptance and a $25–40 all-in hour give $2–5 per usable demonstration.
  • Bimanual fine manipulation: 3–6 demos an hour, 75–85% acceptance and $35–60 an hour give $7–27.
  • Contact-rich work with tactile and force capture: 2–4 demos, 65–80% acceptance and $40–70 an hour give $13–54.
  • Mobile manipulation and humanoid whole-body: 1–3 demos, 60–75% acceptance and $45–90 an hour give $20–150.

These figures cover collection labor only. Hardware, pipeline engineering and program management sit on top, and the next two sections price them.

7 Cost Lines Behind a Robot Data Collection Quote

A quote usually shows one or two lines. A program has seven. Teams that budget from the quote miss the difference and run out of money at about the 60 percent mark. Each line below carries its share of a contracted program.

  • Operator time, 55–70%: recording, scene resets, object staging and retakes.
  • Supervision and QA review, 8–15%: episode grading, sampling and rejection handling.
  • Pipeline and format conversion, 5–15%: segmentation, sync checks and LeRobot or HDF5 packaging.
  • Program management and spec iteration, 8–12%: task definition, revisions and weekly sample reviews.
  • Rig hardware amortization, 3–10% contracted and far higher in-house: arms, cameras, sensors, servicing and spares.
  • Consent, provenance and licensing admin, 1–3%: operator releases, per-episode chain of custody and rights terms.
  • Storage, transfer and archive, under 2%: object storage, egress and cold copies.

Two of them deserve attention up front. Program management is where a vague task specification becomes expensive, because every revision invalidates episodes already recorded. Consent and provenance is small as a percentage and decisive as a risk: a dataset without signed releases and a per-episode record of who produced it on what hardware is difficult to license, sell or defend later.

Our physical AI training data collection programs treat that record as part of the deliverable rather than paperwork attached to it.

Pricing 1,000 Demonstrations: 3 Worked Budgets

Below are three budgets for the same 1,000 usable demonstrations. Each uses the throughput and acceptance figures from the tiers above and states its assumptions so you can substitute your own.

Budget lineA. Single-arm, contractedB. Bimanual, contractedC. Tactile, built in-house
Acceptance rate assumed88%78%70%
Episodes that must be recorded1,1401,2801,430
Operator hours required95320480
Collection labor$2,850$15,360$21,600
Rig hardware and sensorsIn rateIn rate$26,000
Rig build and operator trainingIn rateIn rate$12,000
Pipeline and format tooling$1,200$2,000$8,000
QA review and curationIn rateIn rate$6,000
Program management$340$1,840$9,000
Storage and transfer$40$110$400
Program total$4,430$19,310$83,000
Cost per usable demonstration$4.43$19.31$83.00

Assumptions: recorded throughput of 12, 4 and 3 demonstrations per operator hour; all-in operator rates of $30, $48 and $45; engineering time costed at $100 per hour; program management at 12 percent of collection labor for the contracted routes.

The spread across those three columns is nearly 19×, and every column is defensible. Cost is set by what the task demands, so a quote that looks expensive against a benchmark from a different tier is being compared against the wrong thing.

Every rate and total in this guide is a planning model rather than a quoted price. Cost per usable demonstration moves with task complexity, sensor coverage, operator skill, rig type, acceptance thresholds, scene and object diversity, the local labor market and the hardware and pipeline you already own. Use these numbers to structure a budget and compare quotes on the same terms, then price your own program against your task specification and a vendor’s measured yield.

Why the First 1,000 Demonstrations Cost More Than the Next 1,000 Demos?

Column C carries $46,000 of spend that happens once: hardware capital, rig build, operator training and the pipeline that turns raw recordings into training-ready episodes. Run a second program of 1,000 demonstrations on the same rig with the same trained operators and those lines drop out.

The second program costs about $37,000, or $37 per usable demonstration against $83 for the first. Blended, the two come to $120,000, or $60 per demonstration.

That 2.2× ratio decides build against buy more cleanly than any hourly comparison. Building your own floor pays off when you will collect continuously for many months on tasks specific to your product. Contracting pays off for a bounded program, for scene breadth and for the first program of all, where the honest question is whether the data moves policy success at all. Teams often answer that question with a contracted pilot and build the floor afterwards, once the tasks worth owning are known.

Need training data for your models? Scope a data-collection or labeling pipeline in a strategy session with our team.
Book a strategy session →

Does Offshore Robot Data Collection Cost Less?

Wages differ by a large multiple. Program cost differs by much less, and the reason is visible once the rate stack is separated by layer. Rest of World’s 2026 reporting on China’s embodied-AI data vendors found home-based operators earning around 20 yuan, about $3, an hour filming household chores, while a data platform with a robot in the loop still bills RMB 500 to 1,000 per hour for the same hour of output. Galaxea’s chief executive put internal production cost near RMB 50 to 100 per hour for wearable capture and around RMB 250 with a robot involved.

At roughly RMB 7.1 to the dollar, the wage is $3–6 an hour and wearable production, with rigs and floor space, is $7–14. A robot in the loop adds depreciation and maintenance for about $35, and the $70–140 commercial rate also covers rejected episodes, QA and margin. That top layer sits above typical North American all-in benchmarks of $28 to $60 per operator hour. Wage arbitrage shrinks as soon as a robot enters the loop, because depreciation, floor space and rejected episodes carry the same cost anywhere. The saving that survives is on wearable and robot-free capture, where labor is the dominant input.

Two questions settle it faster than a rate comparison.

  1. Ask what the quoted hour includes, layer by layer.
  2. Then ask for usable episodes per operator hour, because a $30 hour at 55 percent yield loses to a $50 hour at 90 percent yield.

What 1,000 Demonstrations Buys, and How to Spend Them?

A budget for 1,000 demonstrations is also a decision about where those demonstrations get recorded, and that decision changes policy performance more than the price per episode does.

The Data Scaling Laws in Imitation Learning study collected over 40,000 demonstrations and ran more than 15,000 real-world rollouts to test the question directly. Generalization scaled as a rough power law with the number of environments and objects, while demonstrations per environment hit a threshold beyond which additional ones changed little. The team trained policies reaching about 90 percent success on unseen environments and objects using 32 environment-object pairs at 50 demonstrations each, a total of 1,600.

Applied to a 1,000-demonstration budget, that points to roughly 20 environment-object pairs at 50 demonstrations each rather than 1,000 repetitions on one bench. The second allocation costs the same and generalizes far less.

Some rejection is normal in every program. The DROID dataset recorded 76,000 successful trajectories and labeled roughly 16,000 more as unsuccessful, a rejection rate near 17 percent inside a carefully run academic program with a standardized hardware stack.

Storage, Egress and the Costs Teams Overestimate

Storage often gets listed as a hidden cost. At 1,000 demonstrations it is noise, and the arithmetic shows why.

DROID reports 350 hours of interaction across 76,000 episodes, which works out to roughly 17 seconds of recorded interaction per episode. A 20-second episode carrying three compressed RGB streams plus proprioception runs about 80 to 150 MB; add stereo depth and tactile channels and it reaches 300 to 500 MB. One thousand episodes occupy somewhere between 0.1 and 0.5 TB.

At AWS’s published S3 Standard pricing of $0.023 per GB-month in US East, 300 GB costs about $7 per month to store and about $27 to transfer out once at $0.09 per GB. Those are rounding errors against a five-figure collection budget.

Storage becomes a real line at a different scale. A 100,000-episode corpus at 300 MB per episode is 30 TB, around $690 per month in standard storage, and every full copy pulled out costs roughly $2,700 in egress alone. That is the scale at which to plan the storage class and the copy policy.

The cost teams underestimate instead is spec iteration. Change the object set, the camera placement or the success criterion after week two, and the episodes recorded before the change may no longer be trainable alongside the ones recorded after. That is a re-collection cost, and it is charged at the full rate.

Scoping a robot data collection budget or comparing quotes across vendors? NeuralChainAI runs robot data collection services across teleoperation and egocentric capture, including tactile manipulation data with force arrays, consented at source with a per-episode chain of custody. Bring the task list and the target policy to an AI strategy session and you get back a costed plan with throughput, acceptance and allocation written down before episode one.

What to Demand on a Robot Data Collection Quote?

The following items turn a rate into a budget you can hold a vendor to. Ask for all of them in writing.

  1. Usable episodes per operator hour, separated from recorded episodes per hour. One number is throughput, the other is what you pay for.
  2. The acceptance rate and the rejection criteria that produce it, plus who grades episodes and at what sampling rate.
  3. Scene and object allocation: how many distinct environments, object instances, lighting conditions and viewpoints the episode count is spread across.
  4. Delivery format and schema, named specifically. LeRobot and HDF5 are the common targets for physical AI training data, and with LeRobot it is worth asking which version, since v3.0 changed the storage layout and a v2.1 delivery means a conversion step you have not priced.
  5. Embodiment, end effector, action space and camera set for teleop data. Ask which arm or humanoid recorded the episodes and which gripper or hand it carried. Then ask whether actions are logged as joint positions or end-effector poses and where each wrist and scene camera sits, so you can match the episodes to the robot your policy will run on.
  6. Sensor coverage per episode, listed channel by channel with sample rates, including which streams are hardware-synchronized rather than aligned afterwards.
  7. Provenance and consent terms: signed operator releases, a per-episode record tying data to the person and hardware that produced it, plus explicit rights to train, deploy and redistribute.
  8. Re-collection terms for spec changes, including who absorbs the cost when the task definition moves.

A vendor who answers all these with numbers is quoting a program. A vendor who answers with an hourly rate is quoting an input. Teams weighing a data budget alongside a wider build can scope both together through physical AI and robotics consulting, where hardware, capture and model strategy get costed as one plan.

Frequently Asked Questions on Robot Data Collection Cost

Three variables set it: the all-in hourly rate for an operator, how many demonstrations that hour produces and what share of them survive quality review. Divide the rate by throughput multiplied by acceptance and you get cost per usable demonstration, which is the number worth negotiating. Simple single-arm pick and place sits at the low end of the range. Costs step up sharply for bimanual work, for contact-rich tasks needing tactile and force capture and for mobile or humanoid whole-body tasks, because throughput falls and rejection rises at the same time.
It depends on the task tier and on how much of the setup you already own. A contracted program on a simple manipulation task is the least expensive route by a wide margin. A contracted bimanual program costs several times more, because operators record far fewer usable episodes per hour. Building the capability in-house for the first time is the most expensive, since hardware, rig build, operator training and pipeline engineering all land inside that first program. Ask a vendor for throughput and acceptance alongside the rate, then run the arithmetic against your own task.
Hardware capital, rig build, operator training and pipeline engineering are paid once. In a first in-house program those lines account for roughly half the total, so a second run of the same size on the same rig with trained operators costs around half as much per usable demonstration. That ratio is the number that decides build against buy, more cleanly than any hourly comparison. Continuous collection on tasks specific to your product favors building. A bounded program, or a first program testing whether the data moves policy success at all, favors contracting.
For wearable and robot-free capture, yes, because labor dominates the cost. Once a robot enters the loop the saving narrows sharply. Reporting on Chinese collection facilities shows a wide gap between what an operator earns and what a data platform bills for the same hour, with depreciation, floor space, quality review and rejected episodes filling the difference. Those costs are similar wherever the floor sits, so commercial service rates at the top of that stack can meet or exceed North American benchmarks. Compare usable episodes per operator hour rather than headline rates.
A robot data collection quote should state usable episodes per operator hour separated from recorded episodes per hour, the acceptance rate with its rejection criteria, how the episode count is allocated across environments and object instances, the delivery format and schema by name and the sensor coverage channel by channel with sample rates. It should also set out consent and provenance terms with rights to train and redistribute, plus who absorbs re-collection cost when the task specification changes. A quote answering all these with numbers is a program. A quote answering with an hourly rate is an input.

Leave a Comment

Build the Dataset Your Models Need.

30 minutes with a senior consultant to scope multimodal capture, labeling, or a physical-AI data pipeline.

Book Your Session
Discuss your Physical AI project Discuss your project