Startup Lessons Learned

SEPTEMBER 7, 2008

It seems many startups these days are under a lot of pressure to outsource their development organization to save costs. Names have, of course, been changed to protect the innocent: Hope youre well; I thought Id relay a recent experience and thank you. Case Study: Continuous deployment makes releases n.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

MAY 9, 2012

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. In order to save on our costs we decided to make those batches very small and as a result of making small batches you can iterate on them if anything is successful.

Entrepreneur 167

Entrepreneur Lean Southern California San Diego 167

Startup Lessons Learned

JANUARY 19, 2009

Lessons Learned by Eric Ries Monday, January 19, 2009 Lean hiring tips In preparing for the strategy series panel this week, I have been doing some thinking about costs. I want to talk specifics, and when you come right down to it, most technology startups dont have a very interesting cost structure. The blog is fantastic as well.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

SEPTEMBER 13, 2008

Since we were only paying per click, it didnt cost us anything to cast a wide net. We would pretty much bid on any phrase that was "[name of competitive product] chat" and variations like that. Case Study: Continuous deployment makes releases n. We tried obvious competitors as well as long-shots.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

JANUARY 12, 2009

Some of them are probably still cursing my name, because - lets face it - PHP can be pretty painful. Almost every PHP-based website is burdened with ugly URLs that contain the name of the file that implements each page. Through my platform choices, I have forced many people to learn PHP and to work with it on a regular basis.

PHP 166

PHP Software Review Ruby San Francisco 166

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

JUNE 5, 2009

If it costs $0.10 to acquire an early adopter, how much should it cost to acquire a mainstream customer? We're starting our new business, fanminder.com, to help small merchants instantly communicate with their customers, and I'm increasingly hearing your name and reading your keen insights. But $10.00?

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

NOVEMBER 8, 2008

There are three fundamental situations that change what your company needs to do: creating a new market (the original Palm), bringing a new product to an existing market (Handspring), and resegmenting an existing market (niche, like In-n-Out Burger; or low-cost, like Southwest Airlines). Case Study: Continuous deployment makes releases n.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

JULY 2, 2009

Pay attention to whether people are comfortable “naming names&# in the meeting. Yet in every situation where I have asked, nobody has been tasked with making a realistic estimate, either of the impact of this lack of training or the real costs of the solution. Case Study: Continuous deployment makes releases n.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

AUGUST 1, 2009

Which comes to the second major principle: halt work that leads to more waste, even if it means abandoning sunk costs. Just because something looks pretty, or feels like a good idea, or has a lot of sunk cost in it, does not mean it should be pursued. Case Study: Continuous deployment makes releases n.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

JULY 29, 2009

We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design. Although it costs to pay down the principal, we gain by reduced interest payments in the future. The human tendency to moralize about debt affects engineers, too. One last thought.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

APRIL 14, 2009

Now, in some situations, this over-selling would lead to a secondary problem, namely, that customers would realize they had been duped and refuse to re-subscribe. 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. Case Study: Continuous deployment makes releases n.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

JANUARY 4, 2009

Imagine you want to store data about customers, each of whom has "last name" field in your database. The problem should be familiar to anyone who plays Scrabble: not all letter are equally likely to be used as the first letter of someones name. Give each entity a name. For example, consider this simple scheme.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

OCTOBER 20, 2008

But we were cutting corners in the development methodology as well as in the code, in the name of increased speed. I now believe that the "pick two" concept is fundamentally flawed, and that lean startups can achieve all three simultaneously: quickly bring high-quality software to market at low cost. Our profession is in trouble.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

MARCH 13, 2009

Who doesnt want to see their name in print? Here was our experience at IMVU, which I have seen replicated at many other consumer internet startups. Now that were beginning our first marketing, the key partners we need have heard our name long enough to trust us. Slow progress, but has cost less than 150k aud so far.

San Francisco 168

San Francisco PR Lean Early Stage 168

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. They stay around and continue to speak out vocally at every opportunity.

Community 158

Community Management Lean Software Review 158

Startup Lessons Learned

DECEMBER 7, 2008

I'd be interested to hear your thoughts on split testing SSL certificates and the effect of domain names. Does having an expensive Verisign branded SSL and site logo gain higher conversion than the low-cost GoDaddy equivalent? Case Study: Continuous deployment makes releases n.

San Francisco 132

San Francisco Lean Continuous Deployment DC 132

Startup Lessons Learned

FEBRUARY 12, 2009

Having worked with dozens of founders over the past few months, I think I can safely say, without naming any names, that most of us are not too clear on what were talking about when it comes to markets. Resegmented market (low cost variety). Heres a situation where you offer to do the job for 1/10th the cost.

San Francisco 89

San Francisco Continuous Deployment Ruby Lean 89

Startup Lessons Learned

FEBRUARY 11, 2009

Why do Citizens of Humanity jeans cost $200 , when physically similar pants can be had for one-tenth the price? The same is true of brand-name products in almost every category (and it can be measured ). Case Study: Continuous deployment makes releases n. and more ► January (6) Lo, my 18891 subscribers, who are you?

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

OCTOBER 23, 2009

Namely, that they agree to use it free of charge if we deliver it to them and it is capable of X, Y and Z. Namely, that they agree to use it free of charge if we deliver it to them and it is capable of X, Y and Z. Case Study: Continuous deployment makes releases n. Two Ways to Hold Entrepreneurs Accountable (for Ha.

San Francisco 144

San Francisco Customer Wiki Lean 144