Remove Blog Remove Continuous Deployment Remove CTO Hire Remove Revenue
article thumbnail

Lessons Learned: The three drivers of growth for your business.

Startup Lessons Learned

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?)

article thumbnail

Lessons Learned: The lean startup

Startup Lessons Learned

This slinging of whatever against the wall to see what sticks does not a market make, is to me a sign of too much capital in the wrong hands, and it's already the most over invested area in recent years- in both human and financial capital- particularly relative to revenue. Great blog! Good stuff.

Lean 168
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Lessons Learned: SEM on five dollars a day

Startup Lessons Learned

Slowly, over time, we optimized (or eliminated) each step in the process of becoming a customer by giving us money. And one day a remarkable thing happened: we started making more than five dollars a day in revenue. Case Study: Continuous deployment makes releases n. Two Ways to Hold Entrepreneurs Accountable (for Ha.

SEM 164
article thumbnail

Lessons Learned: Q&A with an actual reader

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, September 29, 2008 Q&A with an actual reader One of my favorite things about having a blog is the feedback I get in comments and by email. Case Study: Continuous deployment makes releases n. Hes also a blogger, at Inquiries Into Alignment ). Two Ways to Hold Entrepreneurs Accountable (for Ha.

article thumbnail

Lessons Learned: The lean startup comes to Stanford

Startup Lessons Learned

If you dont make predictions ahead of time, theres no way to call you on it. In fact, in the early days, when IMVU would experience unexpected surges of revenue or traffic, it was inevitable that every person in the company was convinced that their project was responsible. Case Study: Continuous deployment makes releases n.

Lean 68