The billable utilisation rate measures the percentage of paid working hours that directly produce billable client revenue, but studios frequently measure it wrong by calculating against arbitrary targets rather than total paid payroll hours. When a software studio excludes internal meetings, administrative tasks, or development environment maintenance from the denominator, the resulting metric hides operational overhead and distorts cost calculations. A healthy, sustainable billable utilisation rate for a studio with salaried engineers sits between 70 and 80 percent, leaving sufficient capacity for maintenance, business development, and technical learning.
How to calculate your billable utilisation rate correctly
The basic formula for calculating utilisation is straightforward: divide billable hours by total available hours and multiply by 100. The errors happen when studio managers define what counts as total available hours. Many studio leaders calculate utilisation against an arbitrary target, such as 30 billable hours per week, and call 30 billable hours a 100 percent rate. Other managers remove internal administrative work from the denominator entirely, treating unlogged hours as if they never happened.
If an engineer is paid a fixed salary for 40 hours per week, those 40 hours represent your baseline capacity. If that engineer logs 28 billable hours to client accounts during a week, their true billable utilisation is 70 percent. It does not matter whether the remaining 12 hours were spent fixing local staging environments, writing build scripts, sitting in company standups, or reading technical documentation. The cost of those 12 hours remains on your payroll. Excluding those hours from your denominator distorts your actual cost per billable hour and leads to flawed project estimates.
Understanding the capacity denominator
To establish a accurate baseline, every paid hour must be included in your primary calculation. When you evaluate studio performance, you need to know how much paid capacity converted into billable revenue. Using reduced capacity baselines, such as subtracting vacation days or internal meetings before running the calculation, creates a secondary metric called net utilisation. While net utilisation can help evaluate short-term scheduling, gross utilisation against total paid payroll hours is the only metric that tells you if your studio pricing covers your actual overhead.
Accounting for unbilled internal work
When team members skip logging non-billable hours because they feel those hours do not matter, your calculated utilisation figures become artificially high. You end up with studio reports showing 90 percent utilisation while your net profit margin shrinks, because the actual labor cost required to deliver each billable hour is higher than your internal spreadsheets reflect. Encouraging engineers to log all work, including build maintenance and administrative overhead, provides the visibility required to price future client engagements correctly.
Why a 100 percent billable utilisation rate signals systemic failure
In a service business, aiming for 100 percent billable utilisation across a team of salaried engineers is a structural error. A studio operating at complete billable capacity has zero resilience. When client emergencies happen, production infrastructure fails, or scope changes occur, engineers must either work unpaid extra hours or fail client commitments.
The operational debt of maxed-out engineering teams
High utilisation figures frequently hide growing technical debt. When every available hour is scheduled for client deliverables, teams skip critical internal maintenance. Repositories fall behind on dependency updates, automated test suites slow down, and internal documentation becomes obsolete. Over several quarters, this technical debt increases the labor required to ship standard client features, reducing your real profitability even as your reported utilisation figures look perfect.
A studio running at maximum capacity also stops investing in internal tooling and skill development. If senior engineers lack dedicated, paid time to improve deployment automation or evaluate new architecture patterns, studio output quality plateaus. What looks like peak operational efficiency on a monthly management dashboard is usually an early indicator of employee burnout and stagnant service offerings.
Why capacity buffers preserve studio profitability
Maintaining a target billable utilisation rate around 75 percent provides an operational cushion. That buffer allows your team to absorb sudden spikes in client work without burning out staff or hiring temporary subcontractors. During launch weeks, engineers can temporarily step up billable work to 85 or 90 percent by pausing internal research and tooling projects. That operational flexibility vanishes if your baseline plan requires 100 percent billable performance every week.
| Work Category | Weekly Hours | Capacity Share | Primary Studio Value |
|---|---|---|---|
| Client Deliverables | 30.0 | 75% | Direct billable client revenue |
| Internal Operations | 4.0 | 10% | Standups, admin, resource planning |
| Engineering Infrastructure | 4.0 | 10% | Tooling, dependency updates, CI/CD |
| Sales & Technical Scoping | 2.0 | 5% | Estimates, architecture reviews, proposals |
Honest non-billable time tracking makes performance metrics usable
You cannot improve studio capacity allocation until you track non-billable hours with the same care you apply to client projects. Non-billable time is not wasted time; it represents the operational investment required to keep a software studio running smoothly. Categorising internal work into specific areas, such as deployment infrastructure, sales support, and administrative management, reveals where studio resources are actually consumed.
Categorising internal hours without adding friction
To make internal time tracking effective, keep your non-billable task categories broad and straightforward. Four or five clear internal buckets, such as Internal Dev, Sales Support, Admin, and Operations, are sufficient for most small studios. If you force engineers to choose between dozens of granular internal codes, compliance drops and people begin guessing where their time went at the end of the week.
How flat pricing supports complete time tracking
Many studio owners hesitate to track internal projects thoroughly because traditional SaaS vendors increase prices as you add projects, tasks, or users. When vendor costs scale up with every seat or project opened, studio managers start limiting who can log time or restrict internal tracking categories. If you are reviewing software options following Harvest's acquisition by Bending Spoons and their move to per-seat pricing models, you can read our Harvest alternative comparison to see how metered software impacts tracking habits.
Accurate metrics require tracking systems that do not financialise internal operational records. Our flat pricing structure gives your studio unlimited users, projects, and time tracking on a single predictable plan, ensuring you can track internal tooling, client accounts, and administrative hours without paying additional fees for every person or project added.
When high utilisation targets are actually appropriate
There is an exception to the rule against high utilisation targets: contractor-based studios and dedicated subcontractor teams. If your business model relies entirely on external contractors who are paid exclusively for approved, billable client hours, targeting 90 percent or higher billable utilisation for those specific engagements is financially sound. In that model, the risk of unbilled time is priced into the contractor's hourly billing rate, and core studio overhead is managed separately by salaried leadership.
However, applying contractor utilisation targets to salaried staff creates severe operational distortions. Salaried employees expect consistent compensation, paid time off, and investment in professional growth. Their cost to your studio is fixed whether they bill 10 hours or 40 hours in a given week. Trying to force salaried engineers into contractor-style utilisation targets leads to inaccurate time entries, hidden extra hours, and misleading job costing data.
Measuring human utilisation alongside AI agent execution
As studios incorporate automated tools and AI agents to write code, generate test suites, and execute builds, calculating team capacity becomes more complex. An AI agent does not have a 40-hour physical working week, nor does it require administrative buffer time or paid leave. Treating an automated agent as a human seat in your time tracking software distorts your team capacity metrics and inflates software costs.
Instead of forcing autonomous tools into traditional human seat models, track machine execution as task outputs linked directly to project deliverables. Keep human utilisation metrics focused strictly on your engineering, design, and management staff. Measuring human billable hours against total salaried payroll while separately logging machine execution costs ensures your billable utilisation rate remains a clear, dependable indicator of human capacity and studio health.