HomeVideos

This AI Technology Will Replace Millions (Here's How to Prepare)

Now Playing

This AI Technology Will Replace Millions (Here's How to Prepare)

Transcript

517 segments

0:00

So, agentic AI is on its way to replace

0:02

around 50% of all jobs. Tools like

0:04

Claude Coder being used to do around 60%

0:06

of the tasks in companies. And if you

0:07

don't know how to use it, you might end

0:08

up like the hundreds of thousands who

0:10

have lost jobs because of AI. But this

0:12

is simpler than you think. You don't

0:13

need to learn how to code in order to

0:15

stay ahead of this. You need to learn

0:16

one skill, and it's a skill that anyone

0:18

can pick up. I have thousands of members

0:19

in my community who [music] have

0:20

mastered it in just a few weeks, and

0:22

none of them had any technical

0:23

background. So, in this video, I'm going

0:24

to show you what's really happening with

0:25

these jobs, why this AI is so powerful,

0:27

and the simple steps that you can follow

0:29

to learn how to use it. So, let's get

0:30

into it. Now, when you hear AI is going

0:32

to take jobs, you probably picture a

0:34

robot rolling in and replacing you. But

0:35

that's not really how this works. What's

0:37

actually replacing you is just a human.

0:39

And I'll let the CEO of the biggest tech

0:40

company explain this to you.

0:42

>> Um actively and aggressively, you're

0:45

doing it wrong. You're not going to lose

0:46

your job to AI. You're going to lose

0:48

your job to somebody who uses AI.

0:51

Your company is not going to go out of

0:53

business because of AI. Your company is

0:54

going to go out of business because

0:56

another company used AI.

0:58

>> Basically, what happens is that the

0:59

person next to you learns to use AI. And

1:01

they start doing your job and their job

1:02

at the same time. So, the company

1:04

doesn't need both of you anymore. Now,

1:05

why is this happening now and not 5

1:07

years ago? Because the AI we have today

1:09

is different. Old automation only ever

1:11

did exactly what you told it. And if

1:12

something went wrong, you'd have to fix

1:14

it. But the new AI is what people are

1:15

calling agentic. Agentic just means the

1:18

AI can take action on its own towards a

1:20

goal instead of only answering your

1:21

questions. So, instead of you doing

1:23

every step, you just tell it the outcome

1:24

you want, and it will go figure out all

1:26

the steps, and it will do them for you.

1:28

And it's not just me saying that this is

1:29

a big deal. Agents are coming for the

1:31

kind of work people do at a desk all

1:33

day. So, here's how to prepare for this.

1:34

And it's actually really simple. If you

1:35

can't beat them, join them. You're not

1:37

going to stop this from happening.

1:38

There's just no way. But you do get to

1:39

choose which side of it that you're

1:41

going to be on, either the person

1:42

holding the controls or the person who

1:44

might lose their job to AI. And once

1:46

again, the good news is you don't need

1:47

to know how to code or be a super

1:49

technical person in order to do this.

1:50

I'm going to show you how to use it in

1:51

less than 15 minutes. But I'm actually

1:53

going to show you what you'll be able to

1:54

do. So, let me show you three jobs that

1:56

it can already do today. So, let me show

1:58

you guys a few practical examples here.

2:00

The first thing I want to call out is

2:01

I'm using the Claude desktop app. And if

2:02

you earlier when I said Claude code, you

2:04

got a little scared, there's no reason

2:05

to be. This is Claude chat, right? You

2:06

can come in here, you can talk to

2:08

Claude, and it's basically just using

2:09

your natural language to get what you

2:10

want. Except for in the Claude chat,

2:12

we're missing the whole agentic

2:13

capabilities. We're missing the ability

2:15

for Claude to really feel like an

2:16

officer at your company and a full

2:18

employee, rather than just a helpful

2:20

little tool. So, all we have to do is

2:22

switch over from Claude chat to Claude

2:24

code. And this is the interface. You

2:25

know, we've got our ability down here to

2:27

talk. The only difference is now we're

2:28

working out of local folders and files.

2:30

So, if I pull up my file explorer, and

2:32

you can see right here I've got my

2:33

camera roll open. You can see I can go

2:35

to my desktop or my downloads. This is

2:36

all we're doing is we're working with

2:37

Claude, but instead of on the web, we're

2:39

working inside of our actual local

2:41

files. So, that means it can look

2:42

through my pictures, it can look through

2:44

Excel sheets and Word docs that it

2:45

creates for me, and it can help me

2:47

organize those, move them, create more,

2:49

all that kind of stuff. So, it's just

2:51

way more powerful. And it has a much

2:52

better memory than just using Claude

2:53

chat. Even if you're using chat and

2:55

you're organizing stuff by projects, and

2:56

you've got, you know, a few connectors

2:58

plugged in, this is way different

2:59

because like I said, it's looking at all

3:01

of our files. So, real quick, if I just

3:02

said, "Hey, can you quickly tell me who

3:04

I am, what my business does, and you

3:07

know, what are some of our goals for

3:08

this year?" Because my Herc 2 project,

3:11

which is kind of like my AI operating

3:13

system is what I call it, it can read

3:14

all my emails, it can see all of my

3:15

communication, it can look through all

3:16

of my meeting transcripts. It knows

3:18

everything about me and my business, as

3:20

you can see right here with what it is

3:22

currently spitting out. It knows my

3:23

YouTube subs, it knows, you know, our

3:25

two different communities in school, it

3:27

knows our certification program we're

3:28

working on, it knows my book, it knows

3:30

my team, it knows all of this kind of

3:31

stuff. Anyways, the three examples. This

3:33

first one, take a look at this. So, I

3:35

came in here and I did something called

3:36

a slash goal, which means I'm able to

3:38

set a goal, and Claude will keep working

3:41

until the condition is met, which is

3:42

super cool. I mean, how much more

3:44

agentic do you get than that? So, this

3:46

is the prompt I I shot off. I'm not

3:47

going to read this whole thing, but feel

3:48

free to take a look at that if you want.

3:50

I basically wanted it to pull in all my

3:51

videos from quarter two of 2026, analyze

3:53

it, comments, click-through rate, all

3:55

the stats, and help me look at those

3:57

insights and tell me what to do about

3:58

it. So, as you start to go through here,

3:59

what you'll notice is this is not

4:01

technical at all. This is basically just

4:02

Claude thinking about what to do and

4:04

looking through sources. So, it said,

4:06

"I'll start by exploring what YouTube

4:07

data and tooling is already available.

4:09

Then I'll figure out how to pull Q2

4:11

analytics." So, it read a markdown file

4:12

that I have called youtubechannel.md.

4:14

So, it reads the goal and it needs to

4:16

understand exactly what it can pull. So,

4:17

it starts looking through things, right?

4:19

It uses this Python scripts to actually

4:20

be able to get the data from my YouTube

4:23

channel. It has the right token. It

4:24

continues to take action and then

4:26

reason, and take action and then reason.

4:28

And it just goes all the way through

4:29

until everything's done. You can even

4:30

see here, once it's actually created an

4:32

Excel sheet, it screenshots it because

4:34

it's supposed to verify it, right? It's

4:36

going to make sure the colors appear.

4:37

It's going to make sure the spacing's

4:38

right. And it's not going to hand me

4:39

something until it actually feels

4:41

confident that I'm going to like what I

4:42

got. So, let me pull up the full Excel

4:44

sheet so I can show you guys what I just

4:45

did. And just again to prove my point,

4:47

inside of my Herc 2 project, it created

4:49

all of this stuff. And here is the

4:50

actual Excel sheet that it made for me

4:51

locally. So, I opened this up, and this

4:53

is what we got right here. If we go to

4:55

the first tab, what we can see is we

4:56

have an assessment. We can see the

4:57

different tabs like the executive

4:59

dashboard, the video scorecard. We can

5:00

see the views numbers. We can see the

5:02

different data sources. We can see all

5:03

this kind of stuff. I can go to my

5:05

executive dashboard, which shows me from

5:07

April through June I've got these amount

5:08

of views, this much watch time, these

5:10

many new subscribers. And we can see

5:12

some of the most important things that

5:14

matter. Claude code is the engine,

5:15

massive subscriber quarter, and some bad

5:17

things. Impressions and CTR were

5:18

missing. So, for some reason it wasn't

5:20

able to pull those, so we would be able

5:21

to work that back in. Topic

5:22

concentration is a risk. So, as you can

5:24

see, not only is it pulling data, but

5:26

it's helping me analyze it a little bit.

5:28

As we keep going through, we can see a

5:29

video scorecard. So, I can see some of

5:30

the videos that I've uploaded this

5:32

quarter, and it's going to tell me,

5:33

based on the views and the length and

5:34

the viewer duration and all this kind of

5:36

stuff, which ones are good. It's also

5:37

putting them in different pillars. So,

5:38

we've got Claude code and Agentic. We've

5:40

got Voice AI. We've got Other. We've got

5:42

Selling. All this kind of stuff. I can

5:44

go through my monthly trends. I can go

5:45

through content pillars, format and

5:46

length. I can get into the audience and

5:48

traffic. So, all of this stuff is going

5:50

to help me every single quarter do a

5:51

review like this, analyze the insights,

5:53

analyze the data, and then help me work

5:55

on my strategy for the next quarter of

5:56

YouTube videos. And I want you just to

5:58

real quick think about how much data

6:00

that was, and how long would that have

6:01

taken me manually to go to YouTube,

6:04

extract all of that, put all of that in

6:06

an Excel sheet, and then analyze all of

6:07

it. As you can see, I uploaded 75 videos

6:10

in this quarter. So, that would have

6:11

taken me at least half of the day to

6:13

just write all of this down to just pull

6:15

all the data in here, get the

6:16

spreadsheet looking nice, and analyze

6:18

it. Whereas Claude was able to do this

6:19

in about 10 minutes for me. Okay, let's

6:21

look at example number two. I once again

6:23

utilized a {slash} goal prompt so that I

6:25

could set the condition and it would

6:26

keep working. This time, I wanted to

6:27

pretend that I had a small cleaning

6:29

business, and I wanted to build myself

6:30

an app so that I could track my jobs and

6:32

how much I'm getting paid and all that

6:33

kind of stuff. Once again, same thing as

6:35

last time, it reasons through, reads the

6:36

instructions, it decides what to do, it

6:38

makes a plan, and then it starts reading

6:40

files, and it starts executing. And

6:41

every time it executes, it reasons and

6:43

then executes, and then it reasons and

6:44

then executes. And that's basically the

6:46

loop. You can see here, this time what

6:47

it created for me was an HTML file. So,

6:49

let me go ahead and open up this HTML,

6:51

and here's what we have. Cleaning jobs,

6:53

we have today's date, we have how much

6:54

we made this month, how much we're still

6:56

owed. You can see, let's say Sarah Lynn

6:58

paid me. I could go ahead and mark as

6:59

paid and then mark done. If Mike goes

7:01

ahead and pays me, I could mark paid and

7:03

then mark that as done. Let's say for

7:04

some reason Amy Brooks cancels, I can

7:06

just X that out and delete that job. And

7:08

I can also come in here and add jobs.

7:10

And now, the cool thing is, we asked for

7:11

this app to have a memory. So, basically

7:13

that means if I was to refresh this, all

7:15

of that stuff that we've done is going

7:16

to save. It's not just going to reset

7:18

every time. Now, think about this. Do

7:19

you know how to build this? Could you

7:21

manually write this HTML? Nope, I

7:23

couldn't either.

7:25

But, I know how to explain to Claude

7:27

what I want. If I want this to be

7:29

different colors, I just say that. If I

7:30

want there to be more functionality, I

7:32

just say that. If I want to turn this

7:33

from an HTML into an actual URL, an

7:35

actual website that I could pull up on

7:36

my phone, or if I wanted to turn this

7:38

into an iOS app or a desktop app, I

7:40

would just ask Claude to do that for me.

7:42

And once again, this took minutes. And

7:44

finally, this third example, lead

7:45

generation. How many people sit there

7:47

and not only struggle with lead

7:48

generation, but some people's full-time

7:50

job is lead generation and outreach. So,

7:52

look at this. So, for this goal, I had

7:54

it look in Clay to find me 50 leads that

7:56

are my exact avatar. Not only find those

7:58

leads, but enrich them. So, find out

8:00

what their business does, their business

8:01

pain points, Google reviews, things like

8:03

that. And then help me, based on the

8:05

data knows about me and my business,

8:07

create outreach messages for all 50 of

8:09

those leads. Once again, it reasons, it

8:11

executes, it reasons, it executes, it

8:12

reasons, it executes. And what it did

8:14

for me here is it created this Excel

8:16

sheet right here. Leads, July 7th, 2026,

8:18

which is today's current date at the

8:19

time of filming. So, I went ahead and

8:21

opened up the Excel sheet, and what do I

8:22

get? This Excel sheet. I've got 50 leads

8:26

here. If I scroll through, you can see

8:27

that we have 50 columns of actual leads,

8:29

or sorry, rows. And the columns are

8:31

business, decision maker, title, email,

8:34

email verified, prior email status,

8:36

phone, website, location, Google rating,

8:39

review count, business pain points,

8:41

recent current signal, notable

8:42

achievements, personalization hook, hook

8:44

source, email subject, email body, and

8:46

needs review. So, all of this. Think

8:49

about how long that would take you as a

8:50

human to go find, enrich, and write

8:52

outreach messages for 50 leads, whereas

8:54

this took me about 20 minutes by just

8:55

asking Claude code with my natural

8:57

language. And I'm not a master, you

8:59

know, cold email copywriter, but just

9:01

take a look at this. It's not very bad,

9:02

right? So, the business pain point is

9:04

that a recent one-star review calls out

9:06

chaotic communication. And so, if we go

9:08

over here to the email subject, your one

9:10

bad review is about callbacks. And then

9:12

the body says, "Hi Ante, saw your review

9:14

about a customer still waiting on a

9:16

callback a month later. A few different

9:17

people reaching out with no one

9:18

following through. It's a rare miss for

9:20

a shop at 4.7 stars across 41,000

9:23

reviews. We recently helped a local

9:24

business turn calls that it was missing

9:26

into book jobs without adding anyone to

9:28

the phones. So, honest offer, I'm still

9:30

getting this off the ground, no case

9:31

study yet, but I'll set it up on your

9:32

line, run it for free for 30 days, and

9:34

if it doesn't book you jobs, then you

9:35

owe nothing." Now, here's something to

9:37

think about. Claude Chat could connect

9:39

to Clay and could find you leads and

9:40

could enrich those leads, but Claude

9:42

Code knows more about my business. It

9:44

knows our case studies, it knows our

9:46

avatar, and because I'm building my AI

9:48

operating system with its own second

9:50

brain, using Claude to me feels like I

9:51

have a co-founder rather than just, you

9:53

know, hiring a virtual assistant, which

9:55

is what people used to compare AI to a

9:57

lot. It was like hiring a VA. But now,

9:59

you can literally have a founder at your

10:01

business, or you can have an officer at

10:02

your company. And let's say you don't

10:04

own a business, that's completely fine.

10:05

If you're an employee, you now are able

10:07

to manage a bunch of different super

10:09

high-level employees, super

10:10

high-functioning and high-performing

10:12

employees, which makes you look 10 times

10:14

better. Because once again, you can do

10:15

10 times more work and keep the same

10:17

level of quality than other people who

10:19

are in your class or, you know, have the

10:21

same job as you. So, if you've never

10:22

opened up Claude Code because you were

10:23

scared it might feel technical or

10:25

because you thought it didn't relate to

10:26

you in your position, this is your

10:27

wake-up call. Please, please give it a

10:29

shot. All right, now here's the thing

10:30

all three of those examples had in

10:31

common. Every single one of them was a

10:33

job that a real person gets paid to do

10:35

today, or at least used to get paid to

10:36

do. And now, any non-technical person

10:38

can do all of that with Claude. Now, I'm

10:40

going to show you how to use it in three

10:42

simple steps, and we're going to do all

10:44

of this with Claude Code, because right

10:45

now I think it's the best one to learn.

10:47

But real quick, remember at the

10:48

beginning of the video I said you only

10:49

had to learn one skill. That skill is

10:51

being an AI manager. Think about how you

10:53

might manage a new hire. You would

10:55

onboard them. You'd let them get to know

10:56

you and get to know the business and get

10:58

to know their role. And you wouldn't

10:59

dump everything on them in week one.

11:01

You'd slowly phase them in. You'd

11:02

explain exactly what they should do, and

11:04

you'd explain exactly what they

11:05

shouldn't do. And then you'd watch them

11:07

until they prove that they can work

11:08

without mistakes. And when they start

11:09

handing you work back, you don't just

11:11

accept it blindly. You review it. You

11:12

give feedback, and you help them get

11:14

better. That's exactly the mindset you

11:16

should have when you're working with AI.

11:17

You're not the engineer or the operator

11:19

anymore, you are now the manager. Your

11:21

whole job is to make this thing as good

11:22

as possible. And the three steps that

11:24

I'm about to give you are basically just

11:25

that onboarding plan. Okay, so step one,

11:27

just start talking to it. Open up Claude

11:29

Code and treat Treat like a really smart

11:31

person that you're handing a task to.

11:32

Explain what the goal is, what a good

11:34

result looks like, what a bad result

11:36

looks like, and what it should avoid.

11:37

And practice that on small stuff. And

11:39

this is the onboarding part. Let it get

11:40

to know you. Tell it what you do, how

11:41

you like things done, what your week

11:43

actually looks like. The more it knows,

11:45

the better every single answer is going

11:46

to be. Okay, step two. Pick one real

11:48

thing that you already do and try to do

11:49

it with Claude. I mean, grab something

11:51

from your week that you actually do over

11:53

and over. And it doesn't even have to be

11:54

something that's associated with your

11:56

work. Maybe you just want to have AI

11:58

help you plan your gym schedule and your

11:59

meal prep or figure out your groceries.

12:01

The most important thing is that you

12:02

pick something that you will actually

12:03

use because there's a huge difference

12:05

between feeling the ROI yourself and

12:07

just watching demos of other people

12:09

talking about all the stuff that AI can

12:10

do. You're only going to get hooked on

12:12

it when it actually saves you time on

12:14

something that you really care about.

12:15

So, truly, the goal of step two is to

12:17

convince yourself as fast as possible

12:19

that this thing, AI, is actually

12:21

helpful. And when it gives you something

12:22

back, don't just accept it, correct it.

12:24

Tell it what you change and keep going

12:26

until the output is something that you

12:27

would actually use. And this is the

12:29

whole trust-building part because you're

12:30

watching it, you're reviewing it, and

12:31

then you're teaching it, and every

12:32

single correction, every iteration,

12:34

makes it better. And step three, once

12:36

that feels easy, start stacking bigger

12:38

tasks together and connect Claude to the

12:40

tools you already use, whatever you use

12:42

every day, your Gmail, Slack, calendar,

12:44

etc. There's probably a way to connect

12:45

Claude to [music] it or to connect any

12:47

sort of AI agent to it. You guys saw in

12:49

that first example when Claude pulled my

12:50

YouTube analytics, I didn't have to go

12:52

in there and export the data or copy and

12:54

paste anything or upload some

12:55

spreadsheet. I just said to Claude,

12:56

"Hey, go get this data from YouTube."

12:58

And it just did it. And because I have

13:00

that set up and all of my other

13:01

connections set up to all the other

13:02

tools that I use every day, AI can

13:04

actually see what's going on in my

13:05

business and everything from there gets

13:07

easier and better. You just want to do

13:09

it in a way where it's safe and you

13:10

always stay in control. Claude asks

13:12

before it touches anything and you

13:13

decide what it's allowed to reach and

13:15

you give it certain permissions. And

13:16

once you're automating real work, this

13:17

is where you start keeping score. So,

13:19

set a goal, like maybe this week I want

13:21

to save myself 3 hours or I want 100 new

13:24

leads per month. And then, track where

13:25

you're at right now before you start

13:27

using AI, and then check the number

13:28

after, and the next month, and the next

13:30

month. Because if you didn't hit it, you

13:31

can improve the system and make it

13:32

better. And that's really the only way

13:33

that you actually improve is if you were

13:35

keeping the data. So, that's the path.

13:37

You talk to it, you hand it one real

13:38

thing, and then you just stack. Those

13:40

are the first steps to start using Agent

13:41

QA. But this space is moving really

13:43

fast, and every week AI takes more and

13:44

more jobs. But it's also creating a ton

13:46

of new opportunities. So, if you want to

13:48

start mastering how you can use Agent

13:50

QA, you can join my free school

13:51

community. I've got a full free course

13:52

in there around building your own AI

13:54

operating system, which is a great place

13:55

to start. The link for that is in the

13:57

description. But anyways, that's going

13:58

to do it for today. I appreciate you

13:59

guys making it to the end of the video,

14:00

and I'll see you on the next one.

14:02

Thanks, guys.

Interactive Summary

The video discusses the rise of 'agentic AI,' which can perform tasks autonomously rather than just answering questions, and how this technology is transforming the workplace. The speaker emphasizes that workers will not necessarily be replaced by robots, but by other people who know how to effectively utilize these AI tools. He demonstrates practical use cases for Claude Code, including analyzing YouTube analytics, building simple web applications, and generating lead lists. Finally, he outlines a three-step process for viewers to learn the skill of 'AI management,' encouraging them to adopt a manager-like mindset to delegate tasks to AI while maintaining oversight and control.

Suggested questions

3 ready-made prompts