https://effectivedatabase.com/when-vendors-go-bad/ Making data management a revenue generator Tue, 28 Apr 2020 19:43:11 +0000 hourly 1 https://effectivedatabase.com/when-vendors-go-bad/#comment-1002 Thu, 19 Mar 2009 17:40:41 +0000 http://effectivedatabase.com/?p=397#comment-1002 Great thoughts from both Rob and Mike. If a vendor balks at discussing long-term continuity, that may be a red-flag.

]]> https://effectivedatabase.com/when-vendors-go-bad/#comment-1001 Thu, 19 Mar 2009 17:36:05 +0000 http://effectivedatabase.com/?p=397#comment-1001 I would like to reinforce the importance of keeping your “Plan B” up to date. For Saas, your “Plan B” can easily be facilitated as an extension of your disaster recovery plan. Your vendor should provide you with supplementary hosting options that will provide months (years?) of uninterrupted continuity while you search for your next AMS system and/or provider.

]]> https://effectivedatabase.com/when-vendors-go-bad/#comment-1000 Fri, 13 Mar 2009 13:33:44 +0000 http://effectivedatabase.com/?p=397#comment-1000 I want to make one suggestion to help mitigate this issue. If you are engaged in the purchase process, you should request that your vendor provide you audited financials from the most recent reporting period and year-to-date unaudited financials. In addition, I think it is reasonable to occasionally ask your vendor to provide updated financials as the length of your relationship continues – especially if you are prepared to further invest in the company. This will not protect you from all the unexpected issues, but you may be able to identify a pattern early giving you more time to plan.

]]>