This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Lessons Learned by Eric Ries Monday, June 15, 2009 Why ContinuousDeployment? Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuousdeployment , a process that allows companies to release software in minutes instead of days, weeks, or months.
Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuousdeployment 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.
Lessons Learned by Eric Ries Monday, December 28, 2009 Continuousdeployment for mission-critical applications Having evangelized the concept of continuousdeployment for the past few years, Ive come into contact with almost every conceivable question, objection, or concern that people have about it.
This slinging of whatever against the wall to see what sticks does not a market make, is to me a sign of too much capital in the wrong hands, and it's already the most over invested area in recent years- in both human and financial capital- particularly relative to revenue. Case Study: Continuousdeployment makes releases n.
Its had tremendous impact in many areas: continuousdeployment , just-in-time scalability , and even search engine marketing , to name a few. When operating with continuousdeployment, its almost impossible to have integration conflicts. Case Study: Continuousdeployment makes releases n. Small is beautiful.
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: Continuousdeployment makes releases n.
Lessons Learned by Eric Ries Tuesday, April 14, 2009 Validated learning about customers Would you rather have $30,000 or $1 million in revenues for your startup? All things being equal, of course, you’d rather have more revenue rather than less. And yet revenue alone is not a sufficient goal. More on that in a moment.
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.
► 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. Case Study: Continuousdeployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.
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: Continuousdeployment makes releases n. When the numbers started to go down, they started to investigate.
Not even if its generating 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. Case Study: Continuousdeployment makes releases n.
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: Continuousdeployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuousdeployment for mission-critical applica.
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: Continuousdeployment makes releases n. And if you neglect maintenance, you may not have a business left at all.
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: Continuousdeployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuousdeployment for mission-critical applica.
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.
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: Continuousdeployment makes releases n. The key is to be able to refute as many major hypotheses as you can.
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: Continuousdeployment makes releases n.
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.
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.
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: Continuousdeployment makes releases n.
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: Continuousdeployment makes releases n. If you dont make predictions ahead of time, theres no way to call you on it.
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: Continuousdeployment makes releases n. Two Ways to Hold Entrepreneurs Accountable (for Ha.
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.
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.
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.
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: Continuousdeployment makes releases n.
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.
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: Continuousdeployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuousdeployment for mission-critical applica.
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: Continuousdeployment makes releases n.
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."
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content