[consulting] Selling Drupal to consultants
bill at funnymonkey.com
Mon Feb 13 07:35:00 UTC 2006
Yeah, this seems like a pretty hard sell -- not because there isn't
logic in what you say, but because, despite the logic of what you say,
they have made it pretty clear they want to go in a different direction
as far as a business plan. As you say, this is more about your own
sanity, but, if I was in your shoes, I would view these conversations as
opportunities to create points of reference.
When an organization is making money, it's hard to persuade anybody to
change the focus/plan. However, by creating these points of reference
now, you will have less talking to do if/when things slow down.
So, say it now to keep yourself sane. Say it later to help them continue
making money. When it becomes clear that your advice will get them more
business, at that point, I think they'll listen.
Tools for Teachers
Dan Robinson wrote:
>>The "Costs of forking" thread has focused on how to convince clients that OSS
>>software like Drupal is a good thing, and that the benefits are worth it.
>>Good stuff. :-) I have a slightly different problem, however.
>>I work at a small web development consulting company that has just doubled in
>>size in the past few months. The developer (singular) who wrote our old
>>codebase has mostly left, and everyone agrees the old CMS code is
>>unmaintainable. Lucky me, I get to write the new one. :-) Fun as it sounds
>>to write a CMS from scratch on a deadline and then turn around and use it on
>>a client site almost immediately, I'd much rather switch the company over to
>>Drupal then write a rushed Drupal-inspired hacked-up CMS. I've mentioned it
>>a few times, and so far haven't gotten a firm no but mostly have gotten
>>waffling "we'll see".
>well you could always take the drupal code base and fork it :). I mean
>what is their business model? Are they in the business of creating a
>new CMS - doesn't seem very swift to me.
>>If I can get an actual discussion on the table somehow, any suggestions on how
>>to sell both my fellow developers and designers and management on Drupal?
>>They made it clear when I was hired that we're not an open source shop, since
>>I'm a big open source fan, although we do current use some LGPLed stuff in
>>various places and we make it a point that we always own the code, not the
>>client. I want to wedge that door wider, for my own sanity if nothing
>sounds like they think that their business model depends on their
>ability to lock their customers into license agreements. It is a little
>hard to see how this is compatible with a Free software business
>strategy. At any rate my 2 second opinion is that you will get no
>traction trying to argue it from a code/engineering angle. The only way
>to get anywhere is probably to convince them that there business model
>isn't really that workable - that'll be fun :).
>consulting mailing list
>consulting at drupal.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the consulting