What is a System of Record, and what makes some stickier than others?
A system of record keeps track of the atomic units of a business. Calendars for resources and people (busy vs free), inventory (in stock vs not, delivery dates, costs), personnel (hours worked, vacation days, and salaries), shareholders (ownership, options, and types of stock), etc.
Some of these items are “static.” Some are read constantly. Some are written and changed constantly. Sometimes there are far more reads than writes, and sometimes the opposite. Some of these are connected to many different “pipes” through APIs or corporate processes; some are used once and virtually forgotten. Some are intermittently read but of tremendous value (e.g., shareholder records!), and some are frequently read but of relatively low value (e.g, conference room calendars).
Sometimes systems of record bundle these things together, in something that we typically refer to as a “vertical operating system.” ServiceTitan, for example, represents multiple systems of record (or a system of multiple records!). An Air Conditioning business must know its customers (CRM), when its technicians (personnel) are free (calendar), and parts (inventory) that are available for sale, and at what prices (accounting).
A system of record for the busy/free status for conference rooms in your Miami office? Perhaps a pain to replace, but effectively costless.
A system of record for tables in your Miami restaurant that grosses $20M a year? Just dropping one hour of records might cost more than the yearly savings of switching to a lower cost system.
And then, of course, there are systems of record for raw data — literal databases that underpin virtually all systems of record. Ask a CTO running dozens of tables with billions of reads and writes per day how hard it is to swap out a mySQL database for Postgres and you’ll elicit visible anger.
The stickiness of a system of record is a function of all of these different inputs, against the cost (often front-loaded/one-time) and risk (lost revenue, profits, and mistakes) of moving. Imagine paying $100/month for software where a $1/month option exists, but the one-time labor cost of switching is $3000, and there’s a risk that something goes terribly wrong. It’s quite logical to keep paying $100/month!
This is part of why greenfields are often superior to brownfields. It’s why finding things outside of the goldilocks zone of pricing, or outside of acceptable satisfaction levels (too hated), is a possible unlock. And as services become the new battlefield, “migration as a service” could *finally* bend the cost/benefit analysis of switching.
It’s great to be a system of record. I’ve always said that the best companies have hostages, not customers — but the hostages have a lot more tools to free themselves in 2026. Take note.