proprietary CMS
-
One of our clients I work for decided to go for proprietary CMS and get rid of the bespoke CMS solution that worked from last 5 years. But they are now struggling as for each small custom change, the company is asking for money and lot of money. Our existing system also talks to various 3rd party API's and also our apps talks to our API etc. So all this communication needs to be moved over to new proprietary CMS solution. This again will cost them bomb. Now in order to save them some money, I am wondering if somehow we get the users data of the proprietary CMS API on a regular basis (If it can be done on real time, it will be even better) and update our DB. If we can do this autonomously, we will not have to move all other 3rd party integration to this new proprietary CMS solution. Note: I am assuming, that this new CMS API will provide access to the user data which we can export or can autonomously upload to our db. It would be good to know your views on this situation. Has anyone of you experienced something similar and does it makes sense or even possible to get the user data in real time. Thanks
-
pwasser wrote:
I'd love to know how they (your client) decided to go down this path without apparently considering all of the consequences.
You don't expect customers to consider the consequences! It's your job to consider the consequences and tell them why their crazy idea won't work. It's their job to ignore you and do it anyway, and then blame you when it doesn't work. :-D
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
pwasser wrote:
I'd love to know how they (your client) decided to go down this path without apparently considering all of the consequences.
You don't expect customers to consider the consequences! It's your job to consider the consequences and tell them why their crazy idea won't work. It's their job to ignore you and do it anyway, and then blame you when it doesn't work. :-D
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Richard Deeming wrote:
You don't expect customers to consider the consequences!It's your job to consider the consequences and tell them why their crazy idea won't work.It's their job to ignore you and do it anyway, and then blame you when it doesn't work
This is exactly what happened. Obviously, they haven't reached the blaming stage yet. Few key employees left the company due to this decision.
-
One of our clients I work for decided to go for proprietary CMS and get rid of the bespoke CMS solution that worked from last 5 years. But they are now struggling as for each small custom change, the company is asking for money and lot of money. Our existing system also talks to various 3rd party API's and also our apps talks to our API etc. So all this communication needs to be moved over to new proprietary CMS solution. This again will cost them bomb. Now in order to save them some money, I am wondering if somehow we get the users data of the proprietary CMS API on a regular basis (If it can be done on real time, it will be even better) and update our DB. If we can do this autonomously, we will not have to move all other 3rd party integration to this new proprietary CMS solution. Note: I am assuming, that this new CMS API will provide access to the user data which we can export or can autonomously upload to our db. It would be good to know your views on this situation. Has anyone of you experienced something similar and does it makes sense or even possible to get the user data in real time. Thanks
Unfortunately, the decision to go with this CMS or that one is largely based on emotion in the sales and marketing group. So companies suffer. Mostly IT.
-
This won't help you much. I'd love to know how they (your client) decided to go down this path without apparently considering all of the consequences. Surely your access to your client's user data which is now in the hands of a third party (ha ha) depends entirely on the deal you are able to cut with this third party. The fact that the client has allowed their own data to be locked up in this way seems almost bizarre - perhaps I am misunderstanding something.
Peter Wasser "The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." - Bertrand Russell
pwasser wrote:
I'd love to know how they (your client) decided to go down this path without apparently considering all of the consequences.
They were looking for a quick win solution and obviously ignored what technical guys suggested i.e. to go open source CMS route rather than proprietary solution. Few left the company due to this decision. They were just looking at the outer picture.
-
Sounds like they chose the wrong CMS. If customisation is a priority they should have gone with one that supports your own custom modules\plug-ins etc so that the in-house devs can take care of that rather than paying the CMS company to do these things.
-
Richard Deeming wrote:
You don't expect customers to consider the consequences!It's your job to consider the consequences and tell them why their crazy idea won't work.It's their job to ignore you and do it anyway, and then blame you when it doesn't work
This is exactly what happened. Obviously, they haven't reached the blaming stage yet. Few key employees left the company due to this decision.
cp-andy wrote:
Few key employees left the company due to this decision.
I do not envy you. This does not sound like a good culture: "We f*** it you fix it".
Peter Wasser "The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." - Bertrand Russell
-
cp-andy wrote:
Few key employees left the company due to this decision.
I do not envy you. This does not sound like a good culture: "We f*** it you fix it".
Peter Wasser "The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." - Bertrand Russell
There is only one criterion, "Is it cheaper in the short term?"
We're philosophical about power outages here. A.C. come, A.C. go.
-
One of our clients I work for decided to go for proprietary CMS and get rid of the bespoke CMS solution that worked from last 5 years. But they are now struggling as for each small custom change, the company is asking for money and lot of money. Our existing system also talks to various 3rd party API's and also our apps talks to our API etc. So all this communication needs to be moved over to new proprietary CMS solution. This again will cost them bomb. Now in order to save them some money, I am wondering if somehow we get the users data of the proprietary CMS API on a regular basis (If it can be done on real time, it will be even better) and update our DB. If we can do this autonomously, we will not have to move all other 3rd party integration to this new proprietary CMS solution. Note: I am assuming, that this new CMS API will provide access to the user data which we can export or can autonomously upload to our db. It would be good to know your views on this situation. Has anyone of you experienced something similar and does it makes sense or even possible to get the user data in real time. Thanks
-
One of our clients I work for decided to go for proprietary CMS and get rid of the bespoke CMS solution that worked from last 5 years. But they are now struggling as for each small custom change, the company is asking for money and lot of money. Our existing system also talks to various 3rd party API's and also our apps talks to our API etc. So all this communication needs to be moved over to new proprietary CMS solution. This again will cost them bomb. Now in order to save them some money, I am wondering if somehow we get the users data of the proprietary CMS API on a regular basis (If it can be done on real time, it will be even better) and update our DB. If we can do this autonomously, we will not have to move all other 3rd party integration to this new proprietary CMS solution. Note: I am assuming, that this new CMS API will provide access to the user data which we can export or can autonomously upload to our db. It would be good to know your views on this situation. Has anyone of you experienced something similar and does it makes sense or even possible to get the user data in real time. Thanks
-
One of our clients I work for decided to go for proprietary CMS and get rid of the bespoke CMS solution that worked from last 5 years. But they are now struggling as for each small custom change, the company is asking for money and lot of money. Our existing system also talks to various 3rd party API's and also our apps talks to our API etc. So all this communication needs to be moved over to new proprietary CMS solution. This again will cost them bomb. Now in order to save them some money, I am wondering if somehow we get the users data of the proprietary CMS API on a regular basis (If it can be done on real time, it will be even better) and update our DB. If we can do this autonomously, we will not have to move all other 3rd party integration to this new proprietary CMS solution. Note: I am assuming, that this new CMS API will provide access to the user data which we can export or can autonomously upload to our db. It would be good to know your views on this situation. Has anyone of you experienced something similar and does it makes sense or even possible to get the user data in real time. Thanks
Based on reading many of the threads... Make a complete list of everything they need addressed, specifically that they are not thinking of. Using the current pricing/quotes they are getting, calculate out the cost. Build a spreadsheet. Next, compare that cost to going back, and adding what was missing. The problem with cheaper in the short run, is that the long run ALWAYS catches up. We have a client who gladly made that move. They have been waiting OVER 1 YEAR on a change. In the past, their slowest changes were a couple of months. And, in the long run, it will cost more, but "do more". But this ultra slow timeframe to get things done is crazy. It takes a MONTH just to get a quote on a change. LOL. Unless we provide the sourcecode for the change, we cannot get it in under 3 months. And even then 3 is typical! The challenge you face is this: If they don't choose quickly, they will NEVER switch back/away because of not understanding sunk costs. The people who left were probably smart (consider that), and the company could possibly end up out of business. And yes, I have seen that happen. I was 20 when I threw away a newly designed (and quite buggy) system, and rewrote it from scratch. I did it on my own time, after hours, knowing it would be a huge success. It was. On every metric. And in the end, I was ALMOST PUNISHED (certainly chided) for throwing away an "asset" they felt had value, and not starting with that. (I claimed I started with that as the wrong approach, and it helped me design a better approach. Luckily they bought it). But it was obvious to me. When you find yourself in a whole. STOP DIGGING! LOL
-
One of our clients I work for decided to go for proprietary CMS and get rid of the bespoke CMS solution that worked from last 5 years. But they are now struggling as for each small custom change, the company is asking for money and lot of money. Our existing system also talks to various 3rd party API's and also our apps talks to our API etc. So all this communication needs to be moved over to new proprietary CMS solution. This again will cost them bomb. Now in order to save them some money, I am wondering if somehow we get the users data of the proprietary CMS API on a regular basis (If it can be done on real time, it will be even better) and update our DB. If we can do this autonomously, we will not have to move all other 3rd party integration to this new proprietary CMS solution. Note: I am assuming, that this new CMS API will provide access to the user data which we can export or can autonomously upload to our db. It would be good to know your views on this situation. Has anyone of you experienced something similar and does it makes sense or even possible to get the user data in real time. Thanks
