The Software Retired With Her

Call her Darlene. She gave notice the week before Thanksgiving. Thirty-one years in the office, the last eleven of them as the only person who really ran the dispatch and ticketing system you bought in 2015. She sat through the vendor's admin training when nobody else could spare the week. She built the product codes, loaded the customer list, set up the rate tables, and figured out the override for split loads after the vendor's own support line couldn't. When anything in that system needed changing, the whole company had one procedure: ask Darlene.

Everyone assumed the software held the knowledge. It was the other way around. Darlene held the knowledge, and the software held Darlene.

What she actually knew

Nobody wrote her job down, because her job was never officially a job. It accreted. By the time she left, it included which of the three "Hendricks" customer records was the real one and which two were duplicates from the 2015 migration. Which product code meant washed sand and which one, misnamed years ago, meant screened topsoil. The sequence of four screens that had to be touched, in order, to close a month without orphaning tickets. The password to the admin console, which was also the password to the report builder, written in her handwriting somewhere.

There was a binder once. The vendor's consultant left it after go-live. It described the system as configured in March 2015, and the system stopped being that system by the following fall. The real documentation was Darlene.

How a rollout dies

Nobody shuts a system like this off. It erodes.

In February, your supplier raises the price of 57s and you quote customers the new number the same week. The number in the rate table doesn't change, because the rate table screen asks questions nobody left in the building can answer. So the office starts correcting invoices by hand before they go out. One workaround.

In April you start selling screened compost. It needs a product code. The vendor's support line is helpful and patient and says, twice, "your system administrator can add that in configuration." Your system administrator is in Fort Myers. Compost gets ticketed under an old mulch code at the mulch price, $4 a yard light, and a note taped to the scale house monitor says to fix it at billing. Workaround two, and this one leaks money every load until somebody catches it.

By June the scale operator has quietly gone back to the carbon book for anything the screens fight her on, which is more things every month. The office keys invoices from paper. Workaround three swallows the first two: the paper is the system again. What you bought still runs, technically. It prints a ticket if you only ask it for things it already knows. But the operation has stopped believing it, and once that belief goes, a system is done. The $30,000 license and the eighteen months of setup end their life as a login nobody has.

No meeting was held. No decision was made. That's the signature of this failure mode: the software doesn't get cancelled, it gets routed around, the way traffic routes around a closed bridge.

The failure wasn't Darlene leaving

People leave. Retirement, a better offer, a spouse's transfer. A back office that can't survive a departure isn't unlucky; it was built wrong. It wasn't your build, though. The software made her memory into infrastructure. That was the design.

The systems sold to quarries, elevators, and hauling outfits between 2000 and 2020 shared this shape. They were configurable, which the demo presented as flexibility. In practice, configurable meant that the software arrived empty and somebody at your company had to pour the business into it: every product, every customer, every rate, every exception, expressed in the vendor's terms, maintained in the vendor's screens. That somebody became a single point of failure the day she finished the training.

Compare the tool the software replaced. A carbon ticket book has no administrator. A new clerk can read last year's tickets her first morning, because the knowledge is on the page: customer, product, quantity, date, a signature. Price lives on a rate sheet anyone can photocopy. When the person who writes the tickets leaves, the next person picks up the same book and writes the next ticket. The owners who looked at the admin console in the demo and kept their ticket books were pricing exactly this risk, mostly without a name for it. Call it what it is: key-person risk, built in at the factory, sold as a feature.

Some will say the fix is discipline, that you should've cross-trained a backup and kept the binder current. Ask anyone who sat through one of these rollouts how that plan held up. A shop running eleven hundred tickets a month doesn't have a spare person to maintain a shadow copy of Darlene, and a binder describing a living configuration is stale the month after it's printed. If a system needs that much ceremony to survive normal turnover, the system is the problem.

What the holdouts got right

What finally changed is that software learned to read your paperwork instead of demanding you re-key your business into its screens. Termco works from the tickets your operation already writes: the carbon book stays, the scale house keeps doing what it already does, and the software digitizes the tickets as they are, flags the ones that don't comply, applies your billing rules, assembles invoice totals, and keeps the customer and product lists straight. The reference data still exists, but it's maintained as part of the service, not by whoever in your office drew the short straw in 2015.

Which means the operation that let its rollout die, or never started one, skipped nothing that mattered. The paper you kept is the input. If you want to see that demonstrated on your own paperwork, send 10-20 sample tickets to hi@termco.ai and you'll get findings within 48 hours.

Either way, run this test in the office tomorrow: ask who could add a new product code to your system by Friday. If the answer takes the form of one person's name, you don't have a software system. You have that person, and a countdown you can't see.