The question I actually ask
Every few months I go through my business and ask one question: is this thing earning its keep, or is it just sitting there. “This thing” might be a piece of equipment, a software seat, a block of my own working hours, or a rented server. The metric that answers this is capacity utilisation rate, and it’s simpler than it sounds. It’s the ratio of how much a resource is actually used to how much it could theoretically be used, over a given period.
You don’t need a factory or a fleet of trucks to care about this. If you’re a one-person business, you own or rent things right now that sit idle more than they run, and you’re paying for the idle time either way.
What capacity utilisation rate actually measures
The formula is:
Capacity utilisation rate = (actual output or usage / maximum possible output or usage) x 100
That’s it. The hard part isn’t the maths, it’s deciding what counts as “actual” and what counts as “maximum” for the specific thing you’re measuring, because those two definitions change completely depending on what you own.
For a physical machine, maximum capacity is usually hours available to run, and actual is hours it actually ran producing something useful. For a software subscription with per-seat pricing, maximum is seats you’re paying for, actual is seats logged in and doing something. For your own time, maximum is hours you’ve set aside for client or production work, actual is hours that went to work that moved something forward.
The number that comes out the other end is a percentage. A rate near 100% usually means you’re close to the ceiling and might need more capacity soon. A rate that’s low and staying low usually means you’re paying for capacity you don’t need yet.
Equipment: the clearest case
This is the easiest one to picture because it maps to something physical. Say you own a piece of production equipment, a printer, a render machine, a piece of studio gear, whatever runs your output. You define your maximum as the hours it could realistically run in a week, say 40 if you’re not running it overnight. You track actual hours it ran doing billable or production work.
If it ran 18 hours out of a possible 40, that’s a 45% utilisation rate. That’s not automatically bad. It might mean you built in buffer capacity on purpose so a busy week doesn’t break you. It might also mean the equipment was a mistake, or that you bought ahead of demand that hasn’t shown up yet. The number doesn’t tell you which one it is. You have to know your own business to read it.
The trap here is measuring “hours turned on” instead of “hours doing useful work.” A machine that’s on but idle between jobs, or running test passes, inflates your actual usage number without inflating anything that pays you. Be honest about what counts.
Staff hours and your own time
If you have even one contractor or VA, capacity utilisation applies to them too, and it applies to you. Maximum capacity for a person is the hours you’re paying for or the hours you’ve committed to the business. Actual is hours spent on work that produced something, not hours spent in the account logged in.
I track this for my own time because it’s the resource I run out of first. If I set aside 30 hours a week for actual production work and I can only account for 19 of those hours going to something that shipped, that’s a 63% utilisation rate on myself. That’s useful to know because it tells me the bottleneck isn’t more hours, it’s what’s eating the other 11.
Be careful with this one and with staff. A low number doesn’t automatically mean someone is slacking, and treating it that way will make people hide their real hours from you. It might mean the work isn’t scoped well, or that you’re overpaying for capacity you don’t currently need, or that admin overhead is eating time that should go to output. The metric flags where to look. It doesn’t diagnose the cause.
Subscriptions and software seats
This is the one solo operators skip and shouldn’t. If you pay for tools with per-seat or per-license pricing, and you’re the only one using most of them, you already have a 100% utilisation rate on seat one and 0% on every seat past that. But the more common version for a one-person business is tool utilisation, not seat utilisation: are you paying for features you configured once and never touch.
Maximum here is the full feature set or usage tier you’re paying for. Actual is what you use in a normal month. If you’re on a plan that includes automation workflows, API calls, or a usage tier you’re nowhere near hitting, your utilisation rate on that spend is low, and that’s a straightforward cost review, not a growth question. This is one of the few places where a low utilisation number has an obvious, low-risk fix: downgrade the tier or cancel the seat.
Space and infrastructure
If you rent a studio, an office, storage space, or run a server, the same logic applies. Maximum is what you’re paying for, capacity, square footage, server hours. Actual is what you use. A render server that’s provisioned for peak load but idle most of the month has a low utilisation rate, and depending on how it’s billed, that idle time might be costing you the same as active time.
The judgment call is the same one as with equipment: some idle capacity is intentional buffer for your busiest period, and collapsing it down to exactly what you use on an average day means you can’t handle a busy day when it comes. Utilisation rate tells you the number. It doesn’t tell you how much buffer is reasonable for your business.
How to actually track it without a system
You don’t need software for this. A simple version:
Pick the resource. Decide what “maximum” means for it in your business, in hours, seats, or units. Log actual usage weekly or monthly, even roughly. Divide, multiply by 100, and look at the trend over a few periods rather than a single snapshot.
A single week’s number is close to meaningless on its own, because almost everything has natural variation. What matters is whether the rate is trending up, trending down, or sitting flat for months. A flat, low number for three months running is a much stronger signal than one slow week.
What this metric can’t tell you
Capacity utilisation rate tells you how much of something you’re using. It does not tell you whether the thing was worth buying in the first place, whether the work that filled the capacity was profitable, or whether a high number is good news. A machine running at 95% utilisation might be running at full tilt on low-margin work while better-paying work waits. A person at 90% utilisation might be busy with the wrong things.
It also doesn’t account for quality. Hours logged as “used” aren’t automatically hours well spent. Pair this metric with something that measures output value, not just output volume, before you make a decision based on it alone. And treat any single period’s number as a starting point for a question, not as an answer by itself.
This isn’t financial or investment advice, and it won’t tell you whether to buy, cancel, or hire. It’s one input, alongside your own judgment about your business, into decisions you still have to make yourself.
If you want more explainers like this on the metrics and methods behind running a one-person business, you can find the rest of them on the Data Research Analysis Collection home page.
Get new guides and videos first — join the Telegram channel.