Open source contribution is often framed as altruism — giving back to the community. The more compelling business case is strategic. Companies that contribute meaningfully to open source attract better engineers, build stronger technical reputations, and accumulate influence over the tools their products depend on. The ROI is real; it's just measured in timescales that quarterly business reviews struggle to accommodate.
The Recruitment Signal
Engineers evaluate potential employers by their technical culture. A company with public GitHub repositories, regular contributions to major open source projects, and engineers who speak at conferences signals something important: this is a place where technical excellence is valued for its own sake. The best engineers — the ones you most want to hire — have options. A strong open source presence differentiates your employer brand in a way that perks and salary alone cannot.
Practical Starting Points
You don't need to open-source your entire product to start. Begin with utilities: internal tooling that has no competitive value but solves a problem other engineers face. Developer tools, testing utilities, configuration libraries. Contribute bug fixes and documentation improvements to your key dependencies — you get influence over the roadmap and your engineers develop expertise in the codebase your products rely on. Sponsor maintainers of critical libraries. The open source ecosystem that your business depends on is a shared commons — contribute to its maintenance or accept the risk of building on unmaintained infrastructure.