# I Built a Full Marketing Campaign With Claude in One Afternoon **Channel:** HubSpot Marketing **Source:** https://www.youtube.com/watch?v=VkJnxeAvy4E **Transcript page:** https://www.withtranscript.ai/video/VkJnxeAvy4E ## Chapters - 0:00 — Why Small Businesses Need AI Context - 3:21 — Setting Up Claude Projects Properly - 6:03 — Connecting Live Business Data Sources - 9:34 — Reusing Approved Work for Consistency - 12:14 — Turning Repeated Work Into Skills ## Transcript **[0:00] Speaker A:** I just built my new brand's very first marketing campaign using AI in one afternoon. These posts send people here. This page gives away a free guide, and this is the email that delivers it. I built all of it with the same Claude you're using. If you have a small business, you're the marketer, the customer service desk, and the person who reorders printer ink. And figuring out AI probably takes longer than just doing it yourself. The other Claude tutorials that you've been watching, they hand you a prompt and wish you luck. What they don't tell you is that there are six essential rules to follow if you want AI to actually save you time. We're going to go over each one and how they work together to build a full marketing campaign in a voice that actually sounds like you. I'm going to use a few prompts from HubSpot's complete guide to Claude. **[0:55] Speaker A:** It is free. It's linked in the description. Make sure to grab it. We'll start using it in like two minutes. Now, the number one mistake I see in small business marketing comes from skipping rule one. Don't skip rule one. **[1:14] Speaker A:** If your AI copy sounds like everyone else's, it's not your prompt. I want you to think about how you would brief your newest hire. Would you say create a landing page for our upcoming campaign? No. You would walk them through the brand voice and guidelines, maybe even give them a copy or samples, right? You'd go over business goals and you chat about what you're actually trying to do. If AI doesn't have this kind of context, it fills in the blanks, which is exactly how you get something like this. With the right context, you get something like this. So, rule one, treat Claude like a new hire from day one. Before I even open Claude, I'm going to take 10 minutes to dump all of my knowledge into a document. This doesn't have to be a manifesto, okay? Just has to exist. Now, if a blank doc is where you freeze that guide in the description does have a prompt that flips it and Claude just interviews you instead. **[2:14] Speaker A:** So here's the campaign I'm building. Who it's for? Small business owners and solo creators who know that they should be posting but tend to freeze up. The offer is a free kit that tells you what to post based on how much energy you have today and the goal is email signups because an email list is the one audience no algorithm can take away from you. So I need a plan, a landing page, an email, and posts. And it all has to sound like it came from me. So I'm going to gather whatever I would hand a new hire on day one. For me, that is my brand guidelines, the kit, my logo, a few posts I've actually written, screenshots of my social profiles, website, and even landing page inspo. The more context, the better. So here's a list of ideas. You can pause the video and screenshot this. **[3:04] Speaker A:** Now I could just upload all of this to Claude every single time I open a new chat, but that kind of defeats the whole time-saving thing. So where does all of this actually go? **[3:21] Speaker A:** Everything gathered needs to live in one place that Claude can access. A Claude project is a workspace where the setup that you add applies to every chat inside of it. There are three layers and most people mix them up. Instructions are the job description, how to work. Context is the onboarding folder, what you know. But here's the difference. This is where most people are confused. Claude follows the instructions in every chat. The context is just there for it to use, but it won't necessarily read all of it until you tell it to. Memory is what they pick up on the job. You don't write it, Claude does. And Claude is a lot better at remembering than the person that you were going to hire. Just saying, I'm not judging. Your Claude project instructions only need four things. What's their job? That's the lens that it looks through for everything you asked. **[4:12] Speaker A:** What's the first step? Read all the context. That's what makes it actually use everything that you uploaded. What should it do before handing anything in? Check it against the guidelines so it catches the off-brand stuff before you do. And if it doesn't know something, say so. Do not guess. For the context, I will copy my campaign overview and add it as text context. Text context. That's a lot to say. Then I'll upload everything else I gathered. So that's the setup. Now let's test it. No uploads, no explaining. I'm just asking one question about my audience. Seems to have worked. It even caught me breaking my own style rules. Rude. Also accurate. And at the bottom, Claude is telling me what it doesn't know. So that is instruction four doing its job. It is not guessing. This list that you get is the to-do list. Fix it once in the project and then every chat after that gets the update. **[5:10] Speaker A:** So now let's plan my entire marketing campaign with Claude. There is a prompt in the guide for this. I just filled it in for my campaign. It's basically telling it plan a full campaign, content calendar, posts, landing page, and email. But before it writes anything, it should ask me what it needs to know. So Claude just handed me the plan and asked some questions. I'll just answer these. And now it's writing out the whole plan. So we've got a calendar, a real script, 12 posts, even a landing page and email copy. That is crazy, right? So I'm just going to rewrite the reel in my own words, review the landing pages, review everything, and send any notes to Claude to make the changes. So I'm happy with this. I can just download it and add it to the project as context. **[6:03] Speaker A:** But some context changes every week. What your customers say, what your numbers show. Uploading that by hand is a part-time job. So how can we get Claude to read it directly? **[6:21] Speaker A:** Think about where your business actually lives. It's not one PDF, docs and spreadsheets, your inbox, your CRM. Right now you are the middle man. You copy from here, paste into there every single time. We do not have time for that. A Claude connector lets Claude read all of those places itself. A lot of software that you already use has a connector. There's a whole library that you can browse to find what you need. I will use two connectors, Drive so it works for my latest files and HubSpot so that it can read data from my CRM. Whenever you start a new chat, turn on only the connectors that Claude will need for that task. That way it knows where to look. And if you're not sure which ones to use, just ask. So now Claude knows the business. It's connected to the tools. Naturally, this is where people go a little crazy and send it some hefty tasks. **[7:13] Speaker A:** And that is usually where this all falls apart. **[7:23] Speaker A:** Okay, your new hire is great. You've onboarded them. They know your business. Now what do you say, build our whole website by Friday and then walk away? No, you'd say let's map it out first. Start with one part, we'll reconvene and then figure out the next steps from there. It's the same with Claude. The more you hand over at once, the more places it can break and the harder it is to find which part broke. So Rule Wuthey Rule four, if it is hefty, plan it first and then build it in sections. This is where it gets really cool. You do not have to be a developer or a designer to build a landing page anymore. In a new chat, just ask Claude to build it for you based on the project context. Section section with a walkthrough on how to do it on whatever page builder you use. **[8:12] Speaker A:** Claude builds the page as code, and then you paste that code into your page builder, and the builder turns it into the page that people see. Now, I don't understand code in the slightest, but if I just follow the instructions and paste in the first section, **[8:31] Speaker A:** I can see that the logo is missing. So, I'm just going to screenshot it and then send it back, and Claude will walk me through fixing just that piece. Something's still going to break, it always does, but going by section just means that it's a small thing, not the whole page. So, this is what my whole page looks like built out. Now, the same flow will get me an email. So, I just go into a new chat and ask Claude to turn the email from the campaign plan into HTML for my email tool. Quick side note because this is genuinely cool. If you are already on HubSpot, you can do a lot of this without even leaving it. Look, so I can use HubSpot's campaign agent, give it the same goal, and it'll plan the campaign from what's already in my account, my brand, my audience, and what's worked before. **[9:23] Speaker A:** Then it actually builds it all right there inside HubSpot. Or you can just build it in Claude like I did and use the HubSpot connector to push the draft straight into your account. **[9:34] Speaker A:** It's pretty nifty. So, now I have a page and an email, but nothing is connected yet. Right now, the form doesn't send anyone anything. Connecting that form and everything that happens after someone signs up, that will be covered in the next video of this three-part series. So, make sure you subscribe so you don't miss it. And by the way, if this video is helping you out so far, make sure to hit like to let me know. Now, this campaign still needs me to create two weeks of posts, but if I were to start from scratch, I'm going to be straight back to generic. **[10:14] Speaker B:** Your new hire writes one great reply to a customer. Do they write the next one from a blank page? No. You approve it, they implement the same feedback for the next email. Every time that you start from scratch, you're asking Claude to guess again, and guessing is how you got generic in the first place. So, rule five, once something gets approved, it becomes the starting point for the next thing. When I answered Claude's questions for the campaign plan, I said that I want one hub piece of content, a short reel about what my kit is about and why I made it. The 12 posts that it outlined here are all repurposed from that one hub. So, in a new chat, I'll just ask Claude to create the posts. And now it's designing them out one by one. So, it's done, and I can click into any slide and then change it myself, colors, fonts, sizing, and then I can export the designs. **[11:11] Speaker B:** Now, anything that Claude makes that you can open and edit and come back to like this is called an artifact. You can find all of your artifacts within the artifacts tab so that you don't have to go searching through past chats. The captions for all of these posts are already in the campaign plan, so I'll just pull them up and edit them to sound like me. And because I already rewrote the hub piece, that reel in my own words, everything else already sounds pretty on brand. Now, when I feedback any changes that I made, Claude will learn from the edits and save it to memory. Whenever you approve something, upload the final version to the project context so that Claude always has the good version to work from. If you make a better version later, then swap it in and delete the old one. So, we are doing everything by hand so far, and by hand is exactly where to start. **[12:02] Speaker B:** But once something works, you'll start wondering what you can stop doing yourself. **[12:14] Speaker B:** So, your hire has done the job well a few times. You don't want to keep walking them through it. You document how it was done and then you automate the repetitive things. That's rule six. Once it's proven itself, stop micromanaging. When Claude does something well and you want to use that process again, ask it to turn that into a skill. It basically saves the steps so we can repeat the whole process. I'm going to create a brand voice skill simply by asking so that next time I use this project I can implement it easily. Almost anything in this video can be turned into a skill simply by asking. The guide in the description that I mentioned breaks down a few other skills that are super helpful for small business owners. But imagine not having to prompt Claude to do anything. It just does it like a campaign report that's waiting in your inbox every Monday morning. **[13:08] Speaker B:** Signups, what's working before you even open your laptop. I'm going to show you exactly how to do that in video three of this series, but for now get the hang of doing it by hand. These are the six essential rules that you need to follow if you want AI to actually save you time. We just proved it. A full campaign strategy, a landing page, an email that delivers a guide and two weeks of post all in one voice built in an afternoon. So here is the first step. Write down your guidelines, your voice, your goals, and what you're working on right now. Messy is fine. It just has to exist. Every other rule on this board runs on that one page. And when you go to build out the rest of your campaign, you're definitely going to want to download that guide that I mentioned. **[13:55] Speaker B:** It is free in the description. So this video built all of the assets, but right now none of it's switched on. And if people find you and nothing happens next, all of this was just very nice content. So in video two of the series we turn all of this into a lead gen machine so that the people who find you actually turn into the people who pay you. And in video three, we automate it so it keeps running without you. If those videos are already out, they will be linked on screen here in just a second. And if not, subscribe so you don't miss them. Thanks so much for hanging out with me. My name is Bridget Dorial. Feel free to connect with me online and I will see you in the next one. Bye.