# Node Economics: Human Time vs. System Time

The arithmetic behind the transformation outlook. Show the math to the executive, out loud, step by step. The goal is understanding, not a black-box number. And state plainly, more than once: this is about the capacity an organization can bring to its mission, not about profiteering or replacing people to cut cost. We are modeling impact, not headcount reduction.

## Human Time vs. System Time

Show this comparison first, with real numbers:

- **Human node.** A standard work commitment is 40 hours per week, roughly 52 weeks per year, less vacation and holidays. Use **~1,880 productive hours per year** as the default (40 x 47 working weeks) and let the executive adjust. A human node also degrades: fatigue, context-switching, meetings, sleep.
- **System time.** An agent node runs 24 hours a day, 7 days a week, 52 weeks a year: **8,736 hours per year**, with no fatigue and the ability to run tasks in parallel.

The raw ratio is roughly **4.6x** on hours alone (8,736 / 1,880), before accounting for parallelism (one agent running many concurrent tasks) or the agents an agent can itself spin up. Show this ratio; then show that parallelism can multiply it further. Be careful and honest: a raw hours ratio is not a raw output ratio. Many roles are not throughput-bound, and quality, judgment, and accountability do not scale with hours. Say so.

## Per-role productivity and cost

For each role in the org chart the executive wants to model:

1. **Human hours/year:** default 1,880, adjustable.
2. **Average annual salary:** benchmark by the company's HQ location, the role, and the industry. If you can find credible public benchmark data, use it and cite it. Otherwise ask the executive for an estimate for that role in that location and industry; an estimate is fine, tag it `estimated`.
3. **Fully loaded cost:** salary x a loading factor (benefits, overhead) if the executive wants it; default loading 1.3, adjustable. Optional.
4. **Agent running cost:** estimate the annual cost to run an equivalent agent node (tokens/inference, orchestration, tooling). This varies enormously by task; give a modeled range, not a false-precision point, and label assumptions. A light augmentation agent and a heavy autonomous agent differ by orders of magnitude.
5. **Node-hours available:** track, for the whole organization, total human node-hours per year (headcount x hours) and total potential agent node-hours (agent count x 8,736 x an average parallelism factor). This is the "capacity available to the mission" number.

## Scenarios: bear, base, bull

Model three cases for how much capacity gets added and what it does to output, revenue, and profit. Always three; never a single line.

- **Bear:** slow adoption, low parallelism, heavy governance drag, conservative output-per-hour assumptions. Adoption constrained by the readiness gaps and risk posture.
- **Base:** the most likely path given the org's actual velocity, readiness, and constraints.
- **Bull:** fast adoption, high parallelism, agents spinning up agents, readiness gaps closed on schedule.

For each scenario track: added node-hours, resulting output multiple, and a modeled effect on revenue and profit. Keep every assumption visible and adjustable. Label all forward numbers `modeled`.

## The framing (state this to the user, clearly)

We are not here to profiteer. The point of measuring capacity in node-hours is to show how much more an organization can accomplish toward its mission, its customers, and its people, not to justify cutting the workforce. When a human node stops laboring on what a machine can do, the human node moves to what only humans can do: judgment, relationships, creativity, accountability. Make this explicit in the conversation and in the deliverable. If the executive frames the exercise purely as a cost-cutting play, push back and re-anchor on impact.

## Numbers to carry into the template

The transformation-outlook template expects, per its schema: human hours/year, system hours/year, the raw ratio, per-role rows (role, human hours, salary, agent cost estimate, provenance), org-level node-hour totals, and the three scenario tracks (added hours, output multiple, revenue effect, profit effect). The template renders the Human Time vs. System Time math, the per-role table, and the scenario chart; you supply the numbers and the assumptions.