Startup Lessons Learned

AUGUST 26, 2009

As a result, the companies get a lot of exposure to VCs, investors, and partners in larger, more traditional startup hubs. And do your customer development. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Some of the mentors are based in Boulder, but many are not.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

MAY 27, 2009

This will be an in-depth discussion with a handful of entrepreneurs and founders that have been pre-selected. Herein lies the reason my partner and I started Dillotronics - as well as the reason your take on the matter resonated so well here. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

JUNE 8, 2009

I got a powerful taste of datablindness recently, as I’ve started to work with various large companies as partners in setting up events, speeches, and other products to sell around the Lean Startup concept. There are lots of good reasons why I can’t have instantaneous access to this data, and each partner has their own.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

JANUARY 1, 2009

As for a topic Im particularly interested in, Id be curious about partnerships: the type of formal or informal relationships one tech co has with another in terms of either cross marketing or integrating each others products. I question what numbers I would need to be considered respectable and/or worth a potential partners time.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

MARCH 13, 2009

Establish credibility with potential partners. You need to combine your product with others, and this requires partners like OEMs or system integrators. A marketing launch can help you get in the door with those partners, if youre having trouble getting their attention. Do some Customer Development instead.

San Francisco 168

San Francisco PR Lean Early Stage 168

techcrunch.com

OCTOBER 23, 2010

Tech Gadgets Mobile Enterprise GreenTech CrunchBase TechCrunch TV Disrupt SF More TechCrunch TV Beta Invites Crunchies Elevator Pitches Gillmor Gang Podcasts TechCrunch Europe TechCrunch Trends TechCrunch France TechCrunch Japan Whats Hot: Android Apple Facebook Google Microsoft Twitter Yahoo Zynga Subscribe: From Nothing To Something.

Technical Review 84

Technical Review Cofounder Technical Cofounder Software Review 84

Startup Lessons Learned

OCTOBER 6, 2008

Lessons Learned by Eric Ries Monday, October 6, 2008 When NOT to listen to your users; when NOT to rely on split-tests There are three legs to the lean startup concept: agile product development , low-cost (fast to market) platforms , and rapid-iteration customer development. Or to some passionate customers. Were doomed!

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

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

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. What about companies, like Siebel, that started with partner distribution first? and for which customer? and for which customer?

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

DECEMBER 7, 2008

At the end of the day, the product development team of a startup (large or small) is a service organization. It exists to serve the needs of customers, and it does this by offering its capabilities to other functions in the company, and partnering with them. No departments The Five Whys for Startups (for Harvard Business R.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

OCTOBER 23, 2009

This is especially useful in situations, like most B2B businesses, where the total number of customers is likely to be small. This case study illustrates one company’s attempt to do customer development by testing their vision with customers before writing a single line of code. Oh, this is just a Photoshop file?

San Francisco 144

San Francisco Customer Wiki Lean 144

Startup Lessons Learned

JANUARY 2, 2010

Sure, when entrepreneurs create startups that grow up into mature companies, they become part of an established industry, with its own ecosystem, norms, partners and best practices. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Teaching at Berkeley (and beyond).

San Francisco 122

San Francisco Lean Continuous Deployment DC 122

Startup Lessons Learned

SEPTEMBER 11, 2009

But it became clear that if IMVU was ever going to become a mainstream business, we had to effectively fire these early customers. Suffice to say that our partners, vendors, and most importantly regular mainstream customers all found the idea disturbing. The reasons were many and complex, so I won’t rehash them all here.

Community 158

Community Management Lean Software Review 158