Last month, a supply chain manager at a logistics company presented a blockchain-based product tracking proposal to the board. The presentation was technically impressive — distributed ledger, smart contracts, immutable records. The board asked one question: ‘Why can’t our current central database solve this problem?’ The manager had no answer. The project was shelved. This scenario is becoming increasingly common in Turkey’s corporate world. The blockchain conversation has shifted from a technical matter to a business justification matter.
One fundamental characteristic separates blockchain from other technologies: it enables multiple parties to agree on a shared record without needing to trust one another. This definition also reveals when blockchain is unnecessary. If a single organization produces, updates, and stores the data; if all parties already access the same central system; if record immutability is sufficiently guaranteed at the existing ERP or database layer — blockchain solves no real problem in these scenarios. It only adds cost and complexity. Clarifying this distinction before writing a business case is the most critical step in determining whether a project will succeed.
Distributed ledger creates genuine value in situations with a specific structure: multiple independent parties claim rights over the same data, trust between parties is absent or building it requires a costly intermediary, and post-hoc modification of records creates serious legal or commercial risk. In Turkey’s concrete context, these conditions surface most often in export documentation, multi-party supply chains, and financial instrument tracking. A textile exporter disputing a document with its buyer, freight forwarder, and customs broker; or a food manufacturer needing to document product origin from supplier to retailer — these are scenarios where blockchain architecture offers a real solution.
Building the financial dimension of the business case requires running total cost of ownership (TCO) and return on investment (ROI) analyses across two scenarios: improving the existing central solution versus deploying a blockchain architecture. In most cases the central solution produces lower TCO over the first three years; blockchain’s advantage only emerges as the number of network participants grows and intermediary costs fall. The business case presented to the board must define this threshold explicitly: ‘When X suppliers join the network and Y Turkish lira in annual intermediary costs are eliminated, the project becomes self-financing.’ Without this framework, a blockchain project cannot move beyond a technology experiment.
Pilot project design forms the most concrete evidence layer of the business case. The majority of enterprise blockchain projects in Turkey stall at the proof-of-concept stage, primarily because success criteria were not defined in advance. A realistic pilot is built around three to five measurable metrics: transaction verification time, dispute resolution cost, document error rate. If the pilot produces no meaningful improvement on these metrics, scaling the project to the board becomes impossible. If measurable improvement is present, the budget conversation rests on far stronger ground.
The greatest challenge in practice is organizational, not technical. Blockchain architecture requires multiple independent parties to join the system, which means each party must align its own internal approval processes, data standards, and legal frameworks. Given that Turkey’s e-Invoice and e-Ledger infrastructure operates through the Revenue Administration (GIB), any blockchain solution must address how it relates to this regulatory framework — and the business case must tackle this directly. Beyond that, most suppliers joining the network are SME-scale, meaning their technical integration capacity may be limited; this makes ease of use a critical design criterion rather than an afterthought.
As a decision-maker evaluating a blockchain investment, three questions must be answered before the decision process begins. First: why is a central database insufficient for this problem — is it distrust, multi-party complexity, or immutability requirements? Second: how many parties need to join the network, and what is their readiness level? Third: are the success metrics and pilot duration defined in advance? A business case that answers these three questions clearly transforms a blockchain project from a technology trend into a strategic investment decision. If answers are not available, the most rational choice may be to optimize the existing system and revisit the blockchain conversation when the organizational conditions are more mature.
This article was originally written in Turkish by Gökhan MERCANOĞLU on June 19, 2017 and has been automatically translated into English and other languages using machine translation.