Monkey Kode
Estimating work done by people who direct AI agents
- MODEL
- Amdahl · USL · Brooks
- INPUTS
- 11
- OUTPUT
- hours · price · days
- SITE
- calculator.monkeykode.com
Agents made some software work dramatically faster and left other work exactly as slow as it was. This formula takes a conventional estimate and adjusts it for a team where each person directs a handful of agents, so the time and cost I quote reflect how the work actually gets done.
The formula
Human hours equal H times the sum of one minus f, plus f divided by s times C of a, all multiplied by one plus gamma times P minus one. C of a equals a divided by one plus alpha times a minus one, plus beta times a times a minus one. Price equals hours times rate times one plus buffer. Duration equals hours divided by P times focused hours per day.
Point at any symbol to see which input it stands for in the calculator below.
Try it with your project
The estimate
How it works
Start with the conventional estimate
H is the number of hours an experienced team would need without agents. It is still the best measure of how much work a project contains, so everything else adjusts it.
Split it into two kinds of work
A share f is work agents can carry out, such as writing code, tests, migrations, and documentation. The remainder is work only people can do: understanding what you need, making decisions, and signing off on the result. That part takes as long as it always did.
Speed up the agent share
One agent multiplies a person's output by s. More agents help with diminishing returns, because every agent's work still passes through one person for direction and review, and agents working side by side step on each other. C(a) describes that curve. With my starting values it rises, peaks at about four agents per person, and then falls.
Account for the team
Every added person brings handoffs and shared decisions, so γ adds a small cost per extra teammate. A bigger team finishes sooner on the calendar while the total hours go up a little.
What each symbol means
| Symbol | Meaning | Starting value |
|---|---|---|
| H | Conventional estimate in hours | per project |
| f | Share of the work agents can carry out | 95% |
| s | Leverage from one agent: hours of conventional work delivered per hour spent directing it | 9 |
| a | Agents each person directs | 4 |
| C(a) | Effective agents per person once review and overlap are counted | 2.11 at a = 4 |
| α | Review bottleneck: how much agent output waits on one person | 0.10 |
| β | Agent overlap: conflicts and drift between agents working in parallel | 0.05 |
| P | People on the team | 1 |
| γ | Coordination cost per extra person | 0.08 |
What the formula tells you
There is a sweet spot
Past about four agents per person, the person becomes the bottleneck and extra agents slow things down. Adding agents past that point is the wrong lever.
There is a ceiling
If 5% of a project needs human judgment, the work can never go more than 20 times faster, however many agents are running. Clear requirements raise that ceiling more than anything else.
People buy speed
Three people with agents cost about 16% more than one and finish in well under half the time. When a deadline matters, that trade is usually worth making.
The starting values reflect my own experience running two to five agents at a time, so treat them as a starting point. The share agents can handle changes with the kind of work, and the numbers get more accurate the more real projects they are checked against.
The structure borrows from three older ideas: Amdahl's law for the split between human and agent work, Neil Gunther's Universal Scalability Law for the agent curve, and Brooks's law for team coordination.