WEBVTT 00:00:00.000 --> 00:00:55.965 I just built a complete lead generation pipeline end to end in just a few minutes all while using Clot, and it literally does everything. This is wild because we're in a time where this used to take my team and I countless hours of repetitive manual steps, and honestly, no AI tool has ever come close to getting it to the quality that it needs to be until now. We've sent over 2,000,000,000 cold emails for businesses across pretty much every industry that you can think of. So I've personally seen exactly where AI tends to break down. So in this video, I'm gonna show you how to build this entire system from scratch. So you can just copy me and start to automate your lead generation with AI and send emails that actually book meetings. Let's dive in. Firstly, you gotta get yourself familiar with Claude. So in this case, I'm using Claude Code. And just as a quick overview, there are several ways that you can get started with Claude code. Number one is the terminal, the good old CLI. This is one of the very basic 00:00:56.125 --> 00:01:15.860 black screen where you just type in a command and you have yourself a chatbot where you can literally do everything from, you know, end to end to right from the terminal. There's no additional apps. Your Windows or your Mac machine or even Linux is definitely going to have the CLI there. Then you have Versus Code or Cursor. So essentially an IDE, 00:01:15.860 --> 00:01:18.180 also known as an integrated development environment. 00:01:18.675 --> 00:01:21.395 And this is the way that I personally like to do it because 00:01:21.475 --> 00:01:40.530 you actually bring it into an environment where you see the list, you see tabs, you can go to websites, you can generate a lot of things all inside of one window. Then we have the good old desktop app. So you have Mac OS or Windows. You just basically download the app. You have the chat, Cloud Code, and even Cowork, 00:01:40.610 --> 00:02:01.035 which are very powerful. They're all great. In this scenario, it could basically do a lot of the same thing, but it's all about just whatever harness that you're gonna be using. Then we also have the web and JetBrains, which we won't go into. But for this scenario, I would just recommend you get familiar with the way various ways of how to actually use Cloud Code. And then from here, next up, you're gonna need to give context and capabilities. 00:02:01.530 --> 00:02:03.130 So as part of the capabilities, 00:02:03.130 --> 00:02:05.450 right now, if you go to top of funnel.com 00:02:05.530 --> 00:02:08.090 and in the upper right, you just click resources, 00:02:08.410 --> 00:02:11.770 you're gonna see that we have agent tools and CLIs. 00:02:11.770 --> 00:02:38.940 And for this, you're gonna need to get instantly CLI if you're using instantly for this scenario. And this is gonna allow the agent that we're about to use to actually not only verify leads, but create campaigns and do all that kind of stuff. So if you just simply go to install from NPM, that is going to bring up this site right here, and you're gonna have one command in order to install this. If you're an agency or you manage multiple clients, you're gonna want to install the Instantly CLI 00:02:38.940 --> 00:02:59.840 at the project level. So, really, you just remove this. Honestly, it's just gonna be just like this. N p m I for install and then instantly CLI. So we're gonna go ahead and copy this, and then we're gonna hop over into cursor. Finally, you're gonna want to go to instantly. In order to get your API key, you just need to go to the lower left here. You're gonna click on settings. 00:03:00.080 --> 00:03:02.800 And then from there, you're gonna click on integrations, 00:03:02.960 --> 00:03:04.400 go to API keys, 00:03:04.480 --> 00:03:09.280 and then just create yourself an API key. We're gonna call this Claude code demo, 00:03:10.055 --> 00:03:19.815 and we're gonna select all scopes, and we'll go ahead and copy it from there. And we have our new API key. Now from here, the IDE that I use all the time is Cursor. 00:03:19.975 --> 00:03:27.850 Basically, like I said, it's an integrated development environment in which I actually have just one window where I can view all my files and 00:03:28.010 --> 00:03:30.890 folders and scripts and CSVs, 00:03:30.890 --> 00:03:40.005 which you'll see get built out here. What you're gonna wanna do is go to the marketplace here, and you're gonna wanna make sure that you have Cloud Code actually installed. 00:03:40.325 --> 00:03:52.740 And we're gonna just gonna go ahead and click on Cloud Code right there. And then from here, you could see I've already prepared a list. This is a list that I've scraped, but if you use something like instantly super search or any other data provider, 00:03:52.980 --> 00:03:59.380 you're gonna be able to pretty much narrow down the leads of your ICP, and then you're gonna want to download that CSV. 00:03:59.540 --> 00:04:08.795 Just bring it into an empty folder right on your hard drive, and then what you're gonna wanna do is to actually make your cursor or Claude code that current working directory 00:04:08.875 --> 00:04:16.635 so it can, uh, reference those files. So we have our CSV right here. Now I have my brand new chat session. Again, I have different levels of permission, 00:04:16.715 --> 00:04:26.930 which you're gonna wanna configure to how you want to work. For the most part, I would recommend being on auto mode so that way you don't do anything crazy. So I'm gonna use an app called Spokenly, 00:04:27.090 --> 00:04:29.330 which is a speech to text application. 00:04:29.330 --> 00:04:38.985 So I personally like to speak to my agents and use the keyboard for fine tuning and things like that. So this is a brand new project in which we are going to 00:04:39.705 --> 00:04:40.425 enrich 00:04:40.665 --> 00:04:43.705 and clean up the CSV in here, 00:04:44.185 --> 00:04:46.425 which is geared towards 00:04:46.745 --> 00:04:49.705 going after our ideal customer profile 00:04:50.030 --> 00:04:50.830 for 00:04:51.310 --> 00:04:52.110 SpaceX. 00:04:52.110 --> 00:04:53.310 In this example, 00:04:53.390 --> 00:04:56.830 we will be using this list to target 00:04:56.830 --> 00:04:59.950 and generate cold emails in a campaign 00:05:00.030 --> 00:05:02.030 in order for us to offer 00:05:02.295 --> 00:05:04.055 different lines of SpaceX, 00:05:05.095 --> 00:05:07.335 in rural areas where 00:05:07.495 --> 00:05:17.255 businesses can actually benefit from high speed Internet such as Starlink. So what I want you to do is to firstly pull into context about SpaceX. 00:05:17.420 --> 00:05:20.060 I want you to establish skills 00:05:20.060 --> 00:05:23.580 in order to know more about SpaceX 00:05:23.580 --> 00:05:25.020 as it relates to 00:05:25.260 --> 00:05:26.060 your 00:05:26.140 --> 00:05:27.900 taskings and requirements. 00:05:28.140 --> 00:05:32.485 And then I also want you to in implement skills 00:05:32.485 --> 00:05:37.685 in order for you to know what cold email good cold email looks like. Firstly, 00:05:37.765 --> 00:05:38.965 every cold email 00:05:39.205 --> 00:05:48.620 has to be very carefully considered and spoken to the person as if you wrote the email on a one to one basis. There will be no templates. 00:05:48.620 --> 00:05:49.740 There will be no 00:05:49.980 --> 00:05:52.700 custom merge tags that are inserted 00:05:53.020 --> 00:06:00.895 as a piece of the entire copy. There are no templated pieces of copy. Every single email 00:06:00.895 --> 00:06:05.855 needs to be carefully crafted as if you research the company for 00:06:06.175 --> 00:06:18.070 an unknown amount of time, but let's just speculate to say about twenty minutes to an hour so much so that you know exactly what you do. Imagine if you are a business development representative 00:06:18.070 --> 00:06:20.390 or a sales development representative 00:06:20.630 --> 00:06:23.030 and you are personally researching 00:06:23.030 --> 00:06:29.785 this person who is the ICP on the CSV list, and you really understand 00:06:30.105 --> 00:06:41.020 their potential pain points in such a way that you would like to reach out to them and pique their curiosity and start conversation. The way to do it nowadays 00:06:41.020 --> 00:06:44.300 is not so much to go direct value proposition 00:06:44.540 --> 00:06:50.780 because nobody nowadays likes to be sold to directly unless they have a very 00:06:51.115 --> 00:06:57.275 much of a pain point. Instead, what we need to do is to reach out to these professionals 00:06:57.275 --> 00:06:59.275 who we reach out to and 00:06:59.435 --> 00:07:00.235 instead 00:07:00.315 --> 00:07:06.090 let them know about something that they may not already know that is interesting, 00:07:06.490 --> 00:07:07.450 insightful, 00:07:07.690 --> 00:07:08.970 and most importantly, 00:07:09.610 --> 00:07:16.090 The biggest thing here is that we are reaching out to prospects in which we have no idea who they are. 00:07:16.330 --> 00:07:35.090 They have no idea who we are, and therefore, there is absolutely zero trust. So it is critical that the copy that we send is extremely relevant, that every single sentence and every single word is carefully crafted, that there's no small talk, there's no em dashes, 00:07:35.170 --> 00:07:42.610 there's no, I hope this email finds you well. And it needs to be able to be read in roughly three to five seconds. 00:07:43.035 --> 00:07:49.995 And the email needs to be probably no more than 100 words, and it needs to be formulated 00:07:50.075 --> 00:07:57.835 in an optimized way that could be easily read on a mobile device. So, therefore, we're talking one to two sentences 00:07:57.835 --> 00:08:08.930 per paragraph. The frameworks that I want you to implement as skills are as follows. We have the greeting because everybody needs to be nice and say hello first name. 00:08:09.330 --> 00:08:10.690 The first name variables 00:08:10.690 --> 00:08:11.970 defined by Instantly 00:08:12.305 --> 00:08:19.345 is in what you call camel case. A lot of times you'll actually get snake case, but it's actually camel case. Finally, 00:08:19.825 --> 00:08:25.905 what I want to make sure that you do ultimately is that your goal is to reach the prospect 00:08:26.145 --> 00:08:28.145 and peak their curiosity 00:08:28.440 --> 00:08:31.880 in such a way that makes it easily 00:08:31.960 --> 00:08:38.680 welcoming and in such a way that they want to know more about you. A call to action 00:08:39.080 --> 00:08:42.200 should ideally be something that is a no brainer. 00:08:42.645 --> 00:08:46.485 It's not necessarily asking for a meeting. It's not necessarily 00:08:46.725 --> 00:08:49.125 asking for them to do anything. 00:08:49.365 --> 00:08:53.365 It's purely insightful in such a way that it is obvious 00:08:53.365 --> 00:08:56.565 and very easy for them to say yes 00:08:56.900 --> 00:09:08.740 that they are really trying to learn more about it. They're gonna do one of three things. They're gonna either not respond or they're going to respond and say kick rocks, unsubscribe, 00:09:09.015 --> 00:09:14.375 or hey, I'm interested. Or there's the third one which is they will not respond 00:09:14.695 --> 00:09:26.570 but they will actually go to your website, they'll sniff you out, they'll check out your LinkedIn, they'll check out your YouTubes, they'll check out your website. They'll do all the things because a lot of buyers are very intelligent now, 00:09:26.970 --> 00:09:33.930 and they won't ever respond. But you know what they will do is they will actually self serve and probably book a meeting, 00:09:34.250 --> 00:09:41.535 or they will probably just sign up on their own. So that is usually the outcome that is going to happen. But nonetheless, 00:09:41.535 --> 00:10:11.265 what I would like you to do is to always send an email with the intention of getting a reply regardless if it is a yes or no, but we wanna make it as easy as possible for the user to actually catch their attention, understand what we're trying to say in order to improve their current state or resolve a pain point, and then ultimately start a conversation. So you can see right there, I took a bit of time to actually talk to the agent. I'm giving it full context around 00:10:11.265 --> 00:10:26.250 what I wanted to do. Now the next thing I'm gonna do is I'm gonna give it instantly CLI, but I'm trying to make this a crash course and just make it as easy as possible. You can already see it's starting to create some, uh, markdown files and scaffolding this project right here. 00:10:26.730 --> 00:10:33.210 And from here, once it's done, you wanna do two things. You wanna verify for quality and accuracy, 00:10:33.210 --> 00:10:39.825 and then you wanna refine. And then from here, I will demonstrate exactly once it's done cooking to actually go into the CSV, 00:10:40.305 --> 00:11:05.500 and we will get started with some lead generation. Alright. So it has written a bunch of different markdown files in which you can see right here if we break this out. We have cold email skills and we have SpaceX knowledge skills. So you can see it's a skill dot m d, also known as a markdown file. So this is, uh, one of the file formats that makes it super easy to tokenize for AI as well as read for humans, 00:11:05.740 --> 00:11:10.595 which is obviously subjective here. But if you do a little shortcut called shift command v, 00:11:10.755 --> 00:11:25.550 it'll actually populate into a really nice kinda Notion like file where it's marked down. So it's very simple to actually review here. So for now, we'll go ahead and pass on that and get this lead generation machine up and going. Alright. Great. Now from here, 00:11:25.870 --> 00:11:39.705 you will see that we have a CSV list that is already scraped and prepared for us. What we wanna do is to go into the CSV. What I want you to do is to start a virtual environment 00:11:39.865 --> 00:11:43.705 so that way we can isolate this project from the rest of our machine. 00:11:43.945 --> 00:11:47.785 And then I want you to use Python and also install 00:11:47.785 --> 00:11:48.585 polars 00:11:48.825 --> 00:11:51.225 in order to quickly navigate 00:11:51.225 --> 00:11:52.105 and understand 00:11:52.680 --> 00:11:58.200 what we're looking at from a list perspective. And then I want you to segment what you believe 00:11:58.360 --> 00:12:00.200 is going to be a 00:12:00.520 --> 00:12:01.560 short win 00:12:01.880 --> 00:12:04.920 and break this into either segments or cohorts 00:12:05.160 --> 00:12:06.120 in order to 00:12:06.945 --> 00:12:20.530 scale this as quickly as possible to know that what we're working with is quality data and good to go. So please look at that, understand where they are, and which Starlink product was gonna be 00:12:20.930 --> 00:12:26.130 advantageous for us to reach out to first. So you notice right here, I'll set up the VENV, 00:12:26.210 --> 00:12:35.505 install polars, and explore the CSV. There are two types of libraries that are used a lot with CSVs that we use, polars, then you have pandas. 00:12:35.585 --> 00:12:38.945 Those are the two types. Polars is much faster 00:12:39.185 --> 00:12:40.305 and requires 00:12:40.385 --> 00:12:55.960 way less RAM. So that way your computer doesn't go, oh, I'm screaming here. Right? So I installed it, multistep. K. You know, we're going through. Polar's truncated in the middle of the industry list. Okay. That's interesting. Pulling pulling the full breakdown plus a few signals. 00:12:56.200 --> 00:12:59.240 So, yeah, sometimes you gotta kinda steer it, and we'll see 00:12:59.640 --> 00:13:16.845 what that does. But now what it's doing is it's generating a Python script and using polars to actually analyze the CSV that we have, and then it's gonna break it down and come back to me with everything that we need. And while that is working, we're actually gonna set up, uh, instantly CLI. 00:13:16.845 --> 00:13:18.605 So I'm actually gonna go here. 00:13:19.170 --> 00:13:20.850 We're gonna start a new session. 00:13:21.250 --> 00:13:22.930 We're gonna go back to our files. 00:13:23.090 --> 00:13:32.290 And then I'm actually going to click on this. We're gonna start a new full or a new file. We're gonna call it .env.local. 00:13:32.290 --> 00:13:34.210 I'm gonna type in instantly 00:13:34.885 --> 00:13:35.845 API 00:13:36.485 --> 00:13:38.085 key equals, 00:13:38.085 --> 00:13:46.405 and I'm gonna paste it. And then we're gonna hit command s to save, and then we'll close it. Then we're gonna go here. We're gonna say, I want you to install 00:13:46.910 --> 00:13:48.590 instantly CLI 00:13:48.830 --> 00:13:49.630 using 00:13:49.790 --> 00:13:51.230 using command 00:13:51.230 --> 00:13:52.750 n p m I 00:13:53.070 --> 00:13:53.870 instantly 00:13:55.550 --> 00:13:56.430 CLI. 00:13:56.430 --> 00:13:58.910 Please install this at 00:13:59.385 --> 00:14:01.145 the project level, 00:14:01.305 --> 00:14:02.905 not user global. 00:14:04.185 --> 00:14:04.985 And 00:14:05.065 --> 00:14:08.345 let me know once this is set up. 00:14:08.825 --> 00:14:12.745 We have the instantly API key that is in our 00:14:13.370 --> 00:14:14.650 ENV file 00:14:14.890 --> 00:14:15.850 which is 00:14:16.170 --> 00:14:17.930 ENV dot local. 00:14:18.250 --> 00:14:23.450 So what the ENV dot local is is definitely a file that you wanna keep confidential. 00:14:23.610 --> 00:14:35.395 That's where your APIs are stored and anything you deploy, it needs to have API keys stored on there. So definitely do not expose those. Allows you to keep things, you know, safe and secure. Perfect. And it just like that installs. 00:14:35.555 --> 00:14:37.235 We have instantly CLI, 00:14:37.235 --> 00:14:50.210 which is now in packets dot JSON, which we can pull up, but it basically says, hey. These are the dependencies that you need in order to run this whole thing. And then let's see here at the project root. Nothing went global. 00:14:50.690 --> 00:14:53.170 Couple of things. K. Loading instantly CLI 00:14:53.170 --> 00:15:08.405 by default. K. Like, need a symlink. Let's see here. Verify that the CLI works. Yes. Please verify that the CLI works. So it says it's working. It's authenticated. K. We're good to go. We have our workspace. 00:15:09.045 --> 00:15:15.230 Alright. Beautiful. And we are done. Alright. And just after a few minutes, we have our sample set for calibration. 00:15:15.550 --> 00:15:55.715 So that's something that we can review to make sure it's good. So you could see right here, this goes over the copy. The Microsoft powered upstream stack at XML only works if the link from each premium pad holds top across hundreds. So it's basically stating a fact here. A few neighboring operators have started dropping legacy GEO and four g. So I was talking about the network. This is kinda where we wanna iterate and make sure that it really sticks out to them. It needs to be really obvious to them that's like, oh, how did you figure that out? We're actually gonna stop this and we're gonna say, based on the feedback that you have sent of the calibration, we have five emails per the tier one a of the subsegment. 00:15:55.715 --> 00:16:00.195 And specific to Christopher Wright, who is head of field communications at ExxonMobil, 00:16:00.195 --> 00:16:02.675 I really want to dive in to 00:16:02.835 --> 00:16:03.555 the 00:16:03.715 --> 00:16:06.915 rural areas of when it comes to latency, 00:16:08.040 --> 00:16:09.400 slow networks, 00:16:09.640 --> 00:16:12.280 having a whole lot of reliability, 00:16:12.440 --> 00:16:16.200 and therefore also can be improved through 00:16:16.440 --> 00:16:22.205 having a dedicated satellite or dedicated dish for Starlink satellites. 00:16:22.605 --> 00:16:32.125 So I would say that with the hook on this specific one and really for the rest of them, we need to have a much stronger hook because the first sentence 00:16:32.125 --> 00:16:45.840 is the most vital piece of it. In other words, it needs to speak to them so clearly that it grabs their attention because you literally have about one to two seconds before they either mark you as spam or they 00:16:46.000 --> 00:16:52.015 actually read on in which we want to have them read the second or the third paragraph. 00:16:52.095 --> 00:16:53.135 So ideally, 00:16:53.295 --> 00:16:55.615 the first hook sentence 00:16:55.615 --> 00:16:57.455 needs to be extremely 00:16:57.535 --> 00:16:58.335 short 00:16:58.335 --> 00:16:59.615 and vital 00:16:59.695 --> 00:17:03.520 and relevant to the prospect. The second sentence 00:17:03.520 --> 00:17:09.200 needs to be in a way that leads with the pain point and something 00:17:09.200 --> 00:17:15.360 about their situation that you noticed in such a way that you have relevant proof, 00:17:15.680 --> 00:17:16.320 good trust, 00:17:17.045 --> 00:17:23.445 and you are able to solve that problem or that pain point or improve their current situation. 00:17:23.605 --> 00:17:42.590 And that is part of the second or the middle part of the email. And then we need to have a soft CTA or call to action that makes it so easy for them to say yes and needs to be in a persuasive soft manner such as would you be open to taking a look or if I could provide you 00:17:42.910 --> 00:17:45.310 a snapshot or if I could provide you 00:17:45.675 --> 00:17:46.555 something 00:17:46.795 --> 00:17:56.075 that's specific to this in which I would need you to tailor this to them, would that be valuable to you? Things like that where if they were to apply sure, 00:17:56.235 --> 00:18:00.090 that's an interested lead. They would reply, yes, this is interesting, 00:18:00.410 --> 00:18:07.610 then yes, that's a good thing. Again, the goal here is to start a conversation, not necessarily going straight for the kill or the close 00:18:07.770 --> 00:18:11.130 because these types of people are professionals. 00:18:11.785 --> 00:18:17.065 They are likely already getting cold emails, and so we want to be as relevant, 00:18:17.145 --> 00:18:18.025 as short, 00:18:18.345 --> 00:18:19.865 and as concise 00:18:20.025 --> 00:18:24.425 and specific as possible. We also need to make sure that no 00:18:24.620 --> 00:18:36.940 paragraph is too long. We need to have maybe one or two sentences at best and ensure that we have new lines to make sure it is spread out. And this should be optimized in such a way that could be read 00:18:37.115 --> 00:18:38.395 on a mobile device 00:18:38.715 --> 00:18:44.715 in about five seconds, no more. So with that said, please generate a new sample set of copy, 00:18:44.955 --> 00:19:07.175 and we need to make sure that we approve of this before we go at scale. So you can see here that oftentimes I'm getting an error here. So this is pretty much very rare, but a lot of times what I'll do is I'll just start a new chat session and then we'll just continue from there. So we will start a new chat session. And, this is part of the benefit of having your code base already established because context will just transfer over, 00:19:07.495 --> 00:19:12.455 and we don't need to explain everything. Although, I'm going to explain because we don't want to waste time. 00:19:15.495 --> 00:19:25.070 Alright. So we have our new copyright here, and we're gonna go see what we have for Christopher Wright. So we're saying, Christopher, ExxonMobil's 00:19:25.070 --> 00:19:27.390 remote Permian pads run 00:19:27.710 --> 00:19:32.670 on its least reliable link. Cellular and legacy satellite choke on real time SCADA 00:19:32.670 --> 00:19:34.270 and methane telemetry okay. 00:19:34.805 --> 00:19:46.565 If I sent a one screen snapshot of what that looked like at a comparable Permian site, would that be worth a look? That's a good one. And then right here, the largest operator in Permian still runs 00:19:46.805 --> 00:19:54.940 on four connectivity vendors. Wells, DJ. Okay. Perfect. One dedicated Starlink layer is how a few peers made that consistent. 00:19:55.020 --> 00:19:59.100 If I put together a short snapshot of how they did it, would that be useful to you? 00:19:59.420 --> 00:20:08.745 Spot on. Love it. At this point, it's just a lot easier especially for cold email to say, hey, would you like to try it or would that be worth a look? Right? So that's the goal here. 00:20:09.145 --> 00:20:15.065 So from here, we are going to so it's all done. I went ahead and approved it already. 00:20:15.225 --> 00:20:20.060 So we're gonna say, great. I want to now push this to instantly 00:20:21.580 --> 00:20:22.860 use instantly 00:20:22.940 --> 00:20:25.340 CLI to create campaigns 00:20:25.340 --> 00:20:26.140 around 00:20:26.140 --> 00:20:26.780 this, 00:20:27.100 --> 00:20:29.340 uh, one to one personalized 00:20:29.820 --> 00:20:30.620 copy, 00:20:30.620 --> 00:20:31.500 and let's 00:20:31.835 --> 00:20:33.835 get the campaign 00:20:34.235 --> 00:20:35.115 created 00:20:35.675 --> 00:20:36.395 and 00:20:36.955 --> 00:20:39.035 with the right sequence 00:20:39.035 --> 00:20:40.075 steps. 00:20:40.155 --> 00:20:42.235 Let's do a three sequence 00:20:42.235 --> 00:20:43.195 campaign. 00:20:43.755 --> 00:20:46.475 And step one will obviously be immediate. 00:20:46.740 --> 00:20:49.380 Step two will be three days after. 00:20:49.700 --> 00:20:52.420 Step three, let's do seven days. But 00:20:52.740 --> 00:20:58.980 on the second email, I want there to be no subject line because that will be in the same thread. 00:20:59.460 --> 00:21:00.980 And on step two, 00:21:01.685 --> 00:21:04.885 we should not and never just follow-up 00:21:04.885 --> 00:21:07.765 or bump this to the top of the inbox because 00:21:08.005 --> 00:21:16.165 everybody loves to be reminded on why we didn't reply in the first place. So, therefore, it's actually a waste of a perfectly good opportunity 00:21:16.325 --> 00:21:19.420 to actually provide additional insights. So therefore, 00:21:19.740 --> 00:21:20.860 step two 00:21:21.100 --> 00:21:22.380 actually needs to be 00:21:22.780 --> 00:21:25.100 a value add follow-up. 00:21:25.100 --> 00:21:29.820 In other words, that we need to be able to provide additional insights or 00:21:29.900 --> 00:21:33.635 reframe the same message in a way that actually 00:21:34.115 --> 00:21:35.955 explains it a little bit differently 00:21:36.195 --> 00:21:43.075 so that way they can actually learn. Because a lot of times, people don't even remember a cold email that they received five minutes ago. 00:21:43.700 --> 00:21:47.060 So it is worth the second email to actually provide 00:21:47.140 --> 00:21:48.980 a little bit more details 00:21:49.220 --> 00:21:51.620 than the first one. The third email 00:21:51.940 --> 00:22:04.115 needs to have a new subject line, and this will result in a net new email that they probably don't even remember they got the first two. So what I want you to do is to word this in a way where we are still 00:22:04.435 --> 00:22:05.955 sending the same message, 00:22:06.195 --> 00:22:09.395 but we need to reframe it in a way that potentially 00:22:09.395 --> 00:22:10.675 is unique 00:22:10.675 --> 00:22:12.675 to their situation 00:22:13.330 --> 00:22:17.970 because most people in b to b will do transactions 00:22:18.050 --> 00:22:21.170 and buy from vendors for three reasons. 00:22:21.490 --> 00:22:22.530 That is to 00:22:22.770 --> 00:22:23.810 make money, 00:22:24.050 --> 00:22:25.170 save money, 00:22:25.490 --> 00:22:28.130 or save time, and that's it. So 00:22:28.465 --> 00:22:37.745 if we approach them at the first one about saving time or saving money or improve, you know, their situation just like I mentioned on any one of those three 00:22:37.985 --> 00:22:53.210 where Starlink is actually going to be a better, faster, cheaper solution. Then on the third email, we just need to do the same thing. We don't need to necessarily overlook it. However, there's always a different approach that we can actually do. So I need you to draft up all three 00:22:53.695 --> 00:23:16.390 for this sample set. And then once that's done, we will run this at scale, but I need to see this in instantly and with all three steps. And let's go ahead and create this. Alright. So with some tough love, Anthropic and Claude Code have finally come in clutch. So with this one, what I had to do for this is I actually started a new chat because the first one I had, I was just getting constant 00:23:16.470 --> 00:23:27.715 just errors there. So I figured, okay. Well, Anthropic's being a little moody. Uh, we're just gonna go ahead and start a new chat session. If we scroll down, I won't bore you with all the details. It was basically making a bunch of commands 00:23:27.795 --> 00:23:31.075 in order to actually produce the campaigns, which it did. 00:23:31.315 --> 00:23:48.720 And then I noticed, uh, the other thing too is once it actually creates a campaign, which we'll look at here in a second, you just wanna verify for two things, which is quality and accuracy to make sure you as the human know you're gonna send good emails for which you want. So that was one of the things it said right here as root cause. It says campaigns 00:23:49.120 --> 00:23:58.075 created, all good to go, copy is solid. Now just verify for it. Right? Now if we just go right into instantly and you go to your campaign section, 00:23:58.395 --> 00:24:05.560 I can go ahead and I could see the campaigns were created, which is great. So we're gonna go ahead and click on this one for the tier one a. 00:24:05.800 --> 00:24:15.240 And we could see right here, we have our sample set of leads already uploaded and good to go. Now you will see you have, you know, your typical ones of email, email provider, 00:24:15.400 --> 00:24:17.400 your ESG or security gateway. 00:24:17.895 --> 00:24:20.455 You have your status, contact company, 00:24:20.615 --> 00:24:25.015 all of the, uh, standard ones. But then what you'll notice here is we have message one, 00:24:25.175 --> 00:24:39.720 message two, message three, and then we have the subjects. K? Then we have the normalized first name. So if we go into sequences, you can see right here, this is the kind of copy that I like. And if we were to go to preview, you could see right here where it says Christopher. 00:24:39.880 --> 00:24:58.875 All of this looks really good. And if we were to choose other leads, it is a completely different email. It's not so much the actual copy that you're using. It is the frameworks around the copy. If we were to go again to say Douglas. Right? We have the hook. K? And then we have facts about your current state 00:24:59.115 --> 00:25:06.720 and, you know, revolving around it of a pain point. And then we have something that is a proposed solution or a, 00:25:06.880 --> 00:25:13.280 uh, scenario in which they can prove their situation. And then we have a very low friction or really no friction, 00:25:13.925 --> 00:25:39.000 valuable call to action on a hypothetical. If I sent a snapshot of how other terminals did exactly that, would that be worth a look? Leading into everything here. There is no small talk of, I hope this email finds you well. There's no just bumping this at the top of the inbox. Right? So if we were to go to step two, you can see again right here, we are leaving the subject line empty because it's gonna be in the same thread of subject 00:25:39.240 --> 00:25:53.355 one or email one. And, we have step two, worth adding the part that most teams miss. The problem on a remote pad usually isn't the outage. It's the latency floor. Right? So it's actually taking the second email as an additional opportunity 00:25:53.515 --> 00:26:03.670 to share more insights or explain more. And then you will notice on the third one, which is generally what we like to do, is we will actually make a brand new net new email, 00:26:03.830 --> 00:26:20.125 and we'll do it, I'd say I mean, it could be three days. It could be seven days later. So if I were to go to preview here, it's really just kind of another unique approach of really reaching out to that person to gauge their interest. So really, the two things here again, we wanna verify for quality and accuracy. 00:26:20.285 --> 00:26:24.160 You wanna make sure the new lines are good. You wanna sure it renders appropriately. 00:26:24.400 --> 00:26:38.160 You do wanna do a deliverability score. So we have perfect. Alright. Spam score is zero. Again, each one of these points, the lowest we can get is actually the best to do it. Right? So that, in my opinion, is best way to do it that we have seen in 2026. 00:26:38.255 --> 00:26:45.535 If you want to make sales, you still have to reach out, you have to follow-up, and you have to have a repeatable system that turns leads into clients. 00:26:45.695 --> 00:26:52.175 So click this video right here where it breaks down exactly what we would do to start a brand new agency in 2026 00:26:52.175 --> 00:26:58.865 from scratch. By the end of it, you'll have everything you need to start making your first dollars. Thanks for watching, and I'll see you over there.