Startup Lessons Learned

FEBRUARY 10, 2009

As Ive argued elsewhere , my belief is that startups (and anyone else trying to find an unknown solution to an unknown problem ) have to measure progress with validated learning about customers. In a lot of cases, thats just a fancy name for revenue or profit, but not always. April 23, 2010 in San Francisco.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

DECEMBER 23, 2009

They were accustomed to measuring their progress primarily by gross revenue compared to their targets. It turned out that, during the course of the decline, one customer segment was losing customers while another was gaining customers. April 23, 2010 in San Francisco. Bring your questions.

Metrics 167

Metrics San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

JANUARY 15, 2010

Usually, they are delivering only a fraction of the revenue they promised. Usually, they are delivering only a fraction of the revenue they promised. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? April 23, 2010 in San Francisco. Bring your questions.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

NOVEMBER 17, 2008

Growth - when you have existing customers, the pressure is on to grow your key metrics day-in day-out. 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. What is customer development?

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

AUGUST 1, 2009

For startups that are tempted to mimic this behavior, I suggest reading the great account of the early Apple in Founders at Work.) 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.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

MARCH 27, 2009

The full formula works like this: runway = cash on hand / burn rate # iterations = runway / speed of each iteration Very few successful companies ended up in the same exact business that the founders thought theyd be in (see Founders at Work for dozens of examples). April 23, 2010 in San Francisco.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

DECEMBER 14, 2009

Each of these four currencies represents a way for a customer to “pay&# for services from a company. A great product enables customers, developers, partners, and even competitors to exchange their unique currencies in combinations that lead to financial success for the company that organizes them.

Customer 156

Customer San Francisco Viral Lean 156

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. April 23, 2010 in San Francisco.

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. That’s because the model is based on assumptions about customers that are totally unproven.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

JANUARY 10, 2011

We also cavalierly lampoon the “suits” that get brought in to run startups after the founders are fired by callous VC’s. They have the ultimate responsibility in a venture-backed company of deciding whether to fire the founders and bring in “professional management.” I also frequently see the reverse. (In

Silicon Valley 167

Silicon Valley San Francisco Lean Investment Bankers 167

Startup Lessons Learned

JUNE 15, 2009

There are a whole range of valid reasons why non-developers would want to dictate the production release schedule (Seasonal/timing issues, marketing, fulfillment concerns, documentation/training, revenue controls, legal/regulatory. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

APRIL 7, 2010

When you read stories of successful startups in the popular and business press, you usually hear about how the founders anticipated several of these challenges in their initial vision. Should you charge from day one, testing the revenue model first? Unfortunately, startup success requires getting them all right.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

JULY 2, 2009

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? April 23, 2010 in San Francisco. Bring your questions.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

JANUARY 28, 2009

They asked for my advice, and we went through a number of recommendations that readers of this blog will already be able to guess: adding revenue opportunities, engagement loop optimization, and some immediate split-testing to figure out whats working and whats not. April 23, 2010 in San Francisco. Bring your questions.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Steve Blank

OCTOBER 10, 2016

How founders find the determination to push through tough times was the focus on today’s Entrepreneurs are Everywhere radio show. The show follows the journeys of founders who share what it takes to build a startup – from restaurants to rocket scientists, to online gifts to online groceries and more. Jacqueline Ros. Christina Stembel.

Entrepreneur 260

Entrepreneur Cofounder San Francisco Campaign 260

Startup Lessons Learned

AUGUST 24, 2009

What is the right revenue model? Aside from the dramatically shorter development cycle that browser games enjoy, the split testing of features (which is intuitive to web application makers) is something that propelled Zynga's games and revenues to the top of the social games vertical. April 23, 2010 in San Francisco.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

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

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? April 23, 2010 in San Francisco. Bring your questions.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

DECEMBER 28, 2009

There are huge classes of bugs that "work as designed" but cause catastrophic changes in customer behavior. No automated test is going to catch that, but it still will drive revenue to zero. Most QA teams are organized around finding reproduction paths for bugs that affect customers. April 23, 2010 in San Francisco.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Steve Blank

OCTOBER 10, 2016

How founders find the determination to push through tough times was the focus on today’s Entrepreneurs are Everywhere radio show. The show follows the journeys of founders who share what it takes to build a startup – from restaurants to rocket scientists, to online gifts to online groceries and more. Jacqueline Ros. Christina Stembel.

Entrepreneur 120

Entrepreneur Cofounder San Francisco Campaign 120

Startup Lessons Learned

OCTOBER 23, 2013

In the Udemy course, Alistair and Ben expand these basics into a description of how to create empathy, stickiness, virality, revenue, and scale. Stickiness, Ben and Alistair say, is where people move on too quickly--they don’t make sure they really have a product that has the right features and functionality to meet their customers’ needs.

Analytics 167

Analytics Lean Widget Metrics 167

Startup Lessons Learned

AUGUST 16, 2010

It requires separating the product launch from the marketing launch (see Dont Launch ) as well as other staple Lean Startup tactics: minimum viable product, split-testing, customer development and the pivot. That is customer development. “But it never happened.&# [Alas, customers dont know what they want!

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

Startup Lessons Learned

OCTOBER 30, 2008

Not just about expenses, about increasing revenue. Make sure for planned revenues you have "leading indicators" to know if you will hit it. Over-communicate with employees, investors, customers. This can take the form of a traditional sales pipeline or a registration-activation-revenue chart. Offer equity instead of cash.

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? April 23, 2010 in San Francisco. No departments The Five Whys for Startups (for Harvard Business R. Bring your questions.

San Francisco 148

San Francisco Lean Continuous Deployment DC 148

Startup Lessons Learned

NOVEMBER 22, 2008

It took us months to realize what we had done, and to eventually apologize and win back the trust of those customers wed alienated. 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.

.Net 158

.Net Operations San Francisco Lean 158

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. As a founder of a company, there is nothing more painful than to see your most loyal and devoted customers suffering. That is what company founders and staff do not get.

Community 158

Community Management Lean Software Review 158

Steve Blank

MAY 17, 2011

After I left the military, I ended up in Palo Alto, a town south of San Francisco. As time went on, I was a co-founder or member of the starting team for six high-tech startups…. In 1999… with the company’s revenue north of $100 million…I handed the keys to a new CEO and left. I had just turned 20 years old.

Philadelphia 335

Philadelphia Miami Thailand Silicon Valley 335

Startup Lessons Learned

JULY 9, 2009

We were focused on revenue, but we didnt understand that revenue is not important for its own sake in an early stage company. In fact, I remember sending him and his obscure-to-me co-founder (aka Reid Hoffman ) a bug report early-on, instead of taking them up on their offer of an in-person meeting. Bring your questions.

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? April 23, 2010 in San Francisco. A: yes, absolutely.

Lean 60

Lean San Francisco Startup Continuous Deployment 60

maplebutter.com

JANUARY 8, 2013

I would focus on one product and set a goal to generate $1M in yearly revenue from it. Near shoring development with your team (ex: your team is based in Canada / India) is cool, but not outsourcing. Outsourcing is something a big company, with a known customer / problem (that has revenue & traction) does to save cost.

Technical Review 44

Technical Review Startup Cofounder Software Review 44

Up and Running

JULY 14, 2015

Read also: Q&A with Business Incubator Co-founder Joe Maruschak. Peter: Yeah, that’s a perfect question for a recent article we posted called Q&A with Business Incubator Co-founder Joe Maruschak. The second reason is actually still a part of team but it’s the single founder. Startup Incubators – (2:13).

Incubator 60

Incubator Email Startup Oregon 60