Read time

5 Common End-User Questions for ISVs

By Rob Waggoner

Curious about how the cloud and Independent Software Vendors (ISVs) go together? Here are 5 common end-users questions for ISVs.

1. If you build a solution, why should I go to the cloud to use it instead of installing it locally? 
Usually customers struggle with installation problems while installing new software. Does it have additional security requirements, or does it make inaccurate assumptions about a customer’s infrastructure? Do you have all the pre-requisites like the appropriate database servers and versions? The great part about leveraging the cloud for ISV-based applications is that you can use the application, without the overhead of installation, updates and troubleshooting. The ISV can provide credentials so you can access the application from anywhere you want to work. 

2. Where is my data stored? 
Depending on how the actual application is built, the data can be stored in the cloud, or stored on your local computer. There are advantages and disadvantages to both options, but generally, your data will be stored within the same Azure Region as the application you are using. For location specific data concerns, please open a dialog with your ISV so you understand where your data resides while respecting any data sovereignty concerns you may have. 

3. It’s all about the customer.  
An ISV is focused on delivering new solutions to the customer. But, typically the ISV spends as much, if not more time integrating their applications into the customer's environment than they do with the development of the productThink of the security policies of your company that truly have nothing to do with the actual application but are required to operate in your infrastructure. By putting the application in the cloud, the ISV can quickly update their product without requiring updates to the customers infrastructure and make it easier to provide technical support and troubleshooting assistance since the ISV also has access to the cloud infrastructure.  

 4. What if I don’t want to move to the newest version of the ISVs application? 
This is not a unique question, it is one that even Microsoft has had to deal with when it comes to Office 365. Microsoft defines a timeframe when a customer can remain on the older version of Office, even after the newest version has been released. The great part of the cloud for an ISV is that they are usually able to publish multiple versions of their application, so customers can test the newer version before migrating all their data to the newer version.   

5. Will the cloud version of the application cost more than the on-premises version? 
The goal of the cloud is to reduce the overall cost of your IT infrastructure. Companies have already realized these cost savings when they consider all of costs of a cloud infrastructure.  Think of the electricity costs for powering and cooling your infrastructure. Think of the traditional hardware demands of each application, do you have to traditionally upgrade your hardware just to upgrade the software? In the cloud, you eliminate these infrastructure costs, including paying for the staff to manage the hardware. When you factor in all your infrastructure costs, including additional servers, like database servers, moving to the cloud will reduce your overall costs.  

Want to Learn How to Modernize Legacy Apps?
Download the Ebook

Tags: Independent Software Vendor

azure cost optimization

Related Articles

3 ISV Strategies for User Growth

Curious about how the cloud and Independent Software Vendors (ISVs) go together? Here are 5 common end-users questions for ISVs.


Topics: Independent Software Vendor

3 Keys to Building an ISV Partner Channel in 2019

Curious about how the cloud and Independent Software Vendors (ISVs) go together? Here are 5 common end-users questions for ISVs.


Topics: Independent Software Vendor

7 Common Cloud Questions & Answers for ISVs

Curious about how the cloud and Independent Software Vendors (ISVs) go together? Here are 5 common end-users questions for ISVs.


Topics: Independent Software Vendor