How we lost a customer

[crnogorac081]

I belive that was an excuse to decline your offer. For many years in my experience, it doesnt matter which CMS you are using as long as you know it in bits. Most glitches and vulnerabilities are not explained and are ony possible to be doen by extreme well know WB user or developer, so I wouldnt worry about security.

And finaly, people are affraid from what they cant understand .

cheers

[okki]

Hello all, I wanted to post a little story on how we lost a big, long term customer after they got to know WB a little better.

One of our clients is a fairly large company, for which we have maintained their website for many years. We are using WB as the "engine" for the whole site with several modules that we have custom made for them. Now they wanted (us) to update their website (new design, content etc.) and naturally we offered them a quote with all the specifications, for example how the site would still be based on WebsiteBaker CMS.

Next, their IT department stepped in and checked out WebsiteBaker.org, Googled up some information and found out about the recent vulnerabilities that are fixed in SP6 RC3.19. They made a summary of their findings for the marketing managers, in which they wrote about the vulnerabilities and how they are fixed in the latest service pack but they were unable to find it anywhere on the download section. The latest version available for download is SP5 (dated Dec 2015) which contains the vulnerabilities. Among some other statements they also wrote that the site Wesbitebaker.org seems vague and does not create a strong sense of trust that they require for future development and would not recommend WB as the CMS for their new site.

Based on those statements the managers rejected our offer and proposition for the CMS and wanted to terminate our cooperation that lasted over six years.

Sadly, I have to agree with them with some extent, although I didn't like how they ignored my comments that I told them (many years of experience with WB and its updates, strengthening security, core functions etc.).  We will still be using WB for other customer projects, but I am a little bit worried about the future because people are becoming more tech-conscious on these matters.