Here is a familiar complaint from small teams: “The monthly bill went up again and we have no idea why.” If that sounds like your inbox, you are in good company. The symptom is a total that moves without explanation. The diagnosis, nine times out of ten, is that nobody is looking at the cost of a single unit of whatever the business sells or serves. Let us walk through the problem and the fix like a quick check-up, no jargon required.
The symptom: a number that cannot answer questions
A monthly total is a poor witness. Ask it why it rose and it shrugs. Did you gain customers? Did one feature get popular? Did something quietly run all weekend? The total is the same in every case, so it cannot tell the stories apart. Teams then fall back on guesses, and guesses produce arguments rather than decisions.
Typical warning signs that you are trapped in this pattern include:
- Different people give different explanations for the same increase.
- The bill is only discussed when it is higher than expected.
- Nobody can say what one customer, one order or one active user costs to serve.
- Good news (growth) and bad news (waste) look identical on the invoice.
Nodding along to a couple of these already? Good, the rest is for you.
The diagnosis: the unit is missing
Doctors do not judge your health by weight alone; they look at readings that compare like with like. The business equivalent of that reading is the unit cost, meaning the total divided by something that the customer would recognise. For an online service it might be the cost per active user in a month, the cost per order placed, or the cost per thousand requests. Pick whichever the team already talks about.
Why does this fix the problem? Because when the number of units changes, the unit cost separates healthy growth from leakage. If the total rose but the cost per user stayed flat, you simply have more users. If the total stayed flat while users fell, the cost per user went up, and that is worth a closer look. The same bill, read per unit, suddenly has an opinion.
The treatment, in four steps
- Choose one unit. Just one, to begin with. A second or third can wait until the first is understood.
- Gather two numbers for the same month. The total spend and the count of units. Divide and write the result down where others can see it.
- Split the cost into fixed and variable. Some items stay the same however many users arrive. Others rise with every request. Knowing which is which tells you where scale helps and where it hurts.
- Repeat monthly. One reading is a snapshot; three readings are a trend. Trends are what let you say whether a change helped.
You do not need special software to start. A shared spreadsheet and fifteen honest minutes will do it. If you are still shaping your growth plans, the walkthrough on building a digital growth plan step by step shows how this kind of measurement fits into the wider picture.
Side effects you will notice
Once the unit cost is on the table, the tone of meetings softens. Engineers stop being asked “why is this so expensive?” and start being asked “what would reduce the cost of one order?” That is a better question, because it points at a design choice rather than a person. Finance, meanwhile, can see that a rising total with a falling unit cost is a sign of a business that is scaling well.
Another benefit is that pricing conversations get honest. If you know what one customer costs you to serve, you know whether your plans make sense. That clarity is also why cost discipline matters to ordinary owners, not only to technical teams; our own piece on catching spending leaks before they drain your runway comes at the same idea from the cash side.
Where to learn the discipline properly
This habit has a name in the technology world. FinOps is the practice of making cloud spending visible and shared between engineering and finance, so that neither side is guessing. FinOpsSchool is a provider of FinOps training and certification, and it is a sensible place for people from both camps to learn the same language before they sit in the same room.
Common mistakes during treatment
Choosing a unit nobody believes in. If the team does not recognise the unit, the number will be ignored. Ask the people who answer customer questions what they would count.
Treating the first number as a verdict. The first reading is a starting point. It will probably look odd, and that is fine; it is meant to make you curious, not judgmental.
Dividing by the wrong thing. If a free trial user and a paying user are counted alike, the unit cost will flatter or punish you unfairly. Decide up front which units count.
Forgetting the fixed part. A cost that does not vary with usage will make the unit cost look worse in a quiet month. That does not mean something broke; it means the same fixed cost is shared across fewer units.
A quick self-check
Before you close this tab, try to answer three questions out loud. What is the unit your customers would recognise? What does one of them cost you to serve this month? And which single line item would change that number the most if you adjusted it? If you can answer all three without opening a spreadsheet, you are ahead of most teams. If you cannot, you now know exactly what to do first.
Follow-up
Schedule a recheck for next month. Same unit, same method, same place on the shared drive. Compare the readings and write one sentence about what changed. The sentence matters more than the figure, because it is the habit that turns a surprising bill into a predictable one.
