We keep a dataset of the automation work our principals have shipped and scoped: one thousand three hundred and twenty-two automations across thirty industries, mapped to the tools they run on. We keep it because pattern-matching against real work beats intuition, and because it forces honesty about what actually gets built versus what gets talked about. After enough entries, two things become clear at the same time, and they pull in opposite directions.
The first: the shapes repeat. Strip the vocabulary away and an enormous share of operational AI is one of a handful of moves. Something arrives: an email, a document, a transaction, a call. It gets read and structured. A decision is made about it. It gets routed to a system or a person. Something is written back, and someone is told. Intake, extraction, decision, routing, record. A logistics dispatcher and a clinic front desk do not think they share a workflow, but at this altitude they nearly do. This is why experience compounds across industries: the engineer who has shipped document extraction for private equity fund reports has already solved most of the retail catalogue problem, even though the two clients would never attend the same conference.
The second: the last mile never repeats. The recurring shape is maybe seventy percent of the system, and it is the easy seventy percent. What remains is the part that decides whether the thing survives: this company's exception rules, the field that means something different in this ERP than in every other ERP on earth, the approval that legally must be a named human in this jurisdiction, the supplier who still sends the manifest as a photographed fax. None of that generalises. All of it is the actual work. This is why we refuse to group industries into neat clusters and sell the cluster: the label flatters the pattern and hides the last mile, and the last mile is where projects die.
The recurring shape is maybe seventy percent of the system, and it is the easy seventy percent.
The practical consequence is a two-speed way of building. Move fast through the recurring shape. It is known territory, and there is no prize for rediscovering it slowly. Then slow down, deliberately, at the boundary where the operation becomes itself. Walk the exceptions with the people who handle them today. Read the weird records, not the clean ones. Budget real time for the fax.
When someone asks whether we know their industry, the honest answer is usually: we have shipped the shape of your problem more than once, and we have never shipped your version of it. Both halves of that sentence matter. The first is why the project will not start from zero. The second is why we will not pretend it starts at ninety percent.