FTE Debt is the organizational capacity you've already lost to data friction. The hours your team burns on manual work, duplication, reconciliation, and waiting. The formula is People × Friction% × Average Cost. On most data portfolios, it's the single largest hidden cost.

Why is it so hard to measure data ROI?

Most companies track data costs (tools, infrastructure, salaries) but not the time lost to data friction. That's where most of the value disappears. Without measuring capacity drain, ROI can't be calculated. It can only be assumed.

How can I reduce data team costs?

Find the low-impact initiatives. Cut the time wasted on manual work, duplication, and delays. The goal isn't fewer headcount. It's recovering the capacity that's currently trapped in friction.

What is a good data ROI metric?

Start by measuring recovered capacity. FTE time saved. That gives you a number you can audit, instead of guessing at revenue attribution.

Should I reduce my data team size?

Probably not. In most cases the issue isn't headcount, it's how that capacity is being spent. Recover the wasted time before you cut the investment.

Do I need to clean my data before we talk?

No. Waiting for 'perfect' data is the most expensive mistake a CEO can make. Start with what you have. The first job is to make the cost visible — what the portfolio is actually spending. Everything else follows from having that number.

What Is FTE Debt? The Hidden Cost Eating Your Data Portfolio

Every data portfolio carries a debt nobody books. It does not show up on the cloud invoice. It does not appear in the headcount plan. It is not in the SaaS line of the budget. And yet it is, almost always, the single largest cost the company pays for its data operation. I call it FTE Debt, the accumulated organizational capacity lost to data friction.

The accounting trick that hides it

Most companies measure data spend: Snowflake, dbt, Looker, Fivetran, salaries, headcount. These are easy to tally because they invoice you. What they do not measure is the time those people spend working around data instead of with it: hunting for the right table, reconciling two dashboards that disagree, rebuilding a pipeline that broke overnight, waiting four days for a question to be answered, explaining the same metric to a different team for the third time this quarter.

That time is paid for. It just is not booked anywhere. The salary line absorbs it silently. Which is why every CFO I've worked with under-counts the data team's true cost by 25–40%.

The formula

FTE Debt is intentionally simple:

FTE Debt = People × Friction% × Average Cost

People, anyone who builds, fixes, requests, or waits on data. Not just the data team. Include the analyst-shaped person on every other team.
Friction%, the share of their time burned on manual data work, duplication, reconciliation, and waiting. The number is almost never below 25%. In growth-stage companies I usually find 35–45%.
Average Cost, fully-loaded annual cost per person (salary + benefits + tools + overhead).

Plug in 30 people × 35% × €85k and you get just under €900k a year, the price tag on capacity that is currently producing nothing. Run the numbers for your own org.

Why the number always surprises CEOs

Three reasons the size of FTE Debt shocks the room:

It compounds invisibly. Each new tool adds a small reconciliation tax. Each new dashboard adds a maintenance tax. Each new team adds a translation tax. None of these show up on the invoice. They show up in the calendar.
It hides inside "we're hiring." Most CEOs respond to data slowness by hiring more analysts. But adding people to a system with high friction multiplies the friction. You buy more capacity, you waste a larger fraction of it, and the dashboard count grows faster than the decision count.
It is socially expensive to name. FTE Debt is not anyone's fault. It is a systemic property of a portfolio that grew faster than its decision architecture. Naming it feels like blaming the data team, which is why most CFOs let it sit.

What FTE Debt is not

It is not "your data team is slow." It is not "you hired the wrong people." It is not technical debt by another name, technical debt is in the code; FTE Debt is in the calendar. It is also not the same as low utilization. A team can be 95% utilized and still 40% in FTE Debt: utilization measures whether they are busy; FTE Debt measures whether the busy work moves a decision.

How to start measuring it

You do not need a year-long study. You need three weeks and a simple time-bucket survey. Ask each data-touching person to categorize their week into:

Decision work, analysis, modeling, recommendation that landed in a decision.
Plumbing, pipeline, infrastructure, tooling work that the company would do anyway.
Friction, searching, reconciling, fixing things that should not have broken, answering the same question twice.
Waiting, blocked on someone else, on permissions, on data that has not arrived.

Add Friction + Waiting. That is your Friction%. Multiply by people and average cost. That is your FTE Debt for the period. Annualize it. The number is your starting point.

What to do with the number

FTE Debt is not a metric you optimize directly. It is a diagnostic. The work is to ask, for each chunk of friction: which decision was this serving? Most of the time the answer is "no decision in particular", and that is where the recovery comes from. You stop building the dashboards nobody uses to make decisions nobody is ready to make.

For the parts that are serving real decisions, the question becomes: what would it take to halve the friction? The answers are almost never glamorous. Better naming. Fewer dashboards. Stronger metric ownership. A documented decision protocol. None of it is a tool purchase.

The CFO conversation

FTE Debt is the only data metric I have found that survives a CFO meeting intact. It is denominated in euros. It is auditable. It compares cleanly to other capacity investments. And it answers the question every CFO asks of a data budget: what would happen if we did not spend this?

The answer, when FTE Debt is named: nothing would happen, because most of the spend is currently funding friction, not decisions. That is when the conversation gets useful.