Windows 2000 Support

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Sunday, 8 March 2009

Licensing changes ... Yes, I still call it Free. Do you?

Posted on 12:03 by Unknown
Starting in Process Lasso v3.50, there have been a few minor changes to the licensing. The free build has these changes:
  • ADDED a system tray balloon tip to ask users to please consider purchasing the Pro build. It disappears by itself in seconds, causing no interruption of work. It only appears once per run of Process Lasso. Since Process Lasso is resident (always running) software, most users will only see when they restart their computer, or when they upgrade Process Lasso.
  • ADDED a new message box asking the user to consider purchasing the Pro build. This is shown after the product has been used for 60 days. It only appears once per run of Process Lasso. Again, since Process Lasso is resident (always running) software, most users will only see this message when they restart their computer, or when they upgrade Process Lasso.
  • REMOVED the 'commercial users: must purchase...' periodic message from the graph. The others still remain, though they are less lengthy and so less obtrusive.
  • REMOVED the installation query on whether Process Lasso is for Home or Commercial use.
  • REMOVED the forced expiration of commercial use installs.
I've already received complaints about these minor nag(s). I don't personally find them very bothersome (I use the free build myself), but apparently some people do.

People say that it is not free if there is a nag. Now, I don't like nags any more than the next guy, but a little nag does not change the fact that you can continue freely using Process Lasso.

Users must understand that my situation has been dire for some time, and my choices are limited:

Options
  1. Give up on Process Lasso
  2. Make it a time limited trial, so you must purchase it to continue use
  3. Keep putting in small nags or moving features to the Pro build until I get enough purchases.
I've tried very hard to make Process Lasso a fine product. It hasn't been easy to do everything from development, documentation, to quality assurance. Sometimes I even make mistakes, despite my best efforts of version control, testing, and code review. Such mistakes, no matter how minor, are devastating to me personally because I am trying so hard to make everything perfect. I say this only to let everyone know that I care about the quality of my software, in contrast to some developers that don't.

Unfortunately, I simply can't seem to profit enough from Process Lasso home sales, so I plan to focus more on the Enterprise. That will take considerable development time though. In the interim, I must continue to feed my family, therefore I must keep getting more aggressive with pestering users to purchase the Pro version.

If and when sales become consistent and sufficient, I will start moving the other direction (more free, less nag). Until then, I encourage those users who DO like Process Lasso to please defend it when you see users complain about it no longer being totally free.

It may be that part of the problem is simply that Process Lasso doesn't have enough exposure/marketing. Without capital, that is a difficult problem for me to solve. However, I'm always thinking of possible solutions. Perhaps if I ever generate enough revenue I can reinvest into advertising.

If more users would purchase, I could actually lower the price of Process Lasso. Heck, if I could get a 100% purchase rate, I'd happily sell licenses for a mere $1 . Unfortunately, the customer to user ratio is 1:1000, or greater. Yes, that high! To be clear, that means that for each 1,000 long-time users of Process Lasso, there is only one person who purchases it.

Lastly, I want be sure to also thank the many people who have purchased Process Lasso over the last few years. Many did so long before I added any real incentives to purchase. In fact, there were many users who made voluntary donations. These users have kept this project alive this long - thank you!
Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in | No comments
Newer Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Process Lasso v5.0.0.28
    This build continues maintenance, fixing several items and also making a nice improvement to the graph's display. Further, the last sele...
  • Tightening the Governor
    Most users of Process Lasso are familiar with its core engine, ProcessGovernor.exe. It is the silent background process that applies all pro...
  • Process Lasso and WDFME
    Since Process Lasso can be complex for the layman, something we are working on, I wanted to list a set of steps to address the commonly abu...
  • Indonesian language added - That makes 11
    Thanks to the work of Ivan Chin, an Indonesian (Bahasa Melayu) translation will be included in v3.99.36. This will be the first time even he...
  • WARNING: Cracks for Process Lasso may modify HOSTS file
    WARNING:  Cracks for Process Lasso have been seen to modify your system HOSTS file so that you can no longer access  bitsum.com  and/or  bit...
  • Optimizing process icon memory use & New core feature coming..
    Two in one post. Yes, here at Bitsum we're going Green by conserving bandwidth ;). Of course, that's just a joke and I fully support...
  • Next update, Options menu gets some changes
    I decided to make the Options menu a little more consistent and move the ProBalnce configuration down with the rest of the rules configurati...
  • Anti-virus software - the #1 cause of PC performance troubles
    Many users realize their anti-virus software consumes massive amounts of system resources, and hope that Process Lasso will somehow keep it ...
  • Process Lasso v5.0.0.48
    Changes: [.48]Change.GUI: Do not show 'Activate Now' menu item after activation [.48]Change.GUI: Adjusted logging thread CPU and I/O...
  • WARNING: Beware of third-party utilities that adjust process priorities (other than Process Lasso)
    Recently I've seen either 'hacked on' additions to existing products, or new products, that have the ability to manipulate proce...

Blog Archive

  • ►  2013 (1)
    • ►  March (1)
  • ►  2012 (6)
    • ►  September (1)
    • ►  July (1)
    • ►  June (2)
    • ►  January (2)
  • ►  2011 (166)
    • ►  December (3)
    • ►  November (2)
    • ►  October (2)
    • ►  September (6)
    • ►  August (12)
    • ►  July (14)
    • ►  June (17)
    • ►  May (19)
    • ►  April (13)
    • ►  March (27)
    • ►  February (31)
    • ►  January (20)
  • ►  2010 (203)
    • ►  December (23)
    • ►  November (34)
    • ►  October (38)
    • ►  September (17)
    • ►  August (19)
    • ►  July (19)
    • ►  June (11)
    • ►  May (16)
    • ►  April (8)
    • ►  March (6)
    • ►  February (6)
    • ►  January (6)
  • ▼  2009 (43)
    • ►  December (6)
    • ►  November (1)
    • ►  October (10)
    • ►  September (3)
    • ►  August (1)
    • ►  July (9)
    • ►  June (2)
    • ►  May (3)
    • ►  April (4)
    • ▼  March (4)
      • Instance count limits coming back to free build
      • v3.53.9 beta - release candidate
      • New feature: Show/hide individual process columns
      • Licensing changes ... Yes, I still call it Free. D...
Powered by Blogger.

About Me

Unknown
View my complete profile