A finance manager at a mid-sized textile exporter in Izmir recently posed a question that gets to the heart of what many Turkish SME owners are wrestling with right now: ‘I have two software-as-a-service proposals on my desk, both on monthly subscriptions, both accessible through a web browser — how do I know which one to choose?’ It is a fair question, and the honest answer is that price alone will not tell you. As broadband internet connections become more common across Turkey, web-based software services are making it possible for smaller companies to access enterprise-grade tools without buying and maintaining their own servers. That convenience, however, comes with a set of strategic dependencies that deserve careful examination before you sign anything.
The fundamental logic of the software-as-a-service model is straightforward: instead of purchasing a software licence outright, you pay a recurring subscription — monthly or annually — and the vendor handles installation, updates, and infrastructure. For a small business that cannot afford a dedicated IT team, this is genuinely attractive. The upfront investment drops sharply, and the technical burden shifts to the provider. What is less obvious is that this arrangement also shifts certain risks onto you in ways that a traditional on-premise licence does not. Understanding those risks is the starting point for any serious evaluation.
The first and most fundamental criterion is data ownership. When you enter customer records, inventory figures, invoice histories, and financial data into the system, who legally owns that information? If you terminate the contract, in what format can you retrieve your data, and within what timeframe? Some vendors leave these questions vague in their contracts or make data export available only for an additional fee. As an SME negotiating from a position of limited leverage, you need to insist that this is addressed in writing before you commit. If the contract does not clearly state that you can export your data in a standard format — something like a spreadsheet or a delimited text file — within a defined window of three to six months, treat that as a warning sign.
The second criterion is integration capacity with your existing systems. If you already run accounting software, a stock management tool, or an order processing application, you need to understand concretely how the new service will exchange data with those systems. Is the transfer file-based, or is there a direct database connection? How frequently does synchronisation occur? Is there an additional development cost to set up the integration? These answers matter both for technical compatibility and for understanding your true total cost. In companies that rely on multiple software tools, poor integration typically creates duplicate data entry and manual correction work — which translates directly into wasted staff time and increased error rates.
The third criterion is the quality of local support. Does the vendor have a physical presence in Turkey? Is technical support available in Turkish, or are you expected to navigate English-language documentation on your own? When tax regulations change — as they do with some regularity in Turkey, including updates to electronic declaration formats — how quickly does the software reflect those changes? A vendor headquartered abroad may deprioritise local compliance updates or handle them with a significant delay. Given how often Turkish accounting and tax rules are revised, choosing a provider that actively tracks local regulatory requirements is not a luxury; it is an operational necessity.
The fourth criterion is growth flexibility. If your team of ten is expected to grow to thirty within two years, you need to model what the pricing looks like at that scale before you commit to anything. Some vendors offer attractive entry-level rates but apply disproportionate per-user charges beyond a certain threshold. Others introduce additional storage fees as your data volume grows. Share your growth scenario with the vendor explicitly and ask for a written cost projection covering a two-to-five-year horizon. A service that looks affordable today can become a significant fixed cost burden if the pricing structure is not well understood from the outset.
The fifth criterion — exit ease — is the one most often overlooked, yet it is as important as any of the others. What happens if the vendor goes out of business or discontinues the service? When you cancel a subscription, how long do you retain access to your data? How long would a migration to a competing service realistically take? Asking these questions is not pessimism; it is responsible management. To bring structure to the whole evaluation process, I recommend building a simple scoring table: rate each vendor from one to five on data ownership, integration, local support, growth flexibility, and exit ease, apply weights that reflect your business priorities, and compare the totals. Price should appear as one line in that table — not as the table itself.
This article was originally written in Turkish by Gökhan MERCANOĞLU on February 19, 2007 and has been automatically translated into English and other languages using machine translation.