A general manager at a mid-sized textile exporter recently put it plainly: ‘Our IT manager says we should move to the cloud, but I have no idea what to say back.’ That single sentence captures the tension playing out across Turkey’s mid-market businesses right now. Cloud computing — the delivery of software, storage and processing power as a service over the internet — is no longer a purely technical preference. It has become a strategic decision that directly shapes a company’s cost structure, competitive capacity and operational risk profile.
There is an understandable reason why boards keep their distance from this topic: the word ‘cloud’ sounds abstract, the technical details are complex and vendor promises vary wildly. But that abstraction is not a valid reason to delegate the decision entirely to IT. On the contrary, the questions a board fails to ask today tend to surface later as financial or operational surprises. The right frame is this: cloud computing is not a technology choice — it is a resource allocation model. And resource allocation has always been a board-level responsibility.
Start with cost. In the traditional IT model, a company buys servers, pays for licences and signs maintenance contracts; all of these expenditures enter the balance sheet as capital expenditure (CapEx). In the cloud model, the same capacity arrives as a monthly or annual subscription and is recorded as an operating expense (OpEx). This difference goes well beyond accounting categories. A CapEx model generates fixed costs that burden the company regardless of utilisation rates — many Turkish SMEs learned this the hard way during the 2001 financial crisis. An OpEx model ties capacity and spending in a more linear relationship. The first question a board should ask is straightforward: ‘What is the true total cost of ownership (TCO) of our current IT infrastructure, and how does that compare with a three-year cloud subscription?’
The second frame is competitive capacity. Cloud-based software — accounting, CRM, project management — can be deployed far faster than systems installed on a company’s own servers. When a competitor can get a new sales management tool running in three weeks, waiting six months to install the same tool on internal infrastructure is a measurable strategic disadvantage. This pattern is particularly visible among Turkey’s export-oriented SMEs: buyers in Western Europe are increasingly expecting faster data exchange, document handling and order tracking from their suppliers. Cloud-based tools make meeting those expectations considerably more practical.
The third frame — and the one boards most consistently overlook — is risk profile. This requires a two-sided assessment. On one side: purchasing a cloud service means moving part of your data and processes to an external infrastructure. If the reliability of the service provider, the location of their data centres, uptime guarantees and contract terms are not scrutinised carefully, operational dependency risk emerges. On the other side, and this is the part that rarely gets examined: maintaining your own IT infrastructure carries its own risk. Hardware failure, licence incompatibility, security patch management — all of it sits on the company’s shoulders. A board cannot honestly answer the question ‘which option is safer’ without putting both risk sets on the table.
In practice, the most common difficulty is making vendor offers comparable. One vendor quotes a per-user monthly fee, another prices by storage capacity, a third bundles modules into a fixed package. Mapping these different pricing models onto a single comparison requires technical knowledge — but the board does not need to do that calculation itself. What it does need is to ask the IT or finance team for a standard evaluation framework: three-year total cost, service interruption compensation terms, data portability guarantees and contract exit conditions. Without these four elements, no cloud proposal can be properly assessed.
The concrete questions a board should put on its agenda are these: Which of our business processes would benefit most quickly from a cloud-based solution? What is the real three-year cost of our current IT spending? If a service outage occurs, how long can our operations continue without disruption? The answers to these questions should not come from the IT department alone — they should come from a documented analysis that the IT department prepares and presents to the board. Leaving a cloud computing decision entirely to the technical team is the same logical error as handing a major lease agreement to the accounting manager to sign. The decision is strategic, not technical; and the accountability for it should sit at the strategic level accordingly.
This article was originally written in Turkish by Gökhan MERCANOĞLU on February 22, 2010 and has been automatically translated into English and other languages using machine translation.