One department hands a rival a free system or capability whose maintenance, licensing, and compliance costs arrive later, after the recipient is locked in and turning it down would have looked territorial.
An example
Built by the underwriting division of a regional property insurer, a document-management platform was offered to the claims department at no charge, along with two engineers for the migration. The claims vice president had an aging system and a tight budget, and the chief executive mentioned the offer approvingly at an operating review, so saying no would have looked like turf protection. Claims accepted in January. The engineers went back to underwriting in June, and every change request after that went into underwriting's queue. In the second year the license renewal, $410,000 a year, was charged to claims under the shared-services agreement, and the platform's audit trail brought claims files into the scope of an outside compliance review. By then eight years of claim documents lived in the platform's format, and leaving would have cost more than staying.
Why it works
At the moment of decision the gift looks better than anything the recipient could buy (a working system, a budget saving) and almost free to accept: no procurement fight, no capital request, no friction with the giver. Keeping independent tooling starts to look worse, territorial or wasteful in front of senior leaders. The lifetime costs are deferred and hard to see. Four things make it work: a recipient who cannot model the total cost of ownership before accepting, a norm that makes refusal expensive, integration that creates switching costs, and a giver who controls the maintenance and upgrade path.
The thinking behind it
Robert B. Cialdini Robert Cialdini's Influence (1984) describes reciprocity: people feel obliged to repay what others give them, including favors they did not ask for. A free system arrives with that obligation attached. Turning it down feels ungracious, and once it is accepted, objecting to the giver's later terms feels like ingratitude. Making a polite no acceptable, and treating gifts like purchases, removes the social pull that keeps recipients from looking closely.
Oliver E. Williamson Oliver Williamson's The Economic Institutions of Capitalism (1985) explains asset specificity: investments specialized to one relationship lose much of their value outside it, so the parties become dependent and exposed to being taken advantage of. Data migrated into the giver's platform, staff trained on it, and workflows built around it are exactly such investments. They turn a gift into lock-in, and they are why the time to set terms is before they are made.
George A. Akerlof George Akerlof's The Market for "Lemons": Quality Uncertainty and the Market Mechanism (1970) shows what happens when one side knows the quality of what is offered and the other cannot tell. The giver knows the platform's maintenance, licensing, and compliance costs; the recipient sees only a working system. A total-cost-of-ownership analysis, or an auditor's review, closes that information gap before the recipient commits.
Warning signs
A peer department offers a system, tool, or budget transfer for free, often with an executive's public approval attached. The terms say little about who pays for licenses, upgrades, support, and audit scope after the first year. After handover the giver keeps control of the maintenance and upgrade path, and declining would have read as territorial to senior leadership.
How to defend yourself
Treat a gift as a purchase. Before accepting, run the same total-cost-of-ownership analysis your procurement function would run on something you were buying, covering licenses, renewals, maintenance staff, integration, and the compliance scope that comes with the data. Ask the giver to put in writing who pays each of those costs in years two through five, and who controls upgrades and change requests. If an auditor or your finance partner can review the terms for embedded liabilities, have them do it before commitment. A polite no is easier when you can show the numbers: thank the giver, state the five-year cost, and propose a smaller arrangement that leaves you owning the way out.
How a leader shuts it down
Run gifts between departments through the same cost analysis as purchases, and make the full lifetime cost visible to the executive who praises the offer. Build norms that make declining help acceptable, and do not treat a department that says no as uncooperative. Shared-services agreements should name who controls maintenance and how a recipient exits.