<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>WebWorks &#187; ROI</title>
	<atom:link href="http://blogs.webworks.com/blog/category/roi/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.webworks.com</link>
	<description>Publishing to the Metaverse...</description>
	<lastBuildDate>Tue, 13 Jul 2010 19:57:35 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>It saves you how much?!!</title>
		<link>http://blogs.webworks.com/aporter/2008/08/29/it-saves-you-how-much/</link>
		<comments>http://blogs.webworks.com/aporter/2008/08/29/it-saves-you-how-much/#comments</comments>
		<pubDate>Fri, 29 Aug 2008 15:38:50 +0000</pubDate>
		<dc:creator>aporter</dc:creator>
				<category><![CDATA[DITA]]></category>
		<category><![CDATA[ROI]]></category>
		<category><![CDATA[ePublisher]]></category>

		<guid isPermaLink="false">5.4</guid>
		<description><![CDATA[Back in March I posted a short note about the white paper I’d written comparing the true long term costs of using the “free” DITA Open Tool Kit to publish your DITA content, against using a productized commercial solution, like ePublisher.
As a follow up to that paper I sat down and created a ROI (return [...]]]></description>
			<content:encoded><![CDATA[<p>Back in March I posted a short note about the white paper I’d written comparing the true long term costs of using the “free” DITA Open Tool Kit to <strong>publish your DITA</strong> content, against using a productized commercial solution, like ePublisher.</p>
<p>As a follow up to that paper I sat down and created a ROI (return on investment) tool that would allow someone to take the concepts I’d outlined in the white paper and apply some actual numbers to it. Of course the numbers I used were estimates derived from a combination of research and educated guesses based on my industry experience.</p>
<p>A few days ago one of our customers took the spreadsheet I’d developed and instead of using my estimated figures plugged his own actual figures in to it.</p>
<p>The results were staggering.</p>
<p>In summary for his twenty five writer technical publications shop</p>
<p><strong>The actual cost</strong> to his organization (when you factored in purchase prices, training costs and time spent) <strong>in implementing and rolling out a DITA publishing solution</strong> using either the DITA-OTK or ePublisher were almost equal. In fact the actual difference was that ePublisher was 0.1 % more expensive.</p>
<p>Our contention has always been that the real savings in using ePublisher over the DITA-OTK is the <strong>long term costs of implementing changes and rolling those changes out</strong>. This customers figures did more than just confirm that – they gave results that we hadn’t even dreamed of.</p>
<p>For this particular customer, he calculated that every time they made a change to a publication design, or template, and rolled it out to all twenty-five writers it would cost them just over $3,000.</p>
<p>Making the same change and rolling it out using ePublisher – the cost would be under $30 !</p>
<p>A 100 fold reduction in cost for each change.</p>
<p>It doesn’t matter how much we as a company, or a marketing team, say that buying and implementing ePublisher is a more cost effective enterprise publishing solution than using the “free” DITA OTK, it only really has meaning when a customer proves it – and this customer has more than proved it.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.webworks.com/aporter/2008/08/29/it-saves-you-how-much/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
