Automation baked in, not bolted on

by Ross Gordon, Founder, Assist IQ

The most instructive build we have shipped was not for a tech company. It was for HALO Intervention Services, an oil and gas well intervention firm whose operational record had always lived on paper, in an industry where the record is the product as much as the work is.

The obvious project would have been digitisation: scan the forms, buy some software, bolt a reporting tool onto the existing process. That is what most of the industry does, and it is why most of the industry still dreads audits.

We did the opposite. The processes themselves were designed around AI automation and augmentation, so the record is produced as the work happens rather than reconstructed afterwards. The entire ISO 9001 management system was generated on the same principles. Compliance stopped being a separate activity that happens after the work, done by tired people at month end, and became a property of how the work runs.

Why this matters outside oil and gas

Every business has its version of the paper lag: the CRM updated from memory on Friday, the expenses reconstructed at year end, the certificate tracked in a spreadsheet nobody opens. In each case the record and the work have drifted apart, and a human is paid to push them back together.

The lesson from heavy industry is that bolting automation onto that gap does not close it. You get a faster way to reconstruct records that are still wrong. The fix is upstream: design the workflow so the record is a by-product of doing the work, then let AI employees and agents carry the reading, filing, chasing and flagging that keep it true.

That principle now runs through everything we build, from property portfolios that chase their own gas certificates to a will-writing business where one person carries the admin of four. If your industry has real compliance stakes, the deeper version of this argument is on our oil and gas and engineering page. It was written for the sector that taught us the lesson.

More from the blog

Claude Code for business: what a real deployment involves

Deploying Claude Code across a company is eight decisions, not an install. Here is the deployment decision document we use, the security questions a client will ask you, and what Anthropic assesses before it issues its Claude Code partner badge.

Read more

Claude certification: what Anthropic actually tests

The Claude Certified Associate exam is proctored, closed book and scored out of 1000. The surprise is what it weights most heavily: not writing prompts, but knowing when the answer is wrong and when a human has to check it.

Read more

Start with a free enquiry

Not a discovery call. Not a pitch with a calendar link. Five questions about how your business actually runs, and it costs nothing. Ross reads every enquiry himself and replies within one working day with a straight first answer: what looks worth automating, and what doesn’t.

If it looks like we can genuinely help, the next step is the AI Operations Day: one working day inside the business, followed by a written Opportunity Map. It shows what is hurting, what should stay human, and the best one or two jobs to prove first. That part comes later, and only if it makes sense for you.

Tell us what is slowing you down

Free to ask. No obligation. Ross replies personally within one working day.