Fab's AutoBackup 6 Pro - a must have tool for techs

I have no problem paying for software, and I certainly want to support Fabs. For me, I'm getting to a point with subscriptions that I'm moving away from products & services that require them. I understand my voice in this discussion doesn't carry much weight, but I would support almost any other option before a subscription model.
 
And its those SOB's I hate.
I know, I know.
Years and years ago I was a self-employed s/w developer.
Well, I suppose there are two main separate issues (IMHO).
Potential loss of revenue (from hacking the licensing code, back-dating, etc.) and someone possibly reverse engineering and stealing the code and profiting from the same.
If sales/renewals/whatever are fairly frequent then I don't think that the loss of revenue in scenario # 1 would be significant.
 
I have no problem paying for software, and I certainly want to support Fabs. For me, I'm getting to a point with subscriptions that I'm moving away from products & services that require them. I understand my voice in this discussion doesn't carry much weight, but I would support almost any other option before a subscription model.
Do you consider an annual maintenance fee that includes updates/upgrades to be a 'subscription' or is it merely semantics?
 
Do you consider an annual maintenance fee that includes updates/upgrades to be a 'subscription' or is it merely semantics?
Oh, it's probably semantics to some degree. I would prefer to see something that would include patches/updates for the first year after purchase. A reasonable (whatever that might be) yearly charge for patches/updates. A product that continues to function unimpeded should I opt not to pay the yearly fee.

I'm old, so I recall purchasing a license to use software, which included all the .x.x stuff at no additional charge. Major version changes like 1.0 - 2.0 required a discounted upgrade fee rather than a complete repurchasing. That said, I certainly can see the difficulty of working with such a model and am not suggesting it's viable or desirable. What I am saying is, I've developed an aversion to monthly fees/subscriptions which are so pervasive. Making a single purchase of a product or service is getting scarce. Even Amazon wants us to subscribe to laundry soap! Enough with the subscriptions already!
 
Oh, it's probably semantics to some degree. I would prefer to see something that would include patches/updates for the first year after purchase. A reasonable (whatever that might be) yearly charge for patches/updates. A product that continues to function unimpeded should I opt not to pay the yearly fee.

I'm old, so I recall purchasing a license to use software, which included all the .x.x stuff at no additional charge. Major version changes like 1.0 - 2.0 required a discounted upgrade fee rather than a complete repurchasing. That said, I certainly can see the difficulty of working with such a model and am not suggesting it's viable or desirable. What I am saying is, I've developed an aversion to monthly fees/subscriptions which are so pervasive. Making a single purchase of a product or service is getting scarce. Even Amazon wants us to subscribe to laundry soap! Enough with the subscriptions already!
I understand and agree that your conditions would be my closest to my best scenario.
I did not know about the Amazon subscription for laundry soap.
I am going to have to read up about it when I need a good laugh!
Unfortunately, re-occurring revenue looks good on the balance sheet and to investors.
Even Team Viewer which was already really expensive (IMHO) is/has switched to a monthly subscription.
 
I'm getting to a point with subscriptions that I'm moving away from products & services that require them. I understand my voice in this discussion doesn't carry much weight, but I would support almost any other option before a subscription model.
Do not believe that. Any opinion is important. I am just exploring new ways, no decision has been made at the moment. Just thinking
 
  • Like
Reactions: GTP
I understand and agree that your conditions would be my closest to my best scenario.
I did not know about the Amazon subscription for laundry soap.
I am going to have to read up about it when I need a good laugh!
Unfortunately, re-occurring revenue looks good on the balance sheet and to investors.
Even Team Viewer which was already really expensive (IMHO) is/has switched to a monthly subscription.
I understand subscriptions offer a more stable and increased income. I get that. I don't think it's the right model in every scenario. There are products/services I might wish to purchase for a specific use, but my usage would not be consistent enough to warrant a subscription. In several instances that's not an option for me as a subscription is required to gain access to the product. That's not the case here, but the allure of the subscription model is becoming over-used and I'm finding myself becoming resistant to it.
Do not believe that. Any opinion is important. I am just exploring new ways, no decision has been made at the moment. Just thinking
Sorry for not being more clear. I was referring to the over-all business model change toward subscriptions across many industries. It was my voice in that I was thinking of, not on this board, nor with you.
 
I understand subscriptions offer a more stable and increased income. I get that. I don't think it's the right model in every scenario. There are products/services I might wish to purchase for a specific use, but my usage would not be consistent enough to warrant a subscription. In several instances that's not an option for me as a subscription is required to gain access to the product. That's not the case here, but the allure of the subscription model is becoming over-used and I'm finding myself becoming resistant to it.

Agreed.
IMO options would be great
 
A product that continues to function unimpeded should I opt not to pay the yearly fee.
I hate subscriptions as anyone but to "support" a software developer, is to maintain the pament hence support in these cases are subscription. In this case what we have will always work online or not. If Fab decides to add more features then it is his choice. He can charge what he wants and you can take it or leave it.

We all agree here that his work is worth it. You can not make a living on selling software with one payment (lifetime) and expect fixes and upgrades for free.

Once every one has the product that wants it no more income.
 
I hate subscriptions as anyone but to "support" a software developer, is to maintain the pament hence support in these cases are subscription. In this case what we have will always work online or not. If Fab decides to add more features then it is his choice. He can charge what he wants and you can take it or leave it.

We all agree here that his work is worth it. You can not make a living on selling software with one payment (lifetime) and expect fixes and upgrades for free.

Once every one has the product that wants it no more income.
Nothing to do specifically with FABS but ....
if the developer closes shop for whatever reason how does the software 'call home'?
 
I hate subscriptions as anyone but to "support" a software developer, is to maintain the pament hence support in these cases are subscription. In this case what we have will always work online or not. If Fab decides to add more features then it is his choice. He can charge what he wants and you can take it or leave it.

We all agree here that his work is worth it. You can not make a living on selling software with one payment (lifetime) and expect fixes and upgrades for free.

Once every one has the product that wants it no more income.
Not sure where you're coming from on this. Neither I nor anyone else I've read here has suggested such a thing.
 
Well you paying to use a product. If you stop paying your car payment how long do you think you will still be able to drive it.
Sorry, I do not think that I explained the question properly.
What I mean is that assuming the product 'calls home' to ensure that the subscription is current....
It is possible, regardless of the type of subscription, that the developer can close down and the software calls home and does not get an answer.
As a result, the software may then stop functioning.
This is not specifically related to anything that FABS has said, proposed or done.
I think that his software, support, etc. are top notch.
 
If you bought it outright then you can expect to drive it until it falls apart and you need to buy a new one, or you need/want a newer model with additional features or better performance.

It's an old-fashioned idea but still valid.
Yes, like Mike was saying above.
Personally, I think that FABS has been way beyond fair but don't tell him that I said that :).
My choice would be a one-time purchase of a specific version with x amount of days of support (including updates).
Then, when a new version is published, the end-user can decide if the upgrade is worth the cost.
That is it in a nutshell in a simplified format.
 
My choice would be a one-time purchase of a specific version with x amount of days of support (including updates).
Then, when a new version is published, the end-user can decide if the upgrade is worth the cost.
That is it in a nutshell in a simplified format.
Yes, that looks a lot more simple to handle for me too. Once upon a time when Fab’s AutoBackup 4 Tech arrived on the market, it used to have time limited updates. I felt people not that happy with it. Thinking about it, it was not that bad since it could bring recurring fees for me and no subscription constraints for the users. I tend to prefer this solution.
 
Last edited:
The question being debated here isn't about the value of the product, his work, or whether we should support Fabs. I think we're all agreed in those areas. Rather, the discussion is regarding what business model he might choose to use. It is entirely his choice. That he's considering the input of his customers in his decision speaks well of him.

I'm not the only one who is beginning to struggle with what I'll call Subscription Saturation. That said, sometimes it's the correct model to implement. The MSP model is an appropriate example. MSP's offer a service. We use products & services in providing that service, and our cost for those products & services we provide are included in what we charge for our service. Something similar might be the person who takes care of your yard. He too provides a service which he may pay for products & services to be able to offer his service. Usually, the service provided is continuous and on-going. Occasionally, either example might do project work for a fee, but generally the subscription model is appropriate.

An area where the subscription model might be used and not be a "best fit" is marketing content. Companies or individuals who write marketing or advertising content sometimes use the subscription model. More often, there's a campaign of some sort which has limited duration, and therefore the subscription model may not be the best fit for the intended use. ABC company has $xx.xx in their advertising budget, but XYZ company requires a subscription to gain access. ABC company can afford to pay for piece work, but is put off by the subscription requirement and either goes elsewhere or chooses not to advertise in that way.

While those scenarios may not be the best examples, the point is that a subscription business model isn't always the best fit. In this case, Fabs has several options open to him.

  • Monthly subscription
  • Fee per use
  • Update/bug fix yearly subscription
  • Version upgrade fee
  • Some hybrid
Whatever he decides, he has our support.
 
As a result, the software may then stop functioning.
Yes ignoring Fabs like you said. How long do you expect to have use of my fictional car (repo)
I'm not the only one who is beginning to struggle with what I'll call Subscription Saturation.
I hate it as well. I was fourtnate to get in on many things a ground level and was granfathered. Rouge killer and UVK for example.
 
Not having a subscription model, but a plain once a year licence fee would stop any funny business, yeah?
I mean that by paying a yearly fee, you would get whatever extra Features Fabs released in that year. That would give the benefit of extra support (income) for Fabs, as well as we all have the the most up to date current version.
Just my .02
 
Last edited:
Back
Top