HomeVideos

You’re Not Behind (Yet): 40 AI Hacks in Under 15 minutes

Now Playing

You’re Not Behind (Yet): 40 AI Hacks in Under 15 minutes

Transcript

436 segments

0:00

77% of employees using AI say it's

0:03

actually making them less productive,

0:04

not more. That means that AI isn't

0:06

achieving the results that everyone had

0:07

[music] hoped for, and it's all because

0:09

almost nobody understands how AI

0:12

actually [music] works. I went from

0:13

wasting hours and burning thousands of

0:16

dollars in tokens a day to now using AI

0:18

as the backbone of my whole portfolio of

0:20

companies that's about to cross $250

0:22

million in enterprise value in only 16

0:25

months. And along the way, I learned 40

0:27

brutal truths about AI that could have

0:29

saved me all this time and money. So,

0:31

let's start with number one. More

0:32

context isn't always better. Too much

0:35

just confuses AI. If we just dump

0:37

everything into it, it buries what

0:39

actually matters. If instead we give it

0:42

the cleanest, tightest version, exactly

0:44

what we want to give it, not just like a

0:45

junk drawer, but very specific

0:47

instructions, then it will do the work

0:49

we need. It's even got a term called

0:50

context rot when we do this. Number two,

0:53

one good example beats the perfect

0:55

prompt. We don't want to burn 20 minutes

0:58

wordsmithing the perfect prompt. We just

1:00

have to give it a great example. If you

1:02

just give it three to five great

1:04

examples of what you want to look like,

1:06

you can save yourself hours of time

1:08

trying to fix your prompt to get the

1:09

perfect output. Number three, AI doesn't

1:12

read minds. It needs instructions. It's

1:15

not like a person who just gets it. You

1:17

have to spell it out. You have to tell

1:19

it who you want it to be, what you're

1:21

doing, what you want. Vague requests

1:23

just gets vague answers every time.

1:25

Number four, lazy in, lazy out. AI can't

1:29

want it more than you do. If we don't

1:31

work on putting the time into the

1:33

prompt, into the AI, then we shouldn't

1:35

be upset if we don't get great responses

1:37

because the energy we put in is the

1:39

energy we get back. If we put a lot of

1:40

effort and time, guess what's going to

1:42

come back? Detailed work done. Number

1:45

five, don't ask AI for answers, argue

1:47

with it. It will agree with everything

1:50

because its job is to make you happy.

1:52

What you want to do is tell it to be a

1:53

ruthless mentor and actually poke holes

1:56

in what you're asking it to do. You need

1:57

bulletproof thinking, not a cheerleader.

2:00

Six, with AI, be the [music] boss, not

2:02

the buddy. I know with people you want

2:04

to be nice and you want to be clear.

2:06

With AI, you actually have to be strict.

2:09

You have to tell it what you want. It

2:10

actually responds better if you say

2:11

never do this than could you please

2:14

maybe sometimes do it this way? It does

2:17

better when you tell it what not to do

2:19

than ask it to do a general thing.

2:21

Number seven, stop typing, start talking

2:24

to your AI. When we want to get the most

2:26

out of the AI, the best way to do that

2:27

is to use your voice. It's three times

2:29

faster. Instead of just typing

2:31

everything you're thinking, just ramble

2:33

to it like a real person and then just

2:35

hit enter and watch it take your voice

2:37

and text and make sense of it all. And

2:39

there's apps to do this like Whisper

2:40

Flow. Number eight, if AI sounds like a

2:43

stranger, it's because you never

2:44

introduced yourself. The more you give

2:47

it about who you are, the better it can

2:48

answer your questions. So, if you want

2:50

to write an email, for example, have it

2:52

scan your email and say extract how I

2:54

write my emails and then you could say,

2:56

"Now write more emails like me." It

2:58

can't sound like you if you've never

2:59

introduced yourself. Number nine, AI's

3:02

first draft is a rough cut, not the

3:03

final cut. What the AI spits out is not

3:07

the finished product. Our job is to look

3:09

at it, react to it, push back,

3:11

>> [music]

3:11

>> reshape it. See, the gold is in round

3:13

three, not in round one. What it spits

3:16

out is like the clay, but our job is to

3:17

mold it.

3:19

Number 10, trust AI's speed, not its

3:22

accuracy. It can do in seconds what used

3:25

to take days for any human to do, but

3:26

the problem is is that it hallucinates.

3:28

And the crazy part, it will hand you a

3:30

confident answer, but if you don't

3:32

inspect what you expect to make sure

3:34

everything works good, then you might

3:35

move faster just find out that it

3:37

created something wrong. Just like

3:39

humans, it makes mistakes. And if it

3:41

does, number 11, make AI check its own

3:43

work before you do. Don't be the first

3:45

set of eyes on it. You can actually get

3:47

another AI to look at the work to give

3:49

it feedback. Take [music] that feedback,

3:51

give it to the AI, and it'll make an

3:53

even better version. That way, when we

3:54

see the final version, we'll know that

3:56

it's a more cleaned-up, polished version

3:58

that it battled with itself to produce.

4:00

Number 12, AI should make you work less,

4:02

not more. Don't spend 20 hours building

4:05

something that only takes you 30 seconds

4:07

to do. Keep that one, get rid of the

4:09

stuff that takes a lot of work to do.

4:11

13, if you can talk the task, AI can do

4:14

the task. If you know every step, you've

4:17

done this, and it's a process, and it's

4:18

a checklist, then AI can crush [music]

4:20

that. But if you're still trying to

4:22

figure it out, it has a hard time.

4:23

Number 14, playing with AI feels like

4:26

progress, but truth is, it rarely is.

4:28

When we play with the newest tools, it

4:30

feels so productive. It's so cool. Look

4:32

at this brain I created. Look at this

4:33

script I created. Look at this

4:34

automation. But we forget that it took

4:36

us like a week of exploring AI, and for

4:39

some reason, our revenue didn't go up.

4:41

So, we have to make sure we aim the AI

4:43

at an actual problem, not just things

4:45

that feel productive. 15, you can't

4:48

automate what you've never done. If we

4:50

can't do it by hand, then we can't hand

4:52

it off. Think about that. If you can't

4:55

explain it, then AI can't run it. 16,

4:57

nobody cares how the meal is cooked,

4:59

they care if it was great. Founders

5:02

panic all the time. What if people find

5:04

out that they use AI to do this? Won't

5:06

my customers be upset that I didn't do

5:08

all the heavy work? I don't think we

5:09

should worry about that. I think the

5:10

customers paid for an outcome. It's

5:12

like, if I'm a video editor, and I edit

5:14

videos, and I charge for an edited

5:16

video, whether I use AI or did it

5:18

myself, the client doesn't care, they

5:19

care if it's great. 17, if your AI isn't

5:22

moving a number, it's just a hobby. Be

5:25

honest with me, is it really changing a

5:27

number in your business, or does it just

5:29

feel cool? Is revenue going up? Is the

5:31

time being saved? Cuz if nothing moves,

5:34

then using [music] AI is kind of just a

5:36

hobby. You might love to do it, but it's

5:38

not moving our business forward. Number

5:40

18, falling in love with the tool is how

5:42

we forget the outcome. The tool or AI

5:45

was never the point, the outcome was.

5:48

The reason why we use AI is cuz we hope

5:50

we get to the outcome faster. If we're

5:52

just collecting logins and API tokens

5:55

and subscriptions instead of actually

5:56

getting work done, then we've lost the

5:59

plot. Number 19, a finished workflow

6:02

beats the newest model. It seems like

6:04

every week there is a new model that

6:06

comes out. We got to stop chasing it.

6:08

The person who finished that one system

6:10

on last month's model beats the person

6:13

chasing the new thing that still hasn't

6:14

gotten done. If it ain't broke, don't

6:16

fix it. Stay with what you've got and

6:18

get back to work. Number 20, it's faster

6:21

to build a feature than to actually have

6:23

a meeting to talk about it. I've seen

6:25

people spend hours debating something in

6:27

a meeting that AI could have just did

6:29

for them in minutes. Instead of sitting

6:32

there and debating how something could

6:33

look or how it work or how it would

6:35

feel, they could just stop the meeting,

6:37

do the thing, and come back and talk

6:38

about it. For example, I was in a

6:40

meeting the other day with a team member

6:41

and I said something before the meeting

6:43

was done, 30 minutes later he showed me

6:45

a prototype of what I just said I wanted

6:47

him to work on. 21, simple scales.

6:49

Complexity is just procrastination with

6:51

extra steps. When we put so much effort

6:54

in the setup, we think we're being

6:56

smart, but we're actually [music] just

6:57

delaying putting something out in the

6:59

world. The thing that actually scales is

7:02

the simplest, tiniest, easiest version

7:04

of it that we get in front of customers

7:06

that we can scale. We need to make sure

7:08

we don't overthink it, we don't

7:09

overengineer it, we just get it done.

7:11

22, one well-built agent beats 10

7:15

half-built ones. Most people have a

7:17

graveyard of half-finished automations,

7:20

half-finished agents, half-finished

7:22

scripts or processes or workflows that

7:24

they started but never finished. We need

7:26

to make sure we deploy one agent that

7:28

runs a daily beat that creates a lot of

7:30

value instead of experimenting with 10

7:32

other ones that are half-done. 23, you

7:35

need a polyamorous relationship with

7:37

your AIs. Yeah, I said it. You got to

7:39

around with the other AIs to figure

7:40

out which one's the best one. There's no

7:43

single model that is best at everything.

7:46

There's a site called Openrouter and I

7:48

will use 30 to 40 different AIs to

7:50

figure out which one is the best. And

7:52

what's crazy is they're leapfrogging

7:54

each other every week. So, we need to

7:56

pick the best tool for the job, not the

7:58

one that we're just used to. You can't

8:00

be married to just one of them. You have

8:02

to play with all of them.

8:04

24, stop using AI and let it run without

8:07

you. This is a big one. I want you to go

8:10

from I use AI to AI runs. There's a

8:14

difference. Using it means that you're

8:15

still doing the work. Running means it's

8:17

doing a whole process, workflow, or even

8:19

managing a department. You go from being

8:21

in the work and doing it, copying

8:23

pasting things, to it doing the work for

8:25

you and you're just reviewing. That's

8:27

the whole shift. And look, everything so

8:29

far you can do on your own laptop

8:31

tonight. But if you're a founder or CEO,

8:33

the real money isn't you getting a

8:34

little better at AI. It's AI running

8:36

your departments for you. That's why I

8:38

built a whole AI company operating

8:40

system. It's the exact playbook for

8:42

plugging AI into every part of your

8:43

business. It's all the workflows, the

8:45

agent setups, the templates my own team

8:47

uses to get the work done while we

8:49

sleep. If you want it, find me on

8:51

Instagram and DM me the word YouTube OS

8:53

and I'll send it right over. 25, you

8:55

can't automate a moving target. If your

8:58

process changes every week, there's

8:59

nothing stable to automate. Which is

9:02

fine. If you're growing really quick,

9:03

you're going to be breaking your

9:04

processes every 3 to 6 months. But the

9:06

ones that are locked and loaded, lock

9:08

them down, make it boring and

9:10

repeatable, and then build on top of it.

9:12

26, a prompt you can't repeat isn't a

9:15

skill, it's just luck. Have you ever did

9:17

a prompt and you got a magic result, but

9:19

then you can't do it again, it's just

9:20

kind of gone? My favorite thing to do is

9:22

once I get it to create that magic

9:24

output, I ask it to write the system

9:26

prompt behind it so that I can save that

9:28

in my system. Now I'm building a machine

9:31

that prints results on demand. It's not

9:33

a one-time magic trick, it's something

9:34

you can repeat. 27, never explain

9:37

yourself to AI twice. I use this

9:39

philosophy called dry, it's a

9:40

programming term that stands for don't

9:42

repeat yourself, which means I document

9:45

everything. I document all my meetings,

9:47

I document my decisions, I document my

9:49

processes. And so that I don't have to

9:51

repeat myself again, I just point it to

9:53

the folder with all those documents.

9:54

Number 28, a tool with no owner is just

9:57

a toy. If nobody owns the process,

9:59

nobody can maintain it and honestly

10:01

it'll just die. No owner, no results.

10:04

Every tool you build with AI has to have

10:07

a name of a person that owns it. That's

10:09

called the direct responsible

10:10

individual. Number 29, AI is fuel, not a

10:13

fix. If I take jet fuel and I put it in

10:16

my Volkswagen, it will explode because

10:19

that's a broken process. It's not built

10:21

to go fast. If I put jet fuel in a jet,

10:23

it will take off, it will get us to

10:25

space. A broken system will explode, a

10:27

kick-ass system will scale. Fix the

10:29

system first before you add the fuel.

10:32

30, let AI take the task, you can keep

10:35

the human moments. Hand the repetitive,

10:38

soul-sucking, soul-draining stuff to the

10:40

machines. We want to keep the hugs, we

10:42

want to keep the heart talks, we want to

10:44

keep the creative conversation. Let the

10:47

AI take the tasks that we don't even

10:48

want to do in the first place so that we

10:50

have the time to be human. 31, AI won't

10:52

replace your people, it'll free them. I

10:55

didn't have to get rid of my assistant

10:56

because she stopped triaging emails, she

10:58

just became my chief of staff. She now

11:00

has the time to focus on bigger

11:01

problems, human problems, not doing

11:03

triaging and automation that the AI does

11:05

better than her. Now, if you do need a

11:08

task done, then we got to go to 32.

11:10

Token first, hire second. See, before we

11:13

deploy money to labor and people, we

11:16

need to first ask ourself, can we use

11:17

the tokens or the AI to get it done

11:19

first? It's way cheaper to get AI to do

11:23

something 24/7, never gets upset, never

11:25

quits, never gets mad at us, than to

11:27

hire somebody, have to train them, and

11:29

then hope that they don't leave. If AI

11:31

can do it, that's when we hire someone

11:33

who can actually run the AI to manage

11:35

it. 33, if your best people are doing

11:38

what AI could do, you're the problem. If

11:40

we use our most expensive talent on a

11:42

task a machine can handle, that's a

11:45

waste. We need to make sure that that's

11:47

not happening because if it is, it's a

11:48

failure. 34, the future belongs to

11:51

directors, not doers. The way I think

11:53

about it is we want to be the editor,

11:55

not the author. We want to make sure

11:57

that we come in and we let the machine

11:59

do the work and then we become the

12:01

director. We direct it. We're the human

12:03

on the loop, not human in the loop. So,

12:04

we need to actually challenge ourselves

12:06

to stop being the best worker and start

12:08

being the best director. 35, your talent

12:11

strategy is your AI strategy. When we

12:14

hire people, we're taking money and

12:16

we're bringing people into our business.

12:18

We need to make sure that we qualify and

12:20

we start bringing people into our

12:21

business that know AI natively. So,

12:24

every hire that you're considering

12:26

should be showing you on their interview

12:28

how they've partnered with AI to do that

12:30

work. 36, AI isn't a department, it's a

12:33

way of operating. Oftentimes leaders try

12:36

to delegate AI down to the tech people

12:38

and I think that's why it fails. For me,

12:40

it's not one team or one department,

12:43

it's how the whole business runs and it

12:45

has to come from the top because number

12:47

37 is your team will never out adopt

12:49

their leader. [music] You are the

12:50

ceiling. If you're just dabbling with

12:52

AI, your whole team will dabble. It's

12:54

what John Maxwell calls the law of the

12:56

lid. Your team will never rise above the

12:58

leader. So, it's not about getting them

13:00

to use AI, it's about you as a leader

13:02

showing them how you're using it. If you

13:04

do that, the whole team will follow. 38,

13:07

you're not too busy to learn AI, you're

13:09

actually busy because you haven't. When

13:11

I hear people say, "I don't have time

13:13

for this." That's exactly why you should

13:15

do this. This weekend, take some time to

13:18

educate yourself. Talk with the AI, have

13:20

it teach you. Download my workbook. Go

13:22

through the exercises. Learning AI is

13:24

how we get our time back. 39, AI doesn't

13:27

have an identity problem, we do. The

13:29

tech is ready. People are like, "Oh

13:31

yeah, but it's not good enough yet." No,

13:32

it's there. What's actually holding us

13:34

back is that we're scared to let go. The

13:37

bottleneck in most cases has a face and

13:40

it's usually yours. 40, the barrier was

13:42

never the tech, it's your willingness to

13:44

try. What we need to make sure is we

13:46

don't blame the tools. See, the tools

13:48

are incredible. The only gap that I've

13:50

noticed is that we're bad at using the

13:52

tools, but if we stay with them long

13:53

enough, eventually the tools will get

13:55

good because we get better. We just have

13:57

to start, even if it's messy, even if

13:59

it's hard, even if it doesn't do what

14:00

you want right away. That's the whole

14:02

difference is we want to stick to it

14:04

until we get it. The people that are

14:05

going to stay behind are the ones that

14:07

quit in that first try when it didn't

14:09

work exactly the way they wanted it. You

14:11

just made it through 40 brutal truth

14:12

around AI. Most people aren't willing to

14:15

be honest with themselves. They're not

14:16

willing to confront it. They're not

14:17

willing to say, "Hey, I probably got to

14:19

get better at this." But here's what I

14:20

know, if you watched this, you're ready

14:22

for this. Right now, you have the

14:24

opportunity. Doesn't take anybody else's

14:25

permission, no timeline, you just have

14:28

to make a decision to invest in

14:30

yourself, to go all in on this, to

14:32

decide that you want to be the best in

14:33

your peer group. So, leave a comment

14:35

below and let me know, out of these 40

14:37

or anything I shared, what hit you the

14:39

hardest? What did you need to hear

14:40

today? So, just leave your answer below

14:42

and I'll make sure I read every one of

14:43

those comments. And remember, if you

14:45

want my AI company operating system, the

14:47

exact playbook for running your whole

14:49

business on AI, just DM me YouTube OS

14:51

over on Instagram and I'll send it over.

14:53

And if you want to know the six most

14:54

profitable AI businesses to start, click

14:56

here and I'll see you on the other side.

Interactive Summary

This video outlines 40 'brutal truths' about leveraging AI effectively in business. The central message is that many people struggle with AI productivity because they misunderstand how it works, often treating it as a magic solution rather than a tool that requires clear instructions, systems, and active management. The speaker emphasizes that successful AI integration is about changing leadership habits—moving from 'doing' to 'directing'—and ensuring AI is applied to well-defined, stable processes rather than just playing with new tools.

Suggested questions

4 ready-made prompts