Startup Lessons Learned

NOVEMBER 8, 2008

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, and more ► January (6) Lo, my 18891 subscribers, who are you?

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. Case Study: Continuous deployment makes releases n. When the numbers started to go down, they started to investigate.

Metrics 167

Metrics San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

MAY 9, 2012

The problem is when you’re chasing revenue; any and all customers will seem like the right customer. Like Continuous Deployment, whereby IMVU deployed changes to their web application +50 times per day, BetaBrand's aim is to put out a new product every day. It was a fairly organic thing.

Entrepreneur 167

Entrepreneur Lean Southern California San Diego 167

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. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

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

NOVEMBER 17, 2008

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. Case Study: Continuous deployment makes releases n. And if you neglect maintenance, you may not have a business left at all.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

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. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

OCTOBER 21, 2013

So we spent some time iterating--leanly, we thought--on the revenue model. Lastly, we used to track deploys to production because we were so proud of our continuous deployment practice, but past a certain threshold (we are somewhere north of 200 deploys a month) this is a vanity metric. Challenge #2: Technical Debt.

Lean 152

Lean Startup Metrics Silicon Valley 152

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. Case Study: Continuous deployment makes releases n.

Customer 156

Customer San Francisco Viral Lean 156

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. Case Study: Continuous deployment makes releases n. 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

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

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. August 24, 2009 2:17 PM Norbert Mocsnik said.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

APRIL 7, 2010

Should you charge from day one, testing the revenue model first? Their speed should be measured in validated learning about customers, not milestones, features, revenue, or even beautiful design. Should you charge from day one, testing the revenue model first? Case Study: Continuous deployment makes releases n.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

SEPTEMBER 29, 2008

Revenue is always my preferred measure, but you can use anything that is important to your business: retention, activation, viral invites, or even customer satisfaction in the form of something like net promoter score. Case Study: Continuous deployment makes releases n. Two Ways to Hold Entrepreneurs Accountable (for Ha.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

FEBRUARY 10, 2009

Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuous deployment and continuous learning At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it. At IMVU it’s a core part of our culture to ship.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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

usersknow.blogspot.com

APRIL 30, 2010

It’s not enough to just launch a feature and see if your revenue increases. You need to have some sort of plan for testing to see how it’s affecting key metrics , whether those are revenue, retention, registration, user happiness, or some other number you care about. How Am I Going to Get Feedback on this Feature?

Software Review 40

Software Review Agile San Francisco Metrics 40

Startup Lessons Learned

DECEMBER 28, 2009

Lessons Learned by Eric Ries Monday, December 28, 2009 Continuous deployment for mission-critical applications Having evangelized the concept of continuous deployment for the past few years, Ive come into contact with almost every conceivable question, objection, or concern that people have about it.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Startup Lessons Learned

JANUARY 27, 2009

These are companies that generate revenue by offering a free product with an upsell or premium version. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 148

San Francisco Lean Continuous Deployment DC 148

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

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. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

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?" Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Lean 60

Lean San Francisco Startup Continuous Deployment 60

Startup Lessons Learned

SEPTEMBER 22, 2008

is an elegant way to model any service-oriented business: Acquisition Activation Retention Referral Revenue We used a very similar scheme at IMVU, although we werent lucky enough to have started with this framework, and so had to derive a lot of it ourselves via trial and error. Case Study: Continuous deployment makes releases n.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

AUGUST 1, 2009

Not even if its generating revenue. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Heres hoping Steve will share those techniques with us someday.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

SVPG

NOVEMBER 22, 2013

But one of the real advantages from a product point of view is that there’s no legacy to drag along, there’s no revenue to preserve, and there’s no reputation to safeguard. Protect Revenue and Brand. In addition to protecting revenue and brand, we also need to protect our employees and our customers.

Product 67

Product NDA Continuous Deployment Reputation 67

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. Case Study: Continuous deployment makes releases n. If you dont make predictions ahead of time, theres no way to call you on it.

Lean 68

Lean San Francisco Startup Continuous Deployment 68

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. Case Study: Continuous deployment makes releases n.

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

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

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. Case Study: Continuous deployment makes releases n.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79