A Job Ad Just Told You Where AI Actually Saves You Money

A job ad crossed my desk last week that didn’t exist eighteen months ago.

“AI Automation Specialist (Claude Code). Turn messy, manual agency and client work into reliable automations using Claude Code: wiring together APIs, databases, and dashboards so the team stops doing repetitive work by hand.” Full-time. There was a line about a Make.com sequence connecting to Claude, and another about “persistent AI agents across all standard departments.”

Strip away the tooling names and read what they’re actually hiring for. Someone in that company looked at the hours their team burns moving information between systems by hand, and decided it was worth a full-time salary to make it stop. That’s the signal. Not “AI is coming for jobs.” The opposite, almost: there is now a specific, nameable layer of work in most businesses that has quietly become automatable, and companies have started paying real money to capture it.

This post is about where that layer sits, what the work actually looks like, and how to get the value without the new risk it introduces. Because the same tooling that saves you ten hours a week can also, wired carelessly, hand an AI write-access to your live store.

The work lives in the gap between the tools you already pay for

Here’s the thing the job ad gets right. The opportunity isn’t a new app. It’s the space between the apps you already have.

Every business above a certain size runs on a handful of systems it looks at every morning. A code repository. A project tracker. A time tracker. A CRM. An accounting package. An e-commerce backend. Each one is good at its own job. None of them talk to each other without a human in the middle copying, pasting, reconciling, and re-typing. That human-in-the-middle work is invisible on any org chart, but it adds up to days per month across a team.

Until recently, closing that gap meant a custom integration project: brittle, expensive, and obsolete the moment a vendor changed an API. What changed is a boring piece of plumbing called the Model Context Protocol (MCP), the open standard Anthropic released so that AI tools like Claude Code can read from and act on your existing systems through a common connector. It sounds like infrastructure trivia. In practice it means the tools that have always been silent to AI can now be given a voice, safely and one at a time.

That’s the job. Not “build an AI”. Connect the AI you can already buy to the systems you already run.

Three ways this has played out for us

We don’t talk about this in the abstract. We’ve spent the last few months doing exactly this work, for ourselves and for clients. Three examples, three different shapes of the same pattern.

1. The Monday-morning report that writes itself

I used to learn what my team had actually done by skimming merge requests, reading standups, and sitting through a quarterly review. Visibility by archaeology.

We built a small connector between our internal time tracker and Claude, about a week’s work, and pointed it at our code repository and project tracker as well. Now I can ask one question and get back the story of the last eight weeks: which tickets moved, where the hours went, the nine-day debugging arc nobody flagged in standup, the infrastructure cleanup that quietly removed a hundred dollars a month of waste. Three engineers, 590 hours, read and narrated in about twelve minutes.

The repetitive work this killed wasn’t glamorous. It was the manual assembly of status reports, the cross-referencing of “what did we bill” against “what did we ship”. That’s gone. The report assembles itself, and a human spends their time judging it instead of building it.

2. The development flow itself

The second example is the one closest to the job ad’s “messy client work”. Our own delivery process, the one we run on client projects, is wired so that the AI does the mechanical parts and our senior people do the judgement.

A ticket comes in. The system reads it, reads the relevant code, drafts an implementation, and runs it past five specialist reviewers in parallel: architecture, security, quality, user experience, and SEO, each looking at the same change through a different lens. A human approves at each gate. The repetitive part (the boilerplate, the first-pass review, the changelog, the project-tracker bookkeeping) is automated. The expensive part (deciding whether the approach is right) stays with people. We run this for ourselves and on client engagements, and it’s the difference between a senior team covering the ground of a much larger one.

3. A client running her Shopify store through Claude

The third is a customer who came to us with a simpler ask: she wanted to run her Shopify store by talking to it.

Not replace Shopify. Shopify is excellent at being Shopify, and we’d never pitch ripping out a core platform a business already depends on. She wanted the layer on top: “tell me which orders are stuck in fulfilment”, “draft a blog post for this new collection and the product descriptions to match”, “which products haven’t sold this quarter”. Work that’s a dozen clicks and a spreadsheet export each, several times a day.

We connected Claude to her store through a read-first MCP connector: it could see orders, products, collections, and content before it could change anything, and write-access was added deliberately, scope by scope, once she trusted what it was doing. The repetitive merchandising and reporting grind compressed into a conversation. The platform underneath didn’t change at all.

The pattern, and the part that goes wrong

Look across the three and the shape is identical. Low blast radius first. The tools were already there. The connector was small. And in every case the AI was given read before it was given write.

That last point is where this work turns from a productivity story into a risk story, and it’s exactly where an inexperienced “wire it all to Claude” job hire gets a business into trouble. Giving an AI agent the keys to your live systems is a security decision, not a convenience one. The questions that matter are the boring ones:

This is the same governance discipline that separates production software from a working demo. It doesn’t slow the value down. It’s the thing that lets you actually trust the value once it arrives.

You probably don’t need a full-time hire on day one

The company in that job ad decided this work was worth a permanent salary, and at sufficient scale they’re right. But for most mid-market businesses, the honest answer is that the first version of this is project-shaped, not headcount-shaped. You find the two or three places where your team bleeds the most hours into manual system-shuffling, you wire those up carefully, read-before-write, and you measure what it gives back before you commit to more.

The value is real and it’s available now. The job ad is just the market saying so out loud.

If you’d like to find where this layer of work is hiding in your business, and have it wired up by people who treat AI’s access to your systems as a security decision rather than a shortcut, that’s the work we do. Have a chat with us.

Social Package

LinkedIn

A job ad crossed my desk last week that didn’t exist eighteen months ago.

“AI Automation Specialist (Claude Code). Turn messy, manual client work into reliable automations: wiring together APIs, databases, and dashboards so the team stops doing repetitive work by hand.” Full-time.

Strip away the tooling names. Someone looked at the hours their team burns moving information between systems by hand, and decided it was worth a full-time salary to make it stop.

That’s the signal. There is now a specific, nameable layer of work in most businesses that has quietly become automatable. It lives in the gap between the tools you already pay for: the code repo, the project tracker, the CRM, the e-commerce backend. Each is good at its own job. None of them talk to each other without a human copying and re-typing in the middle.

Three ways we’ve seen it play out lately:

  1. A Monday-morning team report that used to take hours of cross-referencing now assembles itself. 590 hours of work, read and narrated in twelve minutes.

  2. Our own delivery flow, where the AI does the mechanical parts and senior people keep the judgement.

  3. A client running her Shopify store by talking to it. “Which orders are stuck? Draft the new collection’s copy.” The platform underneath didn’t change at all.

The pattern is identical every time: low blast radius first, and read-access before write-access. Giving an AI the keys to your live systems is a security decision, not a convenience one.

You probably don’t need a full-time hire on day one. You need to find the two or three places your team bleeds the most hours, and wire those up carefully.

Where’s that layer hiding in your business? Tell me where it hurts in the comments.

#automation #ai

Twitter/X Thread

1/ A job ad crossed my desk last week that didn’t exist 18 months ago:

“AI Automation Specialist (Claude Code). Turn messy manual work into reliable automations: wiring APIs, databases and dashboards so the team stops doing repetitive work by hand.”

Read what they’re actually hiring for.

2/ Not “AI is coming for jobs.”

The opposite. Someone looked at the hours their team burns shuffling data between systems by hand and decided it was worth a full-time salary to make it stop.

There’s a nameable layer of work that just became automatable.

3/ It lives in the GAP between the tools you already pay for.

Code repo. Project tracker. CRM. Accounting. Store backend.

Each is great at its own job. None of them talk to each other without a human copying, pasting and re-typing in the middle.

4/ Three ways we’ve seen it play out:

— A team status report that used to take hours now writes itself. 590 hrs of work narrated in 12 minutes. — Our dev flow: AI does the mechanical parts, seniors keep the judgement. — A client running her Shopify store by talking to it.

5/ The pattern is identical every time:

Low blast radius first. The tools were already there. The connector was small. And the AI got READ access before it ever got WRITE access.

6/ That last one is the whole game.

Read-only access to your orders is a report. Write-access is something that can refund, cancel and edit at machine speed.

Giving an AI the keys to live systems is a security decision, not a convenience one.

7/ You probably don’t need a full-time hire on day one.

Find the 2-3 places your team bleeds the most hours into manual system-shuffling. Wire those up carefully. Measure what comes back. Then decide.

The value’s real and available now. The job ad just said so out loud.

8/ Wrote the long version with the three examples and the questions to ask before you give an AI access to anything:

[link]

What’s the most repetitive between-systems task eating your week? Reply and I’ll tell you if it’s wire-up-able.

Email Excerpt

A job ad crossed my desk last week that didn’t exist eighteen months ago: “AI Automation Specialist (Claude Code). Turn messy, manual client work into reliable automations, wiring together APIs, databases, and dashboards so the team stops doing repetitive work by hand.” Full-time.

Strip away the tooling names and read what they’re hiring for. Someone looked at the hours their team burns moving information between systems by hand, and decided it was worth a permanent salary to make it stop.

That’s the signal. There’s now a specific layer of work in most businesses that has quietly become automatable, and it lives in the gap between the tools you already pay for. I wrote up what that work actually looks like, with three real examples (an internal report that writes itself, our own delivery flow, and a client running her Shopify store by talking to it), plus the questions you should ask before you ever give an AI access to a live system.

Read the full post →