AI Strategy

One month AI is causing layoffs, the next it's creating jobs. What’s really happening?

What the whiplash looks like from the delivery side, where the shift shows up in the work before it shows up in a headline.

If you’ve been following the headlines recently, or been inside a venture circle, you’ve heard these confident lines: AI is creating jobs. More AI products get built, so more people are needed to build them. Demand is up.

All of this despite news of rounds and rounds of layoffs across organizations globally.

Both can’t be the whole story, or can it?

I run an Applied AI firm. We build and ship custom, AI-native software for other companies. Because we’re on the delivery side, we feel a market shift in the actual work months before it turns into a take online.

It is a fundamental change in what the job actually is.

And what we’re seeing isn’t more of the same jobs coming back. It’s a hybrid: much less of the work a machine can now do, and much more of the work it can’t.

Why both headlines are true at once

Here’s how both headlines are true at the same time. The cutting and the hiring are hitting different layers of the same job.

What’s getting cut is the output layer. Turning a clear spec into working code. Turning a brief into a first draft. Turning instructions into a deliverable. For a long time that was most of what junior work was, in engineering and well beyond it. A machine does a competent first pass of it now, so it’s getting cheaper by the month.

What’s getting scarcer is everything above that layer. Deciding what to build. Catching the thing that runs fine in a demo and falls over in production. Owning the call when it actually matters. That work didn’t get cheaper. It got more valuable, because now there’s a flood of fast output and not enough people who can tell what’s actually good.

Our experience with customers turning to AI first

Even a year ago, most of our engagements started from a blank page. Discovery, then requirements, then build. Now a growing share starts with a vibe-coded prototype the client already made. They describe what they want, an AI builds them something rough, and they bring it to us to fix what they couldn’t, or didn’t know needed fixing, before it ships at scale.

That’s genuinely useful. The prototype shows us what the customer actually pictures, which pre-AI used to take weeks to pull out of them.

However, contrary to what most people expect, this doesn’t reduce the work. It just demands a different caliber of skills. Making the inside of that thing correct, secure, and able to hold up at scale is often harder than starting clean.

So from the outside, when you count the jobs and the number goes up. From inside the work, you see the seats filled by different people doing a different job. Both are real. Only one of them tells you whether the work is any good.

And if you’ve been around long enough in the tech world, you’ve seen this play out before.

Compilers were going to end programming. Frameworks were going to end it again. Cloud was going to end the sysadmin. Each time, the mechanical part got cheaper and the scarce part moved up a level. Each time, the people who read it as “fewer jobs” were wrong about the number and right about the fear. The count went up. The job description changed underneath them.

The same thing is happening now, only one level higher.

And not only in engineering. In marketing, design, operations, law, the pattern is identical. What’s getting repriced isn’t the whole role, but the part of the role that involved mostly typing and not problem solving.

If you’re hiring or cutting, based on raw output, you’re trading on the one thing that just got cheap. The people who get more valuable from here are the ones who can decide, judge, and stand behind the call. Most companies don’t have enough of them to begin with, and you can’t conjure them back in a quarter.

Conclusion

So, yes AI is creating jobs, and it is also cutting them. It’s doing both to the same job, sometimes in the same week, and the thing that decides which side you land on is whether the work needs a human to be accountable for it, or only to produce it.

That question is going to sort a lot of careers, and a lot of companies, over the next few years.

If you're hiring, building, or exploring the depths of the world of AI, subscribe for an insider’s view.

Originally posted on "Wide Angle by Pradeep Nalluri" on July 14, 2026.

Try Ayrin

We work through the AI-native vs. AI-enabled decision with teams directly

About the Author

Pradeep is a serial entrepreneur and investor with three prior exits and 20+ years running digital businesses across healthcare, technology, education, and business services. He founded Ayrin to close the gap between what AI can do and what most companies actually ship. He was previously CEO of Beam, a $100M holding company, and President of Mutual Mobile, where he scaled the team to 400 employees shipping 700+ digital products.

Pradeep Nalluri

CEO & Founder

Not sure which legacy modernization path your business needs?

We work through the AI-native vs. AI-enabled decision with teams directly, on systems they keep owning outright. If you have a legacy system on the table, we can pressure-test whether re-architecting around AI is worth it for your case before you commit a budget or timeline.

FAQ

What is custom AI development?

Custom AI development is the process of building AI software, agents, chatbots, automation, or internal tools, designed specifically for one organization's workflows, data, and existing systems, rather than adapting to a generic off-the-shelf product.

What's the difference between build, buy, and blend?

Build means you own the underlying model and its logic. Buy means a vendor controls the model and its behavior end to end. Blend, which MIT's research calls "boosting," means the model isn't yours, but you enhance it with your own proprietary data through fine-tuning or retrieval-augmented generation, and you control how it's validated and used.

Is custom AI more expensive than buying an off-the-shelf AI tool?

Usually, yes, up front: custom projects typically range from $5,000 for a focused chatbot to $150,000+ for an enterprise platform, while off-the-shelf tools carry recurring subscription costs instead of a project fee. Off-the-shelf can still cost more over the long run once usage-based pricing, per-seat fees, and unbudgeted customization work are added, which is why total cost of ownership, not the sticker price, should drive the decision.

How long does custom AI development take?

Most projects go from kickoff to a working prototype in two to four weeks, and to full production in four to sixteen weeks depending on scope, with enterprise-scale multi-agent platforms at the higher end.

What's the most common mistake in the AI build vs. buy vs. blend decision?

Treating it as a purely technical decision instead of a business one, spreading effort across many workflows instead of proving depth in one.

<