Startup Lessons Learned

JANUARY 2, 2010

Lessons Learned by Eric Ries Saturday, January 2, 2010 Towards a new entrepreneurship When I started writing about the lean startup , my aspiration was to do more than just share a handful of tips and tricks that work for consumer internet startups. This belief led me to the lean startup, and to an amazing 2009. Writing a book.

San Francisco 122

San Francisco Lean Continuous Deployment DC 122

Startup Lessons Learned

MAY 9, 2012

It took the idea of Customer Development and made it accessible to a whole new audience. But commercial fishermen have to -- day in, day out -- in good weather or in bad -- acquire their target fish and then sell it for more than cost of catching it. Not an online clothing catalog, mind you, but a clothing company.

Entrepreneur 167

Entrepreneur Lean Southern California San Diego 167

Startup Lessons Learned

DECEMBER 14, 2009

A business that strives for something like this should absolutely be charging money from day one, in order to establish baselines for their two key metrics: CPA (the cost to acquire a new customer) and LTV (the lifetime value of each acquired customer). This is the simplest ecosystem and simplest driver of growth. Sorry about that.)

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

SEPTEMBER 10, 2008

But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. If you want to do continuous deployment, youd better be able to certify that build too, which brings us to. For more on continuous deployment, see Just-in-time Scalability. Can you make a build in one step?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

SEPTEMBER 5, 2008

[link] And - of course - going through [link] and reading up on the various different approaches different companies have (successfully) taken towards getting scalability at reasonably low cost. Case Study: Continuous deployment makes releases n. sadly, this blog forces you to use a google account.

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Startup Lessons Learned

SEPTEMBER 13, 2008

Since we were only paying per click, it didnt cost us anything to cast a wide net. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. We tried obvious competitors as well as long-shots.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

SEPTEMBER 30, 2008

If the CEO wants to completely change the product in order to serve a new customer segment, you need someone in the room who can digest the needs of the new (proposed) business, and lay out the costs of each possible approach. In my mind, theyre racking up costs (one month for that part, two months for that other part, uh oh).

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

APRIL 9, 2009

Well be discussing in greater detail the three techniques I highlighted at the Expo: continuous deployment, split-testing, and five whys. How to Build a Lean Startup, step-by-step Get started with a detailed guide to three key lean startup techniques: continuous deployment, rapid split-testing, and root cause analysis (five whys).

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

SEPTEMBER 8, 2008

It cost us a few hundred thousand dollars to get our app up and running, but none of that was dollars spent on software licenses or professional services. I cant really imagine how much it cost our "grownup" counterparts at other dot-com startups to get their first app up and running. Case Study: Continuous deployment makes releases n.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

MAY 27, 2009

The Lean Startup is a practical approach for creating and managing a new breed of company that excels in low-cost experimentation, rapid iteration, and true customer insight. Continuously discover what customers want to buy before building or making follow-on investments in new features. Take a look and let me know what you think.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

APRIL 26, 2009

Plus, we saw some of the intrinsic limitations of supporting such a large staff: slower cycle times, higher cost basis, and - most importantly - the ability to serve only a limited number of customer segments. Case Study: Continuous deployment makes releases n. We didnt think wed able to compete with that.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

SEPTEMBER 2, 2008

Or your cost of customer acquisition just magically floats up to match your customer lifetime value. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. we dont talk enough about how it feels.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

AUGUST 24, 2009

As the costs of production fall, it’s getting easier and easier to send in a proposal or even a complete work. There is no reason why all written content that is produced today for those purposes couldn’t be split-tested – at least to a segment of its audience. Case Study: Continuous deployment makes releases n.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

APRIL 14, 2009

They know how much it costs to bring in a customer and they know how much money they can expect to make on each one. In other words, they have learned to grow renewable audiences. Our cost to acquire a customer on AdWords was only a few cents. Case Study: Continuous deployment makes releases n.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

JANUARY 12, 2009

At the cost of a little extra indirection, you can organize your code around a series of long-lived objects, each of whom communicates with the other objects in simple, easy-to-understand ways. Yes, Python developers DO tend to cost more. Memory-resident code made it slightly slower to iterate on scripts. Im curious.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

MARCH 13, 2009

Thats because a marketing launch is a one-time event, and rarely translates into renewable audiences. Here was our experience at IMVU, which I have seen replicated at many other consumer internet startups. Slow progress, but has cost less than 150k aud so far. Case Study: Continuous deployment makes releases n.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

SEPTEMBER 19, 2009

In my presentation this morning, I emphasized three key areas: reducing the personal cost of failure for entrepreneurs, innovation-friendly legal reforms, and access to the digital means of production (slides from my White House presentation are available at the end of this post). Case Study: Continuous deployment makes releases n.

San Francisco 150

San Francisco Founder DC Washington 150

Startup Lessons Learned

AUGUST 8, 2009

In particular, we would cover customer development, continuous deployment, minimum viable product, and actionable metrics. Because of the cost and intensity of this program, it is designed for startups with significant venture backing or who have reached profitability. The cost is equivalent to an entry-level FTE.

Lean 102

Lean Programming San Francisco Continuous Deployment 102

Startup Lessons Learned

JANUARY 27, 2009

In it, he mentions the core dilemma that all freemium companies face: the key is to create the right mix of features to segment out the people who are willing to pay, but without alienating the users who make up your free audience. Case Study: Continuous deployment makes releases n. Take a look and let me know what you think.

San Francisco 148

San Francisco Lean Continuous Deployment DC 148

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. In the end, we managed to repair the damage, but only after losing a lot of time and at significant opportunity cost. We were totally unprepared for the magnitude of what happened.

Community 158

Community Management Lean Software Review 158

Startup Lessons Learned

AUGUST 20, 2009

Lessons Learned by Eric Ries Thursday, August 20, 2009 The Promise of the Lean Startup Im honored to have a guest post on GigaOm to introduce the concept of the lean startup to their audience. I know the audience on this blog, and Ive become comfortable writing in the long-form style I normally use here. Now for my request.

Lean 68

Lean San Francisco Startup Continuous Deployment 68

Startup Lessons Learned

MAY 22, 2009

marymin : The later you fail, the bigger the audience that sees you fail - and the more you have at risk. If your startup is growing (or aspires to grow), then the costs of a mistake are always going up. Since the cost of failure is monotonically increasing, it actually makes sense to fail sooner, not later.

Lean 76

Lean San Francisco Continuous Deployment Startup 76