Let’s begin by defining “operations software” in one sentence:

Operations software is custom software built to streamline and codify the unique business processes of a team or individual.

There are three critical ideas in this definition.

  • Built for unique business processes: this software is designed for a specialized group of users with unique requirements, like internal users at a company. Unlike a SaaS (software-as-a-service) product, which is designed to serve a broad audience, operations software is built to model a workflow that doesn’t exist in exactly the same way across industries or companies.
  • Built for productivity: this software is focused on saving time for end users, usually by automating or streamlining a process that would otherwise require significant time to complete manually. The user interfaces tend to be focused on productivity (forms, data tables, charts, and so on), versus differentiated visual presentation (eye-catching animations, scroll effects, or fanciful interaction patterns).
  • Built around data: this software enforces rules about how a workflow should be carried out, validating data inputs and outputs, and preventing human errors. It orchestrates multiple data sources, often with privileged access to some or all of them. For that reason, access controls and auditing are usually very important.

You might be as surprised as we were to learn that half of all Software built today fits this description. Forrester estimated that $120 billion dollars is spent developing custom software every year, most of which could be described as operations software.