<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: SaaS is about results</title>
	<atom:link href="http://www.successfactors.com/blogs/business-execution/saas-is-about-results/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.successfactors.com/blogs/business-execution/saas-is-about-results/</link>
	<description>Execution is the Difference.</description>
	<lastBuildDate>Thu, 04 Feb 2010 07:42:47 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Sarfy, Business Development Analyst</title>
		<link>http://www.successfactors.com/blogs/business-execution/saas-is-about-results/comment-page-1/#comment-165</link>
		<dc:creator>Sarfy, Business Development Analyst</dc:creator>
		<pubDate>Tue, 04 Jul 2006 11:53:00 +0000</pubDate>
		<guid isPermaLink="false">http://10.50.0.97/wordpress/workforce-performance/index.php/saas-is-about-results/#comment-165</guid>
		<description>Given the fact that service models out of cost-effective offshore locations (like India) are thriving, and with my fair share of experience in selling web-based IT products, I believe that the pay-as-you-proceed SaaS is here to stay.

It works well when customers don&#039;t have to commit long-term and service provision becomes mere needs-based.

Packaged versions come with its own drawbacks - scalability, fexibility, customization and so and so forth.

For instance, a company like ours provides everything &#039;custom&#039;. Our skills assessment content for various job roles and verticals are custom-and-needs-based written plus our web-hosted SaaS offerings comes with fexible on-demand customizations - all at a fraction of the cost of conventional onshore offerings.

As a typical B-school text book might say... &quot;It&#039;s all about money!&quot;</description>
		<content:encoded><![CDATA[<p>Given the fact that service models out of cost-effective offshore locations (like India) are thriving, and with my fair share of experience in selling web-based IT products, I believe that the pay-as-you-proceed SaaS is here to stay.</p>
<p>It works well when customers don&#8217;t have to commit long-term and service provision becomes mere needs-based.</p>
<p>Packaged versions come with its own drawbacks &#8211; scalability, fexibility, customization and so and so forth.</p>
<p>For instance, a company like ours provides everything &#8216;custom&#8217;. Our skills assessment content for various job roles and verticals are custom-and-needs-based written plus our web-hosted SaaS offerings comes with fexible on-demand customizations &#8211; all at a fraction of the cost of conventional onshore offerings.</p>
<p>As a typical B-school text book might say&#8230; &#8220;It&#8217;s all about money!&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron Woerner</title>
		<link>http://www.successfactors.com/blogs/business-execution/saas-is-about-results/comment-page-1/#comment-164</link>
		<dc:creator>Ron Woerner</dc:creator>
		<pubDate>Tue, 27 Jun 2006 21:37:09 +0000</pubDate>
		<guid isPermaLink="false">http://10.50.0.97/wordpress/workforce-performance/index.php/saas-is-about-results/#comment-164</guid>
		<description>You&#039;re missing a key factor: TRUST.  With the SaaS model, you are completely trusting the vendor.  An inherent business need that is often unspoken is &quot;do we trust the application and the service provider to maintain the confidentially, integrity, and availability of the data.&quot;  Once that trust is broken, it&#039;s almost impossible to get back.
Using your car analogy: Today, it&#039;s easy to trust Car Manufacturers; they publically announce recalls, they have local representatives, you have recourse should you encounter a problem, etc.
With SaaS vendors, that&#039;s not always true. (Note: this is not a reflection of SuccessFactors, but SaaS vendors in general.) The vendor may have no track record of announcing and fixing vulnerabilties.  They may not have been in business very long.  There may be no one who will listen to or address problems.  There&#039;s no one local that you can talk to.
Now I&#039;m not saying that you shouldn&#039;t use SaaS vendors. If the tool fits, use it.  You need to look at the whole picture, the business&#039; needs, and the capabilities of IT. Understand the risks of the approach and choose the best tool to fit the need.</description>
		<content:encoded><![CDATA[<p>You&#8217;re missing a key factor: TRUST.  With the SaaS model, you are completely trusting the vendor.  An inherent business need that is often unspoken is &#8220;do we trust the application and the service provider to maintain the confidentially, integrity, and availability of the data.&#8221;  Once that trust is broken, it&#8217;s almost impossible to get back.<br />
Using your car analogy: Today, it&#8217;s easy to trust Car Manufacturers; they publically announce recalls, they have local representatives, you have recourse should you encounter a problem, etc.<br />
With SaaS vendors, that&#8217;s not always true. (Note: this is not a reflection of SuccessFactors, but SaaS vendors in general.) The vendor may have no track record of announcing and fixing vulnerabilties.  They may not have been in business very long.  There may be no one who will listen to or address problems.  There&#8217;s no one local that you can talk to.<br />
Now I&#8217;m not saying that you shouldn&#8217;t use SaaS vendors. If the tool fits, use it.  You need to look at the whole picture, the business&#8217; needs, and the capabilities of IT. Understand the risks of the approach and choose the best tool to fit the need.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
