The Question Nobody Was Asking

I spent years building complex systems for large organisations. Then I noticed something that changed everything – nobody was managing their most expensive asset with any real intelligence.

I want to tell you about a conversation I kept having.

Not one specific conversation – but the same conversation, repeated across different organisations, different industries, different leadership teams, over the course of several years. The setting changed. The people changed. The scale of the organisation changed. But the substance was always, almost word for word, identical.

It would usually start with a version of this question: “We know we have the talent in this organisation to execute this. So why can’t we seem to make it happen?”

And then would follow a long, slightly uncomfortable silence whilst the room tried to answer it.

The Problem That Kept Finding Me

I come from a background in engineering and complex systems design. I spent years working on large, intricate infrastructure — the kind where failure has consequences, where every component must be understood in relation to every other component, and where “we think it should work” is never an acceptable standard.

That discipline teaches you something: in complex systems, the most dangerous failure points are not the ones you can see. They are the structural gaps – the places where two parts of a system should be connected but are not, where information that should flow freely gets siloed, where strategic intent and operational reality quietly diverge.

When I began working closely with large enterprises, I saw that same pattern everywhere. Not in the technology infrastructure. In the people.

Organisations were carrying enormous capability – talented, experienced, often exceptional individuals – and systematically failing to deploy that capability where it was most needed. Strategic priorities would be defined at the top of the organisation. Resources would be allocated. Plans would be made. And then, somewhere in the vast complexity between strategic intent and daily execution, the alignment would break down.

Roles were filled by people whose skills were adjacent to what was needed, not precisely matched. Critical projects were under-resourced in exactly the competencies they required. Leadership teams had no reliable way to know – with any financial precision – what the gap between where their talent was and where it needed to be was actually costing them.

Nobody had a number. Nobody had a model. Nobody had a way to make the decision with the same rigour they would apply to any other capital allocation question.

And here is what struck me as genuinely extraordinary: this was not a small problem in a corner of the business. Human capital represents up to seventy percent of operating expenses for most global enterprises. It is the single largest line item. It is, by almost any measure, the primary driver of strategic execution.

And it was being managed – if managed is even the right word – almost entirely on instinct.

The Standard Nobody Would Accept Anywhere Else

I started asking a question that, the more I asked it, the more surprised I became that nobody else was asking it.

If you managed your financial capital the way you manage your human capital, what would your investors say?

No systematic allocation framework. No quantified risk model. No scenario analysis before major deployment decisions. No ROI measurement after. No audit trail. No board-level accountability.

The answer, of course, is that your investors would be alarmed. They would demand better. They would consider it a governance failure.

Yet for human capital – the asset that actually executes every strategy, delivers every product, builds every client relationship – this is the accepted standard. It is the norm. It is, in most organisations, simply how things are done.

The more I sat with that question, the less I could accept the answer.

What Already Existed – and Why It Was Not Enough

I want to be precise here, because I think intellectual honesty about the competitive landscape is important – both for the people considering building with us and the people considering investing in us.

The enterprise software market is not short of solutions that touch workforce management. There are large, well-resourced, deeply embedded platforms that handle payroll, compliance, recruitment, performance management, and learning and development. There are people analytics tools that produce sophisticated visualisations of workforce data. There are consultancies that will spend six months producing a workforce strategy report.

I have nothing against any of them. Most do what they were designed to do reasonably well.

But none of them were designed to do what I kept seeing the need for.

They were built around a fundamentally administrative conception of the workforce – people as headcount to be tracked, processed, and reported on. The question they answer is: what is the state of our workforce? It is an important question. It is not the question that determines whether a strategy succeeds or fails.

The question that determines that is: where should our workforce be, what is the gap costing us, and what is the most financially defensible path to close it?

That is not a reporting question. It is a capital allocation question. And to my knowledge, when I started building navio.work, nobody had built a system designed to answer it.

Why Explainability Was Non-Negotiable

One decision I made very early – before a single line of the navio.work Decision Engine was written – was that the AI had to be fully explainable.

I want to explain why, because I think it is one of the most important architectural choices we have made, and it is not immediately obvious.

The decisions the navio.work Decision Engine is designed to support are not low-stakes. They are not recommendations for which playlist to listen to or which advertisement to show. They are strategic decisions about where human capital should be deployed, which roles represent financial risk, where investment should be concentrated, and which scenarios represent the most defensible path forward.

These are decisions that will be made by C-suite leaders and presented to boards. They need to be defensible. They need to be auditable. They need to be understood – not just trusted.

A system that produces a recommendation without being able to explain, step by step, the logic and evidence that led to it is not a decision system. It is a suggestion engine. And no serious enterprise leader is going to restructure their workforce strategy based on a suggestion they cannot interrogate.

Explainability is not a feature. It is the foundation on which the entire platform’s credibility rests.

What I Am Building – and What I Am Not

navio.work is not an HR platform. I want to be clear about that, because how you categorise something determines how you evaluate it, and I would rather be judged against the right standard.

navio.work is a strategic decision intelligence system for enterprise leadership. Its primary users are not HR directors managing processes. They are CFOs who need to integrate workforce performance into financial planning cycles. They are CHROs who want to bring financial evidence, not narrative, to the boardroom. They are CEOs who need to know, with genuine precision, whether their organisation’s capability is aligned with their strategy – and if not, what it is costing them and what it would take to change it.

The navio Decision Engine sits at the intersection of three disciplines that have never been properly integrated in enterprise software: workforce analytics, financial capital modelling, and explainable AI. That intersection is where I believe the most significant value in this category lives. And it is the space we are building in.

A Note to the People Reading This

If you are an investor reading this, I suspect you are evaluating not just the market opportunity – which I believe is substantial – but whether the founding conviction is strong enough and clear-eyed enough to build through the difficulty of creating a new category.

My honest answer: I have been thinking about this problem for long enough that I cannot not build this. The gap is real, the cost is significant, and the tools to address it do not yet exist in the form they need to. That is not a pitch. It is simply where I am.

If you are a senior leader reading this – a CFO, a CEO, a CHRO – and the question I kept asking resonates with something you have felt in your own organisation, I would welcome a conversation. Not to sell you something. To understand whether what we are building would actually solve your problem. Those conversations are how we build something worth building.

And if you are simply someone who found this article and is curious about the intersection of AI, financial strategy, and how enterprises manage their most valuable asset – welcome. There is a lot more thinking to come.

The question nobody was asking turned out to be the question I could not stop asking.

That, in the end, is why navio.work exists.

Simon Mayrhofer is the Founder of navio.work, an enterprise workforce capital allocation platform currently in product development. He writes about enterprise intelligence, AI decision systems, and the future of human capital strategy.