Cindy Zhu.
Free guides
Marketing with AI Claude

How to run a one person marketing agency with Claude

Hey, it's Cindy ๐ŸŒฑ You commented SOLO, so here is the whole system: how I set up one Claude project per client, the five prompts that cover strategy, ads, reporting, content and memory.
btw the waitlist for AI System Club is now open! If you're keen on using AI to automate your content, video editing, job search, business or build AI agents, feel free to sign up (only if you want to hehe). Ps. the waitlist gets first dibs:)
the architecture

One Claude project per client

This is the whole trick, and it is the bit that content about "AI agencies" usually skips. If you run every client out of one long chat, you spend the first ten minutes of every session re-explaining who they are, and their voice slowly drifts into generic marketing mush. A project is a self-contained workspace with its own chat history and its own knowledge base, plus custom instructions that apply to every conversation inside it (Claude help centre). Set one up per client and Claude walks into every conversation already knowing their offer, their audience, their tone and what you tried last month.

Plan honesty: projects are available on every plan, including free accounts, which can create a maximum of five. Retrieval for project knowledge is on every plan too, so as a project fills up Claude switches automatically to a retrieval mode instead of hitting a wall, which is what you want once a client has a year of history in there (how retrieval for projects works). What a paid plan actually buys you here is the project count and the usage headroom to run several clients in a day.


set it up

Build a client project from zero

  1. ๐Ÿ“ Create the project. On claude.com or in the desktop app, open Projects in the sidebar and create a new one. Name it exactly like the client, because in three months you will have eight of these and you want to find them at a glance.
  2. ๐Ÿ“ Write the custom instructions. This is the standing brief that applies to every chat in the project. Use the template in the next section, filled in with the client's real details. Do not skip it, it is doing the work that a whole onboarding doc used to do.
  3. ๐Ÿ“š Load the knowledge base. Upload the things Claude needs to sound like them: brand guidelines, three to five pieces of their best existing copy, their offer or price list, past campaign results, customer reviews or support transcripts, and your own scope of work. Project files are capped at 30MB each, and there is no limit on how many you add as long as the total content still fits what Claude can hold.
  4. ๐Ÿงน Strip anything private first. Customer names, email lists, phone numbers, invoices. You want the patterns, not the personal data, and your client agreement almost certainly has something to say about it.
  5. ๐Ÿงต Give each deliverable its own chat. Inside the project, keep one chat for strategy, one for ads, one for reporting, one for content. They all share the project knowledge, but each thread stays focused instead of turning into one 400 message scroll.
  6. ๐Ÿ” Update the knowledge on Fridays. Drop in the week's results and anything the client corrected you on. This is the step everyone skips, and it is the difference between a project that gets sharper every month and one that gets stale.
copy this

The client project instructions template

Paste this into the project's custom instructions box, filled in. It is the single highest leverage thing in this guide.

๐Ÿ—‚๏ธ client project instructions
You are the marketing strategist and copywriter for [client name], and everything you write in this project is for them unless I say otherwise.

The business: [what they sell, price points, how they make money, what a good month looks like]. The customer: [who buys, what triggers the purchase, what they are worried about, the objection that kills most deals]. The competition and the difference: [two or three competitors and the honest reason someone picks this client instead].

Voice rules: [describe the tone in five adjectives, then list the specific things to never do, for example no exclamation marks, no "unlock", no em dashes, sentence case headlines]. Match the writing samples in the project knowledge over any instinct you have about what good marketing copy sounds like.

How to work with me: I am a one person agency, so give me finished work rather than options to assemble. When you write copy, write the whole thing, not an outline. When you are missing a fact, ask me one specific question instead of inventing a statistic, a testimonial or a client name. When a request depends on numbers, use the data in project knowledge and say clearly which numbers you used.

Never claim a result the client has not actually achieved, never write a testimonial, and flag anything that would need legal or medical substantiation before it goes out.
๐ŸŒฑ Ask the client to record one five minute voice note answering "who buys this and why do they say no", then paste the transcript into project knowledge. It is worth more than any brand deck they will send you.

job one

Strategy: brief in, channel plan out

The first thing a new client wants is a plan they can nod at. Paste their brief and whatever historical data you have, and get a plan with actual reasoning attached rather than a list of platforms.

๐ŸŽฏ the channel plan
Here is the brief and the last 90 days of performance data for this client: [paste the brief, then paste or attach the data]. Build me a 90 day channel plan I could present on a call tomorrow.

Structure it as: where the money should go and why, split by channel with a rough percentage and a dollar figure against my budget of [amount]; the single message we lead with on each channel and why it fits that audience's mindset there; the three offers or angles worth testing first, in the order I should test them; and the two or three numbers we judge this by, with the current baseline from the data and a target I can defend.

Then give me the honest part: what in this plan is a genuine bet rather than a safe assumption, what would have to be true for it to work, and what you would cut first if the budget dropped by half. If the data I gave you is too thin to support a recommendation, say so and tell me exactly what to pull instead of guessing.

job two

Ads: variants in their voice, not yours

Claude is genuinely fast at this because it is a writing job, and inside the client project it already has the voice. Be honest with yourself about the split though: Claude writes the words, a design tool renders the actual creative, and you pick what ships.

โœ๏ธ the variant machine
Write me 30 ad variants for [client name] to test on [platform], for this offer: [describe the offer and the landing page it points to].

Do not give me 30 rewrites of the same idea. Build them across six angles, five variants each: the main pain point, the objection that usually kills the sale, a specific outcome with a real number from project knowledge, social proof or authority, a curiosity or contrarian hook, and a direct offer-led pitch. Label every variant with its angle so I can read the test results by angle later, not just by winner.

Each variant needs a hook line under [character limit], the body, and the call to action, all in the client's voice from the project knowledge. Keep every factual claim to something project knowledge actually supports, and mark any variant where you were tempted to add a number we do not have.

At the end, tell me which five you would put live first and why, and what each one is really testing.
โš ๏ธ Honest note: 30 lines of copy takes seconds, 30 finished creatives does not. The words come out of Claude, the images come out of a design tool, and you check every claim before anything runs. Treat "Claude writes, a tool renders, you approve" as the actual workflow rather than pretending the whole thing is automatic.

job three

Reporting: the CSV to client report pipeline

This is the one that gives you your Sunday back. Export the campaign data from your ad platform as a CSV and upload it straight into the chat. Claude.ai accepts CSV uploads, up to 20 files per chat (supported file types), so a monthly report is genuinely one upload and one prompt.

๐Ÿ“Š the monthly client report
Attached is the campaign export for [client name] covering [date range]. Write the client-facing monthly report.

Open with a three sentence summary a busy owner can read on their phone and understand: what happened, whether it was good, and what we are doing next. Then the numbers section: spend, results, cost per result and the trend versus the previous period, with the percentage change written out. Only use figures that are actually in the file. If a metric I would expect is missing, say it is missing rather than estimating it.

Then three sections: what worked and the specific reason I think it worked, what did not and what we are changing about it, and next month's plan as three concrete actions with what each one is meant to move. Write it in plain language with no jargon, because the reader is a business owner, not a media buyer. Do not use the words leverage, unlock or synergy.

Finish with a short "questions for you" list of anything you need from the client to make next month better.
๐Ÿ’ก Once the format is right, ask Claude to save it as a reusable skill so next month is one line instead of a paragraph. There is a full walkthrough in my Claude skills guide.

job four

Content: one voice memo, a week of output

Talking is faster than typing and it sounds more like a person. Record a five to ten minute voice memo where you walk through one topic properly, then get the text into Claude. On your phone, the Claude app has dictation built in, or use your phone's own voice memo transcription and paste the transcript.

๐ŸŽ™๏ธ memo to a week of content
Here is a transcript of me talking through one topic for this client: [paste the transcript]. It is messy and unstructured on purpose. Turn it into a week of content without adding any idea that is not in the recording.

Give me: three short-form video scripts of 45 to 60 seconds each, written the way people actually speak, each opening on a different hook angle from the transcript; one carousel outline of seven slides with the actual copy on each slide, not slide descriptions; two email drafts with subject lines, one teaching and one selling; and five social captions.

Pull the specific phrases I used out of the transcript and keep them, because they are the reason this will sound like the client and not like AI. Where I said something vague, quote the vague bit back to me as a question at the end instead of smoothing it over with a generic line.

Match the voice rules in the project instructions. No em dashes, sentence case, no invented statistics.

job five

Memory: the Friday close

An agency that stays good is an agency that remembers. Fifteen minutes on a Friday keeps every client project sharper than the week before, and it means a sick day does not reset your brain.

๐Ÿง  the Friday close
Read back through everything we did in this project this week. Write me a handover note I can paste into project knowledge as this week's entry.

Cover: what we shipped and where it lives, what the results say so far and what is still too early to call, every correction the client gave me and what it implies about their taste, the decisions we made and the reasoning behind them, and anything I said I would do that has not happened yet.

Then write the part that makes next week faster: what you now know about this client's voice, offers and audience that was not in the project instructions when we started. Phrase that as instructions I can paste straight into the project's custom instructions, not as observations.

Keep the whole thing under 500 words and factual. No summarising the week as "productive".

the rhythm

What the actual week looks like

๐ŸŒค๏ธ Monday: check and adjust Pull yesterday's numbers into each client project, ask for the one change worth making this week, make it. About 20 minutes per client.
๐ŸŽฌ Tuesday and Wednesday: make things The variant machine and the content prompt, batched across every client in one sitting. This is where the volume comes from.
๐Ÿ—ฃ๏ธ Thursday: client contact Calls, questions, approvals. Do this after the work exists, so you are showing rather than promising.
๐Ÿ“ฎ Friday: report and close The monthly report if it is due, then the Friday close in every project. Ninety minutes total and your Sunday is yours.

the honest bit

What this does not do

Three things worth being straight about. Claude writes the words, the strategy and the structure. It does not make the images or the video, and it does not post for you, so a design tool and your own approval sit in the middle of every workflow. It also cannot tell you a claim is untrue if the false number is sitting in project knowledge, which means the fact-check is still your job and always will be. And a client is buying your judgement, not your tooling, so keep the review step even on the weeks it feels unnecessary.

The upside is the part that actually matters: this is the difference between a solo operator who can hold two clients and one who can hold five without the work getting worse. The system is not the tools, it is one client, one project, one repeatable week.


Proof

the waitlist is now open

AI System Club is launching soon

Build AI systems with me through recorded lessons you can follow at your own pace. Join the waitlist for first access and the founding price.

btw this list gets first dibs
the moment doors open :)