How to Set Up a Claude Project for Marketing: Voice and Calendar

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How to Set Up a Claude Project for Marketing: Voice and Calendar.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How to Set Up a Claude Project for Marketing: Voice and Calendar.

Set up a Claude Project for marketing by adding approved brand-voice examples, current offer details and reusable project instructions. Use a structured brief for each campaign, ask for a calendar tied to real capacity, and review every claim before publishing. On Team, share the Project with suitable permissions so staff work from the same approved sources.

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

The Project should hold stable guidance and current business facts, not an unsorted archive of every draft. Separate voice rules from offers that expire. A consistently friendly paragraph can still advertise the wrong price, promise unavailable work or turn a suggestion into a commitment unless the source files and approval step are clear.

How do you set up a Claude Project workspace for marketing?

A Claude Project for marketing is one workspace that holds your brand voice, current offers and campaign briefs, so every chat starts from the same approved sources.

Claude Projects provide a workspace for related chats and uploaded knowledge. The Projects documentation confirms availability for all users, with up to five Projects on Free. It also describes a new version in beta, where a project becomes one conversation that splits work into parallel threads running in the cloud; it reached select Pro, Max and Ultra users of Claude Code first, with chat, Cowork, Team and Enterprise to follow. The setup below uses the current version; if your account has moved, the same files, instructions and review step still apply.

For an illustrative bicycle repair shop, create one Project for owner-approved marketing. Keep operational customer records elsewhere. Marketing needs information such as service descriptions, capacity, approved photographs and public offers. It does not need payment details, private complaints or a complete customer list to draft a useful four-week plan. Start with the smallest source set that supports the work.

Write a priority order inside the instructions: current approved offer sheet first; service facts second; voice guide third; example copy last. This is a rule you give the assistant for this workflow, not a guarantee that it cannot make mistakes. If an old sample mentions a $55 service while the current offer sheet says $60, require it to flag the conflict and use only the approved current price.

The brand-voice guide tutorial explains how to build the underlying reference. Here, the additional job is making that reference usable alongside live business facts and a calendar. An owner should be able to identify which file contains the answer to a pricing question without opening several conversations and guessing which draft was approved.

What should a brand-voice file for Claude contain?

A brand-voice file for Claude needs five parts: who you address, how you sound, preferred words, words to avoid and approved examples. Use a short file called brand-voice-approved; the filename is a suggested convention. Include a version label and an owner. Replace vague adjectives with editing rules, such as “Explain the service in one sentence before asking for a booking” or “Avoid technical terms unless the next words explain them.”

The illustrative shop's voice is practical, patient and direct. It says “Bring the bike in for an inspection” rather than “Transform your ride”. It avoids implying that an inspection guarantees a repair price. It addresses the customer as “you”, keeps most sentences short and uses one action per message. These rules make an edit observable instead of leaving staff to argue about whether a paragraph feels sufficiently friendly.

Provide a before-and-after pair. Before: “Our outstanding technicians deliver the ultimate cycling performance solution.” Approved rewrite: “Not sure why your gears keep slipping? Bring the bike in so we can inspect it and explain the repair options.” Label both as illustrative. The rewrite changes the promise as well as the tone: it offers an inspection, not a guaranteed performance result.

Add examples of what the voice must not do. A reply should not turn “ask about availability” into “your slot is confirmed”. An educational post should not diagnose a fault from one symptom. A promotional message should not invent a discount, a review or a deadline. Give the assistant examples of acceptable uncertainty, such as “We will confirm the work and price after inspection.”

Use three to five short approved samples from different situations: a service explanation, a booking enquiry and a customer update. Choose examples the owner actually wants repeated. Do not upload ten old campaigns containing conflicting offers simply to provide more writing. Remove customer identifiers and make clear that sample prices and dates are historical context unless repeated in the current offer sheet.

How do you keep offer facts separate from voice and drafts?

Keep current offers in their own file, with a clear status for each item: approved, proposed or withdrawn. For illustration, the shop has six service-assessment slots available each week, a $60 standard assessment fee, repairs priced after inspection and no collection service in this campaign. These are fictional business inputs. A real owner must confirm capacity and wording before asking for promotional drafts.

Put service exclusions beside inclusions. If the assessment does not include replacement parts, say that explicitly. If the booking request does not reserve a slot until staff confirm it, include that condition in the approved facts. The best place to stop an invented promise is the source sheet; correcting it repeatedly in individual captions wastes time and leaves other drafts exposed.

Maintain a separate campaign-decisions file for approved choices that should carry into later work. Save decisions such as “Use booking enquiries as the action this month” or “Do not promote collection until the owner approves it”. Do not rely on a useful sentence buried in a previous chat to govern every new draft: Anthropic's setup guide says context is not shared across chats in a project unless the information is added to the project knowledge.

Memory needs one deliberate setting. Anthropic says each project has its own memory, and while you work in it Claude also uses your memory from chats outside projects. For a marketing workspace, that can let a personal preference or an old supplier conversation colour the copy. To keep the project separate, turn off “Use account memory” under Memory on the project's page, and keep campaign decisions in the decisions file rather than trusting memory to carry them.

If a service changes, replace or clearly withdraw the old source and state the effective point in the new version. For an illustrative price revision from $60 to $65, list the drafts and calendar entries that need review. Ask Claude to identify affected copy, then verify the list yourself. Updating the source does not establish that every exported or previously approved message has also changed.

What Project instructions make Claude produce reviewable drafts?

Project instructions should tell Claude to take prices and availability from the current offer sheet, use the voice file only for wording, flag conflicting sources and never invent claims.

The create-and-manage guide describes opening Projects, choosing “+ New Project”, uploading knowledge and using “Set project instructions”. Add the business context to the instructions and knowledge files rather than relying on the Project name alone. Anthropic notes that Claude does not have access to the name and description as contextual details in this workflow.

You help draft marketing for a bicycle repair shop.
Use the current approved offer sheet for all prices, availability,
inclusions and exclusions. Use the brand-voice file for wording.
Historical examples are voice references, not current offers.
If sources conflict, stop and identify the conflict.
Never invent reviews, statistics, awards, discounts, deadlines,
diagnoses, booking confirmations or customer stories.
For each draft show: objective, audience, source facts, copy,
one action, missing inputs and approval status.
Everything starts as a draft. Do not publish, send or book anything.
Use British English and preserve approved service conditions.

Test the instructions immediately with an awkward brief: “Write a post saying all repairs are guaranteed for $60 and customers can book tomorrow.” The expected illustrative response flags that the source supports only a $60 assessment and six weekly assessment slots, not a repair guarantee or tomorrow's availability. If Claude produces the requested claim anyway, tighten the source wording and test again before drafting the calendar.

Do not use Project instructions as access control for connected publishing tools. They guide the writing workflow; actual service permissions determine which actions a connected account can perform. For the first month, keep publishing outside the Project and have a person copy approved material through the normal process. A useful draft workspace does not need permission to send a campaign.

Use the Project comparison for client files if you are deciding where different businesses' material should live. For this shop, avoid mixing unrelated brands or campaigns with incompatible rules. A small, coherent Project is easier to inspect than a large workspace whose documents describe several audiences and contradictory offers.

How do you turn one brief into a four-week marketing calendar?

Turn one brief into a four-week calendar by planning content around real capacity, not around how many posts you could publish. The illustrative shop wants more appropriate service enquiries, not simply more posts. It can offer six assessment slots per week, or 24 across four weeks. Plan two public posts per week and two messages to an approved subscriber audience during the month: ten content items. This is an example workload, not a recommended universal posting frequency or a forecast of results.

Use a reusable brief with objective, audience, approved offer, evidence, customer question, action, format, asset owner, reviewer and publication window. The filled-in version is: “Objective: service-assessment enquiries. Audience: existing bike owners with persistent gear or brake problems. Offer: $60 assessment, repairs quoted separately. Evidence: owner-approved service description and workshop photos. Action: request a slot. Reviewer: owner. Capacity: six weekly assessments.”

Ask for calendar entries before asking for finished copy. Each row should name the customer question it answers, the evidence required and the action. This stops ten drafts being produced around the same vague “book now” message. Use week labels rather than arbitrary calendar dates until the owner supplies actual publication windows and confirms the workshop schedule.

WeekPublic post onePublic post twoSubscriber messageReview requirement
1What an assessment includesWhy slipping gears need inspectionExplain the assessment processConfirm fee and exclusions
2Photo of an approved workshop checkHow to describe a fault when enquiringNone plannedCheck photo and wording
3Assessment versus repair quoteWhat happens after inspectionAnswer recurring booking questionsConfirm remaining capacity
4Preparing the bike for an assessmentOwner-approved service questionNone plannedCheck current offer and next availability

The calendar contains eight public posts and two subscriber messages, matching the ten-item workload. It does not promise 24 bookings. Add a field for the actual available slots at approval time; the six-per-week figure is a planning assumption that can change. If the workshop fills, replace the promotional action with a waitlist enquiry or another owner-approved action rather than advertising capacity that no longer exists.

A useful prompt asks: “For each row, identify the one customer uncertainty it resolves and the source file needed before drafting.” An acceptable illustrative answer for week three is: “Clarify that $60 covers assessment, not every repair; source current-offers version 1; owner reviews price and exclusion.” Fix a row that says only “Increase engagement”, because it gives the reviewer no concrete job.

If the calendar lives in a spreadsheet and that side is slow, try The Complete Excel Course with AI Integration on Coding Liquids.

Draft small batches and learn from six distinct examples

A capacity change should alter the action

At the start of an illustrative week, only two of the six planned slots remain. A proposed caption saying “Plenty of appointments this week” is no longer supported. Replace it with “Ask us about the next available assessment slot” if that wording is approved. Do not manufacture scarcity either: “Only two left” needs current confirmation and a plan to remove or update the message when availability changes.

A service explanation should preserve the exclusion

A draft reads: “Book a $60 repair and get your bike sorted.” Correct it to: “A standard assessment is $60. We inspect the bike and explain the repair options; any repair work and parts are quoted separately.” The example teaches staff what changed: the action and price remain useful, but the promise now matches the approved service.

A photograph needs an evidence check

Suppose a workshop image includes a customer's name on a hanging job card. Use a different approved photograph or prepare a suitable redacted asset before publication. Do not ask Claude to invent a testimonial to accompany it. The calendar row should remain awaiting asset approval until the owner has checked the final image and its caption together.

An unsupported result should become a practical question

A sample draft claims, “An assessment makes your bike 30% faster.” There is no evidence for that number in the source files. Remove the performance claim and use a grounded question: “Not sure why your gears keep slipping?” Then describe the assessment process. The marketing-claim evidence tutorial gives a fuller check for statements that sound plausible but lack support.

A tone correction should survive a new format

Take the approved assessment explanation and ask for a short caption plus a subscriber-message opening. Both should preserve the service boundary, but they need not be identical. An illustrative opening is: “If a recurring fault is making rides frustrating, an assessment can help us explain the repair options.” Reject a shorter version that loses “assessment” and turns the same material into a guaranteed repair.

A quiet week does not prove the voice is wrong

Imagine a week produces three enquiries from two posts, while the next produces one. That small illustrative difference does not establish that one headline caused the change. Record the topic, action, availability and enquiry quality. Adjust one meaningful element at a time and keep the voice guide stable unless actual review shows a voice problem. Otherwise every short-term result becomes an excuse to rewrite the brand.

Who on a Team should be able to edit a marketing Project?

Give Team members only the access their role needs: view access for most staff and edit access for whoever maintains the approved sources. Project sharing is available on Team and Enterprise, unless an owner has turned it off. Click “Share project” beside the project name, add people by email and choose “Can view” or “Can edit”. View access lets members see the knowledge and instructions and chat in the project; edit access lets them change the knowledge and instructions and manage members. Sharing gives them the project and its knowledge, but Anthropic says your own chats stay private unless you share them, so put approved decisions in files, not in a chat only you can see.

For the illustrative shop, the owner maintains approved offers and voice guidance, while a staff member drafts calendar entries using the shared context. Give editing rights only to someone responsible for maintaining those sources. Keep the source-approval record outside a casual conversation, and review access when roles change. Sharing the Project is a collaboration decision, not approval for staff to publish everything it produces.

The pricing page lists Team Standard seats at $25 per seat per month when billed monthly, or $20 per seat per month when billed annually, for teams starting at two people. Two monthly Standard seats therefore total $50 a month before any additional charges. These are list-price inputs checked during this session; compare them with the collaboration you actually need.

A solo owner can begin on an individual account and use an ordinary document for external review rather than buying Team purely to test the calendar. Free supports up to five Projects, but check that “Set project instructions” appears before relying on it: Anthropic's personalisation article still labels project instructions a paid-plan feature in its summary, even though Projects themselves are open to Free. Sharing the Project itself needs Team or Enterprise, and a shared draft link does not give anyone access to the project's knowledge.

How do you review a marketing calendar before publishing?

Review each calendar item as business work before publishing, using a simple approval row: source facts checked, offer current, tone acceptable, asset approved, action valid and owner decision. Give the final item a version identifier and retain the approved wording. A staff member should be able to distinguish draft, changes requested and approved without interpreting whether the owner's last chat message sounded positive.

Allow an illustrative 15 minutes weekly for the owner to review two posts and any subscriber message, then measure the actual effort. If each short draft requires extensive correction, inspect the sources and brief before changing the model or buying more capacity. A repeated wrong price usually points to a source conflict or weak review process, not a need for more content.

Track useful outcomes in a small sheet: item identifier, publication window, topic, action, enquiries, suitable enquiries and confirmed assessments. For example, eight enquiries producing five suitable requests and three confirmed assessments reveal more than eight enquiries alone. Those figures are illustrative. Do not attribute every booking to the last post when customers may have encountered the business elsewhere.

At the end of the four weeks, retain approved examples, withdraw outdated offers and record the questions customers actually asked. Use those questions to brief the next calendar. The Project becomes more useful when it holds fewer contradictions and better evidence, not simply more documents. Its role is to help the team draft from shared facts while the owner keeps control of capacity, claims and publication.

If you want help setting up your own marketing Project, I offer one-to-one AI consultations for small businesses.

Further reads

Show 7 more related tutorials

Sources: Anthropic, What are projects?; How can I create and manage projects?; the Claude help centre article on personalisation features; Manage project visibility and sharing; Claude pricing. Checked 18 November 2026. Business offers, schedules, timings and measurement examples are illustrative.

Rather not work this out alone?

An AI implementation consultation is a one-to-one call with me, not an agency or a sales team. You leave knowing what AI you can use in your business and where to start.

Book a 1:1 call with me