<?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>Time Tracking with Chrometa &#187; Software Business</title>
	<atom:link href="http://www.chrometa.com/blog/category/software-business/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.chrometa.com/blog</link>
	<description>Official Chrometa Blog</description>
	<lastBuildDate>Tue, 31 Aug 2010 15:00:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Why Aspiring Entrepreneurs Should Stop Planning and Start Doing</title>
		<link>http://www.chrometa.com/blog/entrepreneur-stop-planning-start-doing/</link>
		<comments>http://www.chrometa.com/blog/entrepreneur-stop-planning-start-doing/#comments</comments>
		<pubDate>Thu, 18 Feb 2010 22:43:39 +0000</pubDate>
		<dc:creator>Brett Owens</dc:creator>
				<category><![CDATA[Entrepreneurship]]></category>
		<category><![CDATA[Software Business]]></category>
		<category><![CDATA[Starting a Company]]></category>
		<category><![CDATA[time tracking software]]></category>

		<guid isPermaLink="false">http://www.chrometa.com/blog/?p=177</guid>
		<description><![CDATA[My good friend Adam Kalsey &#8211; Founder of many successful enterprises, including IMified (acquired last year by Voxeo) and SacStarts (Sacramento&#8217;s Startup Network) &#8211; dishes out some refreshing advice for new entrepreneurs over at the SacStarts blog:

I talk to a great many erstwhile entrepreneurs that tell me all about their ideas and all the things [...]]]></description>
			<content:encoded><![CDATA[<p>My good friend <a href="http://kalsey.com/blog/">Adam Kalsey</a> &#8211; Founder of many successful enterprises, including <a href="http://www.imified.com/">IMified </a>(acquired last year by Voxeo) and <a href="http://sacstarts.com/">SacStarts </a>(Sacramento&#8217;s Startup Network) &#8211; dishes out some refreshing advice for new entrepreneurs over at the <a href="http://sacstarts.com/2010/02/13/advice-new-entrepreneur">SacStarts blog</a>:</p>
<blockquote>
<p style="margin-top: 0px; margin-right: 0px; margin-bottom: 1.5em; margin-left: 0px; font-weight: inherit; font-style: inherit; font-size: 12px; font-family: inherit; vertical-align: baseline; padding: 0px; border: 0px initial initial;">I talk to a great many erstwhile entrepreneurs that tell me all about their ideas and all the things that they’re going to do when they start their company. Or people who have started but aren’t really getting anything done because they can’t find the right co-founder or they need to design every last detail first, or they don’t have the marketing copy for their web site quite right yet.</p>
<p style="margin-top: 0px; margin-right: 0px; margin-bottom: 1.5em; margin-left: 0px; font-weight: inherit; font-style: inherit; font-size: 12px; font-family: inherit; vertical-align: baseline; padding: 0px; border: 0px initial initial;">Entrepreneurs do. We take an idea and a market and drive to make it happen. Figure out what’s standing in the way of you getting stuff done and just go through it. Once you’re actually building your company, a lot of those things that looked insurmountable turn out to be no problem at all.</p>
</blockquote>
<p style="margin-top: 0px; margin-right: 0px; margin-bottom: 1.5em; margin-left: 0px; font-weight: inherit; font-style: inherit; font-size: 12px; font-family: inherit; vertical-align: baseline; padding: 0px; border: 0px initial initial;">These are two paragraphs that any aspiring entrepreneur should read over and over again &#8211; this is the essence of why so many wannabe companies never get off the ground.  And why so many wannabe entrepreneurs are forever waiting for the stars to align for them to go whole hog after their vision.</p>
<p style="margin-top: 0px; margin-right: 0px; margin-bottom: 1.5em; margin-left: 0px; font-weight: inherit; font-style: inherit; font-size: 12px; font-family: inherit; vertical-align: baseline; padding: 0px; border: 0px initial initial;">Here&#8217;s an unfortunate fact of life: The stars will <em>never </em>align.  So if you&#8217;re waiting around for a few things to &#8220;fall into place&#8221;, you&#8217;re wasting time.  Just get started and get after it.</p>
<p style="margin-top: 0px; margin-right: 0px; margin-bottom: 1.5em; margin-left: 0px; font-weight: inherit; font-style: inherit; font-size: 12px; font-family: inherit; vertical-align: baseline; padding: 0px; border: 0px initial initial;">As Adam mentions, most problems you&#8217;re planning for right now will never come to fruition.  At least 95% of your planning time and energy is likely being wasted.</p>
<p style="margin-top: 0px; margin-right: 0px; margin-bottom: 1.5em; margin-left: 0px; font-weight: inherit; font-style: inherit; font-size: 12px; font-family: inherit; vertical-align: baseline; padding: 0px; border: 0px initial initial;">On the flip side, there are obstacles that you&#8217;ll <em>never </em>anticipate until you start off on your journey.  That&#8217;s OK &#8211; you&#8217;ll deal with them as they come.</p>
<p style="margin-top: 0px; margin-right: 0px; margin-bottom: 1.5em; margin-left: 0px; font-weight: inherit; font-style: inherit; font-size: 12px; font-family: inherit; vertical-align: baseline; padding: 0px; border: 0px initial initial;">The important thing is to &#8220;fail fast&#8221; &#8211; if something is not working, stop doing it, and start doing more things that <em>are</em> working.</p>
<p style="margin-top: 0px; margin-right: 0px; margin-bottom: 1.5em; margin-left: 0px; font-weight: inherit; font-style: inherit; font-size: 12px; font-family: inherit; vertical-align: baseline; padding: 0px; border: 0px initial initial;">But &#8211; what if <em>nothing </em>is working <em>at all</em>?  That&#8217;s OK too &#8211; actually it&#8217;s completely normal, especially for a startup.  See, you don&#8217;t have to be that far off for it to feel like nothing is lining up.</p>
<p style="margin-top: 0px; margin-right: 0px; margin-bottom: 1.5em; margin-left: 0px; font-weight: inherit; font-style: inherit; font-size: 12px; font-family: inherit; vertical-align: baseline; padding: 0px; border: 0px initial initial;">If I may, let me use <a href="http://www.chrometa.com">Chrometa </a>as an example.  One year ago at this time, we had very little working.  Our messaging and value proposition was not connecting with the market &#8211; people would go to our website, and wonder what the heck we (and our product) did.  Not good.</p>
<p style="margin-top: 0px; margin-right: 0px; margin-bottom: 1.5em; margin-left: 0px; font-weight: inherit; font-style: inherit; font-size: 12px; font-family: inherit; vertical-align: baseline; padding: 0px; border: 0px initial initial;">Our product itself was a little better.  It had evolved to the stage where trial and beta users would say &#8220;I can see where this is going.&#8221;</p>
<p style="margin-top: 0px; margin-right: 0px; margin-bottom: 1.5em; margin-left: 0px; font-weight: inherit; font-style: inherit; font-size: 12px; font-family: inherit; vertical-align: baseline; padding: 0px; border: 0px initial initial;">So we kept tweaking everything &#8211; our focus, the product itself, our messaging, etc.  It can be a maddening process, quite honestly, because you can make a lot of incremental improvements, and have nothing to show for it.</p>
<p style="margin-top: 0px; margin-right: 0px; margin-bottom: 1.5em; margin-left: 0px; font-weight: inherit; font-style: inherit; font-size: 12px; font-family: inherit; vertical-align: baseline; padding: 0px; border: 0px initial initial;">&#8220;How&#8217;s the startup going?&#8221; is a question people love to ask.  And it&#8217;s a question a pre-revenue company usually hates to answer!  Because it&#8217;s tough to say things are going well when you don&#8217;t yet have a product that people will gladly pay for.</p>
<p style="margin-top: 0px; margin-right: 0px; margin-bottom: 1.5em; margin-left: 0px; font-weight: inherit; font-style: inherit; font-size: 12px; font-family: inherit; vertical-align: baseline; padding: 0px; border: 0px initial initial;">But eventually, it came together for us.  We defined who we were.  We kept honing the product (and continue to do so).  And eventually things started to click.</p>
<p style="margin-top: 0px; margin-right: 0px; margin-bottom: 1.5em; margin-left: 0px; font-weight: inherit; font-style: inherit; font-size: 12px; font-family: inherit; vertical-align: baseline; padding: 0px; border: 0px initial initial;">Moral of the story &#8211; inaction is the enemy of the entrepreneur.  Get moving today.  You&#8217;ll figure out what works, what doesn&#8217;t (that&#8217;ll be a real long list initially), and most importantly, you&#8217;ll be able to go from there and start building something of real value.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.chrometa.com/blog/entrepreneur-stop-planning-start-doing/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Should Software Companies Support Their Users for Free?</title>
		<link>http://www.chrometa.com/blog/should-software-companies-support-their-users-for-free/</link>
		<comments>http://www.chrometa.com/blog/should-software-companies-support-their-users-for-free/#comments</comments>
		<pubDate>Tue, 09 Feb 2010 19:38:25 +0000</pubDate>
		<dc:creator>Brett Owens</dc:creator>
				<category><![CDATA[Business Model]]></category>
		<category><![CDATA[Software Business]]></category>
		<category><![CDATA[Support]]></category>

		<guid isPermaLink="false">http://www.chrometa.com/blog/?p=143</guid>
		<description><![CDATA[Support for software, in general, stinks.  Why is that?  Is it an immutable law of nature, or something that&#8217;s evolved over time?
And more importantly &#8211; can software companies provide a good to great level of support, and stay profitable?  Or will their ship inevitably be flooded and sunk by a never-ending barrage of phone calls [...]]]></description>
			<content:encoded><![CDATA[<p>Support for software, in general, stinks.  Why is that?  Is it an immutable law of nature, or something that&#8217;s evolved over time?</p>
<p>And more importantly &#8211; can software companies provide a good to great level of support, and stay profitable?  Or will their ship inevitably be flooded and sunk by a never-ending barrage of phone calls from users?</p>
<p>First, let&#8217;s split the software universe up into two categories &#8211; SaaS (Software as a Service), and traditional.  SaaS companies make their money by charging a monthly or yearly subscription for their product.  The advantage to a user is that you can &#8220;rent&#8221; the use of the product, which means that you can get started for a lower entry price.  The disadvantage being the flip side of the same coin &#8211; you&#8217;re paying month after month, it&#8217;s not a &#8220;rent to own&#8221; type of deal.</p>
<p>It&#8217;s a sweet deal for the software vendor, if they can pull off this model, thanks to the continuity.  And because of this, support from SaaS vendors is usually quite good, because they do have to work to keep your business, and they&#8217;ll factor support costs into the subscription price.</p>
<p>Traditional software is a different animal.  Generally the up front cost is a one-time fee.  After that, the user is generally regarded more as a liability to the company &#8211; we&#8217;ve got your money, now you&#8217;re on your own!</p>
<p>From the vendor&#8217;s perspective, support can easily spiral out of control if left unchecked.  While the software business does carry high margins, these can quickly erode if you&#8217;re spending a lot of time supporting users, especially if you&#8217;re not receiving any more revenue in the process.</p>
<p>But from the customer&#8217;s perspective, they paid for the product, so don&#8217;t they have a right to get help in making it work?</p>
<p>We wrestled with this question in the process of bringing our product to market.  We really wanted Chrometa to work great for everyone&#8230;in fact, we were convinced (and still are) that it had to.  Because we don&#8217;t have a big sales/marketing machine, so we need our users to be our feet on the street, our evangelists.</p>
<p>We don&#8217;t have a subscription based product.  It&#8217;s a one-time, $99 price.  So we received a lot of warnings from people that we&#8217;d &#8220;go broke on support&#8221; &#8211; especially if we didn&#8217;t charge an arm and a leg for it.</p>
<p>It never felt right to me to charge support for a product that&#8217;s supposed to work &#8220;out of the box&#8221;.  Nor to anyone on our team.  And really, when we launched, our potential problem of &#8220;going broke on support&#8221; hinged on us actually having product traction &#8211; so that&#8217;d be a good thing!  Let&#8217;s get the product out there, and worry about the support economics later.</p>
<p>So we advertised free email support with the purchase of a license.  In practice, though, not only did we gladly accept support phone calls, but we&#8217;d often call people back after receiving a support email, because it&#8217;s usually easier to speak live with someone.  That&#8217;s always a fun thing to do, because people just about fall out of their chairs when we call!  The bar on software support is SO low, that it&#8217;s not all that hard to step over <img src='http://www.chrometa.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>A few months after launch, we formalized the phone support, got an 1-800 number, and tossed it up prominently on our website.  A funny thing happened then &#8211; the number of phone calls we received <em>actually dropped</em>.</p>
<p>Why would this be?  I think it&#8217;s a combination of factors, which has included a consistent &#8220;beefing up&#8221; of our online help resources, and the general improvement of our product.  But having the phone # there seems to put people at ease &#8211; it&#8217;s there if they need it.</p>
<p>Overall we&#8217;ve observed that people are very good about searching for help on their own, before they contact us.  Inbound inquiries usually fall into one of the following categories:</p>
<ol>
<li><strong>Bug reports</strong> &#8211; this has tailed off for us significantly in the 6+ months since we launched, as we&#8217;ve been able to address many bugs, as well as enhancements, in product updates.  Bug reports are very valuable to us, we definitely want to know about these.  So the easier we can make the process, the better.</li>
<li><strong>Questions about how to do something</strong> &#8211; We actually launched without a product help guide, videos, anything!  Not that this was a badge of honor for us &#8211; it&#8217;s just that when you&#8217;re bootstrapping a software product yourself, you need to just to the basics, and get it to market.  And ultimately these help resources were not absolute &#8220;must haves&#8221; before launch &#8211; though we sure scrambled to put them together after!  Again, inquiries of this nature are always accepted, and helpful to us, as we can see where people are getting stuck, what may be unclear, etc.</li>
<li><strong>Feature and enhancement suggestions </strong>- The best part of getting a product to market is the user feedback.  All of the product enhancements we&#8217;ve implemented over the last six months have been based on <a href="http://www.chrometa.com/newsletter/january.php">feedback from our users</a>.  If you&#8217;re a software vendor, I&#8217;d think you&#8217;d always want to hear these.  Of course it&#8217;s not possible to implement everything.  But knowing is at least half the battle!</li>
</ol>
<p>We recently started giving <a href="http://www.chrometa.com/blog/free-time-tracking-software-for-law-students/">free licenses to students</a> &#8211; which in theory, would further complicate our support.  How can you support free users without any funding!  Thus far, not a problem at all.  Every student we hook up with a free license is about as nice as could be.  Sure it takes me a few seconds to ping them back with a license code, but then again, I&#8217;m not a programmer, so it&#8217;s not like I&#8217;d be doing something more productive with my time anyway <img src='http://www.chrometa.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Overall our early results on the &#8220;Great Free Support Experiment&#8221; have been very promising.  Our support time continues to trend gently down as our user base grows.  And to be honest, we try to look at support as a marketing function as well.  I always found it ironic that vendors who won&#8217;t accept inbound calls from users often have a telemarketing arm pounding the phones for new business in the next room!</p>
<p>Personally I spent so much time groveling for phone calls and meetings in our very early days with prospective users &#8211; &#8220;please, just try my product!&#8221; &#8211; that I&#8217;m hardwired now to gladly speak with anyone who wants to speak with me!</p>
<p>If you&#8217;re a fellow startup or early stage software company, my advice would be to absolutely give the best support that you can.  Take care of your users now &#8211; you can always worry about &#8220;scaling&#8221; and taking over the world later.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.chrometa.com/blog/should-software-companies-support-their-users-for-free/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
