I think he was trying to point out that you don't actually list any specific issues that webassist could address. Your post has a much better opportunity to hurt webassist's momentum than to help us fix any problems you are talking about. Your complaint has little substance that WebAssist can use to improve our products or work-flow, but has an general tone that could actually make that progress more difficult.
We appreciate constructive advice, and would really appreciate specific examples of what doesn't work for you so we can make sure to fix them. We are currently testing for cs5 and fixing bugs, so please spend some time clearly outlining the issues you are having and we can make sure to try to address them. We need a clear understanding of the problems to fix them.
Your post gives us clear understanding of your opinions and favorable review of competing extension companies, so your post may convince someone to stay away from webassist, but it does nothing to help us improve our products... which is our goal ,and at the same time you criticize us as if it we didn't care, you don't give us enough information to go on when in fact we do care.
We may have already fixed some of the problems you are experiencing. We may be in the process of fixing all of them. But before I can say for sure you need to tell me what those issues are and give us a chance to address them.
If the goal of your post was to give us information about what the issues are and how we can fix them, then it was ineffective because of the lack of detail. If the goal was to generally criticize, hurt our image to those who don't know better, or promote other extension companies, than it was right on target. However you should not be surprised when it will be construed as negative by the people that know that we actually are listening and are working on fixing all of the problems that are reported. The customers that work with us, know we are not only willing, but happy to work with them to fix the issues we run into.