Startup Lessons Learned

MAY 27, 2009

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? Case Study: Continuous deployment makes releases n. Thanks for an enjoyable evening.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

JANUARY 1, 2009

I see that as a great way for my product to grow, but while Ive partnered with companies in my consulting business, its not something Im as familiar with now that Im on the product side. I question what numbers I would need to be considered respectable and/or worth a potential partners time. January 2, 2009 4:53 AM Dave McClure said.

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

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

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

Software Review 94

Software Review Technical Review San Francisco Part-Time VPE 94

Startup Lessons Learned

APRIL 7, 2010

What about companies, like Siebel, that started with partner distribution first? For more on how to figure out which question applies in which context, see Business ecology and the four customer currencies.) It’s the difference between asking “how should we best solve this problem for these customers?&#

San Francisco 154

San Francisco Lean Metrics Design 154

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. Similarly, let me know if youd like to host or attend a simulcast party in your town. Even if you cant attend, you can help shape the curriculum.

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