Startup Lessons Learned

AUGUST 16, 2010

It requires separating the product launch from the marketing launch (see Dont Launch ) as well as other staple Lean Startup tactics: minimum viable product, split-testing, customer development and the pivot. SlideShare asked customers what they had expected in the product; the responses were often literal descriptions.

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

www.instigatorblog.com

MARCH 2, 2010

The Board probably existed beforehand, but was made up only of the founders. We have been lucky enough to have formed strong relationships with family friends and past co-workers, to have a very informal Board of Advisors on hand. Once funding takes place, the angels or VCs will want a seat at the table.

Advisory Board 40

Advisory Board Startup Cofounder Equity 40

Startup Lessons Learned

OCTOBER 7, 2008

Lessons Learned by Eric Ries Tuesday, October 7, 2008 The App Store after the gold rush I wrote earlier about the issue of distribution advantage on the iPhone. Customers and prospects are overwhelmed by the number of media and companies clamoring for their attention. October 13, 2008 8:25 AM Eric said.

San Francisco 68

San Francisco Lean Retention SEM 68

Startup Lessons Learned

JANUARY 6, 2009

The first event is January 21, and is being put on by Dealmaker Media as part of their Strategy Series events: In the Trenches: Cutting Costs in a Tight Economy. One of the other speakers is someone I know well: Seth Sternberg , founder of Meebo. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

FEBRUARY 24, 2009

I liked the flattering Venture Hacks commentary so much Ill just quote it: Many founders believe that early stage startups are endeavors of execution. The customer is known, the product is known, and all we have to do is act. The customer is unknown, the product is unknown, and startups must be built to learn.

Lean 74

Lean San Francisco Continuous Deployment DC 74

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. Sorry about that.)

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

DECEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, December 7, 2008 The hackers lament One of the thrilling parts of working and writing in Silicon Valley is the incredible variety of people Ive had the chance to meet. Labels: five whys root cause analysis , product development 8comments: William Pietri said. December 9, 2008 3:10 AM Amy said.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

MARCH 13, 2009

Do some Customer Development instead. Founders push for it. In some ways, founders are even worse. My experience is that many founders actually have a deep anxiety that maybe they are not succeeding. We used social media to get alpha users as outlined here during Feburary. Help you raise money.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

NOVEMBER 22, 2008

Lessons Learned by Eric Ries Saturday, November 22, 2008 Net Promoter Score: an operational tool to measure customer satisfaction Ive mentioned Net Promoter Score (NPS) in a few previous posts, but havent had a chance to describe it in detail yet. November 26, 2008 9:23 AM Andrew Meyer said. Nice post. Brookeside can do that.

.Net 158

.Net Operations San Francisco Lean 158

SoCal CTO

AUGUST 3, 2010

That’s @MeganBerry to you, blogger and social media expert, marketing manager of Klout.com. Startup Culture Lessons From Mad Men - OnStartups , July 26, 2010 The following is a guest post by Brian Halligan who is my co-founder and CEO at HubSpot (which means he gets to do most of the really hard work). at a $2.5M

Software Review 217

Software Review Startup Venture Capital Technical Review 217