Should I work with a web developer who who wants to use his own CMS instead of open source one?

Question

I'm having a website developed for my business. It's not a very complex site, two to three weeks should do. The programmer I'm working with wants to use a CMS that he developed himself instead of an open-source CMS. Assuming that the CMS he developed himself is good, can someone tell me what would be some pros and cons of me working with a programmer who wants to develop in his own CMS.

Answer 1

If it's YOUR website, and you are hosting it (or paying for hosting), and he's the developer, why wouldn't he work with your CMS? Sounds like he's just lazy and don't have the skillset to work with your CMS. Any proprietary stuff is more difficult to maintain in the long run. You never know if there's any hidden flaws in it you don't know about. How do you know the guy didn't leave himself any backdoors or exploits?

I'd say fire him and hire somebody who knows the CMS you want to work with.

EDIT: PC Magazine outline another problem... What if that guy is no longer in business? Unless you also get the SOURCE CODE of his CMS, if he gets hit by a bus a month after he leaves your job, you are up the creek without a paddle, so to speak. As nobody knows the system except him, and he's... no longer available.

If you have the source code, at least SOMEONE can fix the problem in the future, if that guy's not available. However adding source code to the deal can make the project cost a LOT more. Another thing to think about.

Answer 2

Ask the developer to see an example of the CMS he or she has developed. Find out if it will work for you.

If it won't work for you, then tell the developer it won't work and why. If it does work, then why push something on to the developer unnecessarily.

I would not worry about the developer putting in a back door. The developer's building your site and can put in back doors all over the place if so desired.

Most commercial developers won't give you an option to dictate what CMS you can have on your site, so why should this developer be differnet?

The pro you have to using the developers CMS is he can change the CMS he knows it inside and out. While true, an open source CMS can be edited but the developer has to figure out what needs to change. Open soucre does not mean the code was laid out in an organized way and it may be difficult to make what you would feel is a simple modification.

DON'T tell the developer how to develop, this is his or her job.
DO tell the developer if what's offered is not sufficient when it's not.
DO know up front what's offered to know if it is sufficient BEFORE signing an agreement.


In short:
Know what you are going to get before you buy. When you know you'll be happy with it, then buy it. Finally, let the developer do the job required.

Answer 3

Is there any open source cms that you are comfortable using and fits your website needs? If yes, then tell your programmer to use it for your website, If none, then let your developer create a custom CMS that will fit your needs.

If you choose your developer to develop a custom CMS for you, do not pay until you have tested it to be bug free.

To develop a custom CMS is very time consuming, requires planning and hardwork, etc.. You are lucky if he is offering you to develop a custom CMS for you. Most web designers just use open source CMS that doesn't even fit your needs, and place copyright notices on your website. Then everybody knows what you are using... lol.

Answer 4

If the CMS is correct, why not?
Pre existing CMS, like wordpress generally have quite a bit of "features" that you will be unlikely to ever use. If you have a custom built CMS then it will be customized for your needs, easier to load etc etc.

So yes, it's not a bad idea. Then again like ^ said, he might leave backdoors for himself... but this is all a question of how much you trust said person.

Answer 5

He might want to use his own CMS because hes more comfortable with it, but on the other hand, your completely dependent on him if things go wrong.

I would be personaly use Joomla, its free, easy to set up (if you have the right host) and you can do it yourself with little experience. Theres tons of free add-ons and resources for it, I use it all the time for work.

I have nothing but respect for people who can create there own CMS, but very often, they charge the earth for it.

Did you agree on something beforehand? gave him a brief of what you want the site to do? arrange a price?

Obviously if hes developing the site with his own CMS, it might take you longer to get the site 'live'.