Comparing on-demand CRM and on-premise CRM fees, architecture, functionality

Comparing on-demand CRM and on-premise CRM fees, architecture, functionality

What are the main differences between on-demand CRM and on-premise CRM ?

    Requires Free Membership to View

    Login

    When you register, you'll begin receiving targeted emails from my team of award-winning editorial writers on the latest customer relationship management (CRM)and call center technology issues today. Our goal is to keep you informed on the hottest issues facing this fast-changing industry.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchCRM.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchCRM.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

The differences between on-demand CRM and on-premise are substantial. They are architecturally different, with on-demand CRM being constructed around what is called a multitenant architecture – meaning many clients can run off of a single instance of the applications/services that reside on a server at a remote site. On-demand applications are ordinarily accessed via the Web. Alternatively, the on-premise versions are each a separate version that resides on a server that sits behind the firewall of a company. The CRM application there is ordinarily accessed via the desktop or some remote connection to the desktop.

The on-demand business model is hosted, meaning that the CRM provider is not the company that is using the application, but another company that is assuming the overhead: the server maintenance, the data maintenance and the costs associated with that. The way that a company pays for on-demand CRM is usually through a per-user monthly subscription fee. Oftentimes there are costs associated with start up of the application or the customization required, but the maintenance costs are built into the subscription fee. Alternatively, the on-premise model includes a license fee that pays for the installation and implementation of the software and the hardware that it needs to run. There are usually service fees associated with the implementation. The license to use the software is also often priced per user or by server or by flat fees.

The features and functions are pretty much the same in each, for example, whether it's on-demand or on-premise, the sales functionality is still the same. The on-demand model has gained huge ground over the past few years and only the most complex implementations aren't likely to benefit from going on-demand rather than on-premise.

This was first published in February 2007