Vladimir Shuvalov

Opening

There is a particular kind of professional formed by the early 1990s — someone who learned international structuring not from textbooks but from necessity. The maps did not yet exist. The frameworks were being invented in real time. The clients needed solutions that worked, not solutions that looked good on paper.

I have started my practice in that environment. It shaped everything that followed: a habit of starting with the actual problem rather than the available answer, and a deep scepticism towards ready-made solutions applied to situations they were not designed for.

Thirty Years. Several Disciplines. One Question

The practice that developed over three decades sits across corporate law, international structuring, tax planning, and banking relationships — not as separate specialisations, but as a single discipline. The central question has always been the same: how does a structure look from the outside, and does it hold up when the examination is serious?

That question led naturally across jurisdictions. The work spans the European Union, the United Kingdom, offshore structures in the Caribbean basin, and Asia — principally Hong Kong. Each environment has its own logic, its own regulatory sensibility, its own version of what a bank or counterparty finds legible. Understanding those differences — and designing structures that work across them simultaneously — is where most of the practice has lived.

Cryptocurrency entered that practice not as a trend but as a genuine architectural challenge: how do you integrate a digital asset layer into a corporate or personal structure in a way that banks can read, investors can follow, and compliance teams can approve? The answer, consistently, has been the same as for any other structuring problem: design the architecture first, then build the documentation around it.

The Approach

I do not work from templates. Not as a point of principle — but because templates do not fit. Every client's situation carries its
own specific combination of jurisdictions, counterparties, banking relationships, risk exposures, and objectives. I begin by mapping that combination honestly — before any solution is proposed.

That requires looking at a client's construction the way a bank’s compliance committee would: identifying what generates concern before it surfaces, understanding where the real pressure points are, and being willing to say clearly what needs to change — even when it is not what the client hoped to hear.

That last part matters most. The most valuable thing I can do is tell the truth about what I see. Not what the client wants to hear. Not what makes the next phase of the engagement easier to sell. What is actually there — and what it actually means. Clients who have worked with me consistently describe this as the quality that distinguishes the relationship: an absence of the usual softening, and an insistence on engaging with the real problem rather than a version of it that is more convenient to discuss.

The analytical work behind that honesty is not linear. I approach each problem as a distinct construction — examining it from multiple angles simultaneously, identifying the dependencies and pressure points that are not immediately visible, and designing solutions that hold not only under normal conditions but under the questions that banks, investors and auditors actually ask. This is what creative thinking means in this context: not novelty for its own sake, but the ability to see the problem differently from how it was presented, and to find a path that others have not mapped.

The Network

I work as one principal. Around that, I have built a deliberately curated network of practising lawyers, tax advisers, consultants and auditors across the EU, the United Kingdom, the Caribbean offshore jurisdictions, and Hong Kong — assembled for the specific situation rather than applied uniformly to every engagement.

This is not a compromise. It is a model. The alternative — a large firm with broad coverage and standardised processes — produces standardised outcomes. The situations that require the kind of thinking described above are precisely the situations where standardised outcomes are not enough.

The work is suited to situations where the standard answers have already been tried, or where the construction is complex enough that standard answers were never going to be adequate. Simple problems have simple solutions — and those solutions are widely available. I work with the other kind: structures that do not read cleanly to banks, situations where the usual professional framework does not fit, and problems that have resisted the approaches tried before.
If you are not sure whether your situation falls into that category, the answer is usually visible within the first conversation.

How the Work Begins

I do not send proposals before having a conversation. The conversation comes first — an honest look at the situation, a clear
assessment of what is actually there, and a shared understanding of whether there is a basis for working together.

Every engagement has a clear scope and specific deliverables. I do not bill by the hour. The outcome is what matters — not the time spent reaching it.

If what is described on this page is relevant to a situation you are currently dealing with — a structure that is generating questions from banks, a transaction that requires due diligence preparation, a cryptocurrency layer that needs to be brought into architectural order, or simply a sense that something is not working in the way it should — the first step is a conversation.

Not a proposal. Not a commitment.
A conversation in which we look at the situation honestly, and establish whether there is a basis for working together.

Start the conversation →