Picture the accounting manager of a mid-sized manufacturing firm sitting down in January with two software proposals on the desk. The first is a perpetual license for an integrated ERP package: a single large payment, ownership of the software, and an annual maintenance contract on top. The second offers the same core functionality for a fixed monthly fee with no ownership transfer. The total numbers look comparable at first glance, but their impact on cash flow is fundamentally different — and that difference can determine whether a software project gets approved or shelved entirely.
The dominant model in Turkey’s business software market has long been the perpetual license. A vendor sells the right to use its product indefinitely; the buyer pays once and retains that right regardless of what comes next. Annual maintenance and update fees typically run between fifteen and twenty percent of the original license price. For the business, this means a significant cash outflow concentrated at the start of the project, followed by relatively modest recurring costs. The structure is predictable and transparent, but the initial burden is heavy.
The subscription model distributes that burden across time. For a fixed monthly or annual fee, the business uses the software without ever owning it; the right to use it lasts only as long as the subscription continues. In Turkey, this approach is still finding its footing. A handful of smaller accounting and inventory programs have begun experimenting with it, and the concept is gaining attention in international technology discussions under the label ‘SaaS’ — software as a service. Most Turkish SME managers, however, simply call it ‘monthly rental’ or ‘subscription,’ which is accurate enough for practical purposes.
To make the comparison concrete, consider a straightforward example. Suppose a software package carries a perpetual license price of 20,000 YTL, with an annual maintenance fee of 3,000 YTL. The subscription alternative is priced at 600 YTL per month. In year one, the perpetual model costs 23,000 YTL all in, while the subscription totals 7,200 YTL — a difference of nearly 16,000 YTL in favor of the subscription. By year two, the perpetual model requires only the 3,000 YTL maintenance fee, whereas the subscription again costs 7,200 YTL. Running the numbers forward, the two models reach roughly the same cumulative cost somewhere around the end of year four. Beyond that point, the perpetual license becomes the more economical choice.
The significance of this gap lies not just in the numbers themselves but in what the business can do with the cash it retains in the early years. The roughly 13,000 YTL difference in year one stays inside the company if the subscription route is chosen. That money can cover raw material purchases, reduce a short-term bank liability, or fund another operational need. This is the practical meaning of the time value of money: cash available today is worth more than cash paid out today, because it can be put to work. When bank lending rates are elevated, the argument for preserving cash becomes even stronger — a license financed with a business loan carries an interest cost that pushes the true cost of the perpetual model higher still.
Beyond cash flow, the subscription model offers other advantages worth weighing. If the software no longer fits the business, the subscription can simply be cancelled without writing off a sunk investment. Updates and new versions are typically included in the monthly fee rather than billed separately. On the other side of the ledger, the risks are real: total payments over a long usage period can exceed the perpetual license cost, subscription pricing is subject to change, and the business becomes dependent on the vendor’s continued operation and service quality. For a company that plans to use the software for many years and can secure financing at reasonable terms, the perpetual model may still make more sense.
The right question for an SME manager is not which model looks cheaper in isolation, but which one fits the company’s actual financial position. A two-year cash flow projection is a reasonable starting point: does the business have the liquidity to absorb a large upfront payment without straining operations? If bank credit is involved, what does the interest cost do to the total comparison? How long is the software realistically expected to remain in use? Is the vendor based in Turkey, and are support and update commitments clearly spelled out in the contract? Answering these questions honestly turns an abstract pricing comparison into a grounded investment decision — and that is the kind of analysis that separates a well-managed software project from one that creates financial pressure from day one.
This article was originally written in Turkish by Gökhan MERCANOĞLU on January 28, 2008 and has been automatically translated into English and other languages using machine translation.