Surface Area

You're seeing it when your product's feature set has expanded to the point where every new release risks breaking something else. The surface area of the codebase has grown faster than the team's ability to maintain it.

You're seeing it when expanding into a new geography increases customer acquisition but also multiplies regulatory, logistical, and support complexity. The surface area grew on both sides of the ledger.

You're seeing it when a security audit reveals that each new integration and vendor partnership has added another attack surface. More connections mean more exposure.

Early stage: keep surface area small and focused on the core value proposition. Growth stage: expand surface area deliberately into channels and markets where the marginal exposure is asymmetrically positive. At every stage: prune surface area that creates more maintenance, risk, or complexity than it returns in value.

Leonard built Constellation Software into one of the most valuable Canadian companies by obsessively managing surface area. Constellation acquires hundreds of vertical-market software companies, giving it enormous market surface area — exposure to thousands of customer segments across dozens of industries. But Leonard constrains organizational surface area through radical decentralization: each acquired company operates autonomously, limiting the complexity that typically accompanies sprawling conglomerates. The insight is that you can have high commercial surface area (many markets, many customers) without high organizational surface area (centralized coordination, shared systems) if the architecture is designed correctly. Founders expanding into multiple markets should ask whether their organizational structure can handle the surface area their strategy demands.