The Depot's payroll office pays its pickers and its robots side by side. Find out what one good pick really costs each of them, what autonomy, remote operators and a learning curve do to that number, what a fleet is worth, and who keeps the saving. Every number is computed by a tested model; every assumption is on the page and yours to change. About 60 minutes of play.
The Depot is a warehouse in Busytown. Pickers lift items out of totes into orders, and the Depot's owner is being pitched a robot that does the same. The question a COO, an investor or a founder has to answer is not "can the robot pick?" but when does it beat a human shift, and what has to be true? The payroll clerk upstairs answers it the only fair way: what does one task done right cost each of them? Every term with a wavy red underline is tappable.
Covers unit economics of automation: cost per task · labour cost: BLS wage and benefits data
Start with the number the robot has to beat. The default wage is the national mean for "laborers and freight, stock, and material movers, hand" in the Bureau of Labor Statistics' May 2025 survey, $20.32 an hour. An hour of work costs the employer more than the wage: the benefits load in BLS's December 2025 employer-cost survey was $13.79 on $32.36 of wages for private industry, 42.6%. Then divide by what the hour produces.
A robot isn't paid by the hour, but every year of it has to be paid for. Its payslip, per scheduled hour: a capital charge that repays the price and the integration over its life at the discount rate, upkeep, power, its share of a remote operator, and rework for every miss. Then divide by the good picks it actually makes, which is where uptime, cycle time, success rate and calls for help come in. Cost per good pick = the hour's cost ÷ the hour's good picks.
Covers total cost of ownership · capital recovery vs depreciation · utilisation
The picker costs the same per hour whether the Depot runs one shift or three. The robot's capital and upkeep are fixed per year, so every extra hour it works makes each pick cheaper.
Every number the lab uses, where it comes from, and a slider. Changes here carry through every step. BLS EIA are cited public data (see SOURCES.md); illustrative numbers are assumptions to change; toy marks the teaching model in step 3.
No robot in a real warehouse is fully autonomous. Some of the time it gets stuck (an item it can't grip, a tote out of place) and calls for help: an intervention. A remote operator fixes it by teleoperation. Two numbers describe this: interventions per running hour λ (or its inverse, the MTBI), and the operator time each one takes, τ (minutes per call, written as a share of an hour). Together they set the operator ratio: one operator can keep up with at most occupancy ÷ (λτ) robots.
Covers autonomy as a rate · teleoperation economics · the last 5% problem
Autonomy quoted as a percentage hides the rate. At 10 seconds a pick, the robot attempts 360 picks a running hour, so every point of autonomy below 100% is 3.6 calls an hour.
Every intervention is a labelled example of something the robot couldn't do, recorded exactly where it went wrong. Feed them back into training (the idea behind DAgger and human-in-the-loop learning) and the next software release calls for help less. The more robots deployed, the more hours, the more lessons: a flywheel. How fast it spins is not something this lab can measure, so it is modelled as a transparent toy: interventions per hour fall by a fixed share each time the vendor's cumulative fleet hours double, a learning curve borrowed by analogy from Wright's 1936 study of airframe labour (about 20% per doubling). No robotics company's curve is used or implied.
Covers learning curves · data network effects · one line of DAgger / HIL
Now the Depot considers a fleet. Year 0: it pays for the robots and their integration. Every year after: it saves the payroll for the picks the robots make, minus what the robots cost to run. The clerk reports three numbers: payback (when cash in covers cash out), NPV at the discount rate, and IRR. Then two questions a board asks: rent or buy, and which assumption matters most (the tornado).
Covers capital budgeting: payback, NPV, IRR · RaaS vs buy · sensitivity analysis · break-even wage
Each bar moves one assumption to a low and a high value (labelled), everything else at the books, and shows the fleet's NPV. Widest first.
With twenty robots sharing a remote desk, two of them sometimes get stuck at once, and one waits. A waiting robot isn't picking. This is a queue: calls arrive at random, operators serve them, and the Erlang C formula from the M/M/c queue gives the chance a call waits and how long. The arrival rate depends on how many robots are running, which depends on how long they wait, so the model solves for both together. Then the other fleet question: how many spares.
Covers queueing: M/M/c, Erlang C, the finite-population check · pooling · spares (binomial)
A robot replaces payroll. That payroll is a pie, and the customer is the last to be served: the robot maker takes its hardware and service price, the integrator its fee, the money tied up its interest, the operators their wages, and rework and power their share. This is a one-step illustrative split of one robot-year at the books' numbers, with margins you can change. It shows the mechanics, not any company's economics.
Covers value capture · price ceilings · robotics diligence
A robotics startup's deck quotes an MTBI, an operator ratio and an autonomy rate. Put its claims here; the checklist tests them against each other and the books, and lists what to ask for. The 95% range on MTBI is the exact Poisson interval for the number of interventions behind it.
Three pitch decks from three fictional robot companies, each with one flawed line in its spreadsheet. For each: run the deck's own sheet through the model (it reproduces the claim), pick the fix, re-run it, and name what the deck got wrong. The tempting fixes are on the list; they move the number the wrong way, or not at all. Each deck is scored on the re-run and the diagnosis.
Ten questions. Answer each by operating the widget in the step named, at the books' default assumptions (reset them in step 1 if you've changed any). Eight or more earns the check.
node tests/check.js checks each against hand-computed cases and prints every number this page quotes.Sources (dated, with what each supports, in SOURCES.md): BLS OEWS, 53-7062 · BLS Employer Costs for Employee Compensation · EIA Electric Power Annual · IFR World Robotics 2025 · Wright (1936), "Factors Affecting the Cost of Airplanes" · Erlang (1917) · Ross, Gordon & Bagnell (2011), DAgger.
Part of a series of hands-on labs: Inference Kitchen (serving economics) · Compute Deal Desk (compute deals) · Arm Playground (kinematics and control) · Demos to Deployment (imitation learning) · Robot Payroll (the business of deploying robots)