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

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

OCTOBER 23, 2013

Alistair and Ben, co-authors of the book Lean Analytics, will help you sort it out in our next webcast, Lean Analytics for Non-tech Companies. In the Udemy course, Alistair and Ben expand these basics into a description of how to create empathy, stickiness, virality, revenue, and scale. Alistair: There are plenty.

Analytics 167

Analytics Lean Widget Metrics 167

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

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

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

Up and Running

MAY 23, 2016

Since the term “cloud computing” was coined in 1996—at least as we have come to understand its meaning—the software as a service industry has exploded. In fact, SaaS industry revenue is projected to grow from $49 billion in 2015 to $67 billion in 2018, a compound annual growth rate of approximately eight percent.

Software Review 74

Software Review Software Delaware Forecast 74

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

SoCal CTO

DECEMBER 1, 2010

Equity-Only CTO and Equity-Only Developers - SoCal CTO , November 1, 2010 I had a recent email dialog with the founder of a company looking for a CTO for their startup. And I tried to evaluate the idea and figure out: What did the founder really need here? Was it a Startup Founder Developer Gap ? You got it.

Technical Review 175

Technical Review Technology Product CTO Hire 175

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

www.readwriteweb.com

OCTOBER 18, 2010

These are areas that may be gaps in the portfolio of large companies, and are perfect for M&A deals in three to five years after building enough validation and $10-$20 million in revenue. Raymond has built a nice business through efficient distribution deals and will do about $250,000 in revenue this year.

Marketing 52

Marketing Bootstrapping Incubator Angel Investor 52

www.readwriteweb.com

OCTOBER 18, 2010

These are areas that may be gaps in the portfolio of large companies, and are perfect for M&A deals in three to five years after building enough validation and $10-$20 million in revenue. Raymond has built a nice business through efficient distribution deals and will do about $250,000 in revenue this year.

Marketing 52

Marketing Bootstrapping Incubator Angel Investor 52

Startup Lessons Learned

AUGUST 16, 2010

Rashmi Sinha, co-founder and CEO of SlideShare , describes an early version of the analytics package that’s part of the Pro accounts the company announced today. If your company is using minimum viable product , you’ve probably said the same thing yourself. The process started with a few moving parts.

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

Startup Lessons Learned

JANUARY 27, 2009

These are companies that generate revenue by offering a free product with an upsell or premium version. For founders, I think it also has another big attraction: the ability to avoid a lot of " free vs paid " arguments. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

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. 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.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

FEBRUARY 10, 2009

In a lot of cases, thats just a fancy name for revenue or profit, but not always. This was an effective approach to discovering a business by using a sequence of product prototypes to get early customer feedback. It would be hard to argue against this product development strategy, in general. If it didnt, wed trash it.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

www.quora.com

JANUARY 16, 2011

Find Questions, Topics and People Add Question Add Question Non-Technical Co-Founders Co-Founders Technical Co-founders Finding Co-Founders Startups & "How Important Are Ideas?" " Web Development Startups Solo Founders I am a creative guy with a startup idea.

Developer 42

Developer Technical Review Cofounder Technical Cofounder 42

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). The key is to be able to refute as many major hypotheses as you can.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

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

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

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

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.) 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. Will start to pay attention.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

SEPTEMBER 13, 2008

And one day a remarkable thing happened: we started making more than five dollars a day in revenue. ► 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.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

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. Minimum viable product is a tactic for mitigating risk.

Customer 156

Customer San Francisco Viral Lean 156

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

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

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

mashable.com

MAY 24, 2011

May 23, 2011 by Christina Warren 20 Share on Tumblr email share Share on Tumblr email share The Mobile App Trends Series is supported by Sourcebits , a leading product developer for mobile platforms. Sourcebits offers design and development services for iOS, Android, Mobile and Web platforms. My 2 cents.

Mobile 90

Mobile Web Social Media Software Review 90

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

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