#773 1982 · Andrew Fluegelman (PC-Talk) and Jim Knopf (PC-File) · Software distribution / personal computing
Two solo programmers beat the software industry's piracy problem by asking people to copy their programs as much as possible
the problem
Independent programmers couldn't afford retail distribution, and copy protection couldn't stop copying anyway
background
By the early 1980s, personal computers were spreading fast, but independent software developers working alone or in tiny teams had no realistic way to compete with commercial publishers' retail shelf space, marketing budgets, or distribution deals. Some commercial software fought unauthorized copying with copy-protection schemes meant to physically prevent duplication, an approach that added cost and inconvenience without actually stopping determined copying.
Jim Knopf, an IBM employee in Bellevue, Washington, had written a database program called Easy-File and started sharing it informally with colleagues. As more people picked it up, he ran into a different problem entirely: it was becoming expensive and time-consuming just to track down everyone using his software and notify them when he released fixes or improvements — not too little distribution, but no reliable channel back to the people who already had it.
what everyone would do
Sell the software through traditional retail channels or ship it with copy-protection schemes to prevent unauthorized duplication, the way most commercial software companies did — an approach that required capital, distribution deals, and legal enforcement no independent, one-person developer working from home actually had access to.
what they saw
Jim Knopf, sharing his database program informally with IBM colleagues, realized that the real cost wasn't people copying his software without paying — it was the expense and hassle of finding and notifying his actual users when he released fixes or improvements. Copying was already happening for free and doing exactly the marketing and distribution work a publisher would have charged him for; the only genuine problem left was getting some of those copiers to pay him something and stay in touch. Fighting the copying itself, the way commercial software did with clumsy protection schemes, would have destroyed the one distribution advantage an independent developer actually had.
the move
Knopf embedded a message in his program, renamed PC-File, asking users who wanted to be notified of updates to voluntarily send $10, while explicitly encouraging them to keep copying and sharing the program with others rather than trying to stop them. Around the same time in Tiburon, California, Andrew Fluegelman released his communications program PC-Talk under an identical model he called "freeware," requesting $25 from anyone who liked it. A user who received both programs recognized the similarity and introduced the two developers, who began recommending each other's software on their own distribution disks.
why it works
By explicitly encouraging users to copy and share the program, embedding a friendly request for a voluntary payment rather than a lock users had to break, Fluegelman and Knopf turned every unauthorized copy into a new potential customer instead of a lost sale, since a copied program a user genuinely liked and kept using created its own incentive to pay for continued support and updates — the exact appeal a commercial product's marketing budget would otherwise have had to manufacture. Because two independent developers had converged on the identical model at the same time, when a user who'd received both programs introduced them to each other, they simply cross-recommended each other's software on their own distribution disks, multiplying the reach of both without either paying anything for it.
the payoff
The honor-system model let both developers reach far more users than either could have funded through traditional retail distribution, since every copy anyone made and passed along was free marketing neither of them had to pay for, and a real share of satisfied users chose to pay voluntarily to keep receiving updates and support. The approach, soon renamed "shareware" after Fluegelman's trademarked "freeware" term became legally contested, spread rapidly among independent developers through the 1980s and 1990s.
where it breaks
It only works if the software itself is genuinely good enough that a meaningful share of users who could get it for free choose to pay anyway — an honor-system model has no floor if the product doesn't earn real loyalty, since nothing but goodwill compels a single payment. And it depends on there being some ongoing reason for a user to stay connected to the developer, like Knopf's mailing-list updates and fixes, since without an ongoing relationship to protect, the incentive to pay evaporates entirely once a user already has a working copy.
what came after
Shareware became a defining distribution model of the early personal-computing era, letting a generation of solo developers reach national and eventually global audiences without a publisher, and its core logic — treat free distribution as marketing rather than a threat, and monetize through voluntary or delayed payment rather than upfront restriction — reappeared decades later in freemium apps, open-source-with-paid-support businesses, and pay-what-you-want digital media.
references
- [1]The Origin of SharewareAssociation of Shareware Professionals (Historical Archive), 1995asp-software.org
- [2]Shareware's Legacy on Computing: The Model That Opened the FloodgatesTedium, 2016tedium.co