Part 1 of this blog series depicted the three evolutionary phases (or waves) of software as a service (SaaS) and cloud computing adoption. The article ended with some glimpses into the future and likely implications for SaaS users.

Part 2 explores the apparent opportunities and accompanying challenges (and inevitable soul-searching exercises) that SaaS aspirants face in their endeavors. Some concrete examples of vendors and their new strategies and solutions will be presented. Read the rest of this entry »

The first part (Part II) of this blog series described the opportunities for software as a service (SaaS) or on-demand applications, especially in the current difficult economic milieu. Part IIa then analyzed the top five SaaS assumptions (misconceptions) recently outlined by Gartner.

Before any vendor can embark onto delivering a SaaS offering, it must thoroughly consider a number of harrowing SaaS technology choices and their implications. Thus, Part IIa also analyzed the decision’s impact on the functional footprint (scope) of the future SaaS product, after which the aspiring SaaS vendor must identify gaps within its in-house skill sets and define how to fill them.

This part continues with the other major remaining technical considerations before any vendor can embark on delivery of a SaaS offering. Read the rest of this entry »

Wow, how time flies and how many things have happened in the market these days to distract a market observer! Namely, only over a year after my SaaSy Discusions (Part I) and SaaSy Discussions (Part Ia) blog series, some time has at last become available for more discussions on the intriguing topic of software as a service (SaaS).

The title of this SaaSy discussions series might be somewhat deceiving, since the question might no longer be whether to go for SaaS or the on-demand computing deployment mode, but rather how to go about it for both vendors and users. Indeed, the current tough economic situation certainly has something to do with making this “go on-demand” decision a bit easier for both software providers and users. Read the rest of this entry »

Part I of this blog post introduced the common software deployment models and Consona CRM’s approach in that regard. To the end of enabling Total Customer Management (TCM) via an adaptive CRM offering, Consona CRM is built with a superior core infrastructure (customer data model, BPM, BI, SOA) and a holistic, best-of-breed product portfolio.

Consona claims to be one of the market’s rare CRM offerings that is both operational and collaborative, with many years of a broad range of consulting, technical, and business process services that have created the related methodology and blueprint.

Consona CRM Portfolio

The vendor believes that it offers the best value for price in the market due to the extensive product’s flexibility and adaptability, ease of customization, configuration, integration and upgrades, and due to the depth of the product’s extensibility.

These capabilities come from the combination of Onyx Adaptive CRM (i.e., BPM, BI, SFA, customer service, customer data management and customer data integration [CDI]), KNOVA (i.e., self-service and knowledge management [KM]) and the partnership with Million Handshakes (part of Portrait Software) for marketing automation. Read the rest of this entry »

Much has been said and written lately, on TEC’s web site as well as on many other peer sites, about the on-demand deployment model, especially about multi-tenant software as a service (SaaS). The opinions there have ranged from an absolute infatuation with the “technology of the 22nd century” or so (thereby rendering the traditional on-premise model completely passe) to much more reserved and cautious stances.

My idea here is to start with a series of blog posts discussing the various quandaries about these subtle (or not) technology choices and nuances, and to also give many protagonists in the market a chance to voice their opinions too.

Today’s topic is sort of “Which model will win at the end of the day, if any?” In my opinion, co-existence of the two deployment models will continue for quite some time to come, since each has its advantages for certain situations. Anyone who thinks one model will dominate for every possible use of software is just not an enterprise software connoisseur, is not a serious person, or is just an aggressive salesperson. Read the rest of this entry »