The Next Web

DECEMBER 2, 2013

We interviewed the heads of the top Web and mobile development companies, incubators, agencies and labs to understand what it takes to design and develop the most successful apps of our generation. Here are their breakdowns of the costs and time investments to create 10 of the world’s hottest startups. 1) Twitter.

Cost 168

Cost San Francisco New York City Ruby 168

Business Plan Blog

AUGUST 20, 2013

Every Tech Startup Needs a Chief Technical Officer. In order to be a successful tech startup, the team must consist of a Chief Technical Officer (CTO) level member to help with the technology plan. This is generally achieved in one of the following ways: CTO Level Co-Founder (Equity). CTO Employee (Salary).

CTO Hire 55

CTO Hire Fractional CTO Architecture Cofounder 55

Business Plan Blog

OCTOBER 4, 2013

Aligning the Startup Team Strategy with the Capitalization Strategy. The single most important factor to raising capital for any tech startup is the management team. A bonafide team is the assurance that the idea can be executed and that the business can scale when the time is right. Don’t make everyone a founder.

Part-Time VPE 79

Part-Time VPE Fractional VPE Cofounder CTO Hire 79

View from Seed

MAY 11, 2016

The last time they were starting a company at the raw, pre-product/market fit stage may have been quite a few years ago. The context of starting business may have changed, and some of the tools and practices (especially around early product development and go-to-market) might look very different.

Founder 159

Founder Cofounder CTO Hire Early Stage 159

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. I agree with the less is more product development approach, but for a different reason. Now that is fun.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

OCTOBER 4, 2008

(Maybe youd like to start with The lean startup , How to listen to customers , or What does a startup CTO actually do? ) He serves on the advisory board of a number of technology startups, and has worked as a consultant to a number of startups, companies, and venture capital firms.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

DECEMBER 7, 2008

Those who have the endurance are the ones that tend to lead teams and join startups, because you just cant be successful in a startup situation without empathy. When a startup encounters difficult technical problems, this is the guy you want solving them. I would characterize them as intolerant but not arrogant. Just change it.

Software Review 94

Software Review Technical Review San Francisco Part-Time VPE 94

Startup Lessons Learned

SEPTEMBER 7, 2008

The basic idea is to extend agile, which excels in situations where the problem is known but the solution is unknown, into areas of even greater uncertainty, such as your typical startup. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own. Talk about waste.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

SEPTEMBER 10, 2008

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. are the parts of the Joel Test I think are most out-of-date.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. First of all, why split-test?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

JULY 28, 2010

kaChing has been very active in the Lean Startup movement. With case studies like this, we aim to illustrate specific Lean Startup techniques through the stories of current practitioners. Yet there’s a lot of mystery around pivots, and entrepreneurs ask all the time how you know it’s time to commit to a new direction.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

MAY 7, 2009

For people we hired from larger companies especially, this was challenging. When a new engineer started at IMVU, I had a simple rule: they had to ship code to production on their first day. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? May 11, 2009 9:42 PM Artem said.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

Startup Lessons Learned

SEPTEMBER 2, 2008

This simple feedback loop has proven its worth to me time and again. Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. There are three stages: We start with ideas about what our product could be.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

SEPTEMBER 13, 2008

Only much later did I realize that this was an application of customer development to online marketing. Its now a technique I recommend for any web-based startup. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

SEPTEMBER 2, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. The new startup arms race (for Huffington Post) For Startups, How Much Process Is Too Much?

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Venture Chronicles

AUGUST 2, 2013

I have covered a couple of topics in this series, the first being hiring the best people and the second organizing for success based on the attributes of the people you are hiring. 3) It all starts with the product: Companies can overcome a great many challenges with band-aids, duct tape, and bailing wire.

Product 62

Product CTO Hire Architecture Startup 62

Startup Lessons Learned

JUNE 22, 2009

Lessons Learned by Eric Ries Monday, June 22, 2009 Pivot, dont jump to a new vision In a lean startup , instead of being organized around traditional functional departments, we use a cross-functional problem team and solution team. Each has its own iterative process: customer development and agile development respectively.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

SEPTEMBER 12, 2008

0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May. . Expo SF (May.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 14, 2008

Most of the people building our product werent themselves target customers. So there was simply no substitute for seeing actual customers with the product, live. Today, when I talk to startup founders, the most common answer I get to the question "do you talk to your customers?" The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

SEPTEMBER 5, 2008

October 13, 2008 9:44 PM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May. . Expo SF (May.

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective. Expo SF (May. . Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Steve Blank

JULY 30, 2009

That is until I saw that in startup after startup customers come from places you don’t plan on. If that’s you, by all means hire a VP of Sales with a great rolodex and call on established mainstream companies – and ignore the rest of this post.

Silicon Valley 146

Silicon Valley RSS California Customer Development 146

Startup Lessons Learned

SEPTEMBER 18, 2008

I want to get an idea of how startup guys think. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. Startup Lessons Learned - the Conference (April 23.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

SEPTEMBER 28, 2008

Lessons Learned by Eric Ries Sunday, September 28, 2008 The lean startup comes to Stanford Im going to be talking about lean startups (and the IMVU case in particular) three times in the next two weeks at Stanford. I struggle to try and make the students actually experience how confusing and frustrating startup environments are.

Lean 68

Lean San Francisco Startup Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: continuous deployment 0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 18, 2008

April 27, 2009 10:55 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May. . Expo SF (May.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

SEPTEMBER 8, 2008

Lessons Learned by Eric Ries Monday, September 8, 2008 Waves of technology platforms I still remember the first time I switched to LAMP. I was building a new startup in 1999, and wanted to do it right. So one of the first things we did was to hire an Oracle expert and get to work. Looking back, that was a special moment.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

SEPTEMBER 1, 2008

Labels: Test-driven development 0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?)

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 10, 2008

I see startups struggle with this all the time. You have customers, they are using your product, and you are trying to help them. Update : bonus thought from Dharmesh Shahs 8 Startup Insights Inspired By The Mega Mind of Seth Godin: 6. No departments The Five Whys for Startups (for Harvard Business R. Expo SF (May.

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

SEPTEMBER 10, 2008

0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May. . Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment DC Lean 60

Startup Lessons Learned

SEPTEMBER 6, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. The new startup arms race (for Huffington Post) For Startups, How Much Process Is Too Much?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 16, 2008

thanks for the mention:) September 17, 2008 11:56 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?)

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 2, 2008

A growing startup with a well-run product team will have a history of steady progress. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 You dont need as many tools as you think Im always excited to see someone else writing about lessons learned from their startup, and wanted to link today to Untitled - Startup Lessons Learned -- Take it with a grain of salt. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 29, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. The new startup arms race (for Huffington Post) For Startups, How Much Process Is Too Much?

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

David Teten

OCTOBER 1, 2015

I’ve been looking for suggestions for an initial deal structure that is appropriate for the theoretical case of a trusted dev shop putting in $100k in market-value of services over a 6 month period in time. How would one set up such a startup to eventually raise capital from outside VCs, who will be wary of ‘dead equity’ (i.e.,

Software Developers 60

Software Developers Software Development Software Review Technical Cofounder 60

Hippoland

OCTOBER 9, 2016

I just passed my 2 year mark at 500 Startups. This is one of my favorite startup presentations of all time by Mike Cassidy on going fast. Demonstrate that you can pull the trigger on things quickly — whether it be getting customers, hiring / firing employees, or product development.

Seed Stage 48

Seed Stage CTO Hire Email Later Stage 48