09/01/2026
Your revenue looks great, but how many hours did it take to generate it?
Here's what's at stake: You check the numbers. Revenue is up. You hit your target. Everything looks good until you realize your crew worked 20% more hours than last month to get there. The revenue went up, but so did the labor. That's not growth. That's just grinding harder.
Total revenue hides the truth. Revenue per hour reveals it.
❌The conflict: Most Owners only track total revenue. They celebrate hitting targets without asking how much effort it took. But if you made $50K this week and it took 200 hours, that's $250/hour. If next week you made $50K in 150 hours, that's $333/hour. Same revenue—completely different efficiency and you'd never know if you only looked at the top line.
You're measuring output without measuring input.
✅The resolution: In a recent coaching session, I explained why revenue per hour is the metric that matters: "Over time, the more data that we have, the more that we're going to be able to see how much time it takes to spend per week to generate the revenue that we're generating."
Then I pointed to the gap: "Those hours were less productive, so we know that there's more room for improvement in terms of what we're able to generate per hour."
That's the shift. When you track revenue per hour, you see which weeks were efficient and which were bloated. You find the improvement hiding in your numbers.
Here's the playbook:
🎯Track total hours worked alongside total revenue weekly
🎯Calculate revenue per hour for every week
🎯Compare week-over-week to spot efficiency trends
🎯Identify which jobs or crews are most productive
🎯Use the data to improve scheduling and planning
Revenue tells you what you made. Revenue per hour tells you how well you made it.
❓Question: Do you know your revenue per hour or just your total revenue?
Drop your answer below👇And if this made you look at your numbers differently, share it.