Hello and welcome to the 0ero to1 course

all on cloud code for marketing. By the

end of this video, you guys are going to

know how to use modern AI tools like

Cloud Code to automate virtually the

entirety of the marketing function. Uh

whether you guys run your own company or

working inside of somebody else's,

that's all good. My name is Nick. I run

a marketing business that just did over

$500,000 in revenue last month using an

overwhelming amount of cloud code. I've

also been working with AI for over 7

years now, way back when the smartest

model was called GPT2. Uh and I've

trained some big teams on AI now, like

the Mr. beast team and a couple of

others. So, I know all about how to take

somebody from never having used or

applied an AI tool all the way up to,

you know, generating large returns in a

real functioning business. So, all that

to say, you don't need any programming

experience. You don't need any prior AI

experience to understand all this. I

don't have a degree in coding or

anything like that. I learned everything

I'm about to teach you from free YouTube

videos just like this one. We're going

to start by looking at a really brief

outline and then I'm going to walk you

through it. And you don't need to jump

around. Literally just follow the course

as I laid it out and by the end of it

you'll know everything you need in order

to automate your marketing. Let's get

into it. So the course is going to be

focused on actionable real

implementations. In order to get there,

first I'll show you how to download,

install, and set up Claude Code. I've

uninstalled it from my computer and I'll

actually walk you guys through every

step including signing up, creating an

account, and then what every button in

the interface means. So it'll be very

simple. Then I'll cover the five

marketing functions that we'll be

automating today using Claude code. I'll

also show you guys a framework I'm going

to use for that. Then I'll run you guys

through the difference between prompts,

skills, loops, and cloud routines. And

the way we're going to approach the rest

of the course is I'm going to be showing

you guys how to automate things using

Claude uh at each of these four levels.

And you can think of prompting as the

simplest level, Claude routines as the

most advanced level. Prompting requires

you working on your computer whereas

cloud routines effect effectively is a

loop that is scheduled that runs in the

cloud without you. Then we'll actually

go and build stuff. So I'm first going

to show you guys top of funnel how to

automate the generation of creative. You

guys will be able to automate ads,

creative for organic. We'll be doing

this via images, video, even some audio.

Then I'll show you guys the next

function which is the personalization of

copy. And so we'll be doing newsletters,

we'll be doing pulled emails, we'll

basically be taking a template, and then

I'll show you guys how to use Claude to

automatically um automate the process of

filling really fuzzy variables that it

goes out and finds on the internet and

so on. In the middle of funnel sense,

I'll then show you guys how to make

speed tole systems for appointment

booking. These are systems that allow

you to squeeze way more juice out of ad

spend and then organic growth. Then I'll

show you guys how to set up data

collection, tracking, dashboards, and so

on and so forth. Actually building your

own proprietary analytics platform, uh,

interpreting the data through cloud, and

then ultimately scanning that up

somewhere on a dashboard so that you or

your clients can see what that looks

like. And then finally, at the end, I'll

show you guys bottom of funnel, which is

how to automate highquality follow-ups.

Now, this is basically nurturing. It's

starting to verge onto sales, and I

don't want this to be a sales course.

Um, but I'll show you guys how to

automate the process of sending emails,

SMS, notifications, and so on and so

forth, and doing so in a way that seems

very human despite being entirely

automated. Finally, I'll show you guys

how to maintain and then upgrade these

systems over time before giving you guys

some advanced tips that I have hard

learned, I sort of learned the hard way

after working with a lot of large

businesses, multi-billion dollar

enterprises, and so on. Okay? So, you

don't need to worry too much about any

of this stuff right now. We're going to

go step by step. We're going to start

slow and by the end of the course as

mentioned you'll be able to do

everything that I just talked about. The

first step we need to do is we need to

create an account and the way to do that

is to head over to claude.com.

So I'm going to do that first with you

guys. claude.com right here. Now in

order to create an account all you need

to do is click continue with Google or

continue with email. The interface may

look a little bit different by the time

that you guys are looking at it. But

what I'll do is I'll just go continue

with email and I'm just going to pump in

my own little email address over here.

So this is the name of my startup. I'm

just going to go continue to click the

link sent to this. So I'm now I'm going

to go to my email. Okay. And I have it

right over here. I'm now going to click

sign in to claude.ai.

It's going to take me back to this page

right here. Now this will quickly

basically ask you a couple of questions.

I agree. I consent. And I think I'm not

going to subscribe to the promotional

emails and notifications. Sorry,

Anthropic. Now, we're going to have to

do some onboarding questions. So, just

for the sake of not doxing myself, I'm

just going to put in a bunch of random

dates here. We'll go 010190.

Makes me squarely millennial. Uh, I'm

going to be using this for personal use,

and I'd recommend that you do as well.

They're trying a team/enterprise

feature, but if it's just you for now,

just click personal use. Now, you will

have to pay in order to use claude code.

Hopefully that's clear. This is a

financial transaction. The idea being

you invest, in my case, $24 Canadian per

month into this. Then you make far more

than $24 Canadian a month back in ROI. I

can say as somebody that operates a

business that does half a million per

month. Um, this is by far my number one

investment. I probably receive an ROI uh

something to the tune of an absurd

10,000% or something like that just off

my Cloud Code subscription. Um, you can

use Cloud for free. It's just you can't

use the code aspect. And as you'll see,

the code aspect is very foundational to

us being able to use Cloud to do really,

really high level automation super

quickly. So, I'd recommend that you guys

do this for sure. But if you don't have

the funds, know that you can also just

watch me build things in the course.

Maybe wait until you have the 28

Canadians a month, let's say, to sign up

and then circle back after you watched

it end to end. So, don't worry too much

about that. Uh, but if you want to do

things with this, you will most

definitely have to eventually pay. Okay.

Okay. So, monthly right up here. I'm

going to go down to payment method to

actually put in some info. Okay. And I

just wrapped that up. Cool. So, now once

we're done, it'll automatically take us

to the next step. As mentioned, if your

interface looks a little bit different,

that's okay. What we do after this is

we're going to download it according to

our operating system. Now, in my case,

my operating system is MacOSS. If you

guys couldn't already tell, just based

off the way the Windows look and stuff

like that. It'll be a little bit

different uh if you guys are using

Windows, but it'll automatically pop up

right over here based off of like a

little browser cookie thing. So, I'm

going to give this button a quick click.

And as you can see, a lot of the time on

Chrome, it will automatically block the

download. So, what you can do is you can

just go to download unverified file in

the top right hand corner. Okay? And

then you'll actually be able to see it.

So, claude 6.d. Okay. And then once

you're done with that, all you have to

do is just drag this little Claude app

over to the applications folder. So, I'm

doing that. And I just heard a little

chime in the back end. That's because it

has gone through and actually copied

Claude to my applications. That's just

how you do things on a Mac. On a

Windows, you'll have to go through that

whole prompt uh that you guys are

probably pretty familiar with. And then

once that's done, all you need to do is

actually launch Claude. And then we will

have opened, you know, the Claude

desktop app. So on Mac, all I do that uh

in order to do that, all I do is I take

this little window. This is called

Raycast. Then I just type Claude. You

can see I'm actually right over here.

Don't pay attention to the rest of the

stuff. Once I give that a quick click,

it will then open Claude. And if I go

down to the bottom here, it'll say it's

an app downloaded from the internet. Are

you sure you want to open it? After

you're done, it'll then look something

like this. And all we have to do is

click get started. I'm now going to

relog in. So, continuing with my email

address here. I'm then going to have to

go to my email address and then enter

the verification code, which I will get

right over here. When you click sign in,

it'll take you back to the app and we

should be good to go. Cool. So, I've

already created the account to be clear.

Um, what it's doing here is it's just

double-checking a lot of the stuff. So,

I'm just going to click continue. We'll

start with my name, Nick. What kind of

role we do, I'm just going to say

product management. I'm then going to

say I have my own topic. And now we are

in. So, first of all, there's a lot

going on on this interface and you'll

see so many little widgets and buttons

and tools and things you can push and

pull. Uh, I'm not going to cover every

single one because I don't think that

would be a very good use of time. And

what you'll quickly find is Anthropic,

the parent company of Cloud, is testing

a lot of different user interface

features and they're trying to collect a

lot of data on what people actually

like. So they'll change these up pretty

often and they're pretty short-lived.

But what I will do is show you a couple

of them. Um top lefthand corner. Okay,

we have obviously the three little close

the window buttons. If you're on a

Windows, it'll probably be in the top

right hand corner. Then you have a tab

open or close button, which is how you

open or close the sidebar. Then you have

a search chats and projects button which

allows you to basically um search

through all conversations that you've

had to find more or less any info.

That's actually pretty useful. Next up

you have the home versus code tab. And

so basically there's almost like two

products here. There's like a clawed

product and then there's like a clawed

code product. And so basically what we

want to do is we don't want to use the

home product, okay, which is simpler to

be clear. We want to use the code

product. When you jump over to the code

product, a lot will change. you know, if

it's the first time you've run it, it'll

look something like this. When you don't

have any conversations in the queue or

sessions going on, what it'll do is

it'll give you a quick overview of all

of the conversations that you have

started and uh basically had over the

course of I think it's like the last 6

months or something like that, 3 months

anyway, a lifetime basically from when

you created your account. Now, in my

case, you know, I've created the account

quite a while ago and I've had a lot of

conversations with Claude. So, as you

can see here, it's saying that you sent

12,28 messages, 1,123,

you know, 3,289. I've I've had a lot of

back and forth with them. As a result,

I've used more 241 times more tokens

than Pride and Prejudice supposedly,

which is pretty cool. You can also break

that down on a 7-day basis, 30-day

basis, or all. And, um, you can also see

which models you use the most. In my

case, I use the smartest model as of the

time of this recording, Fable, pretty

often. Okay. And you can see that my

usage started right around July. So

that's enough of everything over here.

Let's go back to the left hand side.

Underneath new is artifacts. In case you

guys didn't know, an artifact is

basically a visual that Claude can

create for you. And so if you wanted to

create a brief visual, what you can do

is build a code artifact. Um well, in

this case, I just clicked new and it

automatically populated this. I want to

build a code artifact, a self-contained

web page published with the artifact

tool. Um make this page about Nick Sar.

Okay. Okay. And then I'm going to press

enter. And what it will do now is it'll

actually go through presumably ask me a

couple of questions. And then it's going

to design a visual interface for me, an

artifact inside of Claude that I can

then access anytime I want. So now it's

confirming the angle, gathering a couple

key facts before designing. And now it's

going to go through and get me some

questions. So what's this page's job? A

personal bio portfolio site. I'm just

going to say it's a personal bio

portfolio page emphasizing the YouTube

channel and automation agency. And what

you'll notice just happened there is

Claude actually suggested an

autocomplete down at the bottom. And so

all I had to do when that autocomplete

popped up is I just pressed tab and then

it automatically went all the way to the

end. This is basically now letting

Claude drive your conversation. And it's

not always the best thing to do to be

clear. Um but it is pretty neat and I

would say it knows what I want to do

next maybe 30 40% of the time which

helps. And you can see it's now coming

up with a bunch of uh information based

off of publicly available work like

leftclick maker school my subscribers

where I live and so on and so forth. Not

all this is up to date because it's been

a while since you know the web pages

that hosted all this information um have

been created but it's pretty dang solid.

It did that in just a few seconds. Okay.

Now here we have what's called a

request. This is asking to see if I

should allow Claude to run this command

because this command requires my

approval. And so you can see there are

three things that have popped up here.

There's a deny button, a one, an always

allow button, which is two, or an allow

once button, which is three. Generally,

it thinks that allow once is the right

answer, which is why it's popping up as

that little highlighted thing. In my

case, I'm just going to go always allow

because this is just building a simple

web page. It's probably not going to try

and delete my computer by accident. Now,

once we've done this, you can see the

interface change more. There's this

little tab that says creating. If you

click on this tab, it'll actually show

you guys the commands that it's running

under the hood. If you guys feel like

supercomputer programming, you want to

see what's going on. And you can

actually see as well the amount of total

time that it's spent working as well as

the total number of tokens that it is

spent as well. Now, tokens are important

to understand because tokens are a big

part of how you are build at the end of

the month. They're also a big part of

how much uh usage you basically have

with Claude. The more usage you have

with Claude, the more tokens you can,

you know, run through. And typically,

the bigger and sexier the project, the

more tokens you will require. So, it's

important to understand and sort of have

visibility into your token budgets,

which is why Anthropic does it right

here. Now, I'm running this in real time

because I want you to actually be able

to see everything that is running. Like,

I want you to know how long it'll take

to run one of these things. Um, I find a

lot of the time on YouTube people will

just cut to the end. And while I will be

doing some cutting later on in the

course when we do larger and bigger

builds, let's say ones that are, I don't

know, 15 or 20 minutes, I'm not going to

force you guys to sit down and and watch

all of that, um, it's important to at

least see what a real flow looks like

start to finish. Okay, once all of this

is done, if I just move my big fat head

out of the way, you can see that we now

have um, you know, we actually have a

web page that we built. Okay, and this

web page is the artifact. Now, this

isn't on the internet to be clear, and

it's not going to be perfect all the

time, but I'd say it's pretty good. You

can see it basically built me this

little portfolio site saying Calgary,

Canada, building in public automation

systems that run without him in the

room. Oo, super fancy. So, it gives a

bunch of information right over here

about my YouTube subscribers, views on

the channel, the number of maker school

graduates. You can then see that uh, you

know, I went to behavioral neuroscience

in school. Uh, this was actually wrong

because I think somebody made a big post

about how I left college or something

that ended up getting really popular,

but I didn't actually leave college. I

graduated with my degree. Um, you can

then see this sort of like timeline here

with maker school and YouTube and stuff.

All all very cool. Anyway, the point

that I'm making is not, you know, you

can make a website. Hopefully you guys

know that by now. If I move my head back

here in the top right hand corner, you

can um click this little button here to

expand it or open it in a default

browser. So now this is actually open in

my Chrome and the really cool part about

opening it in your Chrome is once you

have the artifact online you can

actually share it with people. So what

you can do is you can actually share it

with people that are in your uh company

using a teams or enterprise plan or you

can share it with people um that are

just on the internet like basic any

basically anybody. And so I'm now gone

to share anyone with the link. If I go

copy here, then I open this up in let's

say an incognito tab and then I paste

this, you'll see that I'm now accessing

that artifact despite the fact that I'm

not even signed in. And so in this way,

you can basically host web pages now

with anthropic and and cloud. And it's

really useful particularly for like

dashboards and for managing projects for

clients. You know, I do a lot of client

work now and a big chunk of my client

work these days is actually building

like web interfaces and internal tools

for people. Well, Artifacts solve that

for me completely. I no longer need to

worry about actually hosting a website.

I can just whip up a quick artifact and

then give somebody the link. So that's

that artifacts tab is right here. Okay.

Next up, you have the ability to

customize. I know the second you click

this, it'll look really intimidating and

frankly quite terrifying. Uh but this

customize button is is quite valuable.

It'll basically take you all the way

down to the skills tab under customize,

which is where you can add uh what is

probably going to be one of the most

important parts of this course. skills

which are almost like programs that you

can run on knowledge work. So, Enthropic

will have created a couple for you

assuming you're watching this at least

sometime in the next month or two uh

like morning and uh they'll also have

done I don't know setup writing style

and skill creator. These are just meta

skills to show you how they work but I'm

just going to run you through this one

here morning to start. Now the idea is

this is a skill. This is something you

actually have access to. Render the

user's morning brief as a styled HTML

artifact or set it up as a recurring

weekday task. Use only when the user

explicitly asks to run, see, or set up

their morning brief or if they invoke

/morning by name. You may be wondering

exactly what that means. I'll show you

guys in a second. A question about their

day, schedule, or calendar is not by

itself a request for the brief. So,

answer it directly instead. And so what

this is going to do basically is this is

going to automate the process of coming

up with a prompt and telling a model

what to do. Um you know before I said

hey make me a website. The website is a

one page we're about nixar. Well now

what we have is we have a skill which

all we need to do in order to actually

generate a page is invoke it by going

/wmarning. When you do it'll pump this

prompt in to claude which is quite long

as you guys can see here. You can

actually add a lot of detailed

information. Then all the way down at

the bottom it'll basically generate a

page for you. Okay. So why is this under

the customize button? This is under the

customize button because this is how you

customize your cloud instance. This is

how you optim uh customize cloud code.

You add skills which are basically

domainspecific programs that you can run

to do things for you. And so for

instance when we do ad creative uh later

on in the course when I actually

automate that for you using cloud code

we will be using like an ad creative

skill. I will create one alongside you

and that ad creative skill will automate

the process of like producing a bunch of

ad variants that we can test for

marketing. You know, if you create a uh

uh I'm not sure a dashboard skill or

something. What you can do is I don't

know once a day you can quickly set that

on a loop to automatically pull all of

the different data sources. Let's say

Google Analytics API, a big Google sheet

that contains data, a bunch of I don't

know s you know agency analytics

software and stuff like that and then

just pull all that in and use it to

populate a dashboard. You can do all

that stuff just using skills. So, it's

very important to understand um sort of

what they are and how they work and

we're going to go a lot into detail

about that later. But that's not the

only way you can customize your cloud

code instance in the app. You can also

do so with connectors. Now, connectors,

those you guys that don't know, are

basically just uh ways to hook up apps

to cla. And so what we have here is we

have the ability to connect our Gmail.

We have the ability to connect Google

Drive. We have the ability to connect

Slack. And so as I create these

automations with you guys, we'll be

using connectors to integrate a variety

of different data sources into cloud

code like emails, like you know, Slack

channels and so on and so forth. And you

can automate virtually whatever the heck

you want. I mean, as you guys see, we're

even doing this with Spotify, right?

Spotify is connected right now and has

access to get the current track, get the

player state, get the volume, get the

position, get the repeat, get the

shuffle. These are all functions inside

of this connector. And so, you know, you

could actually ask uh Claude to do

something for you, like, hey, you know,

I want you to turn up the volume of

Spotify and it and it can do so via

connections. So, you can connect things,

disconnect things, and so on and so

forth. A lot of really cool stuff to

play around with there. Finally, you

have plugins. Now, plugins sort of

depend on exactly what you want to do

with Claude. And as you guys can see, I

have a couple set up right here. One's

called Claude Mem, another Superbase,

another's clanged LSP. You don't need to

know what any of these three mean, but I

just wanted to show you guys what this

looks like in an interface. So, when you

click on it, okay, you'll see that there

is a source version, and an author. And

this source is pretty interesting

because if you go on, if you click that

button, you'll see there's actually a

variety of plugins that have been

created by Anthropic and Anthropic's

partners to allow Claude to do things

easier. So for instance there is a

finance plugin which automates the

process of creating journal entries,

financial statement reconciliation,

streamlining your accounting workflows

and so on. Legal which speeds up

contract review, NDA triage, compliance

workflows for in-house legal teams and

so on. There is bio research which

connects to pre-clinical research tools

and databases. There's code

modernization which is a plugin used to

modernize really old code. There's a

variety of different plugins here and

they do everything from changing how

Claude looks. So actually changing I

don't know in this case the output style

or I don't know doing structured actions

for you that are similar to skills but

not exactly skills like code review.

Okay. So we're going to show you guys

how to do all of that in this course

which I think is going to be quite

valuable. Then finally at the very

bottom you have memory. Memory is just

sort of what Claude knows about you. And

so I don't know, remember I'm, you know,

we talked about height, you know, a

couple days ago with Claude and I

remember asking it to do some BMI stuff

for me and it was like, I don't know how

tall you are, so how tall are you? So

what I said now was, hey, you know, I'm

6'2. So what it's done is it's created a

memory profile with basic identity facts

about the user details is 6'2 tall. You

know, you could put in weight

information. My dog's name is beans. you

know, you could put in uh information

about your career, about how much money

you make, about, you know, your

marketing channel, about uh the

priorities of your business and so on

and so forth. And so that is what the

customiz tab is for. Next, you also have

this more tab, which exposes routines,

which is going to be quite an important

part of our work um as we get on a

little bit later. What this allows you

to do is basically create templated

skills. They call them routines, but

they're templated skills that are kicked

off on schedule by API or web hook. Now,

you don't need to know what API or web

hooks mean, but obviously a schedule is

just when you want it to. So, what you

can do, for instance, is you can build a

skill, which is a program like I talked

about earlier. And then you can just run

that at, I don't know, 5:30 a.m. every

morning. And so, this is the last step

of automation. This is like the max

automation where we're not actually

talking to Claude anymore, nor are we

even running skills, nor are we looping

those skills at a regular interval.

We're actually scheduling these to run

on the cloud outside of our computer.

And this is where you really unlock like

fully automated business stuff, which is

typically what people work with me for.

Um, the full sort of endto-end pipeline

automation of a aspect of their

business. So, it's actually quite easy

to do and I'll show you guys how to do

that soon. Finally, you have the ability

to customize the sidebar here. So, I'm

actually going to open that routines tab

so we can also see that underneath you

have the various conversations and

folders that you're working in. So, I'm

actually working in a folder called for

YouTube right now, which is why it says

for YouTube here. If I just zoom in on

this just a tad, you also have the

ability to create new conversations by

clicking this plus button. Then you can

change a bunch of information about

these the status of your conversation,

the environment that you're working on.

um you know all of the stuff is a little

bit more technical and not going to be

super relevant to us immediately. So I'm

just going to leave that for now. Okay.

And then that takes us to the actual

chat window itself. Now as you guys can

see here when you don't have any

sessions in play you have this big um

sort of like dashboard with all the

information about how many tokens you

consumed and stuff like that. So the

number of sessions, the number of

messages, the number of total tokens and

stuff like that. You also have the

ability to check model specific usage

and break that down. Well, I think they

just included this information so that

you wouldn't have to look at a blank

screen and because this looks way sexier

than a blank screen. The parts that are

important for us are first of all this

button which is how you switch between

running stuff locally on your own

computer running stuff in the cloud K

which is Anthropic computer using remote

control which is running it on another

computer that you own and SSH which

stands for secure shell which is uh just

a protocol used back in the good old

days to communicate with computers in a

secure way using passwords and stuff

like that. So we're probably not going

to touch on the SSH stuff. I'm going to

show you guys remote control just sort

of so we all know how to run marketing

workflows um on another computer. But

really the two we're going to be using

the most are local and cloud. And local,

as I'm sure you guys can guess, is

actually quite easy. Um basically what

it is is it's my local computer. And

when you click on that little settings

gear icon, you can actually update that

local environment with a bunch of

usernames and passwords. Now the

usernames and passwords are written in

kind of intimidating ways. Nodeenv

equals production. But what these are,

these are just usernames and passwords.

You know, you can imagine it be like

user nick atclairvo.io,

I don't know, password, hey bros, I love

claude code for marketing, whatever.

Well, now we've actually stored like a

credential called user, which equals

nicer.io, and a credential called

password, which equals that. So, we can

save that. Now, my my local environment

actually has that information. You can

see it's even sort of hidden some of

that from me. Um, so I'm just going to

save the changes back here so that we

don't have anything that confuses

Claude, but you can use that to log into

apps and various APIs like the meta ads

API and whatnot will typically require

you to have like env keys and stuff like

that. Okay, then we also have the cloud

button here. I can click add cloud

environment that'll take me to a panel

here which basically allows me to do the

same thing. Cloud is speaking loosely

here. What this is is this is on

Anthropic's own computer. So, Anthropic

is running this for you and you just pay

Anthropic instead of paying, you know, a

computer company or a server company to

host. Um, I won't get super deep into

the pricing here because we're probably

not going to use cloud environments for

most stuff. We may use them a little bit

later, but this is valuable in larger

teams. And the reason why is because if

you think about it, right now I'm

running stuff on my computer

specifically, but my computer works a

little bit differently than other

people's computers, right? And so

because of that, sometimes you'll create

something that works on my computer uh

but it won't work on somebody else's

computer. And so the benefit to using

cloud environments a lot of the time is

you're standardizing it. Everybody uses

the same cloud environment. It's the

same server with the same environment

variables, same usernames and passwords,

same setup scripts, same everything. And

then as a result, you just know that

like the app that you're creating for

your cloud code for marketing course is

going to work the same whether it's on

my computer or yours. Down over here,

you can actually select the folder that

you want to play in. And so I'm just

going to do um for YouTube. I'll keep

that. You can also just add a new folder

here anytime that you want. So I have a

couple more. Clarbo backend, Fable 25,

and so on and so forth. U over here on

the right, you actually have this little

claude widget. And if you just kind of

move your mouse around, it'll do some

cute fun stuff. Uh kind of funny cuz

this thing is actually galaxy sized

brain, but the company made it look

super cute. It's breaking out of your

shell. Uh and then on the bottom

lefthand corner, you'll see the mode,

which is very important. My

recommendation is to run most things in

auto mode. Basically what modes are is

you guys remember when um I just

launched Nixrive webpage before and

asked me hey do you want to allow the

ability to run XYZ command? Well a

manual will always ask you before it

does anything that is even remotely

considered like you know autonomy in

your computer. And that's good if you're

working on like something really secure,

but obviously eventually it becomes a

pain in the butt, right? Because I don't

want to have to like wait, you know,

around to see what it needs me for. So,

what I typically do is I'll typically

use um accept edits, plan, auto, or

bypass permissions. Now, what accept

edits is is it won't be able to create

new files, but it will be able to edit

pre-existing old files. And so, that's

pretty useful, right? You can run it a

mock in like a codebase or I don't know,

some marketing folder or something like

that and have it upgrade everything. um

but it won't be able to create or delete

any files, which is sort of a a certain

level of control that you could imagine

would be useful. You can also use plan

mode, which is where instead of making

any changes, you create a really

in-depth plan about how you're going to

do it instead. You can then do auto

mode, which is where Cloud will handle

most permission decisions for you. It'll

only ask for your help if there's

something that it considers to be kind

of scary. You know, if you're playing

around in your file systems, and I don't

know, the file systems on your Windows

will delete a certain system 32 folder.

um you know, Claude will cla will tread

very lightly and it'll ask you uh as you

work on things that are close to that

folder, but if you're just working on

like random ad creative or something,

for the most part, you'll never actually

have to worry about a little um dialogue

box popping up. Then finally, you have

bypass permissions mode. Uh I love

bypass permissions mode. It's basically

just like full you only live once, let's

go, Claude, 1v one me. Uh you know, it's

not going to ask you a single thing.

Claude's just going to do whatever the

heck it wants all the time. Um, I am

typically in the loop in some way,

shape, or form. And I typically do not

work on things that are super sensitive.

You know, cyber security projects, super

sensitive like passwords, credentials. I

don't do any of that stuff. So, you

know, I'm just working on little

marketing tasks. I'm usually going to be

auto or bypass permissions. So, as you

can see, right now, I'm actually on

bypass permissions. When you click on

that button, you can then scroll all the

way down to the page and it'll actually

ask you, hey, do you want to allow

bypass permissions mode? And you have to

do that check because obviously there is

the possibility of some sort of

long-term impact. So what I'll do is

I'll just go back here. And now once

I've accepted or allowed this, I can now

just go five and bypass permissions.

When you do so, it'll kind of make your

screen seem kind of scary. So, you know,

don't do it if you're not like actually

okay with it. Um, auto mode, plan mode,

accept edits mode, everything is fine.

Uh, I just wouldn't really recommend

using manual because you'll have to

check in like every 5 seconds as it does

anything. Okay. Okay. Then a little bit

to the right, we are now exposing the

capability to add files or photos. So I

can actually add any file or photo to my

claude code conversation. So I have some

videos here that you could see I did

with, you know, Jack Roberts. I have a

big list of community members. I can

actually export all of these and

actually upload them directly into the

chat. So this is a picture of uh me,

Alexi, and Sam Ovens at uh you know the

school games where they were

interviewing me about stuff. For

instance, maybe I want to ask it

questions about how to make this better

or have it generate a new image using

another model or something like that. I

could do so really easily. You can then

add a whole folder as well, which is

basically the entire folder's worth of

context. It'll just go through

everything in that folder, consume it,

and then, you know, sort of understand

what is going on. And then you have the

ability to expose slash commands, which

if you guys remember earlier were those

slash warnings, the skills and so on and

so forth. So slash commands are kind of

cool. Um, there are a lot, so I'm not

going to go through every single one,

but I am just going to show you guys

what the interface looks like. If you

type slash, you'll see there is a

massive list of all of the different

possible things that you could do here.

There's slash schedule/btwreview

slrefork/mcp/feedback/model/reame.

You know, this is sort of like um you

reading through the help docs of a a

very complicated piece of software.

There are a lot of these and we're

adding more and more and more all the

time. But what is really cool is this

will also include um skills. So just

like you know we had um you know all of

those different functions here we also

have anthropic-skills colon morning. And

so for instance that would actually run

the morning flow the same thing that um

you know we were reading through a

moment ago. So as you can see I'm saying

anthropic-skills morning. This will take

a few minutes. Let me check what's

connected before gathering. And the

reason why it's doing that is because

it's looking to see, hey, do you have

email? Do you have calendar? Do you have

chat, Slack, Gmail, or Outlook? Because

those were the five platforms or six

platforms that were used in the skill in

order to, I don't know, give you your

morning brief. The value to the morning

brief is composed of data you would find

on places like this. So, the fact that I

don't have any of those platforms

connected means that it's probably not

going to be all that valuable of a skill

run, right? But as you guys see, these

things are quite organic and uh Claude

will let you know as you proceed through

building skills and stuff like that,

whether you have the appropriate

permissions to make that skill valuable

in the first place. Okay, there are a

couple of these um slash commands that I

would recommend understanding. Um one is

called BTW. This allows you to ask a

quick side conversation before you

actually stop the prompt. Um so for

instance, I could say, "Hey, what's my

name?" When I do this, what it'll do is

actually open up this little side chat

right next to your main conversation.

And you can ask it a question without

actually interrupting the conversation

that you guys are having down here. And

so that's what's going on up here. Okay,

I'm actually just having a conversation

with it. And it's still technically in

the thread. It has all the context of

the thread, but um we're talking without

actually interfering with anything down

here. So then I'm just going to close

out the /btw. And you can see here it's

now asking me for, hey, can claude open

this folder? I'm now going to click

allow once. And you can see that it's

actually gone through and created the

page for me. But the page is pretty

boring. It says nothing's connected yet.

So there is no day to show you. Nick,

you should get your stuff together,

right? And so that's what that works.

It's going to ask me multiple times. I'm

just going to keep on closing this out.

I don't really need to worry about that.

Okay. Now, I don't like the fact that

this has been talking for a while. So

what I want to do is I actually want to

pause it. And how do you do so? You can

click this button right here. You can

also press escape. The reason why that's

valuable is because sometimes cloud gets

caught in loops where it just reopens

the thing over and over and over again

because you keep exiting it or it keeps

on editing a file for you or you change

tac and you don't want to use /b2w or

something like that. Now moving down

slash commands. Another one that I

really like is slash usage. This will

show your usage plan as well as the um

rate limits and how far you are through

them. So you know I've done a couple of

things with you here on my $20 plan. And

so uh you can see my 5-hour limit resets

in 4 hours and 21 minutes is at 9%. So

I've used 9% of my 5h hour limit. To

make a long story short, Anthropic

currently gives you five whole hours

um as a window in which you can use

Claude and then they give you a certain

amount of cloud usage within those 5

hours. After you hit 100% you can no

longer proceed in that 5 hours.

Then when it resets, you go back down to

zero and then you can run it up all the

way up to 100% again. In addition to the

five hour limit, they will also give you

a weekly limit. And so this allows you

to access all models. The reason why

they do this is because sometimes they

give you limits to specific models,

usually new ones, which are very in

demand. Uh, and so this one here resets

Friday, 9:00 a.m. And you can see I'm 1%

of the way through my weekly limit, 9%

of my way through the 5h hour limit.

[gasps] It'll also give me some

information about the session cost. So

this cost an additional 88 cents. I

think cuz I was using uh I don't know

some smarter model or some API or

something. Um looks like I was using an

API for 1 minute and 2 seconds and I was

using mostly sonnet for this task which

is one of the many claude models. Then

we also have the token breakdown which

is quite valuable as well as what is

actually using my limits. 67% of all of

my limits were used by that one skill.

Okay. And you can see that consumed like

I don't know I guess like 6% or so of my

total 5 hour limit usage which means I

could probably run warning maybe every I

don't know I could run it like 20 times

in a row. So that's pretty cool.

Okay. And then finally uh the last skill

that I wanted to show you guys was uh if

we scroll down here a little bit

there's loop right here. Now loop is

valuable because it allows you to define

an interval. So I could say, I don't

know, let's just say 5 seconds. And then

I'll just say just say hey Nick.

And so what this will do is every 5

seconds it will start a loop that every

5 seconds responds to me as hey Nick.

[gasps] Now there's a rounding rule

currently in place. I think that's

because there's a one minute floor

currently put on by um Claude. But

anyway, just to show you guys, let's do

the one minute loop. Um, what this will

do now is this will set a loop where

basically once a minute, every minute,

this will just say the words, "Hey,

Nick," to me. And so, as you can see,

this is a pretty straightforward thing

to do. Uh, but as I'm sure you guys can

imagine, we can go much more complicated

than this. And in fact, we can actually

run skills like this /morning skill, and

we can do that on a daily or that on a

one minute loop or that every, you know,

45 minutes or whatever. We could also

very trivially set skills that'll do

things like check pages for us. And so,

you know, for a lot of SEO or newsletter

purposes, that's pretty valuable because

what you do is you'll like add

connectors and then you will check,

let's say you're running a big campaign,

a flash sale. Well, you actually set a

loop where cloud will check to see every

5 minutes how many new customers have

signed up. Let's say you can take all

those customers that have signed up and

then provision them access to some asset

or whatever. Um, and it'll just continue

doing this in the background over and

over and over and over again. You can

see we've now done that three times.

Okay. So, if you want to stop the loop,

just say something like stop the loop.

Cloud will kind of hear what you have to

say, find the tool, and actually like

cancel the tool call that it just

generated. And then, uh, yeah, you're

good to go. All right. So, hopefully

that was a reasonable walkthrough of all

of the slash commands. Last thing I want

to do here, um, is, you know, obviously

we have those connectors, which I've

talked about before. We have the ability

to add plugins. You'll see there's a lot

of um redundancy built into this because

they have the same buttons three or four

different places just because they're

testing to see which ones people like

the most. Next, we have the microphone

feature, which is basically how you um

basically talk to Claude via your

microphone.

So, if I hold command D or just press

this button, you'll hear those little

two and then you can talk to Claude

however long you want. And so, that's

what I'm doing right now. I'm actually

having a conversation with Claude via

voice transcription tools. This is built

into Cloud. Now, I also can use my own

voice transcription tools to pump uh

words into this little field if I wanted

to. But you'll find that this tends to

work pretty well. And you can actually

see real time the text that you're

generating being transcribed. So, that's

kind of neat, right? In practice, I will

actually usually end up prompting just

through my voice these days. The reason

why I tend to prompt through my voice is

not because I think I am a better

speaker than I am a better writer. Most

people tend to be far better writers,

but because when you uh use dictation,

you can typically just generate a lot

more in a short period of time than if

you write, the average human being

speaks at around three to four times

faster than they write with their

fingers. So, um you know, this is just a

quick and easy way to like brain dump

whatever you need into cloud. And I

think you'll find that there are a lot

of situations in which you'll probably

want to brain dump stuff into cloud.

I'll show you guys some as we build.

Anyway, you can change your microphones

and stuff like that right over here if

you want. Then we have the actual model.

So, there's Fable 5, which requires

usage credits right now. There's Opus 5,

which is not Sonnet 5, Haiku 4.5.

Variety of different ones here, too,

that are kind of old last generation

ones. Uh, I'm just going to use Sonnet 5

right now because it is pretty smart.

Does most of what I want it to do, and

I'm not super worried about, I don't

know, solving the mathematical formulas

of the galaxy. Finally, we have the

effort tab, which is basically a slider

that allows you to um define how hard

you want Claude to work on one of your

tasks.

This allows you to basically say like,

"Hey, like is this work that I'm doing

today super important? If not, I don't

want you to think too hard. I just kind

of want you to go with your best guess.

Whereas, you know, if you go all the way

to the right, it's like, hey, I don't

want you to try guessing at anything. I

actually want you to triple, quadruple,

sex tuple check everything that you tell

me." And in doing so, um, cloud will

consume a lot more tokens, but the

probability of a high quality answer

goes up way more. It's also note also

worth noting that the speed changes

quite a bit here. Um, when something is

at effort low, it usually works much

much faster than when something is at

effort smarter. So, keep that in mind.

If you're going ultra code, it'll take,

I don't know, like way way longer than

if something is effort low. Effort low

might take like 2 seconds. Uh, effort

ultra code might take like 5 minutes.

So, worth usually operating somewhere in

the middle. I like defaulting to medium

or high for the most part. Um, sonnet

high tends to work pretty quick while

also delivering pretty good results.

Now, you can also see your context

window here in the bottom right hand

corner. What that is is the total number

of things that are consuming your

tokens. So, I just move my again fat

head out of the way so you guys could

see this a little better. Um, as you can

see, we have a certain number of

messages up here at the top that are

consuming a certain section of our

context window. Certain number of system

tools, system prompts, MCP tools,

skills, memory files. You don't need to

know what all these things mean. What

you do need to know though is that

Claude can only hold a certain amount of

information in its head. And that

information is currently bounded by

tokens. And so a token is very similar

to a word. And pretty soon, I'm sure

they will just be called words. But for

now, they're just a little bit

different. Uh right now, you know,

sonnet 5, which is the model that I'm

using, can host 967,000 of those tokens.

We've consumed 112,000, which puts us as

12% of the way to the entirety of Sonnet

5's context window. When you hit the

context window, usually what'll happen

is Claude will compact your context,

meaning it will just like try rewriting

it so that it's way shorter and then

stick all that information up at the

very top. The reason why that's valuable

is now you can continue the

conversation, but a lot of the BS words

are sort of taken out of your context

and you'll usually get build less for

it, too. And that does take me to the

sort of billing and usage aspect. The

longer your context window is while you

talk with Claude, the faster you will

burn through your usage limit. So, my

recommendation is try not to keep a

thread running all the 967,000

tokens uh that are available. I'd like

working somewhere between 0 to maybe

500k or so. I find that's also my

performance sweet spot. If you add more

information than that, cloud starts to

perform a little poorer. That's just

because it gets confused. It doesn't

fully know what it is it's doing. You've

given it a lot of instructions at that

point that it needs to juggle around in

its memory and obviously that can be

pretty tough. Okay, so that context

window can be consumed of messages. As

mentioned, system tools are just

different things that it internally has

access to. System prompt is uh basically

a little snippet of text that you can

define that will be prepunded at the

beginning of every conversation. MCP

tools is another sort of thing like a

skill. It's just skills that other

people host for you. So what you can do

is you can load basically external

skills via MCP tools that other people

have created very easily. And then

memory files are the things that I

showed you guys earlier that basically

define I don't know like in my my case

my height earlier 6'2 and stuff, right?

The rest of the stuff not super

valuable. Obviously that's free space.

We're just going to skip out of that and

you have your plan usage limits. Okay,

so I told you this would be

comprehensive, didn't I? Yeah, we've

covered uh probably 90% of the entire

interface. There's just one more thing.

At the top right hand corner, you have

the ability to spawn a terminal. You're

probably not going to do this, but for

those of you guys that don't know, a

terminal is just um kind of the way that

we used to interact with computers back

in the day. We had a variety of

different commands that you could, you

know, access cdls, print working

directory and stuff like that. You could

see all the files that are in this

directory and so on. Um, but anyway,

sometimes cloud actually needs to use

this terminal in order to do things. We

also have the ability to check your

diff, which is just the changes to the

code that you have made. If you're

developing an application, that can be

quite valuable. You also then have a

browser. So we now have a browser built

into cloud that can do things like

access web pages for you. That's pretty

valuable as I'm sure you can imagine

because you can use that to automate

browser activities. And then finally at

the top right hand corner you also have

a couple of things that are pretty cool.

One is an iOS simulator. So you can

actually set up like apps in cloud code.

Now um these are iPhone apps and they're

fairly cool. Um you can like download

you know Xcode which is how you do it.

Open up the Mac app store and so on and

so forth. I won't do that just for uh my

own sanity. I don't like looking at the

app store any more than I have to. Uh

but anyway, you can you can create like

iPhone apps now, which is pretty badass.

Uh and then you can also open in

whatever you want. You can open in a new

window, VS Code Finder. You can rename

your transcript. You see this Nyx Drive

web page right over here. Well, if I go

to the top rightand corner and I click

rename, I'll say Nyx demo.

You can see we've actually fundamentally

and foundationally changed that. Uh you

can also see the transcripts. you can

actually like see all of the thinking

that Claude has done if you just expand

this transcript view. So, in my case,

I'm just going to do summary. And what

it'll do is it'll just summarize

everything that we have done, our whole

conversation back and forth. I'm now

going to get a summary, which is pretty

cool. Uh, as well as a full transcript

of the conversation at any time. So,

transcripts over here, summaries over

here. This is going to take a fair

amount of time to spawn, unfortunately,

so probably won't happen entirely real

time. Okay. And yeah, now you can see

it's giving me a summary of this

conversation. First, I wanted to build a

self-contained publish artifact page

profiling Nixx as a personal bio

portfolio page. And then uh I don't know

there's a bunch of things like the

outcome, you know, what had what ended

up happening in the session. Well, the

next drive artifact is now done and

sharable, right? Then you can fork a

conversation where you just start

another conversation at the same place.

So that's me forking the conversation

right now. And then you can also archive

a conversation if you don't want to look

at it anymore. So that's what I just did

to that Nyx demo fork. And then uh you

can also delete a conversation if you

want to. That's what I just did to

Nick's demo.

Okay, we are now done. Virtually every

button in this godforsaken interface.

Just kidding. Uh there's a lot and

that's because the Anthropic team has

added a tremendous amount of value to

their app in just uh I don't know maybe

3 or 4 months. So the app was not always

like this. The app is very high quality

now. The app will probably look a little

bit different from what you guys see

just because they are consistently and

constantly updating it. But now that you

guys know how to use the app, you have

no excuses. we know every little literal

button on this entire interface. Um

it'll be very very easy for you to

navigate and do virtually everything

that you need in order to make something

cool happen. Which takes us to learning

the interface right here which is now

check. We have an optional task here

called set up the CLI. CLI in case you

didn't know stands for command

line

interface

which is just a different way of

communicating with cloud code. As

mentioned, you know, they've given us

many different ways to talk to Claude

and and work with Claude. Um, so what

I'm going to do here is I'm going to I'm

going to set up another one just as a

demonstration. And I may use the CLI. I

may end up using the cloud desktop app.

Um, it's really just about what is

simpler and easier for you. Before I

show you guys that, it's worth a brief

uh kind of piece of education here. Uh,

just like we have different websites on

the internet, okay, that are accessible

through different browsers. Like in this

case, this website Google can be

accessed through Chrome, Safari, Firefox

or something else. We also have the same

concept of clawed code which is

accessible through I don't know your

desktop app, your terminal VS code or

something else. And so there are variety

of different ways basically to get to

the same resource. And so what I just

showed you here was I actually just

showed you the desktop app, right? And

so that's what we just looked at, but

you can also use a terminal to do the

same thing. You can also use VS Code.

And so what I'm going to do now is I'm

just going to show you guys what it

looks like in terminal version. And it's

very very straightforward and easy. All

I'm going to do is I'm going to go to

Ghost TTY. When I open up ghost tty,

you'll see I have a terminal. Same thing

that we had before. It's inside of a

folder called business. That's just sort

of the layout. And in order to access

Claude, all I need to do is type

cla-verbose. I like verbose because it

allows me to see what it's thinking. And

if I scroll and zoom way in, you'll see

that, you know, our interface looks a

little bit different. You know, our

cloud is up here. And I don't know what

what is it doing? It's looking up. It's

going down a couple times, but it says

Claude Code Fable 5 with medium effort

in business. So, what's going on? So

maybe I'll say, "Hey,

um, what you'll notice is this is the

exact same product. It's just I'm

accessing the product now in a different

way. Instead of me using that app that

we saw earlier, I'm using my own app and

I'm talking to it through a channel. If

I type slash, you'll see that there are

a variety of different skills that I

could use as well. And so in my case,

this is actually my preferred way of

communicating with cloud code. And the

reason why is because I just, you know,

uh, uh, I I've done a lot more

development stuff over the last 6 or 12

months. I'm just more used to

communicating with it in like a terminal

style interface. That said, it's not the

only way to do so. And hopefully you

guys see now that uh the cloud desktop

app is a very very strong and viable

candidate. And just for simplicity sake,

I'll prefer that wherever possible. But

there are some situations in which I I

do like just diving into the terminal.

Again, it's almost like a different car,

right? Different browser, different car.

Everybody has slightly different

preferences about how they drive it. you

could have the exact same horsepower,

but obviously if you're accessing cloud

code or if you're accessing the the same

horsepower of the engine through a

different model, um it'll react

differently, handle differently and

stuff like that. And that now takes us

to the end of the first step, which was

to download, install, and set up cloud

code. Next, I want to cover the five

marketing functions that we'll be

automating today and the framework I'm

going to use to show you guys how. So I

want to talk a little bit about business

because obviously you're doing this not

for the sake of you know building up

just a cool personal portfolio but

ultimately we want to we want to build

our marketing skills here with cloud

code to do something some sort of

economically valuable outcome and so the

way that I see most businesses and it's

a service business up here but uh really

the more I think about it I think it's

all businesses is as the following

pipeline. All businesses will start with

some form of marketing. Okay, that is

just to get strangers to notice you and

that is basically to get eyeballs on the

business itself or the brand. Then you

will have some sort of sales

transformation event which is what turns

these eyeballs and this interest into

some form of money. Afterwards you have

fulfillment which is where you deliver

what you promised and then finally at

the end you have some sort of

administrative wheel that is what keeps

the machine running. Now the whole idea

here is basically you know during this

process as you go from top to bottom you

convert somebody who is a total stranger

into some form of profit and you can

imagine the same thing applies across a

variety of different business stacks.

You can do this with ecom. You know in

ecom you have strangers that notice a

product. You sell that product. they

receive delivery of the product and you

have some sort of admin to keep uh I

don't know the purchasing and the

inventory in line with like uh

expectations and forecasts. You have

hiring, you have vendor relationships,

logistics managed with your your

manufacturers and stuff like that. Uh

and then you know ultimately these four

working in perfect concert is what makes

you profit. So you know this isn't like

an MBA or anything like that. Certainly

I don't think I could hope to do uh you

know an MBA in this this this time

period that I've allotted for this

course. But you know I want to talk

mostly about this marketing and then

this sales aspect. Um and so this is

really going to be like our focus. This

is what we're going to spend most of our

time working through in this course. Um

but I think it's also important to

understand that marketing and sales they

work in tandem, right? It's not just one

or the other. Realistically there's

there's there's back and forth here. So

a lot of the stuff that we are going to

build for marketing today with cloud

code um we will also sort of build with

uh or build for our sales department at

least to like understand and and know

what's going on. And so this is kind of

secondary and I'm going to have future

courses that are focused specifically on

sales. So you don't need to worry too

much about that. Now the framework we're

going to be using to really crush these

cloud code automations is called race.

race stands for reach, acquire, close

and expand. And the differentiator or

sort of the delineator between sales and

marketing in my view occurs right here.

So everything to the left of this is

technically marketing and everything to

the right of this is technically sales.

Which means our course today is going to

be focused on these two which is how do

I get seen which you know if you think

about the key performance indicators of

getting seen how do I get impressions

how do I get views so how do I get my

brand in front of more eyeballs and then

how do I turn these impressions and

views into some form of intent so how do

I acquire you know so how do I I don't

know book meetings or get form fills get

people to sign up to my newsletter get

people to opt built in to some offer and

so on. And so all of the automations

we're going to be developing are really

going to focus on uh these levers. Okay,

it's all going to be about reach and

acquire. And if you think about business

in this framework and if you you know

race to implement automations that help

you with reach, acquisition, close, and

expansion, typically uh you'll allocate

your time a lot more effectively than

otherwise. So, I'm going to come back to

race pretty often. Uh, when, you know,

somebody wants to work with Leftclick,

my AI automation agency. Um, you know,

typically they're like, "Oh, like I want

to do this crazy admin automation. I

want to do this backend thing." And I'm

like, "Well, why don't we start with

race? Why don't we start with reach,

acquire, close, and expand, and then we

can worry about that later." I find

results are are through the roof. Uh,

people focus on revenue and growth uh

way less than they realistically should.

Race is how I tie them back to, you

know, revenue and growth levers

constantly. And on the right hand side

here we have close and expand. So you

and if you think about it, this is like

a sales transformation threshold. Um,

you know, once we've booked the meeting

or gotten some sort of intent or

something like that for our product,

it's not really a marketer's job to

close them and expand them. Obviously,

we can tee them up for, you know, the

greatest spike of all time. Um, but

that's sort of out of our hands at this

point. So, we're going to work on

optimizing reach and acquisition. And

then later on I'll have courses on sales

that'll also allow you guys to implement

systems that improve your ability to

close and your ability to grow the

lifetime value of your deals. Okay. So

if we think about this now a little more

simply what does that mean for us? Well

under reach there really three major

places that I'm going to uh help you

guys build cloud automations with today.

The first is creative. Now this is the

generation using artificial intelligence

and orchestrated by claude of images,

videos, audio and so on and so forth

typically for the purpose of advertising

although also for organic uh kind of

brand reach and brand growth. So the

cool thing is with claude if you think

about this as like one of these analog

dials on like a control panel we can

pump this puppy all the way up to the

top super easy. you can significantly

reduce any bottlenecks at the creative

stage just by throwing, you know, tons

of uh a couple of different creative

models to Claude and then giving Claude

the ability to to press buttons and

arrange prompts um you know, in its own

way. I'll show you guys how to do a

define system for this. This is the same

system I've used at uh over a company

that does over a billion dollars a year

in revenue to massively increase their

top of funnel and then ultimately the

total number of pieces of content and

ads that they can get out. After that,

you also have copy which is sort of in

tandem with creative for advertising.

Um, but we can also use, you know, cloud

code to customize a lot of the copy in

our marketing mix. So, we could do the

customization of newsletter copy for

instance, which I think is a big lever

not a lot of people are pulling

realistically. You know, your

newsletters don't have to say, "Hey, my

offer does X, Y, and Z." You know what

you can do is you can actually customize

it to say, "Hey, Nick, just wanted to

send you this because I know you talked

about X, Y, and Z last month in your

LinkedIn. You know, my offer does X, Y,

and Z and I think it can help you." That

sort of stuff does really, really well.

And it also starts blurring the line

between direct outreach, too. A lot of

the time people think marketing and then

they go, "Okay, this is all inbound. So,

I make a brand, I make some sort of ad

campaign and then people come to me."

Um, well, you know, marketing can also

be done outbound, which is where, you

know, I have a product or service and

I'm I'm actually actively looking for

customers for it. And so, this is where

a lot of my own experience comes in

because I used to do door-to-d dooror

marketing. So, I would literally acquire

my leads by walking up to a business,

opening the door, shaking the business

owner's hand, and just giving them a big

pitch. So, I'm sure you can imagine it

didn't work well super often, but uh

when it did, it did. And so, I have a

lot of experience around applying AI,

cloud code, specifically to the outreach

stack. And I think it would be remiss of

me if I did not show you guys how to do

that as well. It's a very high

opportunity lever for outbound growth.

Okay, so all of these improve your

reach. Okay, so that's sort of the R in

race. Now on the right hand side here,

um we also have a couple of, you know,

ways to improve the total fraction of

people that opt in or book an offer. And

so the first one is speed to lead. Now

what is this? This is basically just

capitalizing on interest. you know,

presumably between the reach and the

acquisition stage, if you think about it

here, there's some sort of like um

opt-in, which is where somebody will

fill out a form or something like that

to to demonstrate interest. You would be

surprised at how many hundreds of

millions of dollars are lost between

these two stages. Um if you just, you

know, respond to leads really quickly,

which is what speed to lead means. If

you build systems that allow Claude,

let's say, to orchestrate a conversation

within 30 seconds of somebody filling

out a form, you can make companies 300

to 400%. And um that's what the hat that

I'm wearing uh right now represents. I

run a company that actually just does

speed to lead all day. And we've

produced crazy outcomes like taking a

home services company that was

previously doing around $3 million a

month in sales. Um literally just by

implementing the greatest speed to lead

system ever. We took them to $9 million

a month. That's 300% increase in total

revenue simply by optimizing one of

these, you know, six levers here. Okay.

Another is booking percentage. So we can

actually improve booking percentage

through speed to lead, but also through

economizing um you know a lot of the

form fills and a lot of the systems that

people use right now to to gain

interest. So we can have Claude, for

instance, do a lot of research on the

prospect to eliminate the total number

of fields we need in an opt-in form.

Typically, if you have, let's say, 10

questions in an opt-in form, you break

that down to three or four questions,

you'll see a significant improvement in

booking percentage. You do so at the

cost of qualification, but Claude Code

can now do research on the prospect for

you sort of autonomously. um which means

you don't actually need all that much

information. Then also following up. So

this is like nurturing. Um what we can

do is we can use cloud code to

orchestrate autonomous follow-ups and

then do so in like really customized

ways that people seem and feel like

they're are being treated like as people

not as dollar signs which is kind of

funny if you think about it because like

you know we're using AI for this stuff

but the end result is our prospects that

people are marketing to are a lot more

likely to feel like we're talking to

them directly. If you think about it,

one of the reasons why many companies

have been forced to treat people like

dollar signs, you know, not personalize

their outreach, not even personalize

their their billing or their

communications or the templates of their

invoices and stuff like that is simply

because we haven't had the manpower to

do that and provide a good experience.

But what I really like about cloud code

and AI is that it allows us the ability

to produce the manpower to give every

single person that works with our

business a customized experience.

They'll have customized creative,

customized copy, customized outreach.

Their speed to lead will look really

customized. We'll we'll customize, you

know, information by doing research

automatically on people to enrich, you

know, fields in our newsletter databases

will u customize follow-ups. Everything

will be super super unique and and also

very personalized. Before we actually

build things, you need to understand

bottleneck thinking, just sort of

constraintbased thinking. And this is

quite important in marketing because

what you'll find is a lot of the

companies that you work with or maybe

your own company um they have a lot of

one of the things that we talked about.

Okay? Maybe they have a lot of creative,

maybe they have a lot of capacity around

the follow-up end, but you'll find that

there are certain parts of their funnel

that just really suck. And the way that

bottlenecks and pipelines work are the

entire operation is always constrained

by the narrowest step of that chain uh

or like the weakest link in the chain is

another way of thinking about it as

well. The classic example is a factory.

And for those of you guys that have

played those like I don't know factorial

games or whatever um you'll intuitively

understand this but let's say I have a

factory and the way it works is every

day I get 100 units of some raw

material. I don't know let's say it's a

rock or something like that. And now

this enters my big factory. Okay. And

this is what my factory looks like.

[sighs and gasps] And basically what

happens is you know what we have to do

every day is we have to put this raw

good through two steps. We have step A

and step A has a capacity of 100 units

per day

and step B

has a capacity of 10 units per day.

How many units in one day can we get

through this pipeline? How many units

can we get through this factory? Well,

if we start with 100 units on the left

side, okay, and then we pass it through

A, A has a capacity of 100 units per

day. So, what that means is the

intermediate between, you know, A and B,

like we'll we'll generate 100 units.

That's fine. You know, we've made it

past the first step. You'll see B only

has 10 units per day, which means, you

know, despite the fact that we're

feeding in 100 units, we can't get all

of them. Um what we can do is we can

transform 10 units per day. What that

means is what is the sum total daily

output of the factory? It's 10 units per

day.

You know basically the entire factory

can only work as quickly as the weakest

step in their process.

Now if I give you an mission to improve

the total capacity of this product you

know in total number of units generated

per day um you know and then I say hey

like which step would you improve in

order to increase the total output of

the factory would you improve step A or

would you improve step B you know let's

say I allow you to double any of these

well if you doubled A you'd be at 200

units per day what would the total

capacity of the factory now be well you

wouldn't actually have changed anything

because the bottle neck the thing that

all other steps are sub subservient to

is still 10 units per day. However, if

you changed B from 10 to 20 units per

day, then the total output of the

factory would go up. Okay, so anyway,

this is just a very simple and

straightforward um analogy hopefully

that allows you to think about how to

optimize a marketing process. The

reality is, you know, we have a lot of

processes in our business that are very

similar to what I just talked about. And

in this hypothetical example, what we

have is we have um you know a lot of

capacity at the creative step. We have a

lot of capacity at the lead step, but we

don't have a lot of capacity the booking

step. So this is sort of our you know uh

example that is analogous to 10 units

per day. It doesn't really matter if we

improve our creative in this example.

Doesn't really matter if we improve our

follow-ups or the total number of leads

we have. you know, none of that's going

to matter because the pipeline, the

narrowest part of our whole business is

this booking stuff. So, what that means,

too, is it's not bad. It's actually

quite freeing. Um, we can spend zero

work on creative leads or following up

at this point. If we just improve our

booking by a tiny little bit, our entire

business will improve by that same

multiple. For instance, if we can move

it from 10 units a day of capacity to 20

units a day of capacity, what we've done

is we've effectively doubled our

business. Okay? Then we do it 30. you

know, maybe we'll triple our business

and so on. And so I I just bring you

guys this analogy because I find a lot

of the time people want to rush to

automate literally everything that they

can in a business. And despite the fact

that that sounds nice and it's sexy,

you'll make way more money for yourself

or for the companies that you work with,

if you spend a little bit of time trying

to figure out what the bottleneck is and

then building systems that alleviate

that bottleneck versus just trying to do

everything everywhere all at once. So

all the systems that I'm going to show

you from now on, I would like you to

think of as solutions to bottlenecks.

But don't just throw these systems at

the companies that you work with because

that isn't necessarily going to do

anything unless that is actually the

current constraining step. Like if

creative for instance was a very narrow

bottleneck in this instance, you know,

if it looked maybe something more like

this, right? Um and it was a lot more

narrow, then widening it with the

creative system that I'll show you guys

in a minute would make sense. You know,

if booking was really the bottleneck as

mentioned here, then widening it,

widening it with a booking system and

doing more speed to lead, that would

make sense. But if you guys are already

really really good across the stack and

everything that you guys are attempting

to process automate is already sort of

not the bottleneck in a process, you're

not actually going to see uh much

monetary return. Okay, so that takes us

back to the five marketing functions

we'll be automating today and the

framework to do it. Why don't we now

talk about how to prompt versus build

skills versus schedule loops versus

create routines? And once we're done

with this, we can actually start the