The mistake is more common than it should be
One strategic mistake keeps showing up in this space: domestic banks borrowing global-bank roadmaps.
The logic often sounds reasonable. A larger bank is moving. Major infrastructure players are investing. Market discussion is accelerating. So a domestic bank assumes the same broad capability build must now be the prudent answer.
Usually it is not.
The economics are often different. The operating case is often different. The product opportunities can be different too.
Crypto adoption is a footprint-and-franchise decision, not a generic innovation decision.
That is why this is not mainly a geography question. It is a question about where value appears first for this bank, what kind of franchise it already has, and what role it is actually trying to play.
Why global banks often have a clearer early case
Global banks can often justify earlier investment because the value can appear in places that are already material to the business.
Cross-border settlement is one. Liquidity coordination is another. So are international customer flows, custody, and the ability to support customers operating across more than one market.
In that context, digital-asset or new-rails capability is not only a product story. It can also be an infrastructure and Treasury story. If the bank already lives with multi-market movement of money, fragmented operating windows, and cross-border servicing demands, earlier investment can be easier to justify on hard operating grounds.
That is part of why a bank such as HSBC can have a clearer logic for engaging earlier. The case is not only about launching something visible. It also sits underneath, in how money, liquidity, and customer activity move across a much broader footprint.
Why domestic banks need a different answer
A domestic bank often starts somewhere else.
It may not have the same cross-border settlement problem to solve. It may not have the same international Treasury case. It may not have enough customer demand to justify building broad capability early.
That does not mean waiting passively. It means being more disciplined about scope.
If the local market is moving toward digital securities, token-based payments, or new forms of market infrastructure, readiness can still be strategic. A bank may need to participate to stay relevant in its own market even if it does not have a global-scale case.
Product mix matters here as much as footprint.
A bank with a meaningful wholesale or institutional business may still find useful early opportunities in custody, digital securities servicing, collateral, or selected settlement flows. A bank focused mainly on savings and core retail products may have fewer reasons to build broadly in the near term.
So the better question is not whether the bank is domestic or global in some abstract sense. The better question is where this bank can justify investment first.
Domestic does not mean delay
This is where the conversation often becomes too binary.
Domestic banks do not need to choose between copying a global bank and doing nothing.
There is a narrower path between those extremes.
One practical example is Krungsri's THBC pilot in Thailand. The point was not to replicate a global-bank strategy. It was to test a local-market use case in the Bank of Thailand's programmable-payment sandbox using a baht-backed digital value unit for social-commerce payments, with funds released only when the buyer confirmed receipt.
That kind of move is strategically different from building for global scale. It starts from local relevance, a specific proposition, and a contained operating question.
For many domestic banks, that is the more useful pattern. Stay close to a real use case. Learn what operating readiness is actually required. Avoid importing global-complexity layers before there is a franchise reason for them.
The role decision underneath the roadmap
There is another decision underneath all of this: what role does the bank actually want to play?
Most banks do not need to own everything. But they do need to decide where they want to lead, where they want to participate, and where they are better off orchestrating access through partners.
Lead in a narrow product or use-case area
Some banks may have a good reason to lead in one or two selected areas.
That could be because the customer need is local and defensible, because the operating model can support it, or because the bank has an existing product franchise it can extend credibly.
Help shape or connect to shared market infrastructure
Others may be better placed participating early in shared market infrastructure rather than trying to own the full stack.
UOB's early work on digital bond issuance in Singapore fits closer to that model. The logic is less about owning everything alone and more about getting involved early enough to help shape the market and connect into it well.
Orchestrate access while partnering for infrastructure
Some banks will be strongest as orchestrators.
They may not own the core platform, but they can still stay close to onboarding, customer access, compliance, servicing, and the parts of trust and distribution that still matter. The digital euro model is useful here. It shows how a bank can remain central to the customer relationship without owning every infrastructure layer itself.
Those are different strategies. Treating them as if they require the same roadmap is where copied complexity usually begins.
What to do now and what to defer
The practical task is to sequence around real franchise economics.
That usually means answering a tighter set of questions early:
- Where does the bank's real opportunity sit first: cross-border efficiency, local-market participation, or selected product expansion?
- Which role is the bank actually choosing: product leader, infrastructure participant, or orchestrator?
- Which capabilities need to be owned directly, which can be bought or partnered for, and where does control ownership still remain inside the bank?
- Which low-regret capabilities should be built now, and which global-complexity layers should be deferred until the business case is clearer?
That fourth question matters more than many banks expect.
Low-regret capability usually means the things that make later choices easier without forcing premature scope: clearer ownership, usable controls, better reconciliation design, decision rights across Business, Treasury, Risk, Operations, Legal, and Technology, and enough architectural discipline to avoid building isolated stacks.
What should usually wait is complexity that only makes sense for a much larger footprint or a much broader product ambition than the bank actually has.
The better strategy is usually narrower
I see more banks get themselves into trouble by borrowing too much of someone else's roadmap than by starting too narrowly.
Narrower does not mean timid.
It means matching scope to the business model, building only what the bank can justify, and staying clear on the role the bank wants to play as local markets evolve.
If the roadmap only really makes sense for a cross-border franchise or a very different balance sheet, it is probably the wrong roadmap.
The useful question is simpler than it first appears.
Are we designing around our real franchise, or copying someone else's?