[consulting] Still need help with a Drupal one page handout

[Evan Leibovitch]

Boris Mann wrote:
> I'm writing to ask for more help with a one page handout [1], as Dries
> and I are fully booked doing final preparations for DrupalCon.

IMO what's there already is fine (except that "friendliness" isn't 
spelled with a "y").

If anything there are too many words, not too few. Don't feel the need 
to pack text into every corner of the paper; this isn't a spec sheet. 
White space is your friend. The main goal of a one-pager is to attract 
attention, tickle peoples' curiosity, and GET THEM TO THE WEBSITE where 
all the real information should lie. You can't do full justice to the 
system in one page so don't try.

Unfortunately this sheet won't be of any use to me as we sell solutions, 
not features. If I'm marketing right, clients care more about speed, 
quality and value than choice of tools. The use of Drupal matters to my 
company as the implementor, because it allows us to provide clients with 
projects done faster, better and less expensively than competitors. But 
clients don't care about our choice of CMS any more than they care about 
choice of text editor, OS platform, or brand of motherboard running the 
whole thing.

When you hire someone to do a home renovation, do you only choose 
contractors who use Makita tools? Do you only take Ford taxis? Do you 
know why Red Hat has *never* used penguin logos?

At the end of the day, are you selling Drupal, or are you selling you?

- Evan