Newsletter
192 hours worked. $50,000 short on billing. The problem was not effort
If you find out at the invoice run, you found out a month too late. But the scoreboard that fixes it is still built from hours, and hours can lie.
For engineering firm owners
If you find out at the invoice run, you found out a month too late. But the scoreboard that fixes it is still built from hours, and hours can lie.
Updated November 2026 from my August letter. What changed: our scoreboard counts hours times rate, not invoices, so I show how far apart the two ran and what that means on fixed-fee work.

Picture your best team leader at the end of a month. He worked 192 hours, a full month plus a couple of Saturdays. 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 the invoices went out and the number was $50,000 short.
Every operations leader I have described that month to knows exactly which person on their team it is.
Nobody did anything wrong that month. The lead was watching the only scoreboard anyone had given him. Hours were visible. Billing was not. So he chased the number he could see.
People do not optimize for what they are told matters. They optimize for what they can see.
You know the ritual that follows. The number comes in light. You call the meeting, walk through the target again, and everyone recommits. Thirty days later you are in the same meeting with a different excuse. That meeting is an autopsy.
A shortfall discovered at the invoice run is a fact. The same shortfall discovered on the 12th is a decision: move a designer, push a proposal, pick up the phone.
There is research behind seeing it often. A 2016 review of 138 experiments found that getting people to check their progress more often helped them reach their goals, and the effect was larger when progress was written down or made public. It is a moderate effect, not a law. A number your team can see every day tends to beat a target you explain once a month.
What we built
The least glamorous thing we shipped this year.
On July 29 we gave each team leader a billing tab in our own platform. Every hour logged in time tracking, times that person's billing rate, by project, by person, by service item. It rolls up per team leader, month to date, against a monthly goal set once that carries forward on its own.
The pacing is what makes people look at it. A mid-month number against a full-month target paints everybody red, and the board gets ignored by the fifth. Ours works out how much of the month has gone by. On day 12 of a 31-day month, 39 percent of the month is gone, so a leader at 40 percent of goal shows green.
We built it so a missed month can't hide. A team leader with a goal who logs nothing still counts. Projects with no manager land in their own bucket with their own total. Hours with no billing rate show up in a warning instead of quietly counting as zero. Time spent chasing a job before it's won is left out.
The tradeoff I skipped in August
The fix is still built from hours.
In August I wrote that this was the same number the client gets billed. It isn't. It is the hours-times-rate math finance starts from, not the invoice. For July, August and September work, the logged total came within about 1 percent of what we invoiced the month after. Month by month, we invoiced 2 percent more, then 10 percent less, then 4 percent more. Line the dates up on our 16th-to-15th billing period instead, and one month misses by 12.

The bigger problem isn't the gap. It's what the number rewards. About 70 percent of what we billed this year was fixed fee. On a fixed fee, an extra hour doesn't raise the invoice. It lowers the margin. On an hours scoreboard, a job running past its fee looks great: more hours, more value, a greener bar. I wrote in August that the number cannot flatter anyone. It can. It flatters exactly the job you should be worried about.
Run the team leader from the top of this letter through our own tab, and his 192 hours could well light it up.
Goal-setting research has warned about this: a goal can produce a narrow focus that neglects everything the goal doesn't count. Here, what it doesn't count is the fee.

In October we added a second number on top: a month-end forecast. It now leads the email I get on the 17th. For a fixed-fee job with a deliverable due that month, the forecast uses the contract amount, not the hours. Where all it has is hours, it calls the number a provisional stand-in and asks the project manager to confirm the real amount.
That helps. It doesn't solve it. Any job without a dated deliverable still leans on hours. Hours arrive every day. Invoices arrive once a month. The early number is the biased one, and I would still rather have it, as long as nobody mistakes it for the invoice. Read hours next to the fee, never alone.
Here's the exercise for this week. On the 12th of the month, what can your team leaders actually see? If the answer is hours and nothing else, you know which number they will chase. If it is hours times rate, ask a second question: on which of your fixed-fee jobs would that number look best right now? Open those jobs first.
Tell me your answer to both through our contact page. I read every one.
Michael Groselle, PE
Founder and CEO
Modern Engineering Solutions
mod-eng.com
Keep reading
More to read
- Your project manager inherits the files. Everything that actually matters stays with whoever sold the work
- I spent eight rounds making a blind tool smarter. A plain chat beat it, so I closed it
- I told you to audit the setting. I didn't audit mine
- You do not stop the work to fix the work. You just write it down
What we do
Planning a project?
Talk to an engineerTalk 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