Fichaloto

Blog Profitability

A margin built from hours alone is incomplete

7 min read

People cost is the one everybody measures. The other cost shows up after you have already closed the engagement.

The four that always slip through

When a firm builds its first profitability calculation, it almost always does it as hours times cost per hour. That is correct, and it is the big part. The problem is stopping there, because four kinds of direct cost never pass through a timesheet.

  • Subcontracting. The freelancer or studio you hand part of the work to. Pure direct cost, and usually the largest of the four.
  • Travel and subsistence. Individually small, systematically invisible. On an engagement with weekly client visits it accumulates to amounts that surprise people when they finally get added up.
  • Single-project licences and services. The subscription taken out for this specific piece of work, the third-party service used once. Often fronted by a contractor and recharged later.
  • Materials and purchases. Anything bought for the engagement that never gets used again.

Why the error always runs the same way

These costs are not forgotten at random. They are forgotten with a bias, and the bias always flatters the apparent margin.

The reason is that they arrive late. The subcontractor invoices on thirty or sixty day terms. The contractor recharges the licence when they remember. Expenses go in at month end. Meanwhile the project profitability report is showing a number containing only hours, and that is the number people look at to decide whether the engagement is going well.

The practical result: the project looks healthy until the month after it closes, when the invoices land and the margin drops. By then you have already used that engagement as the reference for pricing the next one.

How to record it so it is useful

In Fichaloto expenses are recorded on the project record itself, with a description, an amount, a date and a category, and they feed directly into the margin calculation alongside the cost of hours. There is nothing to keep on the side and nothing to reconcile afterwards.

The project's financial view separates the two lines: what people cost and what external expenses cost, broken down by category. That separation matters more than it looks, because the two are fixed in different ways — people cost through better allocation, expenses through better budgeting or by recharging them.

One deliberate detail: the description is mandatory and will not accept an empty string. Three months from now «miscellaneous» explains nothing, and an expense you cannot explain is one you can neither discuss with the client nor learn from.

Expenses land in the audit trail like everything else: who recorded them, when, and what changed if they were amended.

Recharged or absorbed: the distinction to make while recording

An expense you bill on and an expense you absorb are very different things, and conflating them makes the margin wrong in both directions.

The rule when recording is simple: ask whether that amount will appear on a client invoice. If it will, it is a recoverable cost and the thing that matters is not forgetting to bill it. If it will not, it is margin that has gone, and you want to see it now rather than at close.

The second question, for when the engagement ends: was it foreseeable? An unforeseen expense on one project is bad luck. The same unforeseen expense on the third project of that type is a pricing problem, and that is a different conversation.

Frequently asked questions

Who should be able to record an expense?

Recording, whoever knows about it — usually the project lead. Seeing it is another matter. In Fichaloto amounts and margin are visible only to people with profitability permission, and the project view hides them from everyone else, because people costs are very easy to infer from a full expense breakdown.

What about overheads like the office?

Those do not belong here. Office, general tooling and administration are indirect cost and should sit inside each person's cost per hour, not be charged to a project. Recording them as direct expense counts them twice and artificially sinks whichever engagement happens to catch them.

Do I need an approval workflow?

In a small firm, no: the project lead records and whoever watches profitability sees it. An approval circuit earns its keep when external contractors are recharging amounts and somebody internal has to validate them before they count. If that is your situation, the practice that works today is to let only people who can authorise spend record it.

All of this is built into Fichaloto. See how it works.

Keep reading