▪ TODAY’S ISSUE VALUE
⏱️ Time check.
The utilization gap, a 10-person team
Assumption
Reality
Billable rate assumption
85%
60%
Non-billable hours per person
25
64
Leaked Revenue per team/month (at $100/hr)
$25,000
$64,000
▪ THE PROBLEM
On paper, your team is 85% billable.
In reality, it's closer to 60%.
This is a number we see repeatedly when working with agencies and consultancies - and this is also the number we had ourselves before we started to actively work on becoming more efficient.
You do the math on your team size and your average rate, and the number usually lands somewhere between uncomfortable and alarming.
One obvious cause is the pipeline. If leads dry up, utilization drops. That's a sales problem and a separate conversation.
This issue is about the internal problems - the ones you can actually fix right now.
Why your team is losing 25 points of billable time
1. Sync culture instead of async communication
Most of your team meetings exist because nobody built the habit of recording a Loom instead. A 45-minute status call with six people costs you 4.5 billable hours. A 5-minute Loom costs one person 5 minutes.
2. Scope creep, nobody reports until it's too late
For most of the teams, this will be rated #1.
Here’s how you get there:
You agree on a maximum cap with the client.
Work runs over.
The team knows it, but nobody escalates.
By the time you find out, the overage is already non-billable. You cannot tell your client, “Hey, we agreed on 100 hours max for this job, but we actually spent 250 - here’s your invoice.”
The issue isn't dishonesty, it's human nature.
People don't like delivering bad news, especially when they're hoping they'll somehow catch up. So they don't say anything, and you only find out when the budget is burned.
3. Unbalanced workload across the team
Some people are booked out three weeks ahead. Others are searching for things to do.
You don't have a live view of capacity, so the same senior people keep absorbing work while juniors sit underutilised. The overbooked person is burning out. The underutilised one is quietly disengaged.
The more complex and diverse your team structure is, the harder it might be to fix this one.
4. Admin work that was never systematised
Your team is manually preparing reports where all the data already exists in your systems.
Someone is copying timesheet rows into an invoice format every billing cycle. Another person is reformatting data before it goes to the client.
None of this is billable, none of it is hard to fix, and all of it compounds silently across every team member every week.
5. Poor time tracking discipline
People log hours in batches at the end of the day (or worse, the end of the week). Memory degrades.
Work that happened gets attributed to the wrong project or is never logged at all. Your utilisation data becomes unreliable, so every decision based on it is unreliable as well.
6. Context switching between too many projects
A team member jumping between five active projects in a day loses more time to context switching than most people realise. Each context switch carries a cognitive tax. The result is fewer billable hours completed than the raw time available would suggest.
Need help automating your processes?
Start with an efficiency scorecard here
▪ BACK TO TIME & EFFICIENCY
What you can actually do about it
Communication:
Looms solve the meeting problem without any automation. No tool required — just a cultural default. For client calls that do happen, Fathom automatically records, transcribes, and summarizes.
Send the summary to the team. Stop inviting people who only need to read the outcome.
Scope creep:
This needs to be caught proactively, not discovered after the fact. Set automated triggers in your project management tool to fire at 50% and 75% of a task's allocated hours.
This can be done directly in your tools, let’s say in ClickUp with built-in automations, or with an external automation, e.g., n8n-run.
When the threshold hits, the system pings the team member for a quick status update. Not a meeting, but a one-line reply.
This gives you the window to act: extend the budget, reduce scope, and flag it to the client. You can only manage what you know about in time.
Load balancing:
A Looker Studio dashboard connected to your project management and time-tracking data gives you a live view of workload vs. capacity for each team member. This isn't a complex build — it's usually a few hours to set up. The payoff is immediate visibility into who's overbooked and who has room.
Admin work:
This is where automation delivers the clearest ROI. Report generation, invoice prep, timesheet formatting - all of it can be triggered automatically using n8n and your existing tools. The data is already there. You're just paying people to move it around manually.
Time Tracking Discipline:
This is a tool and process problem. The tools you give to your team must be easy to use and allow real-time tracking.
Even if your team is doing on-site work or does not have laptop access - there are solutions that allow them to track time the moment it’s spent, not 3 days later.
Additional automated daily reminders help to enter any time that has not been tracked during the day.
Context Switching:
This one is purely a process issue. You need to limit the number of projects any team member is working on at a given moment. Moreover, you need to control how they switch between those projects.
Ideally, 1 day equals 1 project.
This way, there is zero cost of context switching within a day.
The bottom line
The gap between 85% and 60% isn't one big problem. There are six small problems running simultaneously. None of them requires a big budget to fix. Most of them require a system and a decision to stop tolerating the leak.
What if we don’t bill hours?
Most efficient businesses I know don’t sell hours.
They sell retainers, one-offs, outcome-based, productized services, etc.
However, they still have hours as a primary internal metric - people spend hours working on tasks.
If you don’t track and control those numbers, you lose efficiency.
We (at 2V) sell different things, and my goal is to make our team 10x more efficient without any new hires.
But in the end of the day, even the most efficient team members that utilize AI and automation at its full capacity, still have 40 hours per week - very efficient hours now, but still 40.
— Valerian