Building the Company

Do More Faster

TechStars Lessons to Accelerate Your Startup

Brad Feld & David Cohen · 2010 · Wiley

Short, practical essays from the Techstars accelerator on moving fast, using mentors well, and avoiding common early mistakes.

The big idea

What the book argues

Feld and Cohen collect short essays from Techstars founders and mentors, organized around the themes the accelerator teaches. The common thread is that speed comes from focus and fast feedback, not long hours alone: cut the plan to what matters, put the product in real users' hands early, treat conflicting advice as input to test, and choose investors and teammates carefully. An accelerator's deadlines and mentor network act as a forcing function that any founder can partly recreate.

Key takeaways

7 ideas worth keeping

1

Speed comes from subtracting, then sprinting

Moving fast is less about hustle than about stripping the plan to the one or two things that matter and shortening feedback loops. A team that ships something rough early learns more than one perfecting a spec for months. Every extra feature or initiative slows down the learning that actually matters.

2

The accelerator's real value is the forcing function

The cash an accelerator invests is modest. The bigger benefits are dense access to mentors, a cohort working at the same pace, an alumni network, and a fixed demo day with an audience. Deadlines that other people will witness force decisions that founders otherwise postpone.

3

Give before you get, and keep no score

Techstars culture asks people to help others first without keeping score: make the introduction, share the insight, answer the question. Over time this builds the relationships that lead to warm introductions, mentors who go to bat for you, and early checks. It is a long game, not a transaction.

4

Treat mentor whiplash as data to test

In a program with many mentors, founders hear confident, contradictory advice. The answer is neither to obey the loudest voice nor to split the difference. Collect the advice, identify where it truly conflicts, and design a quick test with customers to settle it. Evidence, not seniority, breaks the tie.

Illustration: One mentor says sell to large enterprises, another says small businesses: run a set of discovery calls with each and let the results decide.
5

Usage is like oxygen for ideas

That essay title, from WordPress founder Matt Mullenweg, captures a core theme: a product only starts teaching you once real people use it. Release earlier than feels comfortable, even as a manual or concierge version, because a rough product in users' hands beats a polished one nobody has touched.

6

Choose investor quality over the highest price

The biggest valuation is not always the best deal. A poor-fit investor or an inflated price can lead to a painful board relationship and a down round later. Check investor references the way you would check a co-founder, including founders whose companies struggled. Price is one term among many.

7

Get people decisions right, including founder vesting

Several essays stress that people mistakes compound quickly: hire carefully, address poor fits quickly, and put vesting on founder shares early. Vesting protects the company and the remaining founders if someone leaves, and it is ordinary practice, not a sign of distrust. Agree on it before outside investors ask.

The framework

The accelerator rhythm you can recreate

01

Meet many mentors

Early on, take lots of advice meetings and record every suggestion without acting on all of it.

02

Pick the focus

Cut to the one or two bets that matter most; drop the rest.

03

Ship and test

Get usage quickly and use customer tests to settle conflicting advice.

04

Demo to an audience

Set a fixed date to present progress to people whose opinion matters.

“Usage is like oxygen for ideas.”

— Matt Mullenweg, in Do More Faster

Apply it this week

Three moves to make now

  1. Set a fixed demo date about 90 days out, invite real people to it, and plan weekly progress backward from that date.
  2. Each week, do one genuinely useful thing for a contact, such as an introduction or insight, without asking for anything.
  3. When advisors disagree, write down both views and design the smallest customer test that would settle it.

Read next

Pairs well with

This page is an original summary and commentary prepared by XRAYCLOUD.AI with AI assistance. It is not affiliated with or endorsed by the author or publisher, and it is no substitute for the book — read it for the full argument.