Buy Software, Pay a Subscription or Build Your Own App? The Comparison Few Companies Make

When a company, school or office needs a new tool (billing, enrollment management, inventory), it almost always compares three things: the license price, the monthly fee or the development quote. It rarely compares what really matters: what that decision will cost over three years. That is where support, servers, training, integrations, price increases and the maintenance nobody budgeted for show up.

In this article I compare the three routes with a numeric case, with every assumption in plain sight, so you can replace them with your own. It includes a downloadable Excel cost matrix. Regulatory data verified on October 9, 2026.

Summary. None of the three options is best in the abstract. In the example (12 users), the subscription and the license end up in a similar range and in-house development costs more than double; but at around 40 users, in-house development becomes the cheapest. What matters is that the break-even depends on your figures, and that cost is not the only criterion: vendor dependence, security and the ability to maintain what you build also count.

The three routes and their hidden costs

• Buy a license (one-off payment, perpetual use): you pay most of it up front, but then come support and updates (usually charged as an annual percentage of the license), the server or machine it runs on, backups and whoever administers it.
• Pay a subscription (SaaS): the initial payment is low and the vendor handles servers and updates; in exchange you pay forever, the price may rise and if you stop paying you lose access. When the vendor is abroad, payment is usually in dollars and you must look at VAT and data protection (below).
• Build your own application: you get exactly what you need and the data and code are yours, but you take on development, hosting, security, support and maintenance that never ends. The cost of building is only the beginning.

The case: 12 users over 3 years

Suppose an organization with 12 users. These are the assumptions, all illustrative (not the prices of any real brand) and editable in the matrix:

With those assumptions, the three-year total cost is:

Notice three things. First, the license that is "cheap in the long run" is not that cheap: 73% of its cost falls in the first year, and years 2 and 3 still cost support, server and administration. Second, the subscription looks expensive month to month (US$ 300 a month in year 1) but avoids the initial blow. Third, in-house development is the most expensive with few users, because its cost is almost fixed.

When users change, the answer changes

Sensitivity with the same assumptions and only the number of users varying (computed in the "Sensibilidad" sheet of the matrix):

The break-even points, with these assumptions: the license beats the subscription from about 19 users, and in-house development beats both from about 36 to 39 users. But beware: that is only valid if development costs what was budgeted, if it solves the need and if someone maintains it. Software projects often go over budget; that is why the matrix lets you test a development that costs 50% more and see how the break-even moves.

What the spreadsheet does not show

Cost is one criterion; these others can weigh more than a difference of a few thousand dollars:

• Lock-in. Can you export your data in an open format if you change vendor? With a subscription, ask this before signing.
• Personal data. If the tool stores data on students, customers or employees on servers outside Colombia, Law 1581 of 2012 (Article 26) in principle prohibits transferring data to countries without an adequate level of protection under the Superintendence of Industry and Commerce standards, with exceptions such as the data subject's authorization. Check where the data is hosted and what clauses the vendor offers.
• VAT and currency. Digital services provided from abroad to consumers in Colombia are subject to 19% VAT (Tax Code), usually borne by the user, and a dollar price exposes you to the exchange rate. Confirm with your accountant; it is not included in the matrix.
• Legal software. Companies must report in their management report the state of compliance with intellectual property and copyright rules (Law 603 of 2000): your licenses should be in order.
• Ability to maintain. An in-house application nobody maintains becomes a risk. The question is not "can we build it?" but "who will look after it in year three?".

A checklist before deciding

1. Define the process and how many users will use it today and in three years.
2. Compute the 3-year cost of each route with the matrix, including implementation, training and support.
3. Test the worst case: a 15% price rise, development costing 50% more, a higher exchange rate.
4. Ask about the exit: how you export your data and what happens if the vendor disappears or changes the price.
5. Review data handling and VAT with the right person.
6. Start small: a pilot with a few users before committing three years.

And a question almost always skipped: is there already a simple tool that solves 80% of the need? Sometimes a well-made Excel template, with support, avoids paying for features nobody will use (see the hidden risk of Excel to know when it is not enough).

Colombia, Latin America and the world

Worldwide, the subscription has become the norm: almost all office and management software is sold as a service. In Colombia and Latin America the model has its own nuance: you pay in dollars with income in pesos, so a devaluation raises the cost without the vendor changing the price, and public procurement and schools must also justify spending to boards and administrators. For managers, the question is the sustainability of the expense; for teachers and users, that the tool really saves them work (see how to automate with Excel); for families, what happens to their children's data when the school hires a platform (see student data).

Tools that already exist and you can try

If your need is billing, sending documents or automating office tasks, you may need none of the three big routes. These Excel templates and applications are bought once, with optional support, and run on your own computer:

Keep reading: the cloud is not a backup, basic security mistakes in a company and AI agents with access to your systems.

Frequently asked questions

Is buying a license cheaper than paying a subscription?

It depends on the number of users and the time horizon. In the example, the license only beats the subscription from about 19 users over three years; with few users, the subscription usually costs less.

How much does it cost to maintain an in-house application?

A rule of thumb used in the example is 20% of the development cost per year, plus hosting, security and support. It is an illustrative assumption: adjust it with a real quote.

What is total cost of ownership (TCO)?

It is the sum of everything a tool costs over a period (purchase, implementation, training, support, infrastructure and administration), not just the purchase price.

Does a subscription pay VAT in Colombia?

Digital services provided from abroad to consumers in Colombia are subject to 19% VAT. Confirm with your accountant how it applies to your case.

How do I avoid being locked in with a vendor?

Require the ability to export your data in open formats, keep your own copies and negotiate exit and price-increase terms before signing.

Do your own calculation. Download the 3-year cost matrix, replace the yellow assumptions with your figures and see which route wins, and at how many users the answer changes.

Food for thought

Paying a subscription is renting; buying a license is owning a door someone else keeps locking; building is constructing a house you have to live in and repair. Is technological autonomy a luxury only large organizations can afford, or an investment small ones should make for sovereignty over their own data, even if it costs more at first? And who should decide: whoever pays, whoever uses it or whoever answers for the data?

More guides in AI and technology for teachers