With many companies moving their financial management to the cloud, there are many questions around what the cloud solutions cost and how they are 'priced' compared to traditional on-premise solutions. To add to the confusion, legacy vendors are getting creative on how to keep their customers on their existing system or sole source convert them to their 'cloud' application. This article de-mystifies that process. Credit: Thinkstock The majority of net new financial system implementations today are cloud or Software-as-a-Service (SaaS) financial management solutions. Organizations either outgrew their existing on-premise solution, realized that another upgrade was risky with little benefit and a lot of cost, or have recognized that modern cloud solutions offer many benefits over their existing inflexible 1990s era system. As executives look to the cloud, they are being bombarded with mixed messages about how much these applications will cost. This is especially true with vendors who have an existing on-premise or hosted solution. They are offering “cloud” solutions that typically entail putting their on-premise application “in the cloud” and offering it to you as a single tenant solution. Although “cloud-like,” there are many differences between single tenant and multi-tenant cloud. There is an easy way to tell the difference as outlined in this post. These vendors are desperately trying to protect their revenue stream, so they offer their existing customers either: A low initial subscription cost. They can make the subscription cost very low. However, this pricing is typically only for a short period of time. They want to play the “long game” knowing that most companies will stick with their financial system for 10+ years. They will raise subscription costs over time to match or exceed market rates. A low total cost of entry. They can discount the implementation fees. Why would they do this? They do it because the long term revenue stream that they will receive over time will far outweigh the one-time implementation costs they absorb. You should always remember that you do not get something for nothing. You will pay for it in the out years. Cloud credits. They may offer cloud credits, which are a percentage of your existing maintenance fees that can be applied for future cloud subscription costs. This is a great strategy for these vendors. They defend their maintenance revenue, while at the same time making you biased in the long run to their solution – even if it’s not the right solution for you. The end result of these pricing strategies is that vendors are using their existing revenue streams to freeze out possible competition. For the CFOs and CIOs that need to look for a solution that will meet their needs over decades, they will want more choices, not less. A strategy that CFOs and CIOs should deploy is to look at all of the market leaders. It may be that their existing vendor (along with the above pricing “incentives”) is indeed offering the best solution for them. However, they would be doing their company a disservice by not assessing all of their options. Therefore, CFOs and CIOs should select a solution based on the answers to these six questions: Which vendor offers the best technical architecture? Which vendor has the best solution now and the best long-term product roadmap that meets my needs? What solution offers the best Total Cost of Ownership (vs. just the Cost of Entry/Implementation) over a five to ten year period? Which vendor’s culture and customer service approach will provide me the best value over time? Which vendor can provide references from existing customers about their product and their experience of working with such vendor? What has my experience been with my existing vendor? The reality is that the new solution you choose is a long-term commitment, similar to a marriage. You need to be with that company and product (or spouse!) for a long time. You want someone that can grow with you and be by your side during the good and bad times. Don’t make this long-term commitment without playing the field and finding the right match for you. Related content opinion How IT can help your accounting function prepare for rev rec Accounting standard ASC606 is a notable change to the way revenue is recognized and reported from contracts. Organizations have mostly managed to track and analyze revenue from contracts using a myriad of tools (spreadsheets!), and subsequently enter By John Hoebler Sep 25, 2017 3 mins CIO ERP Systems IT Strategy opinion Can your rev rec software support these complex challenges? A look at some of the more complicated aspects of ASC 606 that your software should ideally accommodate. By John Hoebler Sep 22, 2017 3 mins BPM Systems IT Governance Enterprise Applications opinion What to look for in a tech solution for revenue recognition In my last post, I discussed many of the key challenges in accounting for revenue under ASC 606. I also proposed the idea that an automated revenue recognition solution may be warranted for your organization, depending on the volume and complexity o By John Hoebler Aug 25, 2017 4 mins IT Governance IT Leadership opinion 3 ways that revenue recognition will impact IT A new five-step model will replace more than 150 pieces of guidance on recognizing revenue and consistently apply the same approach across industries, eliminating specialized industry rules. By John Hoebler Aug 09, 2017 4 mins Technology Industry IT Governance System Management Podcasts Videos Resources Events SUBSCRIBE TO OUR NEWSLETTER From our editors straight to your inbox Get started by entering your email address below. Please enter a valid email address Subscribe