Picture the IT manager at a mid-sized manufacturing company: he arrives in the morning to find three open support tickets, a failed backup alert, and a test plan waiting for an upcoming version upgrade. By the end of the day, he has barely worked through half the list. Meanwhile, company management expects the IT team to build a new sales reporting system, improve the inventory module, and automate the e-declaration process. None of it gets done, because most of the team’s time goes toward keeping the existing infrastructure alive. This is a familiar reality inside the IT departments of many Turkish SMBs.
The software-as-a-service model — widely known as SaaS — carries real potential to reverse this equation. In the traditional enterprise software model, a company purchases a license, installs the application on its own server, configures the database, sets up backup routines, and then repeats most of this process every time a new version is released. In the SaaS model, the software runs on the vendor’s infrastructure and users access it through a web browser. Buying servers, managing operating system licenses, and planning version upgrade projects all move off the company’s plate.
The impact on the IT department is direct and concrete. In the traditional model, moving an ERP or accounting application to a new version can become a weeks-long project even at a small company: a test environment must be built, data backed up, compatibility checks run, and users retrained. When a SaaS vendor handles these updates on its own infrastructure and delivers them ready to use, the time the IT team spends on this cycle drops close to zero. Freed from a process that repeats several times a year, the team can redirect that time toward work that actually matters.
The second practical benefit lies in server and infrastructure management. An on-premise application requires ongoing attention to hardware investment, operating system security patches, power redundancy, and physical security — none of which has any direct connection to the company’s core business. In the SaaS model, all of these responsibilities shift to the vendor. The IT team stops being accountable for ‘how many hours did the server run this week’ and starts being accountable for ‘what data does the sales team need and how do we get it to them.’
This shift produces two tangible gains for the business. First, the structure of the IT budget changes: instead of unpredictable hardware failure costs or emergency upgrade expenses, the company pays a fixed monthly service fee, which makes financial planning considerably more straightforward. Second, the content of the IT team’s daily agenda transforms. An IT professional no longer consumed by operational maintenance can develop a deeper understanding of the company’s sales, production, or logistics processes and focus on building technical solutions for those processes. In short, the team moves from being an infrastructure maintenance unit to a partner that thinks alongside the business.
That said, the SaaS model in Turkey’s 2009 conditions comes with real limitations worth acknowledging. Connectivity quality is a critical factor: ADSL is spreading but connection speeds and stability vary significantly by region, and a browser-based application’s performance depends entirely on that underlying infrastructure. The range of SaaS options available in Turkey is also still narrow; some domestic vendors in accounting, inventory, and CRM are moving toward this model, but finding SaaS solutions that cover industry-specific or complex workflows is difficult. Data security also raises legitimate questions among corporate managers: storing company data on a third party’s systems rather than an in-house server requires careful evaluation on both technical and legal grounds.
When an IT department is assessing a move to SaaS, the core question management should ask is straightforward: what share of the team’s time currently goes to infrastructure maintenance, and what share goes to improving business processes? If maintenance work dominates the agenda and the team cannot keep up with strategic projects, the SaaS model is a practical way to address that imbalance. Starting with a single module — accounting or CRM, for instance — limits the initial risk while giving the team time to adapt to a new way of working. Before signing any agreement, it is worth verifying the adequacy of the company’s internet connection, checking the vendor’s client references, and making sure data storage and ownership terms are spelled out clearly in the contract.
This article was originally written in Turkish by Gökhan MERCANOĞLU on June 1, 2009 and has been automatically translated into English and other languages using machine translation.