Picture a mid-sized trading company looking to purchase accounting software. The vendor quotes a license fee first — thousands of dollars for a handful of users. On top of that come the server hardware, installation charges, an annual maintenance contract, and a separate upgrade fee every time a new version ships. Before the software runs a single transaction, the bill has already consumed months of the company’s IT budget. This is exactly the situation where the ‘software as a service’ model — SaaS — presents a genuinely different option.
SaaS means using software through a monthly or annual subscription rather than purchasing it as a product. Instead of being installed on the user’s own machine, the application runs on the service provider’s servers, and users connect through a standard web browser. In Turkey, as ADSL broadband spreads rapidly across offices and business districts, the technical foundation for this kind of model is becoming viable for the first time. A few years ago, reliable bandwidth was hard to find outside major city centres; today, a growing number of offices have a stable, always-on connection that makes browser-based work practical.
Compared to the traditional licensing model, the most visible difference with SaaS is the dramatically lower upfront cost. Instead of a license fee, server investment, and installation expenses, the company pays a fixed monthly charge. For SMEs that need to manage cash flow carefully, this is a meaningful advantage. Calculating return on investment also becomes more straightforward: the monthly subscription cost is known, and it scales predictably with the number of users. With traditional licensing, unexpected maintenance and upgrade costs can strain a budget that was balanced on paper.
Deployment speed is another area where the difference is tangible. Rolling out a conventional ERP or accounting package typically takes weeks, sometimes months — server setup, network configuration, database installation, user training, and customisation all take time before anyone can do real work. With SaaS, once a user account is created, access is available through the browser and work can begin almost immediately. Software updates are also the service provider’s responsibility, so the company does not need to allocate internal resources to patch management or version upgrades. When a new feature or a regulatory compliance update is released, users find it waiting for them the next morning without any intervention on their part.
Data security is the aspect of this model that raises the most questions. The idea of company records sitting on someone else’s server rather than in the office makes many managers uncomfortable, and that concern is understandable. However, professional data centre infrastructure and backup systems operated by a dedicated service provider are often more reliable than what a typical SME can build and maintain in-house. The more useful question to ask is: how secure is the company’s own server today, and how often is it backed up properly? In many small businesses, server maintenance is irregular and backups are either skipped or done incorrectly — a risk that is easy to overlook until something goes wrong.
A practical limitation worth acknowledging is the dependency on internet connectivity. When the connection goes down, access to a SaaS application goes down with it. While ADSL is spreading, connection quality in Turkey is still inconsistent across regions and providers. Companies in industrial zones or smaller towns may find this a genuine operational risk. The long-term continuity of the service provider is also worth considering: if the vendor shuts down or discontinues the service, what happens to the company’s data? Before signing up, it is worth reading the contract carefully for data portability terms and exit conditions — not just the monthly price.
For an SME manager evaluating SaaS, a few concrete criteria can guide the decision. First, the company’s internet infrastructure should be tested to confirm it can support browser-based work reliably; if connection speed or stability is questionable, problems will surface early. Second, any SaaS solution under consideration should be checked for compliance with Turkish legal requirements — tax calculations, e-beyanname compatibility, and local accounting standards. A product built for a foreign market may not map cleanly onto Turkish regulations. Finally, the subscription contract’s data ownership and access terms deserve close attention. A low monthly fee is not enough on its own; the vendor’s references, the quality of technical support, and whether Turkish-language assistance is available should all factor into the evaluation.
This article was originally written in Turkish by Gökhan MERCANOĞLU on January 2, 2006 and has been automatically translated into English and other languages using machine translation.