Due diligence has a reputation as a legal process. Lawyers conduct it. Legal opinions are produced. Contracts are reviewed. Representations are given and warranties are negotiated. And when it goes badly — when it slows down a transaction, produces an unexpectedly large escrow requirement, or causes a potential investor to quietly withdraw — the instinct is to look for a legal explanation.
In my experience, the legal explanation is rarely the right one.
The problems that derail due diligence — the ones that produce delay, discount, and doubt — are almost always structural. They are problems of how a business has been organised over time, and how that organisation reads to someone who approaches it from the outside for the first time. Understanding the difference changes how you prepare. And preparation, in due diligence, is everything.
The formal purpose of due diligence is verification. An investor or acquirer wants to confirm that what they have been told is accurate: that the assets are real, the revenues are what they appear to be, the liabilities are disclosed, and the legal entities are properly constituted.
But the actual experience of due diligence — what it feels like from inside a transaction — tests something quite different. It tests whether the structure of a business can be explained clearly to people who know nothing about it and have no particular reason to give it the benefit of the doubt.
An investor approaching a corporate group is a stranger. They have no shared history with the owner. They do not know why decisions were made at particular moments. They cannot feel the logic that is obvious to everyone who has spent years inside the business. They can only read what is placed in front of them: the corporate documents, the financial flows, the ownership structure, the governance records.
When those materials are coherent — when the structure tells a clear story that matches the narrative the owner has presented — due diligence moves quickly. Questions are answered before they are asked. Concerns dissolve when they meet documentation that anticipated them.
When those materials are opaque, something different happens. Questions multiply. Advisers become cautious. And at some point the investor begins to wonder whether the opacity is accidental or deliberate. That thought, once it takes hold, is very difficult to dislodge. I have watched transactions that were fundamentally sound begin to unravel at precisely that moment — not because of what was found, but because of what could not be explained.
I have been involved in enough transactions — as an adviser helping sellers prepare their structures for scrutiny — to recognise the patterns that produce difficulty. They are not exotic. They are the same patterns I see in banking relationships that come under pressure. The audience changes; the underlying problem does not.
The first is a structure that grew without being governed. Most international businesses do not build their corporate architecture from a plan. They build it piece by piece: incorporate where a client is, add an entity for a specific deal, open an account for a particular purpose, register somewhere new when a new market opens. Each decision made sense at the time. The result, after several years, is a construction that nobody designed — and that nobody, including the owner, can explain in a way that sounds intentional.
I remember sitting across from a client who had built a genuinely successful business over fifteen years. When we went through the structure together, he could tell me the story behind every entity. Every jurisdiction. Every flow. The story was entirely coherent. But it existed only in his head. There was no document in the corporate file that captured any of it. And an investor looking at the same structure, without the story, would see something that looked unplanned at best and evasive at worst.
That is the gap that causes so much trouble. Not dishonesty. Not complexity. Just the absence of a documented logic that the owner has always assumed was obvious.
The second pattern is a cryptocurrency layer with no defined place in the architecture. This appears with increasing frequency as the businesses I work with have grown more sophisticated. A group has conventional operations and, alongside them, some degree of cryptocurrency activity — assets held in wallets, funds received from digital counterparties, a portion of working capital in digital form. Each element, taken individually, is defensible. Collectively, if the crypto layer has never been formally embedded into the corporate architecture, it creates a distinct problem.
Investors today are not categorically hostile to cryptocurrency. Many have substantial digital asset exposure of their own. But they need to understand exactly what the crypto layer is: which legal entities hold it, how it connects to the main business, what the custody arrangements are, and what regulatory framework applies. If those answers require extensive explanation during due diligence — rather than being immediately apparent from the documentation — the crypto element attracts scrutiny far out of proportion to its actual size. And often a discount that bears no relationship to its real materiality.
The third pattern is documentation that describes what the structure used to be rather than what it actually is today. Businesses change constantly. Ownership is reorganised. Entities change roles. Intercompany arrangements that once served a clear purpose become vestigial. Banking relationships are replaced. New jurisdictions are added.
The documentation rarely keeps pace. Shareholders' agreements describe arrangements that have been quietly superseded. Intercompany contracts reflect flows that no longer happen. Board minutes, where they exist at all, record decisions without recording the reasoning behind them. Governance records are thin for the periods when the business was moving fast and nobody was thinking about formal process.
To a due diligence team, documentation that does not match reality is not merely an inconvenience. It is a signal. If the documents say one thing and the business operates another way, the question that follows is entirely predictable: what else is wrong? That question, once asked quietly in an adviser's report, erodes confidence faster than almost any substantive finding.
The response most sellers reach for, when due diligence begins to produce difficulty, is to add legal resource. More review. More representations. More warranties. A larger escrow to cover identified risks. I understand the instinct. The process looks legal. The solution feels like it should be legal too.
But legal instruments treat symptoms. They can protect a buyer against specific known risks. They cannot make an opaque structure legible. They cannot explain why entities exist. They cannot produce governance records that were never created. They cannot give a cryptocurrency layer the architectural coherence it was never given.
There is a layer that sits above the legal layer — an architectural layer — and it is almost always addressed far too late. By the time due diligence has started, the structure is what it is. Substantive changes made during a live transaction are viewed with suspicion. Documentation produced in response to specific due diligence questions looks reactive, because it is.
The only thing that actually works is to address structural legibility before any transaction is in sight. Not in anticipation of a particular deal, but as a discipline of ongoing governance — keeping the structure aligned with the business as it actually operates, ensuring the documentation matches the current reality, and making sure the cryptocurrency layer, if there is one, has a defined and describable place in the architecture.
I am sometimes asked what an investor-ready structure looks like. The answer is not a particular configuration of entities or a favoured set of jurisdictions. It is something more fundamental: a structure that can answer four questions clearly, from its documentation alone, without requiring the owner to stand in the room and explain it.
Why does each entity exist? Every legal entity in a corporate group should have a role that can be stated simply and plainly. If the only honest answer is "it was set up for a deal that never happened" or "we are not entirely sure," that is a due diligence finding waiting to appear.
How does money move between entities, and why? Intercompany flows should follow a logic that is both documented and traceable. The logic does not need to be simple — genuinely complex businesses have genuinely complex flows. But each flow should be grounded in an agreement that explains it, and that agreement should match what actually happens.
Who decides what, and where is that recorded? Governance records are the most consistently underdeveloped element of the structures I work with. Even a modest discipline of recording significant decisions — and, critically, the reasoning behind them — transforms what an investor sees. It signals a business that is managed, not just operated.
Where does the cryptocurrency sit, and under what framework? If there is a crypto layer, it needs its own clear description: which entities hold it, under what custody arrangements, within what operational framework, and how it connects to the main business. A short document that answers these questions removes cryptocurrency from the category of unknowns and places it in the category of knowns — explained, accounted for, and manageable.
There is a version of this conversation I have had many times. A client is approaching a capital raise, a sale, or a significant partnership. They have become aware — usually through an early exchange with a potential investor — that the structure is going to be questioned. At that point, the options narrow significantly.
Restructuring during a live transaction is slow and expensive and immediately noticed. Documentation created under time pressure looks exactly like what it is. And the investor, who has already started forming a view of how the business has been run, is watching how the seller responds to scrutiny. That response tells them something.
The conversation I prefer to have is the earlier one. Before any transaction is in view: if someone conducted due diligence on this group today, with no prior knowledge and no goodwill toward it, what would they find? What would they be unable to explain? Where would the documentation fail them? Where would the cryptocurrency layer become a source of concern out of proportion to its actual weight?
Those questions, asked honestly and in advance, are almost always answerable. The structural problems they reveal are almost always fixable — not quickly, and not without effort, but fixable. The same problems, surfaced by an investor's advisers during an active transaction, are considerably harder to manage and considerably more expensive to resolve.
Due diligence tests a structure. The structure, in the end, is something you build. The only real question is whether you build it for scrutiny — or wait for scrutiny to reveal what you did not build.
Vladimir Shuvalov works with international businesses and private clients on corporate structure, banking acceptability, and cryptocurrency architecture from Nicosia, Cyprus.
Thinking Globally — thinking-globally.com
Thinking Globally Consulting Limited
Registered in England & Wales · Company No. 17138834
128 City Road, London EC1V 2NX, United Kingdom
© 2026 Thinking Globally Consulting Limited · All rights reserved