Good morning.
Can I ask you something a little uncomfortable? If you disappeared from work for a month, what would actually stop moving?
Not who would miss you. What would stop? Today’s story is about a man who learned that, for his employer, the answer was “nothing.” Honestly, that answer is coming for more jobs than most people want to admit, and hiding from the question is the risky move.
— Khadin
Real Talk · 4 min read
In today’s issue:
The journalist who lost his job, then watched AI publish under his name
The gap between being employed and being needed
The employee who automated 90% of a data job
Your four-step move for this week
They laid him off. His byline kept working.

The Scoop: Journalist Ben Touati lost his role in March 2026. Two months later, he found five AI-generated articles carrying his name.
Picture opening your old employer’s website and seeing fresh work under your byline, even though you never wrote it and would never have signed it. Press Gazette reported that this happened to Touati after his contract with ClickOut Media ended. Managers had told him freelancers were being cut as the company raised output with AI.
Then, in late May, he found five machine-made articles published under his name. He said the work fell far below his standards, filed a GDPR claim over the use of his identity, and the company removed the byline.
I’ll say the quiet part: his name had become an asset that could keep producing without him. His reputation was inventory. The shift underneath the layoff headlines is bigger than a few automated tasks because the output can continue while the person becomes optional.
So what for you: build value that a workflow cannot quietly claim. Your judgment and relationships matter, and so does publishing work where you control the name attached to it.
Look at your own week. How much of what you produce could ship without you?
The uncomfortable gap
You can feel busy every day and still be easy to route around. The question that decides your bargaining power is simpler: what breaks if you stop?
Here’s what I actually think. The people in the most danger are the ones who refuse to inspect their own work. You cannot reposition around a risk you will not name. The useful place to stand is on the building side, where you understand the workflow and can explain where human judgment still earns its keep.
Which side are you building toward this week?
Live Webinar: SSP Automation, Native to Your Billing Platform
Most finance teams still track SSP in spreadsheets — manually updated, disconnected from billing. On July 22, Tabs' product and marketing leads show what changes when SSP runs natively inside your billing platform: built from real billing data, connected to your Product Catalog, and generating audit-ready documentation automatically.
You'll leave with a clear view of how SSP and billing connect, what transaction price allocation looks like under ASC 606 in practice, and what it takes to close faster without reconciling SSP to contracts by hand.
July 22, 2026 · 1:30–2:00 PM EDT · Live + recording
Register now to save your spot, or read more about how Product Catalog powers billing automation.
She automated 90% of her job. Nobody noticed.

You should know this example came before the current AI rush. In a February 2025 Mumsnet post, an anonymous UK education employee said her predecessor spent more than 50 hours a week running a database and producing reports. Within a month, she had automated the recurring work and connected the systems.
She said the job now took four to six hours a week, including small tasks like fixing printers and laptops. This was database automation, not a chatbot doing magic, which makes the lesson more useful: repeatable work was vulnerable long before today’s models arrived.
My take is simple. The person who maps the work sees the risk first, and that person has a chance to own the new system. What is the most repeatable hour on your calendar?
The numbers, then your move
You do not need a scary prediction when the hiring mix is already changing. Reuters reported that Thomson Reuters planned to cut up to 500 engineering roles while expecting to add more than 250 net-new engineering jobs over two years, most of them senior and “AI-native.”
Across tech, roughly 120,000 people at 228 companies had lost jobs in 2026 by mid-July, according to Layoffs.fyi figures cited by Reuters. That does not prove AI caused every cut. It does show that the safer position is moving toward people who can direct the systems and own the outcome.
Your four-step move:
Write down the repeatable outputs your job rewards.
Circle one a workflow could already handle.
Name the part that still needs your judgment or trust.
Make that part visible to the people who pay you this week.
That is your insurance. Small, honest, and worth one focused hour.
Explore the AI Insiders tools directory →
Find the tool for the part of your workflow you should own next.
Quick question
Honestly, how much of your job could a workflow do today?
Prefer words? Reply with one word: SAFE, NERVOUS, or BUILDING. I read the replies, and they help shape what I write next.
Tomorrow on Money & Career: what people who own the workflows are charging for them right now.
— Khadin
P.S. If your team has a messy workflow you want AI to handle, reply with AI AUDIT, the tools you use, and what a win would look like.
Want to reach 60K+ people learning to use AI for real? Reply to this email and we’ll send rates.



