Discuss Home · Bootstrapped Podcast · Scribbleton Personal Wiki · HelpSpot Customer Service Software · Thermostat NPS

Monthly billing for downloadable software?


#1

Any of you guys use monthly billing for desktop software? I was doing some data analysis and I just discovered that there is a large company still using my software from 2011. That is, the software was built in 2011 and they have never desired an upgrade.

I guess I should be happy, but it looks like I have left money on the table, at least with this particular customer. The analysis is manual and at a glance, there are other customers like this.

Reasons to switch to pay-as-you-go billing:

  • People can use your application for years. You should get paid for that.
  • Low up-front investment for customers

Reasons to remain on a fixed price scheme:

  • I don’t like money

This is a little tongue-in-cheek, but perhaps you can give me some of your own experiences.


#2

I think that monthly recurring for a desktop app is hard to explain and justified unless some piece of the software runs on your server (Slack) or you add some cloud feature.

Microsoft is now charging their downloadable office by month, but they add a few cloud features (Cloud drive, skype, email) so that make sense.

YNAB switch to a 100% could offering instead of adding MRR to a desktop software

Why not going for a yearly license? That’s standard practice in Desktop software.


#3

If you can go SaaS with your desktop app, go for it. However, not all desktop apps can (and maybe should) be SaaSified. In the recent past Adobe and JetBrains had to face a lot of flak from their customers for doing so.

Few questions that you can ask yourself before going the SaaS route

  • Does my software add constant value to the customer every month? For example a stock ticker that fetches stock data every day

  • Can hosting the software (or data) add value to the customer - by way of not needing a sys admin to take care of servers.

  • Has my software traditionally been in a one time payment business model and will my customers be mad if I cut them off for not continuing a subscription. Code editors have always been a one time payment. You could charge for upgrades, but you cannot disable a code editor if the subscription ends. (well you technically could - but be prepared for serious bashing)

Even if the answers to the above are not encouraging, you could still be stubborn and go the SaaS route. But then you are vulnerable to any competition that still sticks to the one time business model.


#5

If you want them to pay frequently, then you should add some value to it frequently either by adding new features and selling upgrade licenses or going the SaaS model. The SaaS model of course should have more benefits than the desktop software. Like, to be able to access from a mobile app, export, share with others etc.

Since it is a data analysis software, can you provide them with new algorithms, charts? They can also buy new latest data from you, required for analysis.


#6

-It is simpler to administer.
-You get all the cash up front.
-Some customers prefer it (and may choose you over a competitor with a subscription model).


#7

On the topic of going SAAS (rather than just changing to subscription billing), this is at the forefront of my mind too: http://www.blisshq.com/music-library-management-blog/2015/09/08/big-idea/

Other advantages:

  • Easier support
  • More marketing channels opened up (or are accessible in an easier way)
  • More stuff to sell (anonymised aggregated data may be of use)

#8

I’m not sure it is standard.

There is a standard option to have an annual support license, that is true.

But annual license for right to use? I’d say it is unusual. I only can remember one desktop software vendor - SmartBear - that tries to sell their SoapUI with this scheme. I do not believe it works well for them.

What could be a benefit for the consumer to pay every year for the same software?

Updates are coming with the support license.

Fixes must be coming for free (for the same version).

So what could be the incentive to pay annually? I do not see any.


#9

I get quite a few support tickets asking whether the software has a perpetual license or is a subscription, it seems many peoples expectation is it will be a subscription.

My guess is within a few years it will be the norm.


#10

It could be just that your pricing page is not clear, eh.

Subscription, if spread over say 5 years, could be a cheaper option, true. But maintaining the subscription on the client side is extra cost + a risk to overlook the renewal and block the business process that the software supports.

I’m not sure it is wise for a buyer to switch to subscription.

On the other hand, why not try to offer both options?

  • Outright purchase at price N for a perpetual license
  • Annual subscription at price N/5 (if the average time a buyer uses the software is more than 5 years)
  • +Upgrade price, too

#11

I was getting a fair few questions about whether my fee was one-off or a sub. So I A/B tested some highlighted text on the buy page emphasizing it was a one-off payment. This made a significant improvement in conversion rates (I can’t remember how much). So, if you have a one-time fee, make it very clear on the buy page.


#12

Probably for software that costs 100s or 1000s of $. But probably not for $10-50 ‘utility’ software. IMHO.

BTW I recently bought the Screaming Frog SEO software. It’s quite good. But I was very nearly put off by their £99/year subscription pricing.


#13

I don’t agree with this. No software is perfect and if you want me to amortize the cost of fixes for every version in the field, that’s going to jack up prices significantly. What I’ve done in the past for extreme issues is often just given a one-off license for that day only so the user can download the latest. I don’t let them do it again though. Hasn’t caused a problem yet.


#14

Here’s how I see it as a buyer:

I’m paying for a software that is advertised as doing X. It turns out that it cannot do X in a particular valid situation. I give the seller the benefit of the doubt, and assume they did not do a false advertisement; it is just a bug. But to fulfill their original promise (for which I have already paid for!) the bug should be fixed for free.

If the defect is unprofitable to fix, well, a free upgrade to a version having no such defect or a money back should be offered.

There could be exceptions from this rule, however.


#15

Something that I’m considering for my desktop product is making it subscription based and timestamping new features.

A user’s license file has an expiry date (the date that the current subscription ends). They can still use the software forever, and they can even use new versions of the software, but they will not have access to any new features added after their subscription failed.

Why I’m thinking of doing this is, similar to Microsoft with Windows 10, I don’t want to support old versions at all. Everyone can always install the latest version.

Of course, when they try to access a new feature, the product will politely inform them that they are trying to use a new paid feature and they will need to renew their subscription.


#16

I am offering both an annual subscription and a one-time-fee for my desktop product (www.worksheetcrafter.com). This works very well for me.

The one-time-fee version runs “forever” but doesn’t include free updates.

In case of the subscription the application only works while the subscription is active. During that period they do however get all updates for free. Since I am shipping three updates per year, each of them with major improvements and new features, that is quite a benefit for them.

I don’t get any complaints since people can choose, but the majority goes for the subscription.


#17

www.tvcad.tv will be a monthly / annual subscription. It’s a B2B product, a partner product for AutoCAD in a niche market. I am pricing it the same as AutoCAD who are going subscription only at the end of this month (my pricing will match their “advanced support” level. My prospects were far more concerned about ongoing support than owning it. It is also a replacement for a long-unsupported VB6 app so they have already been educated in the value of support.

The reason I tell you this is that each market is different, they have different priorities. A couple have asked about perpetual licenses, I told them that I can make the license perpetual after 3 years but if they stop paying they stop getting updates and support.

Something else for you to consider, I have been asked about floating licenses. Thanks, I need that level of complication in my life right now. :confused:


#18

I have a question for both of you guys:

How are upgrades are handled? Is the subscription price for the newer version generally higher?

And other way around: do you force users to migrate to the latest version with each renewal to save on the support costs?


#19

Hi,

How are upgrades are handled? Is the subscription price for the newer version generally higher?

Customers with non-subscription license can switch to the new version at any time by purchasing an upgrade. This costs 30% of the full price, no matter how many updates they skipped. Simple and fair.

I send them an upgrade offer via mail whenever a new version is released. Purchasing two upgrades a year is more expensive than the yearly subscription fee, thus the non-subscription license only makes sense if a customer wants to upgrade at maximum one time a year. I guess this is why the majority goes for the subscription.

Do you force users to migrate to the latest version with each renewal to save on the support costs?

You refer to customers who go for the subscription, right? I don’t force them to upgrade, but notify them both via mail and inside the application that an update is available. The majority of them then installs the updates.


#20

Still working that one out. Initially it will be reinstalls but I plan on using something like http://wyday.com/wyupdate/
http://wixtoolset.org/documentation/manual/v3/patching/wix_patching.html has links for MSI patching. Fun fun fun.
https://www.firegiant.com/wix/tutorial/upgrades-and-modularization/patchwork/ is in (slightly) more human readable form.

No, my subscription model is basically a clone of AutoCAD’s for a variety of reasons, mostly because it is of similar value to my clients. Theirs is very similar to the Adobe thing - download, install, unlock when you want to use it and let it lapse when you don’t, you get the shiny new one for “free”. Where I depart from that is the offer of a perpetual license after 3 continuous years, although I probably won’t shout that out from the rooftops. A full year on my monthly subscription comes to about 150% of the annual price.

“Force”? No. Insist as the first step of a support process? Yes.
It has to be ridiculously easy for them to stay up-to-date - make it the path of least-resistance. My clients have told me they value support highly so they are very likely to stay up-to-date.

The other thing you need to do is make sure they can easily roll-back or re-install an older version in case something breaks for them. I am thinking about keeping the previous version or few hanging around just in case. You can change shortcuts etc or rename things so they can go back to it. Thinking out loud there.