The Free Tool With One Maintainer

The regional archive used a free program to convert old documents into searchable files. Records officer Tessa had installed it years earlier, and staff now depended on it daily. When a system update broke the program, she posted an urgent request on its support page. The sole maintainer replied that he could investigate after finishing his paid work that weekend.

Tessa's director was annoyed that an essential supplier offered no immediate support. Tessa began to agree, then looked at the program's website again. They had never hired the maintainer, donated to the project or asked about a service agreement. The archive had received years of skilled work without payment and had quietly transformed gratitude into an expectation of availability.

She withdrew the urgent tone of her message and asked what a realistic support arrangement would cost. The maintainer offered a modest annual contract covering specific response times, not unlimited personal access. The archive's purchasing rules made it easier to buy new software than support something already free. Tessa prepared a comparison including migration costs, staff training and the risk of depending on unplanned volunteer labour.

The archive approved the support contract and contributed a set of documented test files that the maintainer could use without exposing private records. The next update went smoothly, but Tessa knew that payment did not make failure impossible. It made the relationship explicit. When she later described the program to another institution, she still called it free to use. She no longer allowed that phrase to suggest that keeping it useful required no resources from anyone.