<?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: Kathmandu Picks iD Over SharePoint</title>
	<atom:link href="http://www.intranetdashboard.com/blog/2009/client_stories/kathmandu-picks-intranet-dashboard-over-sharepoint/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.intranetdashboard.com/blog/2009/client_stories/kathmandu-picks-intranet-dashboard-over-sharepoint/</link>
	<description>Hints, Tips, and things you should know about Intranet DASHBOARD</description>
	<lastBuildDate>Wed, 04 Aug 2010 21:40:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Dave Bartlett</title>
		<link>http://www.intranetdashboard.com/blog/2009/client_stories/kathmandu-picks-intranet-dashboard-over-sharepoint/comment-page-1/#comment-40</link>
		<dc:creator>Dave Bartlett</dc:creator>
		<pubDate>Wed, 04 Aug 2010 21:40:39 +0000</pubDate>
		<guid isPermaLink="false">/blog/?p=262#comment-40</guid>
		<description>Its interesting to see how the subscription (per user) pricing model of iD stacks up against the &#039;big up front&#039; costs of the likes of SharePoint etc. I think the per user pricing model is just what we need in times of budget tightening, and Kathmandu has certainly figured out the savings it offers them compared to the big, complex,  solutions like SharePoint.</description>
		<content:encoded><![CDATA[<p>Its interesting to see how the subscription (per user) pricing model of iD stacks up against the &#8216;big up front&#8217; costs of the likes of SharePoint etc. I think the per user pricing model is just what we need in times of budget tightening, and Kathmandu has certainly figured out the savings it offers them compared to the big, complex,  solutions like SharePoint.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

