Startup Lessons Learned

OCTOBER 28, 2008

We pitch to potential partners, vendors, publishers, conferences, employees, and even lawyers. Dont keep banging your head against the wall - if you cant convince your potential partners that your startup is printing money, try to figure out why. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

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. Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. 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

JUNE 8, 2009

That’s because many of our reports feed us vanity metrics: numbers that make us look good but don’t really help make decisions. Yet even among those who have access to good actionable metrics, I’ve noticed a phenomenon that prevents taking maximum advantage of data. Too much of this data is non- actionable.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

JULY 30, 2009

I thought Id share a little bit of that, too: I’ve been interested in different approaches to software development going back to 1987 when – in my first company Feld Technologies – my partner Dave Jilk and I started talking about “semi-custom software development&# (way ahead of its time).

Lean 68

Lean San Francisco Continuous Deployment DC 68

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? Thanks for an enjoyable evening. June 3, 2009 8:16 PM Tom Gimbel said.

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

APRIL 7, 2010

At least, not in the traditional sense of trying to squeeze every tenth of a point out of a conversion metric or landing page. Instead, we try to accelerate with respect to validated learning about customers. Even if it shows improvement in some micro metric, does that invalidate the overall design? No one feature is to blame.

San Francisco 154

San Francisco Lean Metrics Design 154

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. 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? Startup Lessons Learned - the Conference (April 23.

San Francisco 122

San Francisco Lean Continuous Deployment DC 122

www.vccafe.com

MARCH 11, 2013

Steve Blank on Lean Customer Development. Startup Metrics for Pirates â?? SaaS Metrics Tutorial â?? Mark Suster GRP Partners Advice. Philippe Botteri, Bessemer Venture Partners. Their Partners all come from industry, where each has held senior level executive positions delivering industry-leading products.

Software Review 53

Software Review Technical Review Startup 53

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