Startup Lessons Learned

SEPTEMBER 22, 2008

is an elegant way to model any service-oriented business: Acquisition Activation Retention Referral Revenue We used a very similar scheme at IMVU, although we werent lucky enough to have started with this framework, and so had to derive a lot of it ourselves via trial and error. The AARRR model (hence pirates, get it?)

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

JULY 3, 2009

davemcclure : amazing concepts on Continuous Development => "Cluster Immune System" @EricRies #LeanStartup @fbFund [link] dalelarson : Because most features take longer to argue and prioritize than to build. ericries #leanstartup Another new idea in the section on continuous deployment and the cluster immune system.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

JANUARY 2, 2009

Retention cohort analysis. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. When startups ask me what to measure, I always come back to these three as a starting point: Revenue per customer.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

Startup Lessons Learned

APRIL 14, 2009

This is an incredible skill, one that most engineers overlook. Products can find sources of validation with impressive stats along a number of dimensions, such as high engagement, viral coefficient, or long-term retention. Case Study: Continuous deployment makes releases n. involved before we go into production.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

AUGUST 24, 2009

And anytime you strike a deal for digital distribution of any content, insist that your creators be given real-time access to the big-picture metrics: not just downloads, but engagement, retention and replay. Case Study: Continuous deployment makes releases n. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

OCTOBER 7, 2008

I think its helpful to think about two kinds of competition for distribution: acquisition competition and retention competition. Retention competition is how you get people to come back to your app. If your app has incredibly strong retention, you will probably do very well with the current PR/new app system of acquisition.

San Francisco 68

San Francisco Lean Retention SEM 68

Startup Lessons Learned

JUNE 22, 2009

As the CTO/VP Engineering, I was the worst offender. That means that I (and other engineers) were able to participate in the problem team discussions. Such discussions would have been impossible in our execution-oriented engineering team meetings. Case Study: Continuous deployment makes releases n. Context matters.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167