Thomas Emerald White

I still remember the Meccano set I received when I was six. The bolts, the nuts, the pieces — and the realisation that they could become something. Not something fixed, not something prescribed, but something I decided. That feeling has never left me. Every system I have ever worked on, every business I have ever built, every deal I have ever structured has been some version of the same thing: finding the pieces, understanding how they connect, and assembling something that did not exist before.

It took me a long time to find a problem big enough to deserve everything that wiring can do.

Before the trading floors

Before the software career, I ran a publishing house as Managing Director — twenty-two books for university students, assembled from manuscripts sitting in academics' drawers waiting for a budget that never came. I also ran a software house, where one project involved exporting 50,000 PCs to schools in Uzbekistan during the Soviet era. Many things went wrong. We built a local assembly factory, trained engineers, and delivered. I was a tank commander in the Army Reserve during the same period, where I learned the lesson I have applied in every room since: a plan without execution is just paper. Move fast, test early, stay close to the people the work is actually for.

I also lectured at university. Teaching complex systems to people encountering them for the first time sharpens your thinking in a specific way. You cannot hide behind jargon. You either understand something well enough to explain it clearly, or you discover that you do not understand it as well as you thought.

Twenty-five years finding broken systems

Deutsche Bank, Dow Jones, ICL, Fortent, Forcepoint. The institutions were large, and the problems were real.

At Deutsche Bank, I was working on a real-time foreign exchange trading platform. The traders had four screens each, consumed entirely by their work — it was not easy to notice that the same currency pair on two different screens was showing different prices, with the screens taking seconds to synchronise. At the time, manual trades were still common. I found the design flaw while reading the system, understood what was causing it, and fixed it. I did not fully grasp the financial scale of what had been happening until a trader explained it to me a month later. It had been costing a significant amount of money every day. What struck me was not the size of it — it was how invisible the broken component had been to everyone else who had been looking at the same system.

At Fortent, I designed an application framework for anti-money laundering software used across major US and UK banks — configurable, scalable, built so that deployment teams could modify the interface without specialist programming skills. The framework carried a patent application in the US and EU. It was built six years before the market arrived at the same idea independently and called it React. I was not ahead of my time. I was simply reading the system and building what it needed.

For twelve years at Forcepoint, I led the migration of a large enterprise cybersecurity product across distributed teams on three continents. The consequence of getting it wrong was not a missed deadline — it was the security exposure of enterprise clients who depended on the platform to be current and coherent across every deployment. What I learned at that scale is that clarity of intention matters more than any process or framework. When people understand what they are genuinely trying to achieve, they make better decisions in the gaps between instructions. Manage the individuals, then the teams, then the project — in that order. Reverse it, and everything becomes harder than it needs to be.

What it takes to build something worth acquiring

I left that world when I realised I had been climbing, carefully and competently, a ladder leaning against the wrong wall. I did not spend long looking for the right one.

I turned my attention to business owners facing a specific problem: the gap between what a business is worth to the person running it and what it is worth to the person buying it. Those are almost never the same number, and the difference is almost never about revenue.

What I consistently found was structural. The owner was the business — the relationships, the decisions, the institutional knowledge. Remove them and the value disappeared. My work was to make the business transferable: document the workflows, systematise the decisions, build the conditions under which someone else could step in and scale rather than scramble. Most of the value in a business is locked behind structural problems the owner has stopped noticing. Fix the structure and the value appears — sometimes dramatically. That work taught me more about what drives acquisition multiples than any amount of financial modelling.

The largest system I have ever had the chance to build

Rune and I found each other through that work. I watched what he was building with energy infrastructure and understood it immediately — not as a product, but as a system.

Commercial property in Europe is sitting on a structural problem that most of its owners have not yet priced. A building that draws its energy from a grid that was designed for a different world is not a neutral asset — it is a liability in slow motion. Energy costs compound. Regulatory pressure compounds. And the gap between what the building earns and what it could earn widens every year it stays the same.

What HNordic installs changes the underlying economics of the asset. Integrated wind generation, battery storage, and an AI energy management layer do not just reduce what the building costs to run — they change what the building produces. A commercial property that generates, stores, and intelligently deploys its own energy is a different kind of asset. It earns differently. It is valued differently. The uplift is not cosmetic. It is structural, and it is permanent.

The financial architecture we have built around that insight separates the value streams deliberately. Energy investors and property investors each enter at the level that matches their mandate and exit at the multiple their asset class commands. The structure was designed so that neither is carrying the other's risk. Properties in scope range from standalone commercial assets through to multi-site portfolios — the mechanism scales because the underlying logic holds at every size.

That is the system I now spend my time building. Physical assets, financial architecture, and real consequences for the people whose capital sits inside it. The bolts are real. The pieces matter.

What I am building now

Every stage of my career has been building toward the same underlying challenge: designing systems where technology, capital, and people reinforce each other rather than pull against each other.

I work at the intersection of financial architecture, industrial real estate, and energy infrastructure. The value I look for — and consistently find — is the value that others miss because they continue to analyse each component separately. The energy system, the property asset, and the capital structure are one thing. Treat them as three, and you leave most of the value on the table.

The next generation of commercial assets will be defined by how intelligently capital, infrastructure, and technology are combined. That is not a prediction. It is already happening in the assets we are working on.

The question for owners, investors, and operators is not whether this transition occurs — it is whether they are inside it or watching it from the outside.