Startup Lessons Learned

APRIL 14, 2009

Lessons Learned by Eric Ries Tuesday, April 14, 2009 Validated learning about customers Would you rather have $30,000 or $1 million in revenues for your startup? All things being equal, of course, you’d rather have more revenue rather than less. And yet revenue alone is not a sufficient goal.

Customer 167

Customer San Francisco Lean Hockey Stick 167

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

SEPTEMBER 13, 2008

And one day a remarkable thing happened: we started making more than five dollars a day in revenue. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n. Two Ways to Hold Entrepreneurs Accountable (for Ha.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

JANUARY 2, 2009

We were even more embarrassed by the pathetically small number of customers we had, and the pathetically low amount of revenue we had earned so far. We’d always cringe as we admitted that, no, we really only had a few thousand customers and a few thousand dollars in monthly revenue. Retention cohort analysis. I am chugging along.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

Startup Lessons Learned

JUNE 5, 2009

And so the spreadsheet is built with conservative assumptions, including a final revenue target. No matter how low we make the revenue projections for this new product, it’s extremely unlikely that they are achievable. Just because entrepreneurs tend to forget about these models doesn’t mean their investors do.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

NOVEMBER 8, 2008

This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. Heres the catch.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

NOVEMBER 17, 2008

Strategy - startups first encounter this when they have the beginnings of a product, and theyve achieved some amount of product/market fit. If youre making revenue, you should be finding ways to grow it predictably month-over-month; if youre focused on customer engagement, your product should be getting more sticky, and so on.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

DECEMBER 23, 2009

They were accustomed to measuring their progress primarily by gross revenue compared to their targets. They were accustomed to measuring their progress primarily by gross revenue compared to their targets. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Bring your questions.

Metrics 167

Metrics San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

APRIL 7, 2010

In fact, the curse of product development is that sometimes small things make a huge difference and sometimes huge things make no difference. Our job as entrepreneurs is to invent the future, and any optimization technique – including split-testing, many design techniques, or even usability testing – can lead us astray.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

MARCH 27, 2009

To increase the number of iterations you have left, you can either increase cash on hand (by raising money or increasing revenues), reduce burn rate, or increase the speed of each iteration. Customer Development : a disciplined approach to finding out if there is a market for your product before its too late.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

AUGUST 1, 2009

Most executives, especially in startups, dont have the courage to hold their teams to a high standard for new products or features. Not even if its generating revenue. The only efforts a new product team should be expending are those that lead to validated learning about customers. Will start to pay attention. Great post Eric.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

JANUARY 28, 2009

Still, theyre not really hitting it out of the park, because their product isnt growing new users as fast as theyd like, and they arent making any money from the current users. Because, unless you are working in an extremely static environment, your product development team is learning and getting better all the time.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

JULY 2, 2009

Labels: five whys root cause analysis , product development 15comments: Anonymoussaid. We just add up the revenue we've made in the past few months from Win98 users, and compare to the pain that Win98 has caused as identified in 5Ys. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

SEPTEMBER 28, 2008

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? April 23, 2010 in San Francisco.

Lean 68

Lean San Francisco Continuous Deployment Startup 68

Startup Lessons Learned

AUGUST 24, 2009

When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. What is the right revenue model? In other words, what is the minimum viable product ? The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Is that a lot? Is that good?

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

SEPTEMBER 29, 2008

Either way, you would have been better off focusing your split-test on high level metrics that measure how much customers like your product as a whole. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n. Bring your questions.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

DECEMBER 14, 2009

Now, Andrew’s excellent piece that I quoted from above correctly diagnoses two situations where consumer internet companies often get in trouble: They focus too much on short-term revenue, getting caught in a local maximum via constant optimization. Case Study: Continuous deployment makes releases n.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

OCTOBER 30, 2008

The tips are based on advice JD solicited from great KPCB entrepreneurs. Not just about expenses, about increasing revenue. Make sure for planned revenues you have "leading indicators" to know if you will hit it. This can take the form of a traditional sales pipeline or a registration-activation-revenue chart.

Lean 121

Lean San Francisco Continuous Deployment DC 121

Startup Lessons Learned

JANUARY 27, 2009

These are companies that generate revenue by offering a free product with an upsell or premium version. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n. Two Ways to Hold Entrepreneurs Accountable (for Ha.

San Francisco 148

San Francisco Lean Continuous Deployment DC 148

Startup Lessons Learned

AUGUST 16, 2010

Because the stakes were high, they had to successfully use a technique I call Innovation inside the box which is important for entrepreneurs inside established companies of all sizes. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n.

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 22, 2008

The whole episode cost us hundreds of thousands of dollars in lost revenue. In fact, it was the revenue trends that eventually alerted us to the magnitude of the problem. Unfortunately, revenue a trailing indicator. Its a great time to increase revenues without spending money on acquiring new customers.

.Net 158

.Net Operations San Francisco Lean 158

Startup Lessons Learned

JULY 9, 2009

Lessons Learned by Eric Ries Thursday, July 9, 2009 10 years of entrepreneurship I recently passed my ten-year anniversary of becoming an entrepreneur. We were focused on revenue, but we didnt understand that revenue is not important for its own sake in an early stage company. As a young entrepreneur, this is quite motivational.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

MAY 1, 2009

I covered a few of them on twitter already: Q: "Do you reccomend removing features that youve launched but dont movethe needle on engagement or revenue?" The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n.

Lean 60

Lean San Francisco Startup Continuous Deployment 60

Startup Lessons Learned

SEPTEMBER 11, 2009

This single decision wound up costing the company significant revenue and over the course of several months sent its customer growth into decline. You should know that there are thousands of entrepreneurs who read this blog, some of whom are working on new platforms that will see the light of day someday. Thank you so much.

Community 158

Community Management Lean Software Review 158