The first conversation I have with a potential client is not a sales conversation. I am not trying to convince anyone of anything. I am trying to understand something specific: whether the situation in front of me is one I can actually help with — and whether the person in front of me is one I can work with honestly.
These are different questions. The first is professional. The second is, in a sense, ethical. Both matter.
What I have learned, over time, is that the first conversation is the most important one. Not because it is where the engagement is won — it often is not, and the best outcomes rarely come from the fastest starts. Because it is where the nature of the relationship is established. A first conversation conducted honestly, even when it surfaces disagreement or uncertainty, sets a foundation that the subsequent work can stand on. A first conversation conducted as a pitch — where both parties are performing rather than talking — sets a different kind of foundation entirely.
And I should say this clearly: the first conversation is a mutual assessment. I am evaluating whether I can help and whether I can work honestly with this person. The client — if they are approaching this seriously — is evaluating whether I understand their situation, whether my thinking is useful to them, and whether they trust the way I work. A good first conversation produces clarity for both parties. A bad one leaves both performing. I would rather have the former, even when it produces a conclusion that the engagement should not proceed.
What follows is an account of what I am actually trying to understand in that conversation, and why.
The first thing I am trying to establish is not what the client wants. It is what the client has.
Most people arrive with a request already formed. They want a holding company restructured, or a banking problem resolved, or a cryptocurrency layer made compliant. The request is usually real. It is also usually incomplete — a description of a symptom rather than a diagnosis, a solution proposed before the problem has been fully examined.
My first set of questions is designed to establish the actual situation, not the presented one. What does the structure currently look like? What jurisdictions are involved, and why? Who owns what, through which entities, and how long has that arrangement been in place? What are the banking relationships, and have any of them generated friction in the past two years? Is there a cryptocurrency element, and if so, how is it currently held and documented?
I am not asking these questions to audit the client. I am asking them because the work I do depends entirely on understanding the construction as it is, not as it was designed to be. A structure that functions correctly on paper and generates constant banking friction is a different problem from a structure that is genuinely misaligned with the business it contains. I cannot tell which it is without asking.
The answer to these questions also tells me something beyond the structural facts. How a client describes their own situation — with what level of precision, with what comfort in uncertainty, with what willingness to say "I am not sure" rather than filling the gap with confidence — tells me a great deal about what the engagement will require.
The second thing I want to understand is the history.
Most clients who arrive at a first conversation have already done something. They have spoken to a lawyer. They have opened and closed bank accounts. They have restructured, or attempted to restructure. They have received advice that was followed and did not resolve the problem, or advice that was not followed and left the situation unchanged.
I am not asking about this history to judge the previous advisers or the decisions that were made. I am asking because the history tells me what the situation actually is, as distinct from what it appears to be at first glance.
A client who has had the same banking problem with three different banks has a structural problem, not a banking one. The bank is not the variable. The structure is. A client who has restructured twice in four years and arrived back at approximately the same situation has an analytical problem — the diagnosis has been wrong, or the restructuring has been addressing the visible symptom rather than the underlying condition.
The history also tells me something about what I will be working with. A client who can describe clearly what was tried, what worked, and what did not has a relationship with their own situation that makes the work considerably easier. A client who cannot describe the history — who has delegated the understanding of their own structure entirely to advisers and retained none of it themselves — is in a more vulnerable position, because good structural work requires a client who can engage with it, not only receive it.
This is not a criticism. It is a diagnostic observation. And it shapes how the engagement needs to be structured, if it proceeds.
The third thing I try to understand — and this is sometimes the most delicate — is whether what the client is asking for is what they actually need.
These are often different things.
A client who arrives asking for help opening a new bank account may need, instead, a structural review that changes what banks see when they look at the group. Opening another account in the same structure, with the same documentation, producing the same signals, will not produce a different outcome. The account may open. It will likely generate the same friction within twelve months.
A client who arrives asking to add a cryptocurrency layer to an existing structure may need, instead, to understand what the existing structure will look like to banks once the cryptocurrency element is added, and whether that outcome is manageable. Adding crypto to a structure that already generates compliance questions is not an architectural decision. It is a compounding of an existing problem. That distinction matters, and it needs to be named before the work begins — not discovered halfway through.
I raise these observations in the first conversation, not after. Not because I want to contradict the client's request, but because agreeing to deliver something that will not resolve the underlying situation is not useful to either party. The client spends money and time. The problem persists. The relationship ends in dissatisfaction.
The willingness to hear this kind of observation — to consider that the question being asked might not be the most useful one — is itself something I am paying attention to. Not as a test. As a signal about the nature of the conversation that the engagement will require.
There is a particular kind of engagement I have learned to recognise early and to discuss directly: the engagement where the client has already decided what they want and is looking for someone to implement it, not to examine it.
This is a legitimate need. Implementation work is real work. If a client has done a thorough analysis, reached a well-considered conclusion, and needs a competent professional to execute on it, that is a coherent brief. I can work with it.
What I cannot work with is the version where the conclusion has been reached without the analysis — where the client has a preferred outcome and is looking for a professional who will confirm it, structure it, and sign off on it, without examining whether it is correct. This is the engagement that ends badly. Not because the client's instinct is necessarily wrong. Because conclusions reached without examination are fragile in ways that only become visible under pressure, and pressure is precisely when the structure needs to hold.
So I ask, directly or indirectly: has this been analysed, or decided? Is the client coming with a question, or with an answer that needs execution? The response to this question — both the content of the answer and the manner in which it is given — tells me whether there is room to do the work properly.
There are situations I decline. Not many, but some. And the first conversation is where I establish whether this is one of them.
The situations I decline are not primarily defined by the complexity of the structure or the sensitivity of the jurisdictions involved. Complex structures in sensitive jurisdictions are, in many cases, exactly what this work is designed for. What I am looking for is something different: whether the situation is one where the work I do can produce a genuine improvement, and whether the client's objectives are ones I can pursue honestly.
A structure designed around concealment — not around privacy, which is legitimate and architecturally achievable, but around the active obscuring of ownership or activity from parties who have a legitimate right to know — is not a structure I will help build or maintain. Concealment-based structures are architecturally fragile. They do not hold under the examinations that matter.
A client who is not willing to be honest about the actual situation — who presents a version of events in the first conversation that I can see is incomplete, not from legitimate privacy concerns but from a concern that the full picture would change my assessment — is a client I cannot work with effectively. The work depends on knowing what is actually there. If that information is withheld, the analysis is built on a partial picture, and partial pictures produce recommendations that fail when the full picture emerges.
I say this directly when it is relevant. Not accusatorially. Simply as a statement of what the work requires.
When the first conversation goes well — when the client describes their situation clearly, engages honestly with questions about the history, and is willing to consider that the question they arrived with might not be the most useful one — something specific happens. The nature of the work becomes visible.
Not the scope. The nature. Whether this is primarily an architectural problem, a documentation problem, a banking narrative problem, or some combination. Whether the structure needs to be rebuilt from the ground up or examined and clarified. Whether the urgent issue is a banking relationship that is degrading, a transaction that is approaching and for which the structure is not ready, or a cryptocurrency layer that has been added without the architecture to support it.
That clarity is the output of the first conversation that matters most. Not a proposal. Not a fee estimate. A shared understanding of what is actually in front of us — and whether there is a path from where the client currently is to where the structure needs to be.
When that clarity exists, the engagement that follows has a foundation. When it does not — when the first conversation ends with the client's presented version of the situation unchanged, the real situation unexamined, and the questions unanswered — the work that follows is built on sand.
I would rather have the difficult conversation in the first meeting than discover, three months in, that the foundation was not there.
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