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? Lets return to our team thats failing to hit their targets.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

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. When we’re optimizing, product development teams encounter similar situations. I mean, here we are, paying them to be there, and they won’t use the product!

San Francisco 154

San Francisco Lean Metrics Design 154

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

NOVEMBER 8, 2008

Customer development is a parallel process to product development, which means that you dont have to give up on your dream. Our goal in product development is to find the minimum feature set required to get early customers. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Customer Development 168

Customer Development Developer San Francisco Customer 168

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?

Metrics 167

Metrics San Francisco Lean Continuous Deployment 167

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. In a startup context, numbers like gross revenue are actually vanity metrics, not actionable metrics.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

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

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

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

DECEMBER 28, 2009

Thats a perfectly reasonable reaction, given that most releases of most products are bad news. Even worse, the sad state of product development generally means that the new "features" are as likely to be ones that make the product worse, not better. Its likely that the new release will contain new bugs.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

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? Take a look and let me know what you think.

Lean 68

Lean San Francisco Continuous Deployment Startup 68

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 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? Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 68

San Francisco Lean Continuous Deployment DC 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

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. The real value we create is learning how to craft profitable ecosystems.

Customer 156

Customer San Francisco Viral Lean 156

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. It lets the customer and development team spot problems with calculations almost immediately.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 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. This can take the form of a traditional sales pipeline or a registration-activation-revenue chart. And its hard to know if youre truly succeeding without a focus on revenue.

Lean 121

Lean San Francisco Continuous Deployment DC 121

ConversionXL

NOVEMBER 29, 2018

Freemium and free-trial signups have one thing in common: Neither generates revenue. This post details the freemium and free-trial models and considers the key questions—about your business, your market, and your product—that guide you toward the best option. To generate that financial support, a SaaS product needs mass appeal.

Customer 119

Customer Conversion Acquisition B2B 119

Startup Lessons Learned

JANUARY 27, 2009

These are companies that generate revenue by offering a free product with an upsell or premium version. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th.

San Francisco 148

San Francisco Lean Continuous Deployment DC 148

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. Almost all of them got scooped up by pre-IPO Google this time. That year, right before the IPO, those months mattered a great deal in terms of financial outcomes.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

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

AUGUST 16, 2010

Realizing it had taken a wrong turn, SlideShare rethought its approach to premium accounts and ultimately performed what we’d call a value capture pivot , one where the company changes the way it collects revenue from customers. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

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? A: yes, absolutely. No departments The Five Whys for Startups (for Harvard Business R.

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. "This single decision wound up costing the company significant revenue and over the course of several months sent its customer growth into decline."

Community 158

Community Management Lean Software Review 158