Projects made with a CMS -> Money problems_问答_开发者

Projects made with a CMS -> Money problems

开发者 https://www.devze.com 2023-01-04 08:17 出处：网络

i want to discuss about a problem: i\'ve lately had discussions with some customers to which i\'ve asked money for projects written in Drupal: when they know that i use a CMS they immediately say that

i want to discuss about a problem: i've lately had discussions with some customers to which i've asked money for projects written in Drupal: when they know that i use a CMS they immediately say that they want to pay less "because I use a CMS". I develope since 15 years and i've made many many projects wit开发者_StackOverflow中文版hout using a CMS and by using my libraries; i'm lately using a CMS but this does not mean that i don't write code ... Which could be the best response to give to a similar question? Ciao c.

Explain it to them very simply.

If you have to install and configure any Content Management System, that takes you more time and therefore costs a bit more than a static website. You need be as transparent as possible when you detail the costs, so tell them how much time will be spend designing the theme, how much time will be spend configuring Drupal for their website and so on.

It would be interesting to ask them why they think it should be cheaper, as you will then understand what misconception they have about CMS. You can then explain things better to them so that they understand what using a CMS actually means.

I would say that they are paying for your expertise and experience, regardless of the tools you use. If they want it cheaper, they can ask someone else. The CMS helps to add stability, security and expandability to what they would get if they had a custom solution.

Plus, if it was all custom code it would be extremely difficult to hire someone else to take over if, God forbid, you were hit by a bus. The CMS gives THEM more options.

I would agree that you should explain where the money is going, in general terms, but you shouldn't have to justify every detail. Otherwise how do you itemize "dealing with stupid customers who need their password reset for the millionth time" or "explaining the difference between a 100x100 thumbnail JPG and a 3600x2700 BMP". It could also open the door to a lot of haggling that will just waste your time and frustrate you.

I had a client who asked me over and over again the same kind of question.

If your client doesn't perceive the value you're adding to an Open Source application then give them the source code and point them to the documentation. Tell them to build it themselves.