What pays back the most asks the least of your engineers.
The most valuable way to contribute to open source barely needs your engineers at all. Most companies believe the exact opposite, and that belief costs them more than contributing ever would.
Ask one why it has never given anything back to the software it runs on, and you hear the same answer: we cannot spare the developers. It sounds responsible. It is why they stay stuck.
A while ago I wanted a change in Bitwarden, the open source password manager used by companies and individuals to store their logins. I wanted its authenticator, the part that generates those rotating six-digit sign-in codes, to sync across my devices. I did not write a line of code. I wrote up the request, explained why it mattered, and posted it where the project collects ideas. Months later it shipped. Everyone who uses the tool got it. It cost me an afternoon.
The Linux Foundation put numbers to what that kind of effort returns. It surveyed 567 IT leaders. The highest return of any contribution, 4.8 times the cost, came from foundation membership: paying into the body that stewards a project. It also asked far less of internal engineers than any other form. Writing code returned less, around 3.6 times, and it consumed the most staff time.
And the version everyone pictures is the worst of the lot. Donating full-time engineers to build features is close to the most expensive way to contribute, and it is not even how most of it happens. Reporting a bug, which the study names as the natural place to start, barely counts as effort. The heroic version is mostly a story we tell to excuse doing nothing.
The mistake is counting the wrong resource. Companies act as if the cost of contributing is money. The scarce thing is engineering attention, and the highest-return moves barely touch it. You can sponsor a fix in the shared version everyone uses, the one developers call upstream. You can join the foundation and fund the people who keep the shared version alive. You can file the request, as I did, and let a maintainer, whoever runs the project, decide if it earns their time. None of it pulls your own people off their work.
This is why the study calls contribution an investment, not a donation. And like an investment, it compounds: the study found returns climbing year over year, as organizations grow more efficient at contributing and learn where a small push travels furthest. Fix what other companies also need, and the cost of keeping it alive spreads across all of them instead of landing on you.
You are already paying for open source. The bill just shows up somewhere quieter: in the features you go without, and the private workarounds you keep patching by hand. The only choice is whether that money buys you nothing but invisibility, or something that comes back. What is the smallest thing your organization could send upstream this quarter, and what is actually stopping it?
