System price for mental health clinics with a permanent license: maintenance and update questions

A perpetual license seems to be the cheapest option because it is a one-time payment, and this is only partly true. The down payment buys the right to use, but then the system requires maintenance, updates, hosting, and support — annual terms that the license does not cancel. Whoever compares the price of a license to the price of a one-year subscription is comparing two different things.

The correct question is not “Which is cheaper?” Rather, “Which one is appropriate for your facility’s financial cycle and operational capacity?” This guide details what you should ask before making a choice.

The short answer is cost

A perpetual license means a higher down payment for unlimited use, with a lower annual fee covering maintenance, upgrades and support. And a subscription means a lower down payment for a higher recurring commitment that includes all of that. The real difference between them appears after the third or fourth year, and depends on the annual maintenance percentage in the license offer.

There’s an even more important non-financial consideration: With a perpetual license, your facility has more responsibility for operation — hosting, backup, applying updates, and sometimes security. If you don’t have a technical team, you may later pay more than you save. See deployment options in Privacy and permissions page.

Items included in the estimate

First: the scope of the license itself

Ask carefully: Are you a user of the license? Do you have a branch? Does it include all units or a specific range? Does it apply to a specific version or to the system as it develops? A “perpetual” license that is limited to one version is not actually permanent — after a few years you will find yourself facing a paid upgrade.

Second: Maintenance and modernization

This is the most important point of this model. Ask: What is the annual maintenance percentage of the license value? What does it include — just bug fixes or new releases too? What happens if maintenance is not renewed: Does the system continue to operate with a frozen version, and is support still available? Request that the percentage and the ceiling for its increase be written in the contract.

Third: Hosting and architecture

If operating on your own infrastructure, account for the servers, storage, network, backup and license renewals involved, as well as the time of those managing them. If the hosting is through the provider, it is an annual fee independent of the license, and a clear clause must appear in the offer.

Fourth: Integrals

Integrations are not affected by the licensing model: they are valued, built, and maintained in the same way. But be aware that changing a third-party provider’s interface may require a modification to the connection — and ask: Is this covered under annual maintenance or is it valued as a standalone modification request? Linkage classification details in Integrations page.

Fifth: Operation and Support

Specify the level of support that comes with your license in the same detail as that required with your subscription: coverage times, channels, response times, and out-of-scope. And don’t assume that the license includes open support — it often doesn’t.

How do suppliers’ offers compare?

Do not compare the license to a one-year subscription. Choose a realistic period — five years, for example — and calculate the total for each model over it with the same inputs:

Then add two factors that do not appear in the equation: the cost of your technical team’s time if it endures operation, and the risk of the release being frozen if maintenance stops. The same expansion scenario applies here: how much does it cost to license additional users or a new branch? In some offers, adding a user in a licensing model is much more expensive than in a subscription.

What do you require clarification before contracting?

• What exactly is included in the license: users, branches, modules, and versioning.
• The annual maintenance percentage, what it covers, and the ceiling for its increase over the years.
• What happens to the system and support if maintenance is not renewed.
• Are new versions included in maintenance or a paid upgrade?
• Who is responsible for hosting, backing up and applying updates, and with what effort?
• The cost of adding users, branches, or units after the first license.
• Is it possible to switch from license to subscription or vice versa later, and under what conditions?

The next step is to define your range

Before you choose a model, resolve three questions internally: Does your budget favor recurring capital or operating expenses? Do you have a technical team that can take responsibility for operation? How much do you expect the number of your users to grow in five years? The three answers decide the choice faster than any price comparison.

Then order both offers on the same domain — license and subscription — and compare them over five years. A provider who is confident in what he is offering will not mind offering both formats. See Pricing factors AndImplementation plan Before the meeting.