Joe Brinkman wrote
Using this analysis, DotNetNuke would be deemed inconsequential in the CMS market. I don't think you will find many in this forum who would agree with that sentiment.
In many ways, DNN is inconsequential in the CMS market. Without adequate versioning, approval and workflow features, integrated into the core and available in all modules, DNN is a non-player in the larger world of CMS. This year's roadmap to Cambrian holds promise in overcoming that flaw, but in terms of real money, DNN is out.
I think the point about DNN developers still aiming at the small/personal user is correct. Although DNN is being used for large operations, those who develop the major applications are using DNN as a framework and selling the solution, not a module to add into any DNN site. And that's a promising market for those integrators and vertical markets that have the need and finances to support the market. This isn't unique to DNN, solutions built on web platforms might be DNN, or they might use any other development tool or framework that supports the task. We (a municpal government with ~500 employees and $120 million in revenue) buy many solutions that are web based, and each has been a different platform and programming environment. We don't really care, we're buying the solution, not the framework or tools. If the solution fits our needs then the hardware/software requirements of that solution are secondary to a great extent.
On the other hand, I have a year-long project to migrate internal and external web sites to a CMS, and a budget that allows for several commercial options. I'm in the process of prototyping a solution using DNN, along with some third party modules where needed, that is very promising. It means more work on my part, but saves money and that's always a good thing in local governments. It also gives me the complete solution, where all the commercial options miss on one or more important pieces.
DNN doesn't satisfy my needs completely either. Workflow and versioning are important and integrating both DNN and AD/LDAP authentication is too. Both show promise in future releases, and I'm kind of counting on them being available. I haven't found third party solutions to all my problems, and I'm not willing to invest in any third party module that may possibly be unsupported or abandoned in the future. I am willing, and able, to pay extra for the support and stability of the developer. But I'm getting ready to start tossing some cash at modules which provide possible solutions, even though I may end up not using them. A couple hundred bucks for a module is nothing if the module does what I need, where for an individual it might be daunting. If a module costs less than $50 an hour for the time it would take me to develop it, and I'm slow, it's better to purchase it than develop it on my own, provided the support and maintenance is there.
I can't afford to buy modules that aren't updated to work with a new DNN version until after that version has been out for six months, and that's where many developers fall short. Naturally, I understand the delay, especially if the developer does DNN modules as a side to his/her regular job, but understanding the delay doesn't mean I accept it. If a developer isn't big enough to have a full-time staff, then they aren't big enough to service me. I also can't buy products with PayPal, and I have monthly credit card purchase restrictions. If a developer can take a purchase order, they get preference in my buying choice. The average cost of modules for DNN doesn't justify a purchase order, and it may sound strange but buying a $10,000 item is often easier for me than buying a $29 item. Just give me $10,000 worth of value.
I don't buy the argument that social networking is a fad, though it will definitely change and mature as it gets accepted by enterprises. We're already looking at Wikis and Blogs as options for knowledge transfer between employees, and moving many email conversations to a forum format. All of these are good for business and make us more efficient. None of the current DNN modules work in the ways we need, but the potential is there. We probably won't be doing a Facebook implementation anytime soon, but the principles can be used for some unique data mining options we may not even have thought of yet. As our employee base changes over to users who are more familiar with social networking options, our intranet will likely keep pace.
DNN is not the end product, nor are individual modules. Keep that in mind when pricing and you'll be well served. If you have a total solution, charge for it. If you're just providing a cool widget, understand that you won't get rich.
Jeff