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. Case Study: Continuous deployment makes releases n.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

APRIL 14, 2009

Some products have relatively obvious monetization mechanisms, and the real risks are in customer adoption. Products can find sources of validation with impressive stats along a number of dimensions, such as high engagement, viral coefficient, or long-term retention. Labels: agile , customer development 15comments: Scott Shapiro said.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

JUNE 22, 2009

Each has its own iterative process: customer development and agile development respectively. In a customer problem pivot, we try to solve a different problem for the same customer segment. When doing intense customer development, the problem team can attain a high level of empathy with potential customers.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

DECEMBER 16, 2008

After youve acquired a customer, why would they bother to come back to your service? I wrote about this challenge for iPhone developers, in an essay on retention competition : the battle over what icon the user will click when they go to the home screen. Have you struggled with engagement and retention?

Viral 140

Viral San Francisco Lean Continuous Deployment 140