How to use Claude to plan a month of founder content

A Claude content workflow works when the model organizes material you already trust. It fails when you ask it to manufacture thirty opinions from a blank prompt.

Leon Abboud demonstrates the source-led version in his video, "How I use Claude to make a month of content in 30 minutes." He starts with the buyer and real conversations, then turns selected ideas into YouTube, newsletter, X, LinkedIn, and short-form assignments.^[1]

This page owns the Claude implementation question. For the wider team architecture, read the AI content system for a small team. To extract source ideas safely from meetings, use the sales-call content workflow.

1. Build a Founder Source Room

Create a Claude Project for one founder, one offer, and one audience. Anthropic describes Projects as self-contained workspaces with their own chat histories and knowledge bases. You can upload documents, provide context, and add project instructions.^[2]

The Project should know what the founder sells, who buys it, which beliefs matter in the sale, and what evidence the team may use.

1. Add a customer profile built from approved evidence, including roles, pains, desired outcomes, objections, failed alternatives, and words buyers use.
2. Add source material such as published videos, product demos, public talks, approved transcripts, research notes, and verified customer questions.
3. Add three to five pieces that sound like the founder at their best.
4. Add a short rule file for each channel.

Do not dump the company drive into Claude. More context is not automatically better. Every file should help the model understand the buyer, the founder's judgment, or the proof behind a claim.

2. Write the content contract

Project instructions should act as a contract. Define the job, allowed inputs, required output, exclusions, and rejection rules.

You plan founder-led content for [offer] and [buyer].

Use only the uploaded sources and facts in this chat.
Every idea must include its source file and timestamp or passage.

Prioritize ideas that answer a recurring buyer question, resolve an objection,
show a technical tradeoff, or teach a decision the founder has made.

Return a monthly board with:
- working title and buyer question
- one-sentence answer
- source evidence
- founder input still needed
- best primary format and distribution channels
- CTA matched to intent

Reject ideas that repeat an existing page, depend on private details,
make an unsupported claim, or could come from any founder in the category.
Do not invent quotations, outcomes, market data, or personal stories.

Anthropic's prompt engineering guidance says to establish success criteria and ways to test them before tuning prompts.^[3] Use five checks: traceability, buyer relevance, need for founder judgment, format fit, and ease of rejection.

3. Add source material safely

Remove credentials, personal data, private pricing, customer names, unreleased plans, security details, and confidential results before upload. Record who approved each source and whether it may be quoted, paraphrased, or used only to identify themes.

For Claude for Work, Anthropic says the organization's Primary Owner manages the account and associated data, including conversations and uploaded files.^[4] Review your plan, agreement, access settings, retention, and internal policy before uploading private business material.

One customer conversation can reveal a useful objection without giving you permission to publish the customer's identity. Preserve the lesson. Remove the identifying trail.

4. Generate a monthly decision board

Do not ask for thirty posts. Start with ten to fifteen ideas and require Claude to rank them against the evaluation. Remove duplicates and weak ideas before assigning dates.

Each row should include the buyer question, answer, source reference, founder input needed, primary asset, channel adaptations, funnel stage, next action, and rejection note.

A monthly plan can contain fewer than thirty primary ideas. One detailed article or video can support several useful distribution assets. Leon's demonstration shows one source idea becoming separate work for long video, newsletter, X, LinkedIn, and short form.^[1] The channel versions should share a thesis, not identical copy.

5. Make channel assignments native

A search article answers a durable question with evidence. A YouTube video can show the work and preserve spoken reasoning. An X post can make one sharp claim. A LinkedIn post can open a professional problem buyers recognize. A newsletter can carry the longer explanation to people who already know the founder.

Define length, opening style, evidence requirements, tone, CTA, and forbidden patterns for each channel. Give Claude strong examples. A channel rule file is more useful than a vague request to "make this LinkedIn friendly."

Google recommends people-first content that serves an existing audience, demonstrates first-hand expertise, and helps the reader achieve a goal.^[5] Those checks still apply when Claude helps with the plan.

6. Run the 30-minute founder review

The founder should review decisions, not polish every sentence.

1. Reject ideas that feel obvious, repeated, or unrelated to the buyer.
2. Correct the argument where Claude flattened a technical tradeoff.
3. Add the lived detail that the source cannot supply.
4. Confirm which claims need an external source.
5. Pick the primary asset and CTA.
6. Approve production or send the idea back with one clear reason.

Leon describes reviewing a finished content calendar instead of starting each day with "what should I post?"^[1] Founder time goes toward judgment. The software handles sorting and preparation.

Keep the plan editable. Product news changes, customer language gets sharper, and some ideas fail when the founder tries to explain them.

7. Measure whether the plan helps

Track ideas accepted on first review, ideas rejected for weak evidence or repetition, founder review minutes, assets that required a full rewrite, recurring buyer questions covered, and qualified conversations assisted by the content.

A board that generates thirty drafts and twenty-eight rewrites is not efficient. It moved the blank page downstream.

Connect commercial results to the founder brand ROI guide. Record which source, buyer question, and primary asset helped a prospect understand the problem or move toward a conversation.

Install the first version in seven days

1. Choose one offer and one buyer.
2. Create the customer profile from approved calls, CRM notes, and sales language.
3. Add three to five strong founder examples and a small set of source files.
4. Write the content contract and rejection rules.
5. Generate fifteen sourced ideas and score them.
6. Ask the founder to approve five and add the missing judgment.
7. Produce one primary asset, adapt it for one other channel, and record the edits.

The goal is not a calendar full of boxes. It is a short list of buyer-relevant ideas that still sound like the person who earned the expertise.