25 software tools that changed how entire industries work

The history of industrial transformation is usually told through machines — the steam engine, the assembly line, the transistor. But some of the most consequential disruptions of the past half-century arrived not as hardware but as code. A spreadsheet program released in 1979 rendered entire rooms of human calculators unnecessary. A database tool built for medical researchers eventually became the backbone of global enterprise. A mapping application designed for military navigation became the invisible infrastructure beneath the modern economy. Software, more than any physical invention, has had the peculiar ability to reshape industries from the inside — not by replacing workers with robots on a factory floor, but by changing the fundamental logic of how decisions get made, how information flows, and what work even looks like.

The tools on this list were chosen for one reason: they didn't just improve an existing process. They changed what was possible. Some of them created entirely new job categories. Others destroyed old ones. A few did both simultaneously. What unites them is that the industries they touched look fundamentally different because these programs exist. Accounting was one kind of profession before VisiCalc and a different kind after it. Architecture was practiced one way before AutoCAD and another way after it. The same is true of logistics, medicine, music, filmmaking, retail, and a dozen other sectors.

These aren't necessarily the most popular software tools, the highest-grossing, or the ones with the most users today. Some have been superseded by newer platforms. Some are showing their age. A handful are barely remembered outside the industries they transformed. What matters is what each one changed — the before and after it created. The industries covered here span finance, healthcare, design, media, science, logistics, and more, reflecting the breadth of software's reach across the modern economy.

Understanding these tools is also a way of understanding how change actually happens in complex systems. It rarely arrives all at once. It often comes through a small utility that solves a specific, unglamorous problem — and then quietly rewires everything around it.

Credit: Derek Xing  /  Pexels

VisiCalc arrived in 1979 as a product for the Apple $AAPL II, and it solved a problem that had plagued financial analysts, accountants, and business planners since ledger books were invented: recalculation. Before VisiCalc, a financial model built on paper meant that changing one assumption — a tax rate, a growth projection, a cost figure — required recalculating every downstream number by hand. That process took hours. It was prone to error. It made scenario planning impractical for anyone without a team of clerks or a mainframe computer.

VisiCalc, developed by Dan Bricklin and Bob Frankston, offered something that had never existed before: a grid of cells in which each cell could contain either a value or a formula referencing other cells. Change one number, and the entire model updated instantly. The concept seems obvious in retrospect, but at the time it represented a genuine conceptual leap. Bricklin has said the idea came to him while watching a professor at Harvard Business School erase and redraw numbers on a chalkboard — and imagining a "magic blackboard" that would do the recalculation automatically.

The impact on finance and accounting was immediate and far-reaching. VisiCalc is widely credited with driving early Apple II sales into corporate America, giving the personal computer a business justification that turned it from a hobbyist curiosity into an office staple. The tool also fundamentally changed what financial analysts did with their time. Instead of spending most of the workday on arithmetic, they could now spend it thinking about assumptions and strategy. Scenario modeling became practical. Sensitivity analysis, which asks "what happens if this variable changes," became a routine part of financial planning rather than a luxury.

VisiCalc itself was eventually overtaken by Lotus 1-2-3 and then by Microsoft $MSFT Excel, which remains the dominant spreadsheet tool today. But the concept it introduced — the interactive electronic spreadsheet — persists across every modern finance, accounting, and data analysis platform on earth. The profession of financial modeling as it is practiced today, with its intricate linked workbooks and automated scenario analyses, descends directly from the "magic blackboard" Bricklin imagined in a Harvard lecture hall.

The tool also had an underappreciated effect on small business. Before VisiCalc, sophisticated financial modeling required either expensive professional services or large internal accounting departments. The spreadsheet democratized that capability, allowing small businesses to build their own models and make more informed decisions. It shifted power — quietly, without fanfare — from specialists to generalists.

Credit: ThisIsEngineering /  Pexels

Before AutoCAD, architectural and engineering drawings were made by hand. Drafters worked at large flat tables with pencils, rulers, compasses, and mechanical lettering guides. Producing a complete set of construction documents for a building could take weeks. Revisions meant erasing and redrawing. Sharing documents meant shipping physical prints. The skill of technical drafting was a distinct profession, and drafting rooms at large engineering firms employed dozens of people.

Autodesk $ADSK released AutoCAD in 1982 as one of the first computer-aided design programs for personal computers. It allowed designers to create precise two-dimensional drawings on screen, store them digitally, print them at any scale, and revise them without starting over. The time savings were substantial: tasks that took a drafter a day could be done in hours. More importantly, iterations became cheap. A designer could explore variations, test proportions, and refine details without the cost of redrawing everything from scratch.

The effect on architecture and engineering was not just about speed. It changed the nature of design itself. When revisions are expensive, designers commit to ideas early and change them reluctantly. When revisions are cheap, designers explore more. AutoCAD enabled a more iterative design process, which over time shaped how architects and engineers think about their work. The tools you use change how you think, and CAD tools encouraged a more experimental approach to design development.

AutoCAD also eventually expanded into three dimensions, and the broader ecosystem of 3D modeling software it helped establish — including tools like Revit, SolidWorks, and CATIA — transformed manufacturing, product design, and construction. The concept of a digital model that contains not just geometry but data about materials, costs, and specifications became the foundation of Building Information Modeling, a methodology now standard in large construction projects around the world.

The drafting profession itself was profoundly affected. The occupation of "drafter" — a skilled specialist who translated an engineer's ideas into precise technical drawings — contracted sharply as engineers and architects began producing their own drawings directly. New specialties emerged: CAD technicians, BIM coordinators, computational designers. The tools changed not just how buildings were designed but who did the designing and what expertise was valued.

Credit: Brett Sayles /  Pexels

SAP, founded in Germany in 1972, built software to solve a problem that affected every large manufacturer: the disconnection between departments. In a typical industrial company of that era, the accounting department ran its own systems, the warehouse ran separate inventory records, the purchasing department kept its own supplier files, and the production floor tracked its own output. These systems didn't talk to each other. Reconciling them required armies of clerks manually transferring data between them.

SAP's early R/2 system, and then the landmark R/3 release in 1992, introduced what became known as enterprise resource planning, or ERP. The idea was to put all of a company's core business processes — accounting, inventory, purchasing, human resources, manufacturing planning — into a single integrated system sharing a common database. When a purchase order was placed, the inventory system knew. When inventory was consumed, the accounting system reflected it. The organization could see itself as a whole, in near-real time.

R/3 was designed for client-server architecture at a time when that model was becoming practical for large organizations, and its timing was near-perfect. Companies that had previously relied on custom-built systems or department-specific software began migrating to SAP in enormous numbers through the 1990s. The list of industries affected is essentially the list of large industries: automotive, chemicals, consumer goods, banking, utilities, retail, healthcare. Volkswagen, Procter & Gamble $PG, and Microsoft $MSFT were among the early adopters. By the early 2000s, SAP was running the back-office operations of a substantial share of the world's largest companies.

The effect on business operations was profound. ERP systems made it much harder for departments to operate as independent fiefdoms with their own data. They enforced process standardization — often painfully, since SAP implementations frequently required companies to change their workflows to match the software rather than the other way around. This rigidity was a source of frustration, but it also drove genuine operational consistency and visibility.

SAP also created an entire professional ecosystem around itself. SAP consulting became a major industry. Universities developed programs to train SAP administrators. The tool's complexity meant that organizations became deeply dependent on specialists who understood it — a dependency that persists today and has made SAP one of the most entrenched software platforms in corporate history.

Credit: Pavel Danilyuk /  Pexels

Adobe $ADBE Photoshop launched in 1990 and within a decade had so thoroughly dominated image editing that its name became a verb. To "photoshop" something entered common language as a synonym for digitally altering an image. That linguistic absorption is itself a measure of the tool's reach — few pieces of software have so completely defined their category that they become synonymous with the activity itself.

Before Photoshop, professional image editing was done in darkrooms using chemical processes, or by physical retouching using airbrushes, paints, and dyes applied directly to prints or transparencies. These techniques required years of training, expensive equipment, and considerable time per image. The result was that high-quality image manipulation was the exclusive domain of specialists working at printing houses, advertising agencies, and photography studios.

Photoshop moved that capability onto the desktop. Its layer-based compositing model — which allowed designers to stack image elements independently and adjust them without affecting other layers — became the conceptual foundation for how visual work is done digitally. The tool's approach to color correction, masking, and retouching became industry standards that subsequent software either adopted or defined itself against.

The industries transformed include advertising, publishing, fashion, film, and photography. In advertising and magazine publishing, the retouching of commercial images became so routine and so extreme that it sparked ongoing cultural and regulatory debates about unrealistic standards. In film production, Photoshop became a standard tool for concept art, matte painting, and visual effects work. In photography, it effectively ended the era in which a photographic print was treated as an unimpeachable record of reality.

Photoshop also contributed to the displacement of several traditional print production roles. Color separators, strippers, and paste-up artists — specialists in the pre-digital production of printed materials — found their skills largely obsolete by the mid-1990s. In their place came a generation of digital designers fluent in Photoshop and its companion tools. The profession of graphic design was restructured around digital tools, with Photoshop at the center of that restructuring. Even now, after more than three decades and the rise of competing tools, Photoshop remains the default environment for professional image work in most commercial contexts.

Credit: Tima Miroshnichenko /  Pexels

Before accounting software became accessible to small businesses, a small business owner who wanted to keep proper books had two options: hire a bookkeeper or do it manually using ledger books and calculator tape. Both options were expensive in time or money, and the results were often inconsistent. The accounting profession's services were largely aimed at larger organizations that could afford them. Small businesses operated with limited financial visibility into their own operations.

Intuit $INTU's QuickBooks, first released in 1992, addressed this gap directly. It offered small and medium-sized businesses a way to track income and expenses, generate invoices, run payroll, and produce financial statements without requiring any accounting education. Its interface was designed for business owners, not accountants. It used familiar concepts — checkbooks, invoices, bills — rather than the debits, credits, and journal entries of formal accounting.

The effect on small business accounting was significant and lasting. Businesses that had previously kept incomplete or informal financial records began maintaining systematic books. This improved their ability to make informed decisions, manage cash flow, and comply with tax requirements. It also changed the relationship between small businesses and their accountants: instead of handing over a shoebox of receipts at year-end, business owners began arriving with organized QuickBooks files that their accountants could review and work with directly.

QuickBooks also redefined what small business accountants did. With basic bookkeeping largely automated, accountants serving small businesses could shift toward advisory roles — helping clients interpret their financial data and plan for growth rather than spending the bulk of their time on data entry and reconciliation. The profession adapted, though not without friction, to a world in which the mechanical work of bookkeeping was substantially handled by software.

The platform's reach today is enormous: QuickBooks claims tens of millions of users globally, spanning virtually every small business sector. Its dominance has made it a de facto standard, which has created significant lock-in — a pattern common to successful business software. The accounting ecosystem, including tax preparation, payroll processing, and business banking, has largely built itself around QuickBooks compatibility.

Credit:  Dithira Hettiarachchi / Unsplash

The Global Positioning System, a network of satellites built and maintained by the U.S. military, became available for civilian use in the 1980s. But for years, the hardware was expensive, bulky, and confined to specialized applications in aviation, maritime navigation, and military operations. The transformation of GPS into an everyday tool for ground transportation required not just miniaturized hardware but software — specifically, digital maps and routing algorithms capable of turning satellite coordinates into turn-by-turn driving directions.

The first consumer GPS navigation devices, from companies like Garmin and TomTom, arrived in the early 2000s and sold in enormous quantities. But the shift that most profoundly changed logistics, transportation, and delivery came when GPS navigation software moved onto smartphones. Google $GOOGL Maps launched in 2005, and its mobile version — combined with real-time traffic data and eventually turn-by-turn directions — put precision navigation in every pocket.

The logistics and trucking industries were among the first to feel the transformation at scale. Long-haul trucking had long relied on paper maps, dispatcher knowledge, and driver experience to plan routes. GPS routing systems allowed companies to optimize routes computationally, reduce fuel consumption, improve delivery time estimates, and dispatch more efficiently. Fleet management software built on GPS data became standard across delivery, trucking, and field service industries.

Ride-hailing and food delivery, which became major industries in the 2010s, are essentially GPS software businesses. Uber $UBER, Lyft $LYFT, DoorDash, and their global counterparts could not exist without GPS routing as a commodity service. The ability to match a driver to a passenger in real time, optimize routing dynamically, and give customers accurate arrival predictions is entirely a function of GPS software combined with mobile connectivity.

The impact on physical retail and urban planning has been equally significant. The ability to find businesses by location, read reviews, and get directions to any address transformed consumer behavior and the competitive dynamics of location-based businesses. Small businesses that were previously hidden from passing trade became discoverable. The logic of commercial real estate — in which visibility and foot traffic were the dominant variables — began to shift.

Credit:   Josh Miller / Unsplash

Film editing before digital nonlinear systems meant working with physical film. An editor cut film with a razor blade and tape, arranging strips of celluloid on a flatbed editing table. Changing a cut meant physically rearranging the film. Making a rough cut required printing a work print — an expensive and time-consuming process. The editing of a feature film was a months-long physical and logistical operation requiring dedicated editing rooms and skilled technicians.

The shift to digital began with tools like Avid Media Composer in the early 1990s, which allowed editors to digitize footage and edit it nonlinearly — meaning any part of the timeline could be changed without affecting other parts. Adobe $ADBE Premiere, which launched in 1991 and evolved into Premiere Pro, brought a similar capability to a broader audience at a lower price point, eventually becoming the dominant tool for video editing across television, online content, and documentary film.

The impact on the television and film industries was substantial. Editing teams shrank as digital tools made individual editors more productive. The physical infrastructure of post-production — film printing facilities, flatbed tables, synchronizers — largely disappeared. The craft of editing, which had been a highly specialized physical skill involving the handling of film, became a software skill. New editors learned on digital systems, and the tactile knowledge of film editing became historical.

Beyond Hollywood, Premiere Pro and its competitors enabled an entirely new sector: online video. YouTube's rise from 2005 onward created demand for video production at a scale the traditional film and television industries never anticipated. Independent creators producing content on their own equipment needed accessible, affordable editing software. Premiere Pro — along with Final Cut Pro and DaVinci Resolve — became the tools of this new economy. The barrier to entry for video production dropped dramatically, creating the creator economy that now reaches billions of viewers.

The ripple effects extended into advertising, journalism, and corporate communications. Video, once expensive and logistically complex to produce, became a routine part of marketing and media. The production values expected of professional video content rose, but so did the number of people capable of meeting those standards.

Credit:    Irwan / Unsplash

When Larry Ellison and his co-founders launched Oracle $ORCL in 1977, the relational database was a theoretical concept from a 1970 IBM $IBM research paper by Edgar Codd. IBM was working on its own implementation but moving slowly. Oracle moved fast, delivering a commercial relational database in 1979 that implemented the Structured Query Language, or SQL, a standardized language for querying and manipulating data.

The relational model — organizing data into tables connected by defined relationships — solved problems that had plagued earlier hierarchical and network database systems. It made data retrieval flexible and powerful. It allowed complex queries that combined data from multiple tables in ways that earlier systems made impossible or impractical. And SQL, as a standardized language, meant that database skills were transferable across different systems, which accelerated adoption.

Oracle's database became the foundation of enterprise computing across industries. Banks, airlines, telecommunications companies, government agencies, and healthcare systems all ran their core operations on Oracle. The technology underpinning airline reservation systems, hospital patient records, bank account databases, and insurance claims systems was, for much of the 1980s through 2000s, likely an Oracle database.

The broader impact is difficult to separate from the impact of enterprise software generally, because Oracle's database was the infrastructure on which so much of that software ran. SAP ran on Oracle. Custom enterprise applications ran on Oracle. The explosion of transactional business software in the 1980s and 1990s was made possible by reliable, scalable relational database technology, and Oracle was the dominant provider of that technology for commercial applications.

Healthcare was particularly affected. The move from paper records to electronic systems in hospitals and clinics required robust database technology capable of handling patient records, lab results, prescriptions, billing, and scheduling simultaneously. Oracle's database became one of the most common platforms underlying electronic health record systems, representing a fundamental shift in how patient data was stored and accessed.

Credit: MART PRODUCTION /  Pexels

Before Salesforce $CRM launched in 1999, customer relationship management software was sold as packaged software that organizations installed on their own servers. Siebel Systems, the dominant CRM vendor of the late 1990s, required expensive hardware, lengthy implementations, and ongoing IT support. A mid-sized company deploying Siebel CRM might spend a year and millions of dollars before a single salesperson logged in.

Marc Benioff founded Salesforce on a simple premise: sell software over the internet as a subscription service, eliminating the need for installation or on-premises infrastructure. The company called this model "Software as a Service," or SaaS, and its success helped establish that model as the default for enterprise software delivery over the following two decades.

The direct impact on sales and customer management practices was significant. Salesforce gave organizations a way to track customer interactions, manage sales pipelines, forecast revenue, and coordinate across sales teams without major IT projects. It made CRM accessible to organizations that could not afford Siebel-scale implementations.

The broader industry impact — on how software itself is sold and delivered — was more far-reaching. Salesforce's success demonstrated that enterprise software buyers were willing to rent software via subscription rather than own it outright. This model spread rapidly across every category of business software. Today, the vast majority of new enterprise software is delivered as a cloud subscription rather than an installed product, a shift that Salesforce pioneered at scale.

The model also changed the economics of enterprise software. Subscription revenue is recurring and predictable in ways that license revenue is not. This made software companies more valuable and changed how investors thought about them. The "annual recurring revenue" metric that now dominates software industry analysis emerged from the SaaS model that Salesforce exemplified.

Customer service and marketing have also been transformed. Salesforce expanded beyond sales CRM into marketing automation, customer service platforms, and commerce tools, becoming a full customer engagement suite. The expectation of personalized, history-aware customer service — in which a company representative can immediately see a customer's full history of interactions — was enabled by CRM systems and has reshaped what customers expect from businesses.

Credit:  Al Nahian  /  Pexels

MySQL is a free, open-source relational database management system first released in 1995 by a Swedish company founded by Michael Widenius and David Axmark. It was not the first open-source database, nor was it the most feature-rich. But it was fast, reliable enough for many applications, and — critically — free to use. In the era of the early commercial internet, when startups were building on borrowed infrastructure and tight budgets, those characteristics made MySQL the default choice for web applications.

The LAMP stack — Linux, Apache, MySQL, and PHP or Perl — became the dominant platform for building websites and web applications in the late 1990s and early 2000s. Wikipedia runs on MySQL. Early versions of Facebook $META used MySQL. Twitter $TWTR began on MySQL. WordPress, which now powers roughly 40% of all websites, uses MySQL as its default database. The cumulative effect of MySQL's role in the LAMP stack is that it became the invisible foundation of a significant portion of the web's infrastructure.

The impact on the internet industry specifically is hard to overstate. The availability of a free, functional database removed a major cost barrier for web startups. Before MySQL, building a database-backed web application required either expensive commercial databases from Oracle $ORCL or IBM $IBM, or significant engineering work to build a custom solution. MySQL made database-backed web development accessible to small teams and individual developers, contributing directly to the explosion of web applications and web-based businesses in the late 1990s and 2000s.

The broader software industry was also changed by MySQL's success, which demonstrated that open-source software could be viable in production enterprise environments. MySQL's model — free to use, with commercial support available from the vendor — became a template that many subsequent open-source software companies followed. The rise of open-source as a default development paradigm in the technology industry owes a significant debt to projects like MySQL that demonstrated its commercial viability.

The open-source database ecosystem MySQL helped establish continues to evolve. PostgreSQL, MongoDB $MDB, and other open-source databases now compete with and in many cases supplement MySQL, but the foundational shift — from expensive commercial databases to accessible open-source alternatives — is MySQL's legacy.

Credit:  Lucas Porras /  Pexels

Before digital audio workstations, recording music meant recording to tape. A professional recording studio was organized around a mixing console, a multitrack tape machine, and racks of outboard processing gear — compressors, equalizers, reverbs. Tape was physical: it wore out, it had to be physically edited with razor blades, and the number of tracks was fixed by the width of the tape and the speed of the recording. A 24-track recording required a 24-track tape machine, and adding tracks meant bouncing — mixing some tracks together onto fewer tracks to free up space, a process that degraded quality with each generation.

Avid's Pro Tools, which began as a two-track digital audio editor in 1989 and evolved into a full multitrack workstation through the 1990s, moved audio recording into the digital domain. Tracks became virtual, limited by processing power rather than physical tape. Edits were nondestructive — cutting, moving, or deleting a section of audio didn't alter the original recording, and any edit could be undone. The processing gear that had filled racks of hardware became software plug-ins.

The effect on the recording industry was profound and somewhat paradoxical. On one hand, digital tools made professional-quality recording dramatically more accessible. A home studio with Pro Tools could produce recordings that were technically competitive with what major studios charged thousands of dollars a day for in the 1980s. This democratized music production and contributed to the rise of independent artists and small labels.

On the other hand, the accessibility of digital audio also contributed to excess. When tape was expensive and studio time was billed by the hour, bands arrived rehearsed and recorded efficiently. With unlimited digital tracks and the ability to fix mistakes in post-production, the pressure to perform well in real time diminished. The phenomenon sometimes called "Pro Tools voice" — the slightly over-processed, pitch-corrected sound that characterized much commercial music in the 2000s — is partly a product of what the tool made easy and normalized.

Pro Tools became the industry standard in professional recording, post-production, and broadcast audio, displacing tape-based workflows almost entirely. The major recording studios that survived the digital transition became software facilities as much as acoustic rooms.

Credit:  Max Grakov  /  Pexels

A geographic information system, or GIS, combines spatial data with analytical tools to answer questions that have a location dimension: Where are disease cases clustering? Which neighborhoods lack access to pharmacies? How would a proposed highway affect wildlife habitat? Before GIS software, these questions were addressed by manually overlaying physical maps — a laborious process with limited analytical capability.

ESRI's ArcGIS, which grew from a research project at the Environmental Systems Research Institute in Redlands, California, became the dominant commercial GIS platform over the course of the 1980s and 1990s. It allowed users to layer different types of spatial data — population data, infrastructure data, environmental data, satellite imagery — and run spatial analyses that were impossible with paper maps.

The impact spread across an unusually wide range of fields. Environmental science uses GIS to track deforestation, model climate change impacts, and manage natural resources. Urban planning uses it to analyze transportation networks, zoning patterns, and land use. Public health uses it for disease surveillance and epidemiological analysis — the response to HIV/AIDS in the 1980s was one of the early large-scale public health uses of GIS. Military and intelligence agencies use it for terrain analysis and mission planning.

Perhaps the most visible impact has been in urban and regional planning. The ability to map demographic data, infrastructure, and land use simultaneously transformed how planners analyzed cities and made decisions. Environmental impact assessments, which require analyzing how a proposed development would affect surrounding areas, became substantially more rigorous with GIS tools. The days of planners physically cutting paper maps and overlaying them on light tables gave way to layered digital analysis.

Agriculture was also significantly affected. Precision agriculture — the practice of varying inputs like fertilizer and irrigation across a field based on detailed spatial data — relies heavily on GIS. Farmers using precision techniques can reduce input costs while maintaining or improving yields by applying resources exactly where they are needed rather than uniformly across a field.

Credit: Lukas / Unsplash

Linus Torvalds released the Linux kernel in 1991 as a personal project, posting an announcement to a newsgroup with characteristic understatement. He described it as "just a hobby" and said it wouldn't be "big and professional." What followed was one of the most consequential pieces of software in computing history — not because of what it did in consumer products, but because of where it ended up running: the servers that power the internet.

Linux's technical characteristics — stability, security, flexibility, and the ability to run on virtually any hardware — made it attractive for server deployments. But its decisive advantage was its licensing model: the GNU General Public License made Linux free to use, copy, modify, and distribute. This meant any organization could run server infrastructure without paying operating system license fees, which for large deployments could amount to enormous sums.

By the mid-2000s, Linux had become the dominant operating system for web servers. Google $GOOGL, Amazon $AMZN, and Facebook $META all built their infrastructures on Linux. The major cloud computing platforms — Amazon Web Services, Google Cloud, Microsoft $MSFT Azure — run predominantly on Linux. Android, the operating system running the majority of the world's smartphones, is built on the Linux kernel. The internet infrastructure that modern life depends on runs overwhelmingly on a piece of software that a Finnish university student began writing as a hobby in 1991.

The impact on enterprise computing was also substantial. Companies running Linux servers paid nothing for the operating system itself, which changed the economics of data center operations and made large-scale computing more accessible. Linux also drove the development of open-source software culture broadly, attracting developers who wanted to contribute to a platform that was used at scale and valued contributions from outside any single company.

The model of large-scale collaborative open-source development that Linux pioneered — thousands of contributors, governed by a transparent process, producing software that corporations depend on commercially — has become the standard for infrastructure software. The modern software industry is built on a foundation of open-source tools, and Linux is the most important single example of that foundation.

Credit:  Cedric Fauntleroy  /  Pexels

The shift from paper medical records to electronic systems is one of the most complex and consequential software transitions any industry has undergone. Healthcare generates enormous volumes of data — diagnoses, medications, lab results, imaging reports, billing codes, insurance information — and historically, that data lived in paper charts that were fragmented across providers, difficult to share, and often illegible.

Epic Systems, founded by Judy Faulkner in Madison, Wisconsin in 1979, built one of the earliest and eventually most widely deployed electronic health record, or EHR, systems. Epic's software collects clinical and administrative data across the full spectrum of care — inpatient, outpatient, emergency, specialist — and presents it to clinicians in an integrated view of the patient's history.

The impact on healthcare has been significant in both directions. On the positive side, electronic records eliminate the problem of lost or inaccessible charts, reduce medication errors by providing clinicians with complete medication histories, enable population health management by allowing health systems to identify and reach out to patients who need care, and support clinical research by making patient data analyzable at scale.

The negative side is also well-documented. Physician burnout has become a major issue in healthcare, and EHR systems — including Epic — bear significant responsibility in that narrative. The documentation burden that modern EHRs impose is substantially higher than paper records required. Physicians spend a significant portion of their working day in the EHR, entering data in formats designed for billing and compliance as much as for clinical care. The concern that software designed for administrative purposes has distorted clinical workflows is legitimate and widespread in the medical community.

Epic's market position — it covers the medical records of a majority of Americans through the hospitals and health systems that use it — has made interoperability both important and contentious. The ability for different health systems' records to communicate has improved but remains imperfect, partly because Epic and its competitors have historically had limited incentives to make data easily portable.

Credit: Mikhail Nilov   /  Pexels

Microsoft $MSFT Excel launched in 1985 for the Macintosh, and its Windows version released in 1987 eventually achieved a dominance so complete that for most office workers, "spreadsheet" and "Excel" became synonymous terms. Excel was not the first spreadsheet — VisiCalc and Lotus 1-2-3 preceded it — but it was the most capable and ultimately the most widely deployed, and it fundamentally shaped how quantitative work is done in offices around the world.

Excel's impact on finance is the most obvious: financial modeling, budgeting, forecasting, and analysis are built on Excel to a degree that surprises even technology professionals. Investment banks, corporate finance departments, and consulting firms run on Excel models of extraordinary complexity. The tool's grid, formula engine, and charting capabilities, combined with the familiarity that comes from ubiquity, have made it the default environment for any analysis that involves numbers and doesn't clearly require something else.

But Excel's reach extends far beyond finance. Operations managers track inventory in Excel. HR departments maintain employee records in Excel. Scientists run preliminary analyses in Excel. Marketers plan campaigns in Excel. The tool is used for purposes ranging from personal budgets to complex logistical optimization, making it one of the most versatile — and genuinely used — pieces of software ever created.

Excel also had a structural effect on organizations: it made quantitative analysis accessible to generalists. Before spreadsheets, number-intensive analysis was confined to specialists — accountants, statisticians, engineers. Excel put a functional data analysis environment in the hands of every office worker. This democratization of analysis changed how business decisions were made and who was expected to support them with data.

The tool's familiarity has also made it a point of resistance to newer, purpose-built software. Finance teams that could use more powerful financial planning and analysis platforms often stay with Excel because the migration cost is high and the familiarity value is real. The "Excel problem" — the challenge of replacing entrenched spreadsheet workflows with more appropriate tools — is a genuine and recurring theme in enterprise software.

Credit: cottonbro studio  /  Pexels

Software has always been collaborative, but for most of computing's history, collaboration was logistically difficult. Developers working on the same codebase coordinated through informal processes — emailing files, manually merging changes, maintaining parallel copies on different machines. The result was confusion, lost work, and the constant challenge of keeping everyone's version of the code in sync.

Git, the version control system created by Linus Torvalds in 2005, solved the technical problem of distributed code management. GitHub, launched in 2008, built a social platform on top of Git that transformed software development from an activity done in isolation or in small teams into a genuinely networked, collaborative enterprise.

GitHub's model allowed developers to host code repositories publicly or privately, track changes across contributors, submit proposed changes through a "pull request" process, and manage issue tracking and project planning in one place. The open-source software movement, which had previously relied on mailing lists and fragmented hosting services, migrated to GitHub and flourished. Contributing to an open-source project became as simple as clicking a button to fork the repository and proposing changes.

The effect on the software industry was transformative. Open-source software, which was already important before GitHub, became the default mode of software development. Virtually every major software project — including the operating systems, databases, programming languages, and frameworks that the internet runs on — is now developed on GitHub or a similar platform. The ability for developers anywhere in the world to collaborate on shared codebases without logistical friction produced a global development commons that accelerated the pace of software innovation.

GitHub also changed how developers present their professional credentials. A GitHub profile, showing a developer's contributions to open-source projects, became a standard part of the hiring process in technology. The portfolio of public work replaced, in some contexts, the traditional resume.

Credit: cottonbro studio  /  Pexels

Office communication in the early 2010s was mostly email, with some internal intranets and shared drives. Email is asynchronous by design, organized around individual messages rather than topics or teams, and poorly suited for the kind of rapid, informal communication that collaborative work requires. It also conflated internal communication with external communication, putting client emails and vendor invoices in the same inbox as internal team discussion.

Slack $WORK, launched in 2013 by Stewart Butterfield, organized workplace communication around channels — persistent, searchable conversations organized by topic or team. Messages sent in a channel were visible to everyone in that channel, reducing the email overhead of keeping teams informed. Integration with other tools allowed notifications from project management systems, code repositories, and other services to flow into relevant channels, making Slack a central hub for team activity.

The impact on knowledge work was significant. Teams that moved to Slack reported reducing internal email substantially. The searchable, channel-based format made it easier to find past decisions and context. The reduction in friction for quick questions and coordination changed how teams worked together, enabling faster iteration on projects.

Slack also had an unintended effect: it created a new form of always-on pressure. The expectation of rapid responses to Slack messages, in an environment where it was visible whether someone was online, contributed to a sense of continuous availability that many workers found stressful. The tool designed to reduce communication friction also reduced the friction of interruption.

The broader shift that Slack represents — toward real-time, platform-based team communication rather than email — accelerated dramatically during the COVID-19 pandemic, when remote work became mandatory for knowledge workers globally. Microsoft $MSFT Teams, Slack's primary competitor, saw explosive growth in 2020. The model of channel-based communication has become a permanent feature of how distributed teams work, and the physical office's role as a communication hub has diminished partly because these tools replicate many of its communication functions.

Credit: hookle.app / Unsplash

Before Shopify $SHOP, selling online required either technical expertise or significant investment. The dominant e-commerce platforms for small businesses were complex to set up and customize. A small business owner without programming skills who wanted to sell online faced high barriers: either hire a developer, or accept the significant limitations of a rigid template-based solution.

Shopify, founded in Ottawa in 2006 by Tobias Lütke, Daniel Weinand, and Scott Lake, offered an integrated solution that handled storefront design, product management, payments, and order fulfillment in a single platform. A merchant could set up a functional online store without writing code, and the platform handled the underlying complexity of payment processing, security, and infrastructure.

The effect on retail was substantial. Shopify lowered the barrier to entry for online retail to the point that essentially any small business could have an e-commerce presence. It contributed significantly to the growth of the direct-to-consumer business model, in which brands sell directly to customers through their own websites rather than through retailers. This model had been practiced by large companies for years, but Shopify made it accessible to small and medium-sized businesses.

The platform also created an ecosystem: app developers built integrations and extensions for Shopify, agencies specialized in Shopify store design, and logistics companies optimized their services for Shopify merchants. This ecosystem created economic activity around the platform beyond the merchants themselves — a pattern that appears repeatedly in successful platform businesses.

Shopify's impact on traditional retail was part of a broader shift rather than a single cause. The rise of e-commerce had been underway for years before Shopify. But Shopify specifically accelerated the participation of smaller merchants in that shift, changing the composition of online retail. The long tail of small direct-to-consumer brands that now sell online is substantially a product of platforms like Shopify making it logistically feasible.

Credit: AS Photography /  Pexels

Data has always existed in organizations, but for most of corporate history, accessing and visualizing that data required either programming skills or the services of a specialized IT analyst. Managers who wanted to understand their business data submitted requests to IT departments, waited days or weeks for reports, and received static outputs that were difficult to explore or interrogate. The gap between the people who had questions about data and the people who could answer them was wide and expensive.

Tableau, founded in 2003 as a spin-off from a Stanford University research project, built a visual data exploration tool that allowed users without programming skills to connect to data sources and create interactive visualizations by dragging and dropping fields onto a canvas. The tool's drag-and-drop interface, combined with its intelligent suggestion of appropriate chart types, made data visualization accessible to business users who had no experience with charting software or statistical analysis.

The impact on business intelligence and analytics was significant. The traditional business intelligence model — in which a small team of analysts served as intermediaries between business users and data — gave way to a model of "self-service analytics," in which business users explored data directly. This shift happened gradually, through the 2010s, but Tableau was central to it.

Healthcare, retail, financial services, and government were among the earliest adopters at scale. Health systems used Tableau to track patient outcomes, monitor quality metrics, and manage operational performance. Retailers used it to analyze sales patterns and inventory. Financial services firms used it for risk analysis and regulatory reporting.

The broader effect was an increase in data literacy across organizations. As more business users worked directly with data visualization tools, the expectation that managers could interpret and work with data grew. This in turn increased demand for clean, well-structured data, driving investment in data infrastructure more broadly. Tableau's success helped establish data visualization and business intelligence as a mainstream corporate function rather than a specialist back-office activity.

Credit: Alesia Kozik /  Pexels

Stock markets have existed for centuries, but for most of that history, trading was a physical activity. On the floor of the New York Stock Exchange, specialists stood at posts managing the market in specific securities, matching buyers and sellers through a process of open outcry and negotiation. Prices were determined by human negotiation in real time, and the people on the floor — specialists, floor brokers, traders — had significant advantages in information and execution over those who traded off-floor.

The shift to electronic trading happened over several decades, driven by platforms like NASDAQ's early electronic system in the 1970s and the rise of dedicated electronic communications networks, or ECNs, in the 1990s. But the decisive moment came with the widespread adoption of fully electronic order matching systems, which replaced the specialist and open-outcry systems with algorithmic matching of buy and sell orders.

The effects on financial markets were structural. Bid-ask spreads — the difference between the price at which someone will sell and the price at which someone will buy — narrowed dramatically as electronic systems created more competition among market makers and reduced the informational advantages of floor participants. Transaction costs for individual investors fell sharply. The speed of execution went from seconds to microseconds.

The human cost was also substantial. The ecosystem of people who had worked in floor-based trading — specialists, runners, floor brokers — largely disappeared as electronic systems took over. The NYSE's floor, once a chaotic and densely crowded physical market, is today largely a television backdrop, with most actual trading happening electronically in data centers in New Jersey.

Electronic trading also created new dynamics — including high-frequency trading, in which algorithmic systems execute enormous numbers of small trades in fractions of a second. This development has been economically and regulatorily contested, raising questions about market fairness and stability that remain unresolved.

Credit:  Chris Montgomery / Unsplash

Video conferencing technology existed for decades before Zoom $ZM, but it was expensive, unreliable, and logistically complex. Systems from Cisco $CSCO, Polycom, and others required dedicated hardware at both ends, IT support to configure, and bandwidth that many organizations couldn't reliably provide. Video calls between organizations required scheduling, testing, and technical coordination that made them rare rather than routine.

Zoom, founded by Eric Yuan in 2011, built a video conferencing system optimized for ease of use and reliability over unreliable network connections. Its one-click join links eliminated the need for accounts, downloads, or configuration on the part of guests. Its adaptive streaming technology maintained call quality even on inconsistent connections. The result was a product that could be used routinely by people without technical expertise.

Before the COVID-19 pandemic, Zoom was growing steadily but remained primarily a business tool. The pandemic transformed it into something close to essential infrastructure for education, healthcare, government, and personal communication. Between December 2019 and April 2020, Zoom's daily meeting participants grew from approximately 10 million to 300 million. Schools, universities, courts, and legislatures all shifted to Zoom almost overnight.

The pandemic proved that video conferencing was capable of substituting for in-person meetings in many contexts where this had previously been considered impossible. Telemedicine — the delivery of healthcare consultations via video — expanded enormously. Remote court hearings, long resisted by the legal system, became standard. University classes shifted online. Corporate boards held virtual meetings.

The implications for commercial real estate, urban geography, and knowledge work are still playing out. The realization that many knowledge workers could do their jobs from anywhere — established in stark terms by the pandemic and enabled by tools like Zoom — has had lasting effects on patterns of work and the demand for office space. The relationship between geography and economic opportunity changed in ways that continue to develop.

Credit: Visitor7  / Wikimedia Commons (CC BY-SA 3.0)

Amazon $AMZN Web Services launched its first services in 2006, offering storage and computing infrastructure on demand, billed by usage. The idea was straightforward in retrospect: Amazon had built large-scale computing infrastructure for its own e-commerce operations, and those resources were often underutilized. Selling spare capacity to other companies would generate revenue and create a new business.

What Amazon was actually doing, though, was inventing cloud computing as an industry. Before AWS, a company that wanted to deploy a web application needed to buy or rent servers, install them in a data center, configure networking, and manage the ongoing maintenance of the hardware. This was expensive, slow, and required specialized IT staff. It meant that launching a new product or service required months of infrastructure work before a single line of application code could be tested in production.

AWS made that infrastructure available on demand. A developer could provision a server, a database, a storage bucket, and a load balancer in minutes, paying only for what they used. The startup that had previously needed $5 million in hardware investment before writing a line of product code could now launch with a credit card and scale infrastructure as demand grew.

The effect on the technology industry was profound. The startup ecosystem changed dramatically. Companies like Airbnb $ABNB, Uber $UBER, and Pinterest $PINS launched in the AWS era and built globally scalable products without ever owning a server. The economics of the software industry shifted: the barrier to launching a software product dropped to near zero for infrastructure, concentrating cost in product development and customer acquisition.

Enterprise technology was also transformed, though more slowly. The shift of corporate applications from on-premises data centers to cloud infrastructure — initially resisted by IT departments and security teams — became the dominant trend of the 2010s. The cloud became the default environment for new software development and gradually for legacy systems as they were replaced or modernized.

Credit: Yan Krukau /  Pexels

Human resources management was, for most of the 20th century, a heavily paper-based function. Personnel files were physical folders. Payroll was calculated manually or with basic software that required significant manual input. Benefits enrollment happened through paper forms. Performance reviews were paper documents stored in filing cabinets. The HR department was largely an administrative function with limited analytical capability.

The first wave of enterprise software brought HR into digital systems, but these were often on-premises, heavily customized, and poorly integrated. Payroll systems didn't talk to benefits systems. Workforce planning data lived in spreadsheets disconnected from the systems of record. HR analytics — the ability to understand workforce patterns, predict turnover, or model the impact of compensation changes — was available only to large companies with dedicated analytical resources.

Workday $WDAY, founded in 2005 by PeopleSoft veterans Dave Duffield and Aneel Bhusri, built a cloud-native human capital management platform from scratch. Because it was designed for the cloud rather than adapted from on-premises software, it could offer a unified system that handled payroll, benefits, recruiting, talent management, and workforce analytics in a single application with a consistent data model.

The effect on the HR profession was significant. The administrative burden of paper-based HR processes diminished. More importantly, the availability of workforce data in an integrated system created the foundation for what became known as "people analytics" — the use of data to understand and manage workforce dynamics. Companies could now analyze which managers had the highest employee retention, whether specific training programs affected performance outcomes, or how compensation compared to market benchmarks across job families.

Workday also contributed to a broader shift in how HR departments are perceived within organizations. The availability of workforce data transformed HR from a primarily administrative function into one with analytical capabilities and a stronger claim to strategic relevance. The profession changed in response, with data literacy becoming an increasingly expected skill for HR professionals.

Credit: Pavel Danilyuk  /  Pexels

Online payment processing before Stripe required a merchant to establish a relationship with a payment gateway company, a merchant bank, and often a payment service provider — three separate entities with three separate agreements, technical integrations, and fee structures. A startup developer who wanted to accept credit cards on a website in 2009 faced weeks of paperwork, compliance requirements, and technical work before processing a single transaction.

Stripe, founded in 2010 by Patrick and John Collison, reduced that process to a single API integration that could be completed in minutes. A developer could add Stripe to a website with a few lines of code and begin accepting payments immediately. Stripe handled the relationships with payment networks, compliance with card industry standards, and fraud detection as part of the service.

The effect on internet commerce was direct and measurable. The barrier to accepting payments online — previously a significant obstacle for small businesses and startups — effectively disappeared. Products that required payment processing could be built and launched much faster. The friction reduction was particularly significant for developer-built products: Stripe's developer-first design philosophy made it the default choice for technical founders building internet businesses.

Stripe also expanded the global reach of internet commerce by handling the complexity of accepting payments in different currencies, from customers using different payment methods in different countries. A startup in Dublin or Singapore could accept payments from customers in 50 countries through a single integration, rather than dealing with the regulatory and technical complexity of each market separately.

The company's broader impact on fintech is also significant. Stripe's success helped establish the idea that financial infrastructure could be delivered as a clean, developer-friendly API — an approach that spread to adjacent areas including payroll (Gusto, Rippling), banking (Stripe Treasury), and lending. The expectation that financial services should be programmable and accessible through simple interfaces is partly a product of what Stripe demonstrated.

Credit: Nataliya Vaitkevich   /  Pexels

Filing income taxes in the United States is an unusually complex process by international standards. The tax code involves numerous deductions, credits, phase-outs, and form dependencies that interact with each other in ways that are difficult to track manually. For much of the 20th century, the practical options for most Americans were to hire a paid preparer — a tax professional — or to fill out forms by hand, following IRS instructions that assumed a baseline of accounting literacy.

Intuit $INTU's TurboTax, first released in 1984 as "TaxRax" and renamed and relaunched in 1993, offered a third option: guided software that walked users through a series of questions and completed the appropriate tax forms automatically. Rather than understanding the structure of a 1040 and its supporting schedules, a user could answer questions in plain English — "Did you work from home this year?" "Did you sell any stocks?" — and the software would determine which forms were needed and populate them.

The immediate effect was on the tax preparation industry. H&R Block $SQ and independent tax preparers had built substantial businesses serving middle-income Americans who needed help navigating tax complexity. TurboTax made it practical for a significantly larger share of the population to self-prepare returns, putting direct competitive pressure on paid preparers at the lower and middle complexity ends of the market.

The broader effect was on financial literacy and access. Tax-advantaged savings vehicles — IRAs, 401(k)s, health savings accounts — are more valuable when taxpayers understand how they interact with their tax liability. TurboTax's guided approach helped users understand, at least partially, how their financial decisions affected their taxes, which arguably contributed to better financial decision-making at the margin.

The political economy of tax software is also notable. Intuit spent substantial sums lobbying against the IRS creating its own free filing system, in an effort to protect TurboTax's market. The debate over who should bear the cost of tax compliance — taxpayers, through commercial software, or government, through a free system — reflects how deeply embedded TurboTax has become in the American tax filing ecosystem. Its dominance represents a privatization of a public function that is unusual by international standards.