Run a Whole Launch From One Claude Project

A launch is a stack of pieces that all have to agree.

The sales page makes a promise. The emails repeat it. The social posts tease it. When those pieces drift apart, buyers feel the wobble even if they can’t name it.

Most of that drift comes from where the pieces get written. You draft the sales page in one chat, the emails in another, the posts in a third. Each chat starts cold, so you re-explain the offer every time, and the details shift with each retelling.

One Claude project fixes that by holding the whole launch in a single place.

You load the offer once. Every asset you build after that pulls from the same brief, so the promise on the sales page is the exact promise in email four.

This works because a project remembers. Tell it the price, the bonuses, the dates, and the big promise one time. Then every page, email, and post you ask for starts from those same facts, instead of whatever you happened to type that session.

The cost of scattered launches isn’t only the wobble buyers feel.

It’s the hours you lose re-explaining the same offer to a fresh chat, over and over, all week. One project hands those hours back to you when you need them most.

Think of it as a command centre for one campaign. Not a permanent fixture like your everyday content project, but a room you build for a single launch, run the whole thing from, and clear out when the cart closes. One launch, one project, one story from the first tease to the final call.

Start the way you would with any project.

Open Claude, go to Projects, and make a new one. Name it for the launch itself, like Spring Budgeting Launch, so it never gets mixed up with your everyday work. This project has one job.

Set the instructions to describe the launch, not your whole business. Tell it what you’re selling, who it’s for, and the voice you want across the campaign. Keep that part short. The detailed facts go in a file, which comes next.

The point of a separate project is focus.

Your everyday content project knows your brand in general. This one knows this offer in particular, down to the price and the close date. That narrow focus is what keeps every asset on message.

Before you load anything, decide what this launch includes. A sales page. A five-email sequence. A handful of social posts. Affiliate copy. Support answers. Writing that list now tells you exactly what the project has to produce.

You don’t have to word the instructions from scratch. Describe the launch in a plain chat, ask Claude to turn it into clean project instructions, then paste the result in. Tweak anything that doesn’t sound like you before you save it:

I’m setting up a Claude Project to run a launch for [your offer], sold to [your audience]. The main promise is [your promise]. Write clear project instructions covering the offer, the audience, the voice I want, and two rules to follow on every asset.

Keep this project light on instructions and heavy on files. The instructions set the tone once. The files carry the facts. A short instruction block plus a solid brief beats a long instruction block trying to hold every detail of the launch.

Pin the launch project to the top of your list while it’s live. You’ll open it many times a day during the campaign. A project you have to hunt for slows down a week when speed is the whole point of having it set up.

Bring your voice samples into this project too.

The launch copy still has to sound like you, not like generic sales writing. Drop in two or three pieces you’re proud of, so every asset the project writes carries your tone, not a stranger’s.

Don’t draft launch work in random chats outside this project. Keep it all inside the launch project, start to finish. The moment you write a launch email in a stray chat, you lose the consistency you built the project to protect in the first place.

That short list of assets also becomes your finish line.

As you build each one inside the project, you check it off. When the list is done, the launch is ready, and you never lost track of a piece because they all lived in one place.

The offer brief is the most important file in the project.

It’s a short document that holds every fact about the launch in one spot. Once it’s loaded, you never re-explain the offer again. Every asset reads straight from it.

Keep the brief to one page. List the offer name, the main promise, and who it’s for. Add the price, any bonuses, the open and close dates, and the one big result a buyer walks away with. Plain facts, no selling yet.

Write the promise with care, because it’s the line every asset repeats.

A weak promise spreads weakness across the whole launch. A sharp one, like “set up your budget in a weekend,” gives every email and post a clear point to circle back to.

Load the brief as a project file, not as a chat message. A chat message gets buried as the conversation grows longer. A project file stays in reach of every chat inside the project, which is exactly where the launch facts belong.

If your offer details are scattered across notes, let Claude assemble them for you. Paste the messy pile into a chat and ask for a clean one-page brief. Then drop that result into the project as a file you can reuse all week:

Here are my rough notes on a launch: [paste everything you know]. Turn this into a clean one-page offer brief. Include the offer name, the main promise, who it’s for, the price, the bonuses, the open and close dates, and the one big result a buyer gets.

Put the close date in the brief in plain words, not just a day. “Closes Friday at midnight Eastern” leaves no room for a mismatch later. A fuzzy date in the brief becomes a fuzzy date in three emails and a post you’ll have to fix.

Name the buyer in the brief as plainly as you can. Not a vague crowd, but the person with the problem your offer solves. The clearer that reader is, the more every asset speaks to someone real instead of to no one in particular.

Add a short line on what this offer isn’t.

If it’s built for beginners, say it isn’t for advanced buyers. That one line keeps the copy honest and keeps the wrong people from buying and asking for a refund a week later.

Update the brief first whenever something changes. If you push the deadline or add a bonus, the brief is the one file to fix. Everything downstream reads from it, so a correct brief keeps the next round of assets correct without extra work.

With the brief in place, the project knows the launch cold.

From here you’re not feeding it facts anymore. You’re asking it to turn facts it already holds into a page, into emails, into posts, each one already lined up with the same promise.

Build the sales page first, before any email or post.

The sales page is where the offer turns into an argument. Once that argument exists, every other asset has something to point at, instead of each one inventing its own angle from nothing.

Ask the project for the page in sections, not all at once. Start with the headline and the opening. Read it, fix the promise if it slipped, then ask for the next part. Building in pieces keeps the quality up and the message tight.

Feed it the order you want.

A headline, the problem, the offer, what’s inside, the bonuses, the price, then the close. Handing Claude the structure means it fills your shape, instead of guessing at one that may not fit your buyer at all.

When you know the shape you want, hand the whole thing over in one prompt and let it draft a first pass. You’re not after perfect on this round. You want a full draft on the page that you can then carve down into the real thing:

Using the offer brief in this project, write a sales page for [your offer]. Follow this order: headline, the problem, the offer, what’s inside, the bonuses, the price, and a clear call to buy. Match my voice samples and keep the promise consistent all the way through.

Read the draft against your brief, line by line. Does the price match. Does the promise match. Did it invent a bonus you don’t offer. Fixing those slips now sets the record straight for every asset you build next, since they all follow this page.

Lead with the result, not the feature list. Buyers care what changes for them, so let the page open on the outcome your offer delivers. The list of what’s inside still counts, but it lands harder once the reader already wants the result.

Write the price section to feel earned, not dropped in.

Stack the value first, then name the price, then the bonuses. Tell the project that order, and the number reads as a fair trade instead of a surprise the reader wasn’t ready for.

Add a short part that answers the obvious worry. Most buyers hesitate on the same one or two doubts. Name them on the page and answer them plainly, so the reader’s objection is handled before it becomes a reason to close the tab.

End the page on a single clear action.

One button, one instruction, one promise repeated. A page that trails off with three different next steps loses the reader, so tell the project to close on the one thing you want them to do.

Once the page reads right, save it back into the project as a file. Now the project holds two anchors, the brief and the finished page. Every email and post you write next leans on both, and the launch starts to feel like one piece instead of ten loose ones.

Your launch emails should sound like the sales page talking one idea at a time.

The page already holds the full argument. Each email takes one piece of it, the problem, a bonus, a worry, and gives that piece room to land on its own.

Write the whole sequence in one chat inside the project. That way email five remembers what email one promised, and the arc holds together. A sequence built across five separate chats tends to repeat itself and lose the thread halfway through.

Plan the arc before you ask for a word.

Email one opens the cart and names the problem. The middle emails each take one angle. The last email pushes the deadline. Tell Claude that arc up front so it writes toward a finish, not in circles.

Subject lines deserve their own pass. Ask for two or three per email and pick by feel. The project knows your voice and your offer, so the options come back in your tone instead of the loud, spammy lines that get ignored in a busy inbox.

When the arc is clear in your head, ask for the full sequence in one go. You’ll edit every email afterward, but a complete first draft beats writing them one lonely message at a time across the week. Hand it the plan and let it fill in:

Using the sales page and brief in this project, write a [number]-email launch sequence for [your offer], going to [your audience]. Email one opens the cart and names the problem. The middle emails each take one angle. The last pushes the deadline. Keep each under [word count] and give each a subject line.

Open the first email fast, with no long windup. People skim launch emails, so the offer and the link belong near the top. Tell the project to skip the warm-up and name the offer in the first line or two of email one.

Give each middle email one job and one link. A bonus email sells the bonus. A proof email shares a result. When an email tries to do everything, it does none of it well, so keep them single-minded all the way through.

Vary the rhythm so the run doesn’t read like one long pitch.

A short email, then a story, then a quick reminder. The project can match that mix if you ask, and the reader stays with you instead of tuning the whole sequence out.

Re-read email one and the last email back to back. The first sets the promise, the last collects on it. If they don’t echo each other, the sequence leaks in the middle, so tighten both ends until the arc clearly closes the loop it opened.

Read the sequence as a buyer would, start to finish, in one sitting.

You’re checking that it builds instead of repeats. If two emails make the same point, tell the project to give one of them a fresh angle from the page, and the arc tightens up.

Your launch posts are short echoes of the page and the emails.

They don’t need new ideas. They need the same promise, cut down to a line or two that stops the scroll and points people back to the cart while it’s open.

Build them in the launch project so they match everything else. The project already holds your promise and your bonuses. Ask it to pull hooks from the sales page and turn each one into a post, and the posts line up with the campaign on their own.

Spread the posts across the launch window on purpose.

An opening-day post. A bonus spotlight midweek. A last-chance post on the close date. Tell the project which day each post is for, so the set covers the whole week instead of clustering up front.

Keep the posts plain and platform-light. One promise, one reason to act, one link or instruction. The project will happily write something clever, but a clear post pulls more clicks than a witty one that leaves people unsure what you’re even selling.

Ask for the whole batch at once, sorted by launch day. You schedule them in a few minutes and then forget them, free to spend launch week on emails and buyers instead of scrambling for something to post. Give it the days and the count:

Using the sales page and brief in this project, write [number] short social posts for the launch of [your offer]. Pull the hooks from the sales page. Label each post with the launch day it’s for, from opening day to the close. Keep each post plain, with one clear call to act.

Write a few posts that tease without selling. A question, a quick tip, a hint at what’s coming. Soft posts warm the feed before the cart opens, so the launch-day post lands on people who already know something good is on the way.

Match each post to where the launch stands that day. Curiosity before the open. Proof and bonuses midweek. Deadline pressure at the close. Telling the project the launch day keeps the tone right, instead of a hard sell three days too early.

Keep one link and one idea per post.

A post that asks for two things gets neither. The project will pack in more if you let it, so tell it to hold each post to a single point and a single clear next step.

Pull a line straight from a strong email when you’re stuck. The email already earned attention, so it works shortened into a post. Ask the project to trim your best email line into a scroll-stopper, and you reuse what’s proven instead of guessing.

Glance back at the posts beside your emails before you schedule.

They should feel like the same launch in a smaller frame. If a post promises something the emails don’t, fix the post, because the page and the emails are the version buyers trust most.

Affiliates sell harder when you hand them copy that’s ready to send.

Most won’t write their own, and the ones who do often drift off your promise. Copy built inside your launch project keeps their promotion lined up with yours from the start.

Give them the same anchors your own assets use. The project already holds the brief and the page, so the swipe emails it writes carry your exact promise and price. Your affiliates send a version of your launch, not a blurry copy of it.

Write a small kit, not a single email.

Two or three swipe emails and a couple of social posts cover most partners. Some send once, some send three times, and a small kit lets each one promote at the level they’re comfortable with.

Tell the project who the copy is for, because affiliate copy talks to a different reader. It speaks to the affiliate’s audience, not yours, so it leans on the affiliate’s voice while keeping your facts. That small shift makes the swipe feel native on their list.

Ask for the full kit in one prompt, labeled and ready to drop into a partner page. You hand it over once and answer fewer questions later, because the copy already says what the launch is and what a click gets the reader. Spell out the kit:

Using the brief and sales page in this project, write an affiliate swipe kit for [your offer]. Include [number] swipe emails and [number] social posts. Write them for an affiliate’s audience, keep my promise and price exact, and label each piece so a partner knows when to send it.

Send affiliates the dates and the link in the same kit. Copy without a deadline and a clean link creates a flood of questions. Bundle the swipe, the dates, and the link together, so a partner has everything to promote in one place.

Offer a short and a long version of the swipe email. Some partners want a quick paste, others want a full story. Two lengths cover both without back-and-forth, and the project writes both from the same brief in a single pass for you.

Remind affiliates to send more than once.

Most underestimate how many sends a launch needs. A line in your kit suggesting two or three sends, plus the copy to do it, lifts partner sales without you chasing each one by hand.

Keep your affiliate promise inside your own claims. A partner who over-promises drags your refunds up, not theirs. Swipe copy that stays true to your brief protects your name, since buyers blame the product, not the affiliate who oversold it.

Check the kit against your own emails before you send it out.

The affiliate version should make the same promise in a different voice. If the facts wander, fix them now, because a partner sending the wrong price creates a mess you clean up during launch week.

Launch days bring the same questions every time.

Where do I get access. Does this fit a beginner. What’s your refund policy. How long is the cart open. You can write those answers now, days before the rush starts.

The launch project already knows the facts, so the answers come fast. Ask it to draft a clean reply for each common question, grounded in your brief and your page. You read them once, fix the tone, and save the set as a file.

Pre-written answers keep launch day steady.

When ten questions land at once, you’re pasting approved replies instead of writing under pressure. The buyer gets a quick, clear answer, and you stay free to handle the rare question that truly needs you.

Cover the money questions with extra care. Price, refunds, and the deadline drive the most worried messages during a launch. Get those answers exactly right against your policy, so you never promise something on launch day that you have to walk back the next.

List your common questions, then let the project answer them all in one pass. You end up with a small support file you reach for all week. Give it the questions and the voice you want, and read the drafts before they ever go live:

Using the brief and sales page in this project, write short, warm replies to these launch questions: [list your common questions]. Keep each answer accurate to my policy and easy to read. Flag any question where you’re unsure of the facts so I can answer it myself.

Write the access answer with screenshots in mind. “Where’s my product” is the most common launch question by far. A clear, step-by-step access reply, ready to paste, clears most of those messages in seconds on the busiest day of the week.

Have a kind refund reply ready before you need it. Refund questions during a launch are normal, and a steady, fair answer keeps the buyer warm. Draft it now, so a refund request never catches you writing under pressure on launch day.

Keep a soft reply ready for the not-yet-ready buyer.

Some people write just to talk themselves into it. A warm answer that meets the worry, not a hard push, turns more of those messages into sales than a pushy reply ever will.

Group your answers by topic so you find them fast. Access, refunds, fit, deadline. A small labeled file beats scrolling a wall of text mid-launch. When a question lands, you jump to the right answer and reply before the buyer cools off.

Skim the answers one more time the night before you open.

Check that the dates are this launch’s dates and the price is this launch’s price. A support file from a past launch is worse than none, because a confident wrong answer costs you a sale.

Even inside one project, small mismatches creep in.

The page says the cart closes Friday, an email says Sunday. The page lists three bonuses, a post mentions two. Buyers notice these slips, and each one chips away at their trust in the offer.

The fix is a consistency pass before you go live. Because every asset lives in one project, you can ask Claude to read them together and flag where they disagree. No other setup makes this check so quick, since the files are already side by side.

Point it at the facts that hurt most when they’re wrong.

The price, the dates, and the main promise. A mismatch in any of those reads as carelessness to a buyer on the fence, and it gives them an easy reason to close the tab.

Read the flags Claude gives you, then fix the source, not just the symptom. If an email has the wrong date, the next one might too. Correcting the brief and re-checking is safer than patching one asset and hoping the rest are fine.

Do this pass once more after any edit. Changing the price or pushing the deadline ripples across every asset you already wrote. A second sweep catches the pieces you forgot to update, which is most of them when you’re moving fast near launch:

Compare these launch assets in this project: the sales page, the email sequence, and the social posts. Check that the price, the open and close dates, the bonuses, and the main promise match across all of them. List every mismatch you find and tell me which asset to fix.

Read your own assets out loud once before launch. Your ear catches a wrong price or a clumsy line your eye skips. It takes ten minutes and it’s the cheapest quality check you have, especially on the sales page and the close emails.

Keep a single source of truth and point everything at it. The brief is that source. When two assets disagree, the brief wins, and you fix the asset to match it. That rule ends the back-and-forth about which version is the right one.

Check the links as carefully as the copy.

A perfect email with a dead link sells nothing. Click every link in every asset before launch, because the one broken link always seems to land in the email that pulls the most clicks.

Watch for tone drift, not just fact drift. A page that’s warm and emails that turn pushy feel like two different sellers. Ask the project to hold one voice across the campaign, so the launch sounds like one person the whole way through.

Treat a clean pass as your green light.

When the price, dates, and promise line up everywhere, the launch reads as one tight offer instead of a pile of drafts. That consistency is easy to miss, but buyers feel it, and it shows up in your numbers.

With the assets built and checked, launch week turns into a routine.

The project is your home base. Each morning you open it, pull the day’s email, line up the day’s post, and handle whatever buyers send. Everything you need is already inside.

Work one task per chat to keep the project tidy. Today’s email in one chat. Today’s questions in another. Clean chats are easy to find later, and you avoid the tangle of one endless thread holding a whole week of unrelated launch work.

Lean on the project when a day goes sideways.

If opens are low, ask it for a fresh subject line built from your page. If a buyer raises an objection, ask for a reply that answers it from your brief. The launch facts are always right there.

Watch the numbers and adjust inside the same project. If a bonus is pulling more interest than the rest, ask for an email that leans on it. The project already knows the bonus, so the new email drops into your sequence without a cold setup.

Keep a light log as you go. A quick note each day on what you sent and how it did. You can even ask the project to track it. That record turns into next launch’s playbook, so this week’s lessons aren’t gone by the next campaign:

It’s day [number] of my launch for [your offer]. Based on the sequence and posts in this project, tell me what to send today, including which email and which social post. If opens have been low, suggest one fresh subject line for today’s email.

Set a fixed time each day to run the launch. Same hour, same routine, open the project, send the day’s pieces. A set time keeps a busy week from sliding, and the project makes that daily run short enough to keep up with.

Keep tomorrow’s email half-ready the night before. A quick look the evening before means no morning scramble. The project already holds the draft, so a five-minute review at night turns the morning send into a paste-and-go instead of a rush.

Answer buyers before you chase opens.

A waiting buyer is worth more than a tweaked subject line. Clear the questions first each day, then look at your numbers, because a fast reply during an open cart often closes the sale on its own.

Don’t rewrite the plan mid-launch unless the numbers demand it. A slow day is normal, not a crisis. Trust the sequence you built and checked, and save big changes for the close, where one strong push does more than a week of fiddling.

By midweek the routine runs itself, and you feel the difference a single project makes.

No hunting for the right file. No re-explaining the offer to a cold chat. You show up, the launch is all in one room, and you spend your energy on buyers.

The last day of a launch usually brings a big share of the sales.

People wait for the deadline, then act when it’s real. Your close needs to meet that rush with a clear push, not a quiet email that lets the moment slip by.

Write the final-day emails with extra care, and write them early. Pull them up from the project days ahead, while there’s no rush, instead of throwing them together on a busy close day. The deadline email is the one to get exactly right.

Send more than one email on the last day.

A morning email that names the deadline. An afternoon nudge. A final note an hour or two before the cart shuts. Tell the project to write all three as a small set, each shorter than the last.

Have quick objection replies ready for the close. The last day brings worried questions, and a fast, kind answer can turn a maybe into a yes before the cart shuts. The project knows your offer, so those replies come back in seconds.

Ask for the full close set in one prompt, ordered by hour. You schedule them in the morning and spend the rest of the day answering buyers, not writing. Give the project the deadline and the number of sends you want on the final day:

Using the sequence and brief in this project, write [number] final-day emails for the launch of [your offer]. The cart closes at [time and date]. Order them from morning to the final send before close, make each shorter and more urgent than the last, and keep the deadline clear in every one.

Make the deadline real and easy to see. A countdown, a clear time, a reason it ends. Buyers act on real deadlines and ignore soft ones, so tell the project to name the exact close time in every final-day send without dressing it up.

Resend the close email to people who didn’t open it. The last hours bring the most sales, and many buyers simply missed the first send. A quick resend to non-openers, with a fresh subject line, often pulls a wave of late orders on its own.

Keep the final hour simple and human.

One short note, the deadline, the link. No new pitch, no long story. People deciding in the last hour want a nudge and a clear path to buy, not another full argument they don’t have time to read.

Decide your refund and cart-close mechanics ahead of time. Know when the page comes down and what late buyers see. Sorting that before the close means the deadline holds, and you’re not making rushed calls while orders are still coming in.

When the cart closes, stop selling cleanly.

Send one short thank-you to buyers and one honest close note to the rest. Then step back. A clean ending leaves a good taste, and the people who passed this time are likelier to buy the next.

A finished launch is a stack of proven copy, and most people waste it.

They close the cart, move on, and start the next launch from a blank page. The smarter end is to harvest what worked while it’s fresh in front of you.

Before you archive the project, pull out the winners. The emails that got opens. The posts that got clicks. The subject lines that pulled. Ask the project to gather your best-performing pieces into one file you can lift into the next campaign.

Save the structure too, not just the words.

The order of the sequence, the shape of the sales page, the rhythm of launch week. Those bones work again with a new offer dropped in, so you rebuild the next launch in a fraction of the time.

Write down a few honest notes on what you’d change. A bonus that fell flat. A day that ran quiet. An email that pulled better than expected. Those notes are worth more than the copy, because they steer the choices you make next time.

Then ask the project to package the whole thing into a reusable template. You walk away with a launch kit, not just a memory. The next campaign opens with proven copy and a clear plan, instead of the blank-page dread that stalls so many launches:

This launch is done. Using everything in this project, build me a reusable launch template. Include the sales page structure, the email sequence arc, the social post plan, and any copy worth reusing. Leave brackets where I’ll swap in the next offer’s details.

Note your numbers while they’re in front of you. Opens, clicks, sales, refunds. A few figures saved now tell you what to repeat and what to drop next time. They turn a gut feeling about the launch into something you can act on.

Mark the single best asset of the launch. The email or page section that clearly outperformed the rest. Next launch, you start from that winner and build out, instead of guessing, because this launch already showed you what your buyers respond to.

Keep the template generic enough to reuse.

Strip out this offer’s specifics and leave the structure and the brackets. A template tied too tightly to one product helps once. A clean, bracketed shell helps every launch you run from here on out.

Set a reminder to plan the next launch while this one’s fresh. A week from now the lessons fade. A short note in your calendar to open the saved template keeps things going, so the next campaign starts from a plan instead of a blank week.

Now archive the launch project with a clear conscience.

The campaign is over, the room is cleared, and the parts worth keeping are saved where the next launch can use them. You finished one launch and set up a faster start for the one after it.

A launch feels big because it’s many pieces at once. Running it from one project doesn’t shrink the work, but it lines the work up. Every asset starts from the same brief, so the pieces agree without you forcing them to by hand.

That agreement is what buyers read as trust.

The page, the emails, the posts, and the affiliate copy all tell one story. Nothing contradicts. Nothing makes a buyer pause and wonder which version of the offer is the real one before they decide.

You also stop dreading the setup. The brief, the page, and the sequence sit in one place, ready, checked against each other. Launch week becomes a routine you run rather than a fire you fight from a dozen scattered chats and half-remembered details.

The page, the emails, the posts, and the affiliate copy all tell one story.

None of this asks you to launch differently. The offer, the page, the emails, the close, all the same pieces you already know. The change is where they get built, and that single change is what makes them pull in the same direction at last.

Your next launch can start from this one. Build the project, run the campaign, save what worked, and the launch after opens with proven copy already waiting. One room, one story, and a little less blank page every single time you sell something new.