Building the Company
An Unorthodox Guide to Making Things Worth Making
Hard-won advice from the leader behind the iPod and Nest on building products, teams, companies and investor relationships.
The big idea
Fadell, who led iPod development at Apple, helped create the iPhone and co-founded Nest, writes a mentor's handbook for people making ambitious products. His advice ranges from career choices to hiring, product design, storytelling and boards. For founders, a few ideas stand out: tell a story that makes people feel the problem before you show the product, change one big thing per version and execute everything else well, make calls without perfect data when you must, and treat investors as long-term partners you choose carefully.
Key takeaways
Fadell compares taking venture money to a marriage: you will be tied to that investor for years, and separating is very hard. The specific partner who joins your board matters more than the firm's brand. Understand their incentives and talk to founders they backed whose companies struggled.
Each round should fund the next proof point, such as a working prototype, a shipped product or repeatable sales, plus a buffer. Too little money starves the company. Too much invites premature hiring and loose spending, and changes culture before you know what you need.
Fadell's storytelling approach, learned in part from Steve Jobs, starts by making the audience feel a problem they had stopped noticing. Then explain why this can be solved now, then show the product. Appeal to both reason and emotion and use one simple analogy people can repeat.
Good ideas tend to share a few traits: something has changed so the idea is possible now, it solves a problem many people face frequently, and you cannot stop thinking about it. Investors are scoring the same things, whether or not they say so. If any one is missing, rethink the idea.
Fadell separates data-driven decisions from opinion-driven ones. When you are building something new, the data you want often does not exist. Gather what you can, make the call, own it, and revisit it as real evidence arrives. Waiting for certainty is itself a decision. Speed of decision is part of the job.
A first version should contain one real breakthrough with strong execution on everything else. Trying to reinvent everything at once means nothing ships well. Version one is for early adopters; later versions fix the mistakes and widen the market. Restraint in V1 is what makes it shippable at all.
A board hires and fires the CEO, approves major decisions and advises. Fadell favors small boards that include operators and independent members, materials sent in advance, no surprises, and meetings spent on a few strategic questions rather than a status recital. Board members should never learn bad news in the meeting.
The framework
| Round | Milestone it should fund |
|---|---|
| Seed | Prove the idea: team, prototype, early signal |
| Series A | Ship the product to real customers |
| Series B | Repeatable sales that do not depend on the founder |
| Later rounds | Scale what already works |
Apply it this week
Read next
A practical guide to building, running, and evolving a startup board so it helps the company instead of just supervising it.
A candid operator's guide to leading when the company might fail: layoffs, firings, bad news, and decisions without good options.
A contrarian case for building something genuinely new, owning a small market outright, and designing for durability from day one.
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.