Velocity

Same salary. Same title. 48 times the cost.

Give 3 people the same 3-unit task. One finishes it in 20 minutes. One takes 6 hours. One takes 2 days.

Same salary band. Same job title. Same finished thing handed to the same customer.

Now put a dollar on it. Round numbers so you can follow the arithmetic: at $120,000 a year across 2,000 working hours, that person costs you about $60 an hour.

Finished the same task in	Units consumed	Velocity	What that one task cost you
20 minutes	0.17	about 18	$20
6 hours	3	1.0	$360
2 days	8	0.38	$960

Identical work, and it cost you 48 times as much coming from one person as from another. Your payroll report shows all 3 of them at $120,000, in a tidy column, correctly. It is right about every number on it and blind to the only thing you wanted to know.

That is financial theater with good posture: a report that tells you precisely what you paid and nothing about what you got.

If you are staring at a payroll you suspect is too big, this is the number that tells you whether you have too many people or under-equipped ones. Guessing between those 2 is how founders cut the wrong headcount.

You buy hours. You sell output. Nobody repriced the gap.

The labor market prices people on hours and titles. Margin comes from units delivered.

A trader would call that mismatch an arbitrage. You can just call it the gap between what you pay for and what you sell, and it got wider the year AI landed. No salary survey has caught up, and none of them are built to.

We will say the uncomfortable half out loud, and we have standing to, because it is our own profession that started it. Accountants and lawyers invented the billable hour, and then the rest of the business world copied the homework: 100 years of pricing a human being by how long they sat there. It held up while a person and an hour produced roughly the same work no matter whose hour it was. That stopped being true. The timesheet has not noticed.

Crabtree's ratio, and the thing AI broke underneath it

We have run the Labor Effectiveness Ratio for 15 years. Greg Crabtree's instrument, gross profit divided by direct labor cost, and it worked because of one quiet assumption nobody had to state: 2 people on the same salary produce roughly the same amount of work, so cost stands in for capacity.

AI ended that assumption in about a year. One person with real AI leverage now produces several times the output of an identically paid colleague sitting 6 feet away, and the ratio goes noisy, because overstaffed, underpriced, and AI-illiterate all read the same on it.

So we fixed the denominator rather than abandon the ratio. Velocity is the number that falls out of that repair. The word is borrowed. The denominator underneath it is ours.

The formula, now that you want it

Velocity = Estimated Units ÷ Actual Units Consumed

Both sides are Atomic Units, our fixed 2-hour block of standard work. The estimate comes from a shared, calibrated library, never from the person doing the work. Score somebody against their own estimate and the estimates inflate, quietly, inside a month.

Software teams have a velocity too, and it is a different instrument pointed at a different problem. Story points forecast a sprint. This one prices a payroll.

The scale has 3 readings and that is all it has:

• 1.0 is delivering at the calibrated standard.
• Above 1.0 is faster than standard, and it is usually tooling, skill, or scope discipline.
• Below 1.0 is consuming more than standard, and it is usually a skill gap, unclear scope, or an estimate that was wrong before anybody started.

Read those causes again. Each direction has 3 or more honest explanations, which is exactly why the number is a reading and never a verdict.

Why we will not publish a velocity band

We publish bands. The Labor Effectiveness Ratio entry ships 5 of them, and you can find your own business on that table this afternoon, because gross profit and salaries mean the same thing in your books as they do in ours. Most service firms live between 2.0x and 3.5x, and that number is worth something precisely because it was read off other people's real financials.

Velocity does not work that way, and we are not going to pretend it does so the page looks more authoritative.

Velocity runs on your own calibrated library. Change the library and every velocity in your company moves without one person changing how they work. A published velocity benchmark would be a fact about somebody else's estimating library, wearing the costume of a fact about your team.

A benchmark is only honest when both sides measured the same way.

So the benchmark for velocity is your own team, last quarter, on the same library. That is a smaller claim than a table of industry figures, it is a true one, and you will learn more from watching your own line move than from a benchmark nobody can check.

Too many people, or people you never equipped

Individual velocity rolls up to team, and team rolls up to firm. Firm velocity feeds back into the Labor Effectiveness Ratio and makes that ratio diagnostic again, because it finally separates 2 findings that look identical:

1. We have too many people.
2. We never equipped the people we have.

On a payroll report, on a P&L, and on a weak LER, those 2 are the same picture. Their remedies are opposites. One says reduce headcount. The other says the headcount is fine and you owe them tools, scope, and training. Guessing between them is how a founder cuts good people and keeps the constraint.

Direct labor is the population this runs on, and the Salary Cap is what the whole bill is allowed to be. Velocity is what you get for it.

A low-velocity team is a management finding before it is a people finding

Velocity is governed by scope clarity and tooling access, and both of those belong to management.

Say it in plainer words, because that sentence is still 2 abstractions in a nice coat: nobody wrote down what done means, and nobody bought them the tools. A team running under standard is usually pointing at a choke point in the work, not a shortfall in the person. The number they carry is partly yours.

So before this number is ever used on a human being, go check the 2 things you owed them. Then check them again.

Sometimes it really is the person. That finding is real, it is the easiest one on earth to reach, and that is exactly why you reach it last. The order is the whole ethic here, because the wrong call is not a rounding error. It is somebody's job on one side and your own capacity on the other, and neither comes back cheaply.

Which of the 2 findings you are actually holding is a reading of one company: your library, your mix, your margins, what your team was handed on their first day. Publishing the distinction is the easy half. Making the call is what a CFO Huddle™ is for.