In a conversation last month with the general manager of a mid-sized textile manufacturer, I heard something that stuck with me: ‘When I’m at the factory, I don’t find out what the Istanbul sales team has closed until I get back to the office in the evening.’ That single sentence captures the daily reality of many SME executives in Turkey right now. Decisions require information; information requires being at a desk. Yet business happens in the field, not behind a desk.
At the intersection of cloud computing and mobile communications, a concrete opportunity is opening up for executives. Cloud computing means hosting software and data infrastructure not on in-house servers but in remote data centers accessed over the internet. The practical implication for an executive is straightforward: lower upfront setup costs, reduced maintenance burden, and comparatively easier scaling. The mobile side gains real meaning as 3G networks spread; a manager carrying a laptop can now reach company data from any point with an internet connection.
But hearing these two concepts together and actually implementing them are separated by a significant gap. In Turkey’s SME environment, cloud-based services are still maturing. Local providers offer limited options, and international platforms have notable gaps in Turkish-language support and local regulatory compliance. An executive needs to accept this reality first, then build a priority sequence around it. Trying to roll out every technology simultaneously exhausts both the budget and the organization.
When setting priorities, a useful framework is to answer ‘what information do I need, and where do I need it’ before selecting any technology. If the sales team in the field needs to see offer status and stock availability on the go, the priority should be a mobile-accessible CRM or sales tracking tool. If the goal is to centralize accounting and finance, or to view data from multiple locations in one place, evaluating cloud-based accounting or ERP solutions makes sense. These two needs can be addressed independently; trying to solve both at once typically stalls the project.
From a budget perspective, the cloud model carries a meaningful advantage. In traditional software projects, upfront licensing and hardware costs made up the bulk of total cost of ownership (TCO). The cloud model’s monthly or annual subscription structure makes cash flow more predictable. In a smaller firm, this difference makes it easier to get board approval. That said, when calculating return on investment (ROI), it is important to factor in not just software costs but also staff training, process change, and productivity loss during the transition period. When these line items are ignored, budget estimates fall short and projects stall halfway through.
In practice, the most common obstacles are organizational rather than technical. Teams resist new tools; the ‘we already do it in Excel’ mindset runs deep. The executive needs to take on both the sponsor and the implementer role. Starting a pilot with a small team, demonstrating a concrete benefit within the first three months, and making that benefit visible to the wider organization is the most effective way to overcome resistance. Data security is another concern executives raise frequently; where the cloud provider’s data center is located, what the backup policy covers, and how access controls are defined should all be resolved during the contract phase, not after go-live.
Setting a concrete year-end target makes the project manageable. A reasonable target might look like this: move at least one business process, such as sales tracking or expense reporting, onto a centralized and remotely accessible platform, and ensure that at least seventy percent of the relevant team is using the new tool regularly by year’s end. An executive who reaches that target has tested both the technology and the organization, and has built a solid foundation for the next step. Anyone aiming for a broader transformation cannot skip this first one.
This article was originally written in Turkish by Gökhan MERCANOĞLU on July 19, 2010 and has been automatically translated into English and other languages using machine translation.