Startup Lessons Learned

AUGUST 24, 2009

The other revels in the world as we all know it will be someday: limitless distribution enabled by new technologies, the importance of collaborative filters, and on-demand availability of all content for end-users. When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. Is that a lot?

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

OCTOBER 26, 2009

Customers kept demanding that we add this or that IM feature, and we were routinely refusing. We were afraid that this was just the tip of the iceberg, and that once we “gave in&# to these five demands there would be five more, ad infinitum. Every time you listen to customers, you fear diluting your vision.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

JUNE 15, 2009

As a consumer internet company with millions of customers, it may seem to have little relevancy for an enterprise software company with only a handful of potential customers, or a computer security company whose customers demand a rigorous audit before accepting a new release.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

maplebutter.com

JANUARY 8, 2013

Written By Dan Martell on February 2nd, 2012 | Category: Hiring LeanStartup Marketing Metrics Startup Life | 6 Comments. Building Metrics / Usage Reports / KPI 3. Product/Metrics (70%/30% time) * Get your product activation (sign-up + meaningful action) to 60% * then, Get your product retention to 20% weekly. 10) Metrics.

Technical Review 44

Technical Review Startup Cofounder Software Review 44