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

APRIL 14, 2009

This may sound crazy, coming as it does from an advocate of c harging customers for your product from day one. Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. In fact, this company hasn’t shipped any new products in months. What’s going on?

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

JANUARY 2, 2009

At IMVU, we were terrified by how early we shipped (and charged for) our first product. Despite that, we were able to establish credibility, because we used those early numbers to demonstrate that our customers were getting real value from our product and, more importantly, that we understood how to build more of it. Expo SF (May.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

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

AUGUST 24, 2009

And once you have a relationship with an author, musician, or journalist, it will be quite easy for them to offer new products and services – and for you to give them feedback that helps them shape ever more interesting (and ever more profitable) offerings. There are too many products clamoring for attention. Is that a lot?

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

JUNE 22, 2009

Each has its own iterative process: customer development and agile development respectively. As Steve writes in the Four Steps to the Epiphany , we always seek to find a market for the product as currently specified , not conduct a focus group to tell us what the spec should be.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

OCTOBER 7, 2008

Take a look at The App Store after the gold rush - FierceDeveloper : According to a recent BusinessWeek feature , the flood of new games, productivity tools and related iPhone software is making it difficult for the vast majority of apps to crack the consumer consciousness. Retention competition is how you get people to come back to your app.

San Francisco 68

San Francisco Lean Retention SEM 68