<?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>zoestreet.com&#187; risk</title>
	<atom:link href="http://zoestreet.com/tag/risk/feed" rel="self" type="application/rss+xml" />
	<link>http://zoestreet.com</link>
	<description>Zoe Street &#124; Ad Agency San Francisco &#124; Top Ad Agencies &#124; Saas, B2B and Social Networking</description>
	<lastBuildDate>Tue, 09 Feb 2010 20:21:48 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Two years of Development Can Save You a Month of Research</title>
		<link>http://zoestreet.com/2009/doing-market-research-9</link>
		<comments>http://zoestreet.com/2009/doing-market-research-9#comments</comments>
		<pubDate>Thu, 05 Feb 2009 02:04:23 +0000</pubDate>
		<dc:creator>aj</dc:creator>
				<category><![CDATA[Running Things]]></category>
		<category><![CDATA[focus groups]]></category>
		<category><![CDATA[marketing]]></category>
		<category><![CDATA[research]]></category>
		<category><![CDATA[risk]]></category>
		<category><![CDATA[startups]]></category>

		<guid isPermaLink="false">http://zoestreet.com/?p=9</guid>
		<description><![CDATA[Building the wrong product is way more expensive than any amount of research.]]></description>
			<content:encoded><![CDATA[<p><img class="alignleft size-thumbnail wp-image-109" title="istock_000007201810xsmall" src="http://zoestreet.com/wp-content/uploads/2009/04/istock_000007201810xsmall-150x150.jpg" alt="istock_000007201810xsmall" width="150" height="150" />Grad students have a wonderful saying: “Six weeks in the lab can save you two hours in the library.” The same applies to software companies. Building the wrong product is an expensive proposition, and for startups, it’s usually fatal. The good news is that a well-run research effort can help you avoid this fate. What’s more, it’s actually a well-defined process that will probably cost less and deliver more than you think.</p>
<p>In general, there are two types of research: quantitative and qualitative.</p>
<h5>Quantitative</h5>
<p>Quantitative, unsurprisingly, involves large numbers of respondents. It’s typically structured as some kind of survey and analyzed using statistical methods. It can help you learn things like</p>
<ul>
<li>&#8220;78% of executives who travel rely on their smartphones instead of their laptops for overnight trips&#8221;</li>
<li>&#8220;Only 3% of small business owners have heard the term “VoIP” and know what it means&#8221;</li>
</ul>
<p>Quantitative research is often used to find potential market opportunities, gauge demand for a product under consideration, or justify demand for a product already under development.</p>
<h5>Qualitative</h5>
<p>Qualitative research is typically conducted with small groups (some variation of the focus group model), and with individuals (some kind of one-on-one interview.)</p>
<h4>Use Focus Groups for Insight</h4>
<p>Focus groups help you to identify customer problems and pain points, and allow you to hear the actual language they use. For example, you may think of your product as a “multi-function mobile broadband communications terminal” while your customers think of it as a “phone.” This type of insight is invaluable when defining or positioning a product.<br />
The rules for successful focus groups are pretty simple: get the right people in the groups, work with a great moderator, and run at least two groups for each audience you want to research. (This helps you eliminate any bias that might exist within one particular session.)<br />
A complete focus group project to one audience can cost as little as $15K, and can be done in as little as 4 weeks. You can of course spend more to get better, more reliable insight, but budget at least this to get some real value from the process.</p>
<h4>Use Interviews for Validation</h4>
<p>Individual interviews are best for getting a response to a specific proposition, like a product idea or positioning. This helps you validate and refine your messaging, benefit statements, pricing, and the other specifics of your offering.<br />
The rules for successful one-on-one interviews are also simple: make sure you’re talking to the right people, talk to a minimum of 7 or 8 from each audience, and don’t have someone from your company do the interviews. (No one will tell you that your baby is ugly, but if asked correctly, they will tell someone else.)<br />
One-on-one interviews are usually 30 minutes to an hour long, and can be done over the phone at very low cost.</p>
<h4>Now is a Good Time to Start</h4>
<p>At what phase in the development process should you start your research? Now is probably a good time. In the 20 years we’ve been doing technology marketing, we’ve never heard anyone say “We did the research too early.”</p>
]]></content:encoded>
			<wfw:commentRss>http://zoestreet.com/2009/doing-market-research-9/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Are Your Focusing on the Wrong Kind of Risk?</title>
		<link>http://zoestreet.com/2009/the-wrong-kind-of-risk-14</link>
		<comments>http://zoestreet.com/2009/the-wrong-kind-of-risk-14#comments</comments>
		<pubDate>Fri, 02 Jan 2009 07:03:04 +0000</pubDate>
		<dc:creator>aj</dc:creator>
				<category><![CDATA[Running Things]]></category>
		<category><![CDATA[business model]]></category>
		<category><![CDATA[marketing]]></category>
		<category><![CDATA[research]]></category>
		<category><![CDATA[risk]]></category>
		<category><![CDATA[SaaS]]></category>
		<category><![CDATA[startups]]></category>
		<category><![CDATA[technology risk]]></category>

		<guid isPermaLink="false">http://zoestreet.com/?p=14</guid>
		<description><![CDATA[In my experience, startups usually overestimate technology risk and underestimate adoption risk. There are two reasons for this.]]></description>
			<content:encoded><![CDATA[<p>When you’re starting a software company, your two biggest risks are:</p>
<ul>
<li>Technology risk &#8212; the risk that you can’t make the product you want</li>
<li>Adoption risk &#8212; the risk that customers don’t want the product you make</li>
</ul>
<p>In my experience, startups usually overestimate technology risk and underestimate adoption risk. There are two reasons for this.</p>
<h6>1. Technology Risk is Declining</h6>
<p>As the software market matures, technology risk is actually declining for all but the most ambitious projects. Simply put, there is now a lot of really good infrastructure in place (development languages, open source tools and platforms, hosting infrastructure, turn-key cloud computing platforms, and of course the worldwide web itself). Just as important, there are also a lot of really smart technology people who know how to use these powerful building blocks to make pretty much anything you can dream up. Don’t get me wrong, software development isn’t trivial or a slam-dunk, and many ships have foundered on those shores, but the risk is declining and generally over-emphasized.</p>
<h6>2. Disbelievers Don’t Build Products</h6>
<p>Passion for an idea is the bedrock requirement of being an entrepreneur. Entrepreneurs work with investors and employees who also believe strongly in the mission. After all, who would hire a marketing director, a developer, or a QA person who said “It’s kind of a dumb idea, but what the heck, I’ll give it a whirl.”?</p>
<p>This makes adoption risk that much more dangerous. <span style="font-style: italic;">It’s typically underestimated by the entire organization.</span></p>
<p>This organizational blind spot can play out in three different ways:</p>
<ol>
<li> Bad ideas that should never have been funded</li>
<li> Good ideas that were flawed in execution (this is often cleverly disguised as technology risk, as the dev team scrambles to revise the product to match actual customer needs)</li>
<li> Well executed ideas without a clear path to market (or without a realistic level of funding to get them to market)</li>
</ol>
<p>Fortunately, a well-run research effort can reduce the risk of all of these types of failures. More on that in a future post.</p>
]]></content:encoded>
			<wfw:commentRss>http://zoestreet.com/2009/the-wrong-kind-of-risk-14/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SaaS: And Now the Bad News</title>
		<link>http://zoestreet.com/2008/saas-the-bad-news-18</link>
		<comments>http://zoestreet.com/2008/saas-the-bad-news-18#comments</comments>
		<pubDate>Wed, 31 Dec 2008 01:46:41 +0000</pubDate>
		<dc:creator>aj</dc:creator>
				<category><![CDATA[SaaS]]></category>
		<category><![CDATA[business model]]></category>
		<category><![CDATA[challenges]]></category>
		<category><![CDATA[customer acquisition]]></category>
		<category><![CDATA[lifetime customer value]]></category>
		<category><![CDATA[marketing]]></category>
		<category><![CDATA[profitability]]></category>
		<category><![CDATA[risk]]></category>
		<category><![CDATA[service business]]></category>
		<category><![CDATA[subscription model]]></category>

		<guid isPermaLink="false">http://zoestreet.com/?p=18</guid>
		<description><![CDATA[While there are many inherently good things about the SaaS (Software-as-a-Service) business model, there are also some unique challenges.]]></description>
			<content:encoded><![CDATA[<div id="attachment_103" class="wp-caption alignleft" style="width: 160px"><img class="size-thumbnail wp-image-103" title="thumbs_down" src="http://zoestreet.com/wp-content/uploads/2009/04/thumbs_down-150x150.jpg" alt="thumbs_down" width="150" height="150" /><p class="wp-caption-text">Nothing&#39;s perfect</p></div>
<p>(Part one of this series was called <a href="http://zoestreet.com/?p=16"><em>SaaS: First, the good news</em></a>)</p>
<p>While there are many inherently good things about the SaaS (Software-as-a-Service) business model, there are also some unique challenges.</p>
<h6>Higher cash requirements (Please deposit $24 for the next minute…)</h6>
<p>SaaS companies can be very cheap to start, but because they tend to produce recurring (usually monthly) revenues rather than large lump-sum payments, it’s hard to use current cash to finance future growth. VCs often assume that it takes about $50 million to build a profitable SaaS company. Assuming a 4 year path to profitability, you’re burning through $24 a minute. This problem is made worse by…</p>
<h6>…Lower price points (including FREE)</h6>
<p>Because they’re typically based on a subscription model, SaaS companies try to maximize lifetime customer value through a low entry price and a long subscription duration. This approach, combined with intense competition and strong customer expectations that online content and services should be free or extremely cheap, means in order to reach profitability…</p>
<h6>…You gotta have scale</h6>
<p>If you’re entry price point is free (or something close to it) and you’re relying on some advertising revenue plus conversion to higher priced offerings (a conversion rate of 1% of your total customer base is considered typical) then you have to be able to attract and retain a very large number of customers before you’re in the black. That means your infrastructure and application need to be engineered accordingly, of course. But more importantly…</p>
<h6>…Customer acquisition will be a major expense</h6>
<p>While the online nature of SaaS suggests a pure online selling strategy, the reality is that SaaS companies tend to be very omnivorous in their drive to acquire customers. Between PR, search engine optimization, keyword advertising, webinars, email campaigns, reseller compensation, and other direct and indirect sales efforts, you could easily be spending 2/3 of your money on sales and marketing expense. To get a return on this investment, especially in the early days before your market matures, you’ll need to reach and convert a pool of savvy and influential people who prefer your vision of the future to that of your many competitors. In other words…</p>
<h6>…You’re competing for the attention of Influencers, not just customers</h6>
<p>Early customers are different. They know that others look to them for guidance about which technologies or services to adopt, and that their opinion counts. They will be very hesitant to risk their reputation on a company that doesn&#8217;t deliver a good experience and good value to their friends and colleagues. To be successful, you’ll need to build specific programs and efforts for reaching, influencing and recruiting these early adopters. These programs may be very different (and much more expensive, on a cost-per-customer basis) than your “typical” customer acquisition programs.</p>
<p>More on this in a separate post.</p>
]]></content:encoded>
			<wfw:commentRss>http://zoestreet.com/2008/saas-the-bad-news-18/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
