Build vs. Borrow Product Strategy

Build vs. borrow product strategy is the discipline of deciding which parts of a product must be invented and which can be assembled from existing technologies, components, patterns, or interfaces. In We almost had a smartphone in the 90s. Why did it fail?, General Magic is the overbuilding case, while Tony Fadell’s iPod work at Apple is the borrow-and-compose contrast.

The source says General Magic spent heavily on building operating systems, chips, hardware, servers, interface layers, applications, and other pieces from scratch. Fadell later looked for existing processors, software, batteries, screens, hard drives, and even interface inspiration, using constraints to decide where invention mattered.

Key Claims

• Building from scratch can be justified when the missing capability is core to the product’s customer value.
• Borrowing is not weakness when it accelerates learning, shipping, and focus.
• Too much building can become internal signaling: engineers impress each other while the customer problem remains vague.
• The strategy works with Product Launch Under Constraint because deadlines expose which inventions are necessary.

Connections

• General Magic, Tony Fadell, Apple, and iPod - source contrast.
• Clear Customer Definition, Feature Creep, and Constraint-Driven Product Discipline - decision criteria.
• Product Launch Under Constraint and Fast Feedback Loops - adjacent execution patterns.