Marketing a product is the process of understanding how your product is different from alternatives and communicating your advantages. The first step is understanding why your product is desirable.
That isn't as easy as it sounds. Describing the product is best done by pointing out its "benefits", not it's features. There is an old concept in marketing -- "features, advantages, benefits" or FAB. The features are the specific things your product has that make it different from others. The advantages are how it compares with the alternatives. And the benefits are what the user/customer receives by using your product instead of alternatives. Customers relate to benefits, not features. An example: "web2py's syntax and concepts are easier to learn that Zope/Plone" is a feature. It is true, but it has less impact than pointing out the benefit derived from the feature: "your website is created, debugged, and online in a fraction of the time it would take you to do it in Zope/Plone". The tagline is the most important benefit statement of all. It is the one place where you have a chance to define your product and its reason for existence where it will be read by all. I do agree that web2py could use a fresh marketing strategy, but there is no hurry to develop it. Good ones take some time. They are the products of a lot of thought and deep understanding of the product and where it fits in the whole ecosystem. The tagline is usually one of the last ideas to be developed. -- Joe B. P.S. I used to do some product marketing for one of the Hewlett- Packard instrument divisions. Not that we were all that good at marketing -- the inside joke was that HP would have described sushi as "cold dead fish you can eat!" But I learned a lot about marketing back then and found it very interesting. On Mar 16, 7:54 am, mdipierro <[email protected]> wrote: > I agree with this. The new "who" and "support" pages are an attempt to > do exactly that. > > Although as I have suggested in the past it, we should not just > imitate other open source projects. We should think bigger. Remember > the discussion on the "open source corporation"? There is more than > unites us here than just web2py and we need to capitalize on that. > Web2py should be a tool in our toolbox together with postgresql, linux > etc. Moreover if we "officialize" the concept a team and toolbox it > should be open (anybody can apply) but also selective (not everybody > gets in). > > As I mentioned in the past I have no interest in competing with Django > or Rails. I want to compete for consulting jobs with IBM. I think we > have the people, we don't have the structure in place. > > Massimo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
