Module 4.2: Enterprise Platform Economics
Platform Tax, developer experience ROI, platform team economics, and measuring the multiplier effect of internal platforms.
Lesson 1: Platform vs. Product Thinking
A platform multiplies the productivity of every team that builds on it. Platform investment compounds; product investment is linear. Understanding when to invest in platform is the highest-leverage decision in engineering.
The overhead each product team pays to deal with platform deficiencies: manual deployments, inconsistent tooling, missing abstractions. This is the equivalent of Innovation Tax at the infrastructure level.
Platform investment = (time saved per team per sprint × number of teams × burdened rate × sprints per year) - platform team cost. ROI compounds as teams grow.
Too early (< 3 teams): overhead exceeds benefit. Sweet spot (5-15 teams): maximum leverage. Too late (> 20 teams): debt is entrenched and expensive.
Calculate your organization's Platform Tax: hours lost per team per sprint to platform friction × teams × burdened rate. Is a platform team justified?
Lesson 2: Developer Experience as Investment
Developer experience (DX) directly impacts velocity, retention, and quality. Every minute a developer waits for a build, fights with tooling, or navigates unclear docs is money burned.
A 10-minute build wastes 40-60 minutes per developer per day (context switching included). For a 50-person eng org: 40+ hours/day wasted. At $100/hr: $4K/day burned on build time alone.
How long until a new hire ships their first PR? This is a proxy for DX quality. Good DX: day 1-2. Poor DX: week 3-4.
Developers leave companies with bad tooling. 68% of developers cite DX as a factor in job satisfaction. Replacing an engineer costs $50K-150K.
Measure your DX: build time, onboarding time-to-first-PR, and developer satisfaction survey (1-10). Calculate the cost of each minute of build time across your team.
Lesson 3: Platform Team Economics
Platform teams are cost centers that create value through leverage. Measuring this value is critical — otherwise platform investment gets cut during budget pressure.
Track: hours of manual toil eliminated per sprint. Multiply by the rate of the people no longer doing toil. This is the platform team's primary value metric.
Platform improvements (better CI/CD, infrastructure-as-code, automated testing) reduce incidents. Track: incident count and MTTR before and after platform changes.
Measure: features shipped per team per quarter before and after platform investment. The multiplier effect shows the platform's leverage on the entire organization.
If you have a platform team: calculate total toil eliminated, incident reduction, and velocity improvement. If you don't: estimate potential savings from a 3-person platform team.