For several months now, my company, http://linnovate.net (known internationally as Drupal.fm), is putting efforts in Drupal based products.
These products are using Drupal as an infrastructure for different kinds of products:
- Pre Customized Drupal sites, destined for publics with similar needs (this is what installation profiles is all about more or less).
This allows customers to save lots of money, because there are no huge building and development costs, but still to have a first class website at their command.
- Web based application. Here we really use Drupal as a tool, and not as a website framework. We tailor an application with the customer, and it is then available through the web, as a service (we host the service)
- Portable web based application. Same as above, only here the service is being packed and sold as a package to the customer, who host the service himself.
While developing these products, we encounter various challenges, mostly framework related, and we discover many advantages and disadvantages of Drupal, in regards to templating a project, so it can become a maintainable product/service.
Recently we all heard about the establishing of Acquia, which seems to be doing just this kind of development.
This group is aimed at service providers who are encountering the same issues as we do, so we can all benefit from each other's experience. It can be a great stage for exposing our projects and products.

Comments
Interesting subject matter...
...but aren't Drupal products essentially Distribution profiles, install profiles, whatever you want to call them? If so, it seems we already have this group set up and some relevant conversations?
http://groups.drupal.org/distributions
Just curious...
Gus Austin
PepperAlley Productions
Gus Austin
There is a difference...
The difference between an installation profile and this approach is that typically this is a multisite installation which houses many drupal instances based on the same code.
Providing an installation profile is like giving you the "Recepie" of how to create a "product".
The problem from our experience is that for non technical clients the learning curve is simply too steep.
We're experiencing with products for education and smaller communities and they just want to "lease" a drupal site and "use" the site - not neccesarly build it.
The model is very similar to what bryght has been doing with their hosting blogging platform - I really hope they join the discussion and share their experiences.
Linnovate - Community Infrastructure Care
Drupal Services in Israel
http://www.linnovate.net
Linnovate - Community Infrastructure Care
Drupal Services in Israel
http://www.linnovate.net
There is a difference...
The difference between an installation profile and this approach is that typically this is a multisite installation which houses many drupal instances based on the same code.
Providing an installation profile is like giving you the "Recepie" of how to create a "product".
The problem from our experience is that for non technical clients the learning curve is simply too steep.
We're experiencing with products for education and smaller communities and they just want to "lease" a drupal site and "use" the site - not neccesarly build it.
The model is very similar to what bryght has been doing with their hosting blogging platform - I really hope they join the discussion and share their experiences.
Linnovate - Community Infrastructure Care
Drupal Services in Israel
http://www.linnovate.net
Linnovate - Community Infrastructure Care
Drupal Services in Israel
http://www.linnovate.net