<?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: How to Alienate Your Vocal Supporters</title>
	<atom:link href="http://www.legalandrew.com/2009/04/24/how-to-alienate-your-vocal-supporters/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.legalandrew.com/2009/04/24/how-to-alienate-your-vocal-supporters/</link>
	<description>law for the rest of us</description>
	<lastBuildDate>Fri, 20 Nov 2009 06:49:36 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: My Custom Business Management System &#171; Legal Andrew</title>
		<link>http://www.legalandrew.com/2009/04/24/how-to-alienate-your-vocal-supporters/comment-page-1/#comment-64755</link>
		<dc:creator>My Custom Business Management System &#171; Legal Andrew</dc:creator>
		<pubDate>Sun, 20 Sep 2009 03:06:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.legalandrew.com/?p=1293#comment-64755</guid>
		<description>[...] April, I wrote that I wanted to integrate my main systems. It&#8217;s done now, and this post explains [...]</description>
		<content:encoded><![CDATA[<p>[...] April, I wrote that I wanted to integrate my main systems. It&#8217;s done now, and this post explains [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EchoSign Customer Service To The Rescue! &#171; Legal Andrew</title>
		<link>http://www.legalandrew.com/2009/04/24/how-to-alienate-your-vocal-supporters/comment-page-1/#comment-64208</link>
		<dc:creator>EchoSign Customer Service To The Rescue! &#171; Legal Andrew</dc:creator>
		<pubDate>Mon, 27 Apr 2009 17:44:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.legalandrew.com/?p=1293#comment-64208</guid>
		<description>[...] Friday at 11:53pm, I wrote this post about EchoSign not giving small users access to their API. I wanted to integrate their e-signing [...]</description>
		<content:encoded><![CDATA[<p>[...] Friday at 11:53pm, I wrote this post about EchoSign not giving small users access to their API. I wanted to integrate their e-signing [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Flusche</title>
		<link>http://www.legalandrew.com/2009/04/24/how-to-alienate-your-vocal-supporters/comment-page-1/#comment-64197</link>
		<dc:creator>Andrew Flusche</dc:creator>
		<pubDate>Sun, 26 Apr 2009 04:19:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.legalandrew.com/?p=1293#comment-64197</guid>
		<description>Michelle,

Thanks for stopping by to say hi. I appreciate it!

Being a small business can be pretty tough. We really have to work for maximum efficiency. That&#039;s why I&#039;m so pumped about integrating my applications!

Andrew</description>
		<content:encoded><![CDATA[<p>Michelle,</p>
<p>Thanks for stopping by to say hi. I appreciate it!</p>
<p>Being a small business can be pretty tough. We really have to work for maximum efficiency. That&#8217;s why I&#8217;m so pumped about integrating my applications!</p>
<p>Andrew</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michelle Riggen-Ransom</title>
		<link>http://www.legalandrew.com/2009/04/24/how-to-alienate-your-vocal-supporters/comment-page-1/#comment-64196</link>
		<dc:creator>Michelle Riggen-Ransom</dc:creator>
		<pubDate>Sun, 26 Apr 2009 00:43:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.legalandrew.com/?p=1293#comment-64196</guid>
		<description>Hi Andrew - thanks for the shout-out and so glad you share our love for the solopreneur/micro-business! We think the future belongs to small businesses and are excited that our product will help them to succeed. And it helps being a very small business ourselves :) 

Thanks again and keep on keepin&#039; on out there!

Michelle Riggen-Ransom
Communications Director &amp; Customer Service Bon Vivant</description>
		<content:encoded><![CDATA[<p>Hi Andrew &#8211; thanks for the shout-out and so glad you share our love for the solopreneur/micro-business! We think the future belongs to small businesses and are excited that our product will help them to succeed. And it helps being a very small business ourselves <img src='http://www.legalandrew.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  </p>
<p>Thanks again and keep on keepin&#8217; on out there!</p>
<p>Michelle Riggen-Ransom<br />
Communications Director &amp; Customer Service Bon Vivant</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Flusche</title>
		<link>http://www.legalandrew.com/2009/04/24/how-to-alienate-your-vocal-supporters/comment-page-1/#comment-64194</link>
		<dc:creator>Andrew Flusche</dc:creator>
		<pubDate>Sat, 25 Apr 2009 20:33:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.legalandrew.com/?p=1293#comment-64194</guid>
		<description>Jason,

First of all, thank you for the prompt and thorough reply. You guys definitely have outstanding customer service.

I definitely understand the risk of abuse with the API. I certainly wouldn&#039;t expect you to allow a Pro user to send thousands of documents per month, regardless of the interface being used. You have a great product, and it definitely costs money on your end to process all those transactions. You need to be compensated appropriately for different volumes of use.

I don&#039;t understand what you mean in your last paragraph about integrating EchoSign &quot;for your app&#039;s users and use EchoSign credentials.&quot; My rusty programming knowledge might be failing me here. Perhaps this option you&#039;re mentioning would fit my needs. I would use my current EchoSign credentials, and the app would only be for my use.

Thanks again for the quick response. I look forward to discussing this further with you and your team.

Andrew</description>
		<content:encoded><![CDATA[<p>Jason,</p>
<p>First of all, thank you for the prompt and thorough reply. You guys definitely have outstanding customer service.</p>
<p>I definitely understand the risk of abuse with the API. I certainly wouldn&#8217;t expect you to allow a Pro user to send thousands of documents per month, regardless of the interface being used. You have a great product, and it definitely costs money on your end to process all those transactions. You need to be compensated appropriately for different volumes of use.</p>
<p>I don&#8217;t understand what you mean in your last paragraph about integrating EchoSign &#8220;for your app&#8217;s users and use EchoSign credentials.&#8221; My rusty programming knowledge might be failing me here. Perhaps this option you&#8217;re mentioning would fit my needs. I would use my current EchoSign credentials, and the app would only be for my use.</p>
<p>Thanks again for the quick response. I look forward to discussing this further with you and your team.</p>
<p>Andrew</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason M. Lemkin</title>
		<link>http://www.legalandrew.com/2009/04/24/how-to-alienate-your-vocal-supporters/comment-page-1/#comment-64193</link>
		<dc:creator>Jason M. Lemkin</dc:creator>
		<pubDate>Sat, 25 Apr 2009 15:11:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.legalandrew.com/?p=1293#comment-64193</guid>
		<description>Thanks Andrew.  We appreciate the feedback here.  EchoSign is primarily focused on SMBs as a % of our user base and I agree with all the spirit of your post.  One goal of an API is to allow both integration into other apps and access to your data.  In terms of data, EchoSign as you know has absolutely no data lock.  In terms of integration, as you may know, we provide out-of-the-box integration at no cost to leaders such as Salesforce, Box.net, HR Block Rocketlawyer, Zoho Writer, eFax, and many others.

For our customers, the reason we generally have to limit API access to our Ent edition accounts isn&#039;t the data side -- it&#039;s your data - rather it&#039;s the transactional nature of our product.  A Free account (which is a smoking deal) is limited to 5 transactions / month.  A Pro account is extremely inexpensive, but by design must thus be limited to a SOHO/individual user.  By contrast, almost all our API customers are high volume, high transaction users which align with an Enterprise ($299) account.  Allowing them to send 5,000 transactions a month through a Free or Pro account I am sure you will agree would violate the spirit of those accounts as well as their terms.

Contrast this to most API integrations with paid products, where the goal really is to access data, not as the primarily vehicle to use the product.  With EchoSign, you already have your data.

Limiting it in this fashion minimizes the chance for abuse, which in turn, maximizes the quality of our customer experience.

Having said there, there is absolutely no charge to use the API if your application simply wants to integrate EchoSign for your app&#039;s users and use EchoSign credentials.  This eliminates all the gaming issues above, and is exactly what Box.net, Zoho, DigitalBucket, and Sosius do for example.  Please let support know you want to do this and they&#039;ll get you access promptly.  We should make this clearer on our website under the partner section and will in our next release, which will be an exciting one.

Thanks again for the feedback and support.

Jason M. Lemkin, ceo &amp; co-founder</description>
		<content:encoded><![CDATA[<p>Thanks Andrew.  We appreciate the feedback here.  EchoSign is primarily focused on SMBs as a % of our user base and I agree with all the spirit of your post.  One goal of an API is to allow both integration into other apps and access to your data.  In terms of data, EchoSign as you know has absolutely no data lock.  In terms of integration, as you may know, we provide out-of-the-box integration at no cost to leaders such as Salesforce, Box.net, HR Block Rocketlawyer, Zoho Writer, eFax, and many others.</p>
<p>For our customers, the reason we generally have to limit API access to our Ent edition accounts isn&#8217;t the data side &#8212; it&#8217;s your data &#8211; rather it&#8217;s the transactional nature of our product.  A Free account (which is a smoking deal) is limited to 5 transactions / month.  A Pro account is extremely inexpensive, but by design must thus be limited to a SOHO/individual user.  By contrast, almost all our API customers are high volume, high transaction users which align with an Enterprise ($299) account.  Allowing them to send 5,000 transactions a month through a Free or Pro account I am sure you will agree would violate the spirit of those accounts as well as their terms.</p>
<p>Contrast this to most API integrations with paid products, where the goal really is to access data, not as the primarily vehicle to use the product.  With EchoSign, you already have your data.</p>
<p>Limiting it in this fashion minimizes the chance for abuse, which in turn, maximizes the quality of our customer experience.</p>
<p>Having said there, there is absolutely no charge to use the API if your application simply wants to integrate EchoSign for your app&#8217;s users and use EchoSign credentials.  This eliminates all the gaming issues above, and is exactly what Box.net, Zoho, DigitalBucket, and Sosius do for example.  Please let support know you want to do this and they&#8217;ll get you access promptly.  We should make this clearer on our website under the partner section and will in our next release, which will be an exciting one.</p>
<p>Thanks again for the feedback and support.</p>
<p>Jason M. Lemkin, ceo &amp; co-founder</p>
]]></content:encoded>
	</item>
</channel>
</rss>
