Applied Data Research and Autoflow: Betting That Software Could Be Sold as a Product
Applied Data Research financed Autoflow as a reusable software product when customers expected software to be free, helping prove that proprietary software could support licensing, product R&D, and independent vendors.
Applied Data Research began as a services company because software products barely had a market
Applied Data Research was founded in 1959 by programmers who initially earned revenue through contract development. That was the rational model in an industry where computer manufacturers usually supplied software without a separate charge. The Computer History Museum explains that bundled software made it difficult for independent product companies to thrive.[1] ADR’s eventual decision to invest in a reusable software product therefore required it to challenge both customer expectations and the economics established by hardware vendors.
The obstacle was not only technical risk
ADR could write a useful program and still fail if customers believed an equivalent tool should eventually arrive free from the computer manufacturer.
Autoflow turned an internal capability into a product investment
Autoflow automatically generated flowcharts from program source, reducing a tedious documentation task. Computer History Museum materials identify it as an early independent software product and connect its success to the emergence of a commercial software market.[2] ADR chose to spend development effort on something that could be licensed repeatedly instead of billing every hour to one consulting client. That changed the company’s economics from labor resale toward intellectual-property leverage.
Reusable code created operating leverage
Once the product existed, the same engineering investment could generate revenue from many customers. Gross margins could improve without staffing each sale with a new development team.
RCA’s refusal forced ADR to discover direct software distribution
Historical accounts of Autoflow describe ADR first approaching RCA with a proposal valued around $25,000. When the hardware vendor declined, ADR sold the program directly to computer users instead.[3] This was a crucial business-model innovation. Rather than treating the manufacturer as the only route to market, ADR became the vendor of record for its own software. The company assumed sales, licensing, support, and product-roadmap responsibilities that hardware makers had traditionally controlled.
Direct sales made the software company legible as a separate supplier
Customers could buy value from a company that did not manufacture their computer. That separation is the foundation of the modern software industry.
Licensing protected the investment better than an outright sale
Software ownership became a financeable asset
Software could be copied cheaply, so ADR needed a legal model that preserved ownership while granting customers usage rights. The company developed licensing practices that treated code as intellectual property rather than a physical object sold once. This supported repeat revenue and created legal remedies against unauthorized copying. The business logic was as important as the code: a software product only becomes investable if its creator can capture enough of the value it creates.
Patent strategy was another attempt to protect product R&D
Martin Goetz filed a patent application in 1965 for a computer-programming technique assigned to ADR, and U.S. Patent 3,380,029 issued in 1968.[4] The patent became famous in debates over software intellectual property. From an investment perspective, ADR’s position was straightforward: the company was spending real money to create reusable software and wanted protections comparable to those available for hardware inventions.
ADR’s conflict with IBM was fundamentally a capital-allocation problem
As Autoflow gained traction, ADR feared that IBM could undermine the market by distributing competing programs without separate prices. Martin Goetz’s oral history describes ADR investing millions in new products such as ROSCOE, MetaCOBOL, and LIBRARIAN while worrying that “free” IBM software could erase the return on those investments.[5] ADR’s antitrust complaints and lawsuit were therefore not abstract policy disputes. They were efforts to make software R&D financeable as a standalone business.
Product revenue validated the independent-software model
Goetz later recalled that Autoflow revenue grew enough to shift ADR away from dependence on services, and the company expanded into a significant software-products business.[5] That growth proved software could support dedicated product development, sales, and support organizations. ADR did not have to manufacture the mainframe to earn attractive revenue from the applications running on it. This separation opened the door for a broad ecosystem of specialized software firms.
Why ADR and Autoflow belong in the history of profound software investments
ADR belongs in investment history because it invested ahead of the industry’s pricing model. The company spent money building reusable code, created licensing practices to protect it, pursued patent protection, and fought for a market in which software could carry an explicit price.[1][5]
The return extended far beyond Autoflow itself. Once software could be sold independently, investors could finance companies whose principal asset was code rather than hardware factories. Enterprise applications, databases, developer tools, security software, and eventually SaaS all depend on that economic separation. ADR’s bet was not merely that one flowcharting program would sell. It was that software itself could become a product category worthy of sustained capital.
Productization also changed how ADR could plan its own future. Revenue from one installed base could finance the next tool, allowing the company to build a portfolio instead of restarting from zero with every contract. This compounding loop—software revenue funding more software R&D—became one of the defining financial engines of the later industry.
Works Cited
- 01Computer History Museum — Software Becomes a Product computerhistory.org
- 02Computer History Museum — AUTOFLOW Brochure computerhistory.org
- 03Computerworld — Who Was First? Martin Goetz on Autoflow computerworld.com
- 04Google Patents — US3380029A Sorting System patents.google.com
- 05Computer History Museum — Martin Goetz Oral History archive.computerhistory.org
CodeHistory is a living archive. Citations document the evidence used for this edition; later evidence may refine the account.
Submit a research lead