Newsletter
192 Hours Worked. $50,000 Short on Billing. The Problem Was Not Effort
A team leader worked 192 hours and still missed billing by $50K. The fix was not more effort but a pacing scoreboard that shows the real number on day 12.
Modern Engineering Solutions
Engineer Your Freedom
The Modern PE
September 2026
192 hours worked. $50,000 short on billing. The problem was not effort.
If you find out on invoice day, you found out a month too late.
Your best team leader worked 192 hours last month.
He touched every task on every project. He pulled admin work back from the juniors because doing it himself was faster than explaining it. Then invoice day came and the number was fifty thousand dollars short.
192
Hours worked
last month
100%
Effort
given
-$50K
Short on
billing
That is a story my business coach tells about a CEO he worked with. Every operations leader I have repeated it to knows exactly which person on their team it describes.
Here is the part that should bother you. Nobody in that firm did anything wrong that month. The lead was watching the only scoreboard anyone had given him. Hours were visible. Billed project value was not. So he chased the number he could see and optimized beautifully for a metric that does not pay for anything.
People do not optimize for what they are told matters. They optimize for what they can see.
My coach calls the gap between those two things scoreboard collapse.
The Autopsy Meeting
If you run a firm, you already know the ritual that follows. The month closes. Finance assembles the invoices. The number comes in light. You call the meeting, walk through the target again, and everyone nods and recommits. Thirty days later you are in the same meeting with a different excuse. That meeting is an autopsy, and the body is always cold by the time you get there.
The information arrives at the one moment it is useless. A shortfall discovered on invoice day is a fact. The same shortfall discovered on the 12th is a decision: move a designer, push a proposal, pick up the phone. Every month you learn the number after the month closes, you spend a full month of payroll finding out what two weeks of warning would have fixed for free.
A metric your team can see every day will beat a target you explain to them once a month, every time.
Explanation is a speech. A scoreboard is a system that runs whether anyone is talking or not.
What We Shipped On July 29
We shipped the fix into our own platform, and it is the least glamorous thing we have built all year. Every hour logged in time tracking multiplied by that person's billing rate, broken down by project, by person, by service item. It is the same hours times rate math finance uses to invoice, so the number a team leader steers by all month is the number the client gets billed at month end. It rolls up per team leader, month to date, against a monthly goal that carries forward on its own.
Day 12 of a 31-day month — green means on pace
40% billed
Elapsed-time line
Day 1 Day 12 (today) Day 31
At or above the elapsed-time line on the 12th = on track for the 31st
The pacing is what makes people look at it. A mid-month number compared against a full-month target paints everybody red and the dashboard gets ignored by the fifth. Ours computes how much of the month has elapsed and marks a leader green when they are at or above that line. On day 12 of a 31-day month, 40 percent attainment is on pace, and the tab says so. Green on the 12th means on track for the 31st.
The Number Cannot Flatter Anyone
A team leader with a goal who bills nothing still counts in the denominator. Billing from anyone without a goal is excluded and reported separately. Projects with no manager assigned land in their own bucket with their own dollar total, so a coverage gap shows as a gap.
A scoreboard your team can quietly game is worse than no scoreboard, because now the leadership team believes it.
A missed month stays in the denominator. Unassigned projects show as a gap. Hours that could not be priced get flagged instead of counted as zero.
Team leaders see their own book, enforced on the server. Finance sees cost and margin on top of it. Nobody assembles any of this. It falls out of hours the team already logs.
What Actually Changed
The build was the cheap part. What changed is when the conversation happens. My team leaders now see the same number I see, on the same day I see it. When one of them is behind on the 12th, the conversation is about which project gets staffed this week instead of what went wrong last month.
A shortfall discovered on invoice day is a fact. The same shortfall discovered on the 12th is a decision.
The Question Worth Asking This Week
If your team is working hard and still missing the number, do not audit their effort. Ask one question instead: on the 12th of the month, what can your team leaders actually see? If the answer is hours and nothing else, you already know which number they will chase for the next 19 days. And you already know what invoice day is going to feel like.
Reply and tell me your answer.
I read every one.
Michael Groselle, P.E.
Founder and CEO, Modern Engineering Solutions
mod-eng.com | contact an engineer | 214-833-6748
Talk to an engineer
Tell us about your project.
An engineer reads it
Not a salesperson. Someone who can tell you whether the pathway is real.
You get a first answer
Your options, the agencies involved and the questions that decide cost and schedule.
You decide
No commitment to have the first call.
Prefer the phone? (214) 833-6748