If you give AI a topic and ask it to write a LinkedIn post that leaves out the work that makes the post worth reading: understanding your buyers, finding an interesting angle, pulling together evidence, and knowing what you can credibly say.
These 12 prompts turn that work into a repeatable system, from researching your market to building a content calendar and identifying which posts contribute to real business conversations.
Here's what you'll build:
- A voice guide based on how you actually communicate.
- A research process that finds useful ideas before you need them.
- A draft and review workflow with specific quality standards.
- A reporting loop that helps you decide what to write next.
Claude suits this kind of system because a single Project can hold your files, instructions and memory, and the same conversation can search the web, read what you upload and hand back finished documents and spreadsheets.
Save this for your next content planning session.
## Before You Run a Single Prompt: Load Your Business Context
Claude needs more than your job title and a request to "sound human." Give it enough context to understand who you sell to, what you believe, and which claims you can support.
Paste this first:
> Use the following as the working context for my LinkedIn content. Save it in a reference document I can reuse, and tell me where it is stored.
> Business: [Company name, website, product or service, and typical sales cycle].
> Audience: [Buyer roles, company sizes, industries, and locations]. Their main problems are [problems], their common objections are [objections], and the events that make them look for help are [triggers].
> Positioning: We help [audience] achieve [outcome] through [approach]. Our strongest differences are [differences]. We are not a good fit for [disqualifiers].
> Point of view: I believe [three opinions about my industry]. I disagree with [common advice] because [reason].
> Evidence: Use these approved case studies, results, examples, and personal experiences: [sources]. Do not invent customers, revenue figures, stories, or quotations.
> Voice: Here are [10-20 posts] and [transcripts or writing samples] that sound like me. Avoid [phrases, tones, and formatting habits].
> Goals: My primary LinkedIn objective is [qualified conversations / deal support / recruiting / awareness]. My offer is [offer], and the next step I want interested readers to take is [action].
> Working rules: Use connected sources only where access is available and authorized. If a source is inaccessible, ask for an export or pasted material. Keep LinkedIn publishing, comments, connection requests, and messages with me. Draft into [review destination], distinguish evidence from inference, and flag anything that needs my input.
Keep that context current as your offer, audience, and opinions change. In Claude, replace the file in the Project whenever it changes, so new conversations never start from an old version.
### Where Claude keeps this context
A brief pasted into one chat should not depend on that chat, so give it a permanent home before prompt 1.
At a glance:
| What | Where in Claude |
|---|---|
| Business context, voice guide, research files | Project files |
| Working rules that apply to every LinkedIn chat | Project instructions |
| Personal preferences for all chats | Settings > Your Claude |
| Positioning kept in Google Docs | Project Files -> "+" -> "Drive" |
| Things Claude picks up as you work | Memory |
- **A Project for LinkedIn.** Create one Project for this whole workflow and run every prompt inside it. A Project keeps its own files, links, instructions and memory, and it works in every conversation you open there. Conversations started outside the Project will not see its files.
- **Project files for the long material.** Ask Claude to return the reference document from the prompt above as a file, then add that file (plus the voice guide from prompt 1, once you have it) to the Project's files.
- **Project instructions for the short rules.** Copy the "Working rules" paragraph into the Project's instructions so it applies to each conversation in the Project without being pasted again.
- **Google Docs that stay current.** If your positioning lives in Google Drive, add the doc to the Project from Files -> "+" -> "Drive". It syncs from Drive, so editing the doc updates the context. This option is only offered for private Projects, not shared ones.
- **Instructions for Claude.** Preferences that hold for everything you do, such as spelling or "no emojis", go in Settings > Your Claude (Settings > Account in the older layout).
- **Memory.** Claude uses what it remembers from your chats. If you also write for a client whose details should not mix in, turn "Memory" off in the "+" menu before the first message of that conversation.
## PART 1: RESEARCH + CONTENT PRODUCTION
Prompts 1-8. Run every one of them inside the LinkedIn Project, so each conversation starts with the same files and instructions.
## 1. Build Your Voice Guide
A useful voice guide should explain the choices behind your writing, including how you introduce an argument, use examples, and move between ideas.
"Conversational and authoritative" won't get you very far.
> Analyze my supplied posts and transcripts to build a practical LinkedIn voice guide.
> Identify:
> How I open posts, explain ideas, and close an argument.
> My usual vocabulary, sentence lengths, paragraph lengths, and use of lists.
> How I express disagreement, uncertainty, humor, and confidence.
> Phrases I use naturally, with verbatim examples and source references.
> Writing habits that appear in weaker examples but should not become rules.
> Create a list of phrases and patterns to avoid, including unnecessary repetition, manufactured drama, unsupported certainty, and excessive one-line paragraphs.
> Finish with three before-and-after examples showing how you would edit generic copy into my voice without changing its meaning. Keep the guide specific enough that another writer could apply it.
**In Claude:** upload your posts as one text file or paste them in, and attach transcripts as files rather than splitting them across messages. Ask for the guide as a Markdown document. When a line is off, highlight it, click "Edit with Claude" and say what to change, so the fix lands exactly where you marked it. Once the guide reads like you, add it to the Project's files. When it stops changing week to week, you can turn it into a skill: skills teach Claude how you like a job done, and Claude follows those steps whenever that job comes up. If some of your strongest posts exist only on LinkedIn, Claude in Chrome can open the pages you name and read them, pick posts you would still publish today, because weaker ones teach the wrong habits.
**Why this matters:** A good voice guide makes feedback reusable. Instead of correcting the same phrasing every week, you can improve the instructions that shape every draft.
## 2. Find the Buyer Questions Worth Answering
Your sales calls and customer conversations can reveal questions that never show up in a keyword tool. The useful ones usually involve a decision someone is struggling to make.
> Review the supplied sales calls, support conversations, customer interviews, and closed-lost notes from [period].
> Group recurring questions into:
> Problems buyers are trying to understand.
> Concerns that delay a decision.
> Alternatives they are comparing.
> Expectations that lead to disappointment.
> Questions they ask right before they decide.
> For each theme, include an anonymized quotation, source reference, number of distinct conversations where it appears, buyer role, and stage in their decision.
> Suggest two LinkedIn angles per theme: one that helps the reader diagnose the problem and one that helps them evaluate a solution. Rank the top 10 by recurrence, commercial relevance, and the strength of our available evidence.
> Separate explicit buyer statements from your interpretation.
**In Claude:** if your call notes sit in Google Drive, connect the Google Drive connector and use "+" -> "Add from Google Drive" to attach several documents to one conversation, they all have to fit in the conversation's context. Claude's answer cites which documents it used, with links back to them, which covers the "source reference" column. On Claude Desktop you can instead give Claude access to a local folder of transcripts. Ask for the ranked themes as a spreadsheet with one tab per theme. Note that Drive files are read as text only, so screenshots inside those docs are skipped. Keep recurring call notes in one Drive folder and add the newest ones each month, so the counts grow with your pipeline instead of starting from zero every time.
**Why this matters:** This gives you a content backlog tied to conversations your business is already having, with language you can recognize and evidence you can check.
## 3. Find Topics Moving From X Into Your Market
A discussion gaining attention on X can become a useful LinkedIn post, provided you explain why it matters to your buyers and contribute something beyond a rewrite.
> Using web search and accessible public sources, review the last [seven days] of discussion around [topics] and these accounts: [accounts].
> Find up to 10 developments or arguments relevant to [buyer].
> For each, return:
> The original source, author, publication date, and link.
> A neutral summary of what happened or what is being argued.
> The strongest competing interpretations.
> The practical implication for our audience.
> A possible angle supported by our experience or evidence.
> Label engagement figures as a snapshot, avoid treating popularity as proof, and check factual claims against original sources where possible.
> Recommend three ideas worth developing, explaining what I would need to contribute before each becomes a credible LinkedIn post.
**In Claude:** in the current Claude experience there is no web search toggle, Claude searches the web when the request needs it. For a wider sweep, type /deep-research or choose "+" -> "Research". Claude has no built-in X search, so list the account and thread URLs you care about, and if a page cannot be read, paste the posts into the conversation instead. Research can call your connected tools without asking each time, so switch off connector tools that write or send before you start. Keep the three chosen ideas in a Project file so prompt 6 can pick them up. When Research finishes, ask Claude to list which sources it actually opened, so you can tell a checked claim from one lifted from a search snippet.
**Why this matters:** Research gives you a starting point, your judgment gives readers a reason to follow you. A useful adaptation connects the discussion to a decision they actually face.
## 4. Analyze Posts That Outperform Their Authors' Usual Results
Comparing every post with a celebrity account's biggest hit will distort your research. Compare a post with that author's typical results first, then examine what might explain the difference.
> Analyze this supplied LinkedIn swipe file and the available performance data: [file].
> Where enough comparable data exists, compare each post's engagement with the author's median for a similar format and period. Show the calculation and flag small samples, missing metrics, and unusually recent posts.
> For the strongest outliers, identify:
> The topic and intended reader.
> The opening, argument, supporting evidence, and closing.
> The format and approximate length.
> Whether the discussion suggests genuine buyer relevance.
> Possible confounding factors, including a launch, news event, or unusually large distribution.
> Produce five reusable structural patterns, then propose an original idea for each using my own expertise. Do not copy distinctive wording or present an observed pattern as an algorithm rule.
**In Claude:** upload the swipe file as a spreadsheet or CSV with one row per post. Claude runs code on uploaded data, so it can work out each author's median, show the formula, and hand back a spreadsheet you can sort instead of a paragraph of numbers. If you only have post links, Claude in Chrome or the browser built into Claude Desktop can open each page you list and read it, you still decide which posts go into the file. To see where your own posts sit against your usual results, run them through the [LinkedIn engagement rate calculator](/tools/linkedin/engagement-rate-calculator) first. Ask for one tab with the raw rows and one with the medians, so you can check a single author's numbers without redoing the whole sheet.
**Why this matters:** You get a more useful set of hypotheses to test, while avoiding the assumption that copying a successful post's layout will reproduce its results.
## 5. Turn Recorded Expertise Into Original Posts
A transcript can contain a strong post buried inside a story, an offhand explanation, or a disagreement that deserves more attention than it received in the original conversation.
> Review this interview, podcast, webinar, or meeting transcript: [source].
> Find eight moments that could support an original LinkedIn post. Prioritize decisions, mistakes, surprising observations, practical explanations, and opinions backed by experience.
> For each moment, provide:
> The exact quotation and timestamp or source location.
> The main idea and who would benefit from it.
> Any context needed to avoid misrepresenting the speaker.
> Supporting facts already available.
> One follow-up question that would make the idea stronger.
> Select the three strongest moments and draft a post from each using my voice guide. Preserve the speaker's level of certainty, remove confidential details, and leave placeholders wherever a result or example needs confirmation.
**In Claude:** run this inside the LinkedIn Project so the voice guide is already loaded, then attach the transcript file. Timestamps only come back if your transcript has them, so export it from your recorder with timestamps switched on. If the transcript is a Google Doc your guest has commented on, Claude can read those comments and suggestions too, which helps with the "context needed" column. Ask for the three drafts in one Markdown document, with placeholders in square brackets, so you can see at a glance what still needs confirming. For a long webinar, ask Claude to go through the transcript section by section and report candidate moments for each part before choosing the three, that keeps quotations exact.
**Why this matters:** You can produce content from expertise that already exists without asking someone to manufacture a fresh opinion every time the calendar needs filling.
## 6. Build a Four-Week Content Calendar
A calendar should balance what buyers need to understand with what you have enough evidence to say. Filling every slot with a different version of your offer makes the feed repetitive.
> Build a four-week LinkedIn calendar at [three posts per week] using the approved ideas from our research.
> Include a mix of:
> Practical explanations that help buyers solve a problem.
> Opinions supported by experience or evidence.
> Customer examples we have permission to share.
> Answers to objections and decision questions.
> Occasional offer posts with a relevant next step.
> For each post, specify the reader, single objective, central argument, source material, suggested format, and intended reader action.
> Check for repeated topics, overlapping arguments, unsupported claims, and too many promotional posts. Write full briefs for week one and shorter outlines for weeks two through four.
> Leave room for one timely replacement each week rather than assuming the calendar must remain fixed.
**In Claude:** say "Google Sheet" by name if you want the calendar in Google Sheets, with the Sheets connector on, the file opens in a pane next to the chat and you can edit it while Claude does. A plain "spreadsheet" comes back as a downloadable file instead. Because the research from prompts 2-4 sits in the same Project, ask Claude to cite which file each idea came from. Pick the days with our [best time to post on LinkedIn](/tools/linkedin/best-time-to-post) guide, and when a brief calls for a carousel, lay out the slides in the [LinkedIn carousel maker](/tools/linkedin/carousel-maker). Keep the finished calendar in the Project as well, so prompt 7 can take the week-one briefs by name.
**Why this matters:** A useful calendar reduces weekly planning work while leaving room for better ideas, new evidence, and changes in the market.
## 7. Draft Posts With Something to Say
The research should determine the argument before Claude starts polishing sentences. Otherwise, you can end up with clean writing that takes several paragraphs to make an obvious point.
> Write three LinkedIn drafts from these approved briefs: [briefs].
> Use my business context and voice guide. For each draft:
> Make one clear argument for one intended reader.
> Open with a specific observation, tension, result, or question supported by the brief.
> Explain the reasoning with a concrete example.
> Use bullets where they make parallel points easier to scan.
> Vary sentence and paragraph length, allowing occasional one-line emphasis.
> End with a useful implication or natural next step.
> Aim for [180-300 words] unless the idea warrants a different length. Avoid repeated conclusions, invented personal stories, exaggerated promises, and formulaic contrasts.
> Supply two alternative openings and explain briefly how they change the emphasis. Flag missing evidence separately from the publishable copy.
**In Claude:** paste the week-one briefs from the calendar, or name the Project file they are in. Ask for the drafts as a Google Doc if a colleague or client edits with you, or as a Claude Docs living document if your team works inside Claude. For each opening line, compare Claude's two alternatives with a few from the [LinkedIn hook generator](/tools/linkedin/hook-generator), and if a draft feels flat for its length, run it through the [LinkedIn post booster](/tools/linkedin/post-booster) before you edit by hand. Ask Claude to put the missing-evidence notes under each draft rather than inside it, so the publishable copy can be pasted straight out once you fill the gaps.
**Why this matters:** Clear constraints give you drafts that are easier to judge. Your review can focus on the quality of the argument instead of repairing unnecessary filler.
## 8. Create a Separate Editorial Review
Give the reviewer a defined job: find weaknesses in the draft and explain how to fix them. A reassuring "This is strong" is not an editorial process.
> Review these LinkedIn drafts against the brief, source material, business context, and voice guide.
> Score each out of 100 using:
> Buyer relevance: 25 points.
> Specificity and supporting evidence: 25 points.
> Strength and clarity of the argument: 20 points.
> Match with my voice: 20 points.
> Readability and formatting: 10 points.
> Show the evidence behind each score. Check every factual claim, identify generic passages, and highlight repetitions, abrupt one-line fragments, and paragraphs that would work better as lists.
> Return a publishable revision, a short explanation of meaningful changes, and any unresolved questions. Treat invented evidence, exposed confidential information, or a misrepresented source as a blocking issue regardless of score.
> Keep everything in the review document for human approval.
**In Claude:** open a new conversation inside the same Project for the review, so the reviewer starts from the Project files and the drafts, not from the reasoning that produced them. Branching an earlier conversation is not available in the new Claude experience, so a fresh conversation is the clean way to separate the two roles. If the drafts sit in a Google Doc, Claude can read the comments and suggestions already in it. Before approving, paste the revision into the [LinkedIn post analyzer](/tools/linkedin/post-analyzer) and tidy line breaks with the [LinkedIn text formatter](/tools/linkedin/text-formatter). Put the rubric into the Project instructions only if every review should use it, otherwise keep it in this prompt, so drafting conversations stay focused on writing.
**Why this matters:** A review rubric makes your standards explicit. The score helps organize feedback, while the source checks and editor's judgment determine whether the post is ready.
## The first hour after you publish
Prompt 8 ends with a revision you approve. You publish it yourself, then note the publishing time next to the post in its Project file, prompt 11 needs it to compare posts at the same age. Every other MAXXING technique comes down to the same thing: in the first, golden hour after the post goes live, get as many reactions on it as you can.
**Ask the people you can reach.** Reactions are best requested from colleagues, friends, relatives, clients: anyone you can actually get hold of. Send them the link as soon as the post is live.
**If you don't have those people, use a specialized service.** Pick only one with quality engagement and real moderation.
**Use the proven groups.** The engagement groups in the table below are the ones we have already checked and listed in our other articles.
**Use aaas.market.** It is our own service:
- real people,
- the highest level of moderation and the highest-quality audience, because this is where most of the attention goes,
- a closed community that you join through verification,
- support for every type of engagement.
**Connect aaas.market to Claude.** Claude needs MCP to get engagement on a post. aaas.market runs an MCP server at and through it Claude can request any type of engagement on a post you have already published. In Claude it is added as a custom connector:
1. Open Customize > Connectors (claude.ai/customize/connectors).
2. Click "+ Add", then "Add custom connector".
3. Enter the name aaas.market and the server URL then click "Continue".
4. Keep the authentication settings Claude detects (the server uses OAuth) and click "Add".
5. The first time you connect, an aaas.market sign-in window opens. Sign in and approve the connection.
6. In a conversation, open "+" -> "Connectors" and make sure aaas.market is switched on.
Shortcut: Add aaas.market to Claude. On Team and Enterprise plans, an Owner adds it once in Organization settings > Connectors (Add -> Custom -> Web), and each member then finds the connector with the "Custom" label and clicks "Connect".
Once the post is live, paste its URL into the conversation and say which engagement you want. Publishing, comments, connection invitations and messages stay with you. If you want a really strong result from the engagement step, this is the way to do it. Start free on aaas.market.
## LinkedIn engagement groups you can join
Free communities we checked on Oct 21, 2026. Member counts are what each platform showed that day. Each group is run by its own admins, so check the pinned message before your first post.
| Group | Platform | Members | Language | Best for |
|---|---|---|---|---|
| [LinkedIn Engagement Pod & Group](https://t.me/linkedin_engagement_pod) | Telegram | 1,833 members | en | general LinkedIn engagement pod (likes + comments) |
| [LinkedIn Engagement Pod (RVision Digital)](https://t.me/linkedinengagementpod) | Telegram | 1,064 members | en | share posts for likes/comments, connections, skill endorsements |
| [Linkedin engagement pod](https://t.me/linkedinpod1) | Telegram | 488 members | en | general LinkedIn engagement pod |
| [ Social Linkedin/FB/IG Engagement Pod](https://t.me/socialengagementpod) | Telegram | 77 members | en | LinkedIn pod: react + meaningful comment on last 5 posts before shari... |
| [LinkedIn For Breakfast](https://www.skool.com/linkedin-for-breakfast) | Skool | 6,603 members | en | free LinkedIn community with engagement pods, live events |
| [Linkedin Likes and Engagement](https://t.me/linkedinlikesandengagement) | Telegram | 697 members | en | likes/engagement exchange + connections |
| [Linkedin Pod (SF founders like-for-like)](https://chat.whatsapp.com/DBOyIPrDR5IK27yzW606sF) | WhatsApp | n/a (WhatsApp hides count) | en | founders like-for-like on LinkedIn |
| [r/linkedintips](https://www.reddit.com/r/linkedintips/) | Reddit | 38,314 members | en | LinkedIn tips for promoting your brand |
| [LinkedIn Club](https://t.me/linkedinclub) | Telegram | 552 members | en | LinkedIn networking/connections community |
| [r/LinkedInGrowth](https://www.reddit.com/r/LinkedInGrowth/) | Reddit | - | en | LinkedIn growth and connections |
Want engagement on your own posts without searching through groups? Start free on aaas.market.
## PART 2: PIPELINE + PERFORMANCE
Prompts 9-12. These use sales and CRM material, so check which connectors are switched on before each conversation.
## 9. Build Content Around Stalled Deals
Some of your most useful content may answer a concern that several prospects have raised privately. The goal is to explain the issue well enough that future buyers arrive better informed.
> Review the supplied CRM records and call notes for qualified deals that stalled during [period].
> Identify recurring objections and distinguish:
> Explicit objections recorded in conversations.
> Possible explanations that remain unconfirmed.
> Operational delays that content is unlikely to solve.
> For each repeated objection, record the buyer role, deal stage, available evidence, and the question a useful LinkedIn post should answer.
> Recommend five content briefs. Each should explain the concern fairly, show where our approach is appropriate, acknowledge where it is not, and identify the proof required.
> Draft the two strongest posts without naming prospects or revealing deal details. Separately, suggest which approved existing resources a salesperson could share in a relevant conversation.
**In Claude:** look for your CRM in Customize > Connectors first, if it is not in the directory but offers a remote MCP server, add it as a custom connector the same way as aaas.market above. Without a connector, export the stalled deals to a CSV and upload it. Connected tools can change records, so for this prompt keep Claude in Manual mode, or block the CRM's write tools under Customize > Connectors, and let it read only. Ask for the five briefs as a separate file from the two drafts, so deal notes never end up in a document you share. If you work from an export, delete names and company columns before uploading, it is simpler not to give Claude what the post must never mention.
**Why this matters:** This connects marketing with the questions salespeople repeatedly need to answer. It also helps you avoid writing persuasive content about problems your buyers do not consider important.
## 10. Prepare Relevant Conversation Briefs
When someone responds to a post, the best next step depends on what they said and whether a business conversation would be welcome. Engagement alone does not show real business interest.
> Review these LinkedIn conversations I have supplied: [comments, inbound messages, or manually recorded interactions].
> Group them into:
> Questions that deserve a useful public answer.
> Conversations where sharing a resource would help.
> Explicit interest in our offer.
> General discussion with no commercial next step.
> For each relevant conversation, summarize the person's stated need, available business context, and what remains unknown.
> Draft a response that addresses their actual message before introducing anything else. Where appropriate, suggest one follow-up question or a resource we already have.
> Do not infer business interest from a like, invent familiarity, or force a meeting request into a conversation that does not support one. Keep all replies as drafts for me to review and send.
**In Claude:** copy the comments and messages into the conversation or a text file, Claude does not read your LinkedIn inbox. If a conversation moved to email, the Gmail connector lets Claude search for the thread and draft a reply there, and by default Claude asks for your approval before anything is sent. For short public replies under your post, compare Claude's draft with options from the [LinkedIn comment generator](/tools/linkedin/comment-generator), then rewrite in your own words before you post. Group what you paste by post, so the summary also shows which posts started useful conversations, prompt 11 can use that list.
**Why this matters:** Preparation can make your responses more thoughtful without turning every interaction into a sales sequence. Sometimes the right outcome is simply a useful answer.
## 11. Report on Business Results With Clear Attribution
Impressions help you understand distribution, but they cannot tell you whether the right people became interested or whether a post contributed to a deal.
> Combine my supplied LinkedIn analytics, tracked website visits, inbound inquiry records, and relevant CRM data for [period].
> Report on:
> Reach and engagement by post, topic, and format.
> Qualified inbound conversations.
> Resource sign-ups and demo requests where tracking exists.
> Opportunities with documented LinkedIn touchpoints.
> Content production time and review effort.
> Separate directly tracked conversions, self-reported discovery, and possible influence. Do not attribute an entire deal to LinkedIn because one contact engaged with a post.
> Highlight posts that attracted relevant buyers, posts that reached a broad but less relevant audience, and posts with insufficient data to judge.
> Finish with three findings, three limitations, and one recommended experiment. If possible, assess posts at consistent ages so newly published content is not unfairly compared with older posts.
**In Claude:** upload the LinkedIn analytics export and your web and CRM exports together, and ask for a spreadsheet with working formulas, so you can check every number instead of trusting a summary. Claude can also chart the data in the conversation, or turn the findings into a short deck with Claude Slides if you report to someone. Ask Claude to keep a separate tab of posts that are too new to judge. If tracking is missing for part of the period, tell Claude which weeks, so it labels those rows instead of filling them in.
**Why this matters:** Better reporting gives you a reason to repeat or change an approach. It also makes uncertainty visible instead of turning incomplete tracking into a confident revenue claim.
## 12. Turn Feedback Into a Better System
Every edited draft contains information about your standards. Capture the recurring lessons so you spend less time correcting familiar problems.
> Compare the original drafts, my edits, final published versions, and available performance data from [period].
> Identify:
> Voice corrections I have made repeatedly.
> Claims that needed more evidence.
> Ideas that became clearer after a change in framing.
> Formatting changes that improved readability.
> Topics that generated useful buyer conversations.
> Propose updates to the voice guide, research briefs, and editorial checklist. For every proposed rule, show an example, explain its purpose, and note when an exception may be appropriate.
> Keep stylistic preferences separate from performance hypotheses. Do not create a permanent rule from one successful or unsuccessful post.
> Return a short change log for my approval and suggest one controlled experiment for the next month.
**In Claude:** keep the original drafts and the versions you actually published as two files in the Project, so this comparison has something exact to read. When you approve the change log, ask for an updated voice guide file and replace the old one in the Project's files, a rule that applies to everything you write goes into the Project instructions instead. If you built a skill in prompt 1, update it with the same approved changes, so the next draft starts from them. Memory also picks up corrections you make in chat, but the Project files are what you can read and edit, so treat them as the source of truth.
**Why this matters:** This is how the workflow becomes easier to manage over time. Your corrections become usable guidance, while performance ideas remain testable rather than hardening into superstition.
## How to Use All 12 Prompts
Build the workflow in stages so you can inspect the output before adding another recurring job.
Week 1: Establish the foundation. Load your business context, run prompt 1, and check the voice guide against writing you would actually publish. In Claude, that means the Project exists and the context file is in its files.
Week 2: Build your research backlog. Run prompts 2-4 using a manageable set of customer conversations, market sources, and supplied LinkedIn examples. Connect Google Drive first if your call notes live there.
Week 3: Produce the first batch. Use prompts 5-7 to turn approved material into a calendar and a small number of drafts. Save each output as a Project file so the next prompt can read it.
Week 4: Strengthen the review process. Run prompt 8, publish the posts you approve, run the first hour on each one, and record the changes you make. Open a new conversation in the Project for every review.
Weeks 5-6: Connect content with conversations. Add prompts 9 and 10 where you have enough sales context and inbound activity to make them useful. Add a CRM connector only once you have set it to read-only.
Then repeat monthly: Use prompts 11 and 12 to review results, improve the instructions, and choose the next experiment. This monthly pass is the first job worth putting on /schedule.
For any recurring job, define its inputs, destination, frequency, and owner. Test a run before relying on the schedule, and have Claude report missing access or incomplete work.
**Automating it in Claude.** Repeating jobs can run on a schedule: type /schedule in a Cowork conversation, or open "Scheduled" in the left sidebar to create, view and change them. Scheduled runs happen in the cloud, so they keep going when your computer is off. Good candidates are a Monday sweep with prompt 3 and a first-of-the-month run of prompt 11 on the exports you dropped into Drive. Leave the permission setting on Manual for anything that touches connectors with write access. Scheduled runs prepare material, they do not post to LinkedIn. To remember when each approved post should go out, use our [free social media scheduler](/tools/free-tools/free-social-media-scheduler): we remind you, you publish, and it stays free.
You do not need 12 separate agents on day one.
Start with the job that consumes the most time and produces an output you can reliably evaluate.
## The Real Talk
Claude can help you organize research, retrieve useful evidence, prepare drafts, and learn from your edits. The quality still depends on the experience and judgment you bring into the system.
That means having a real opinion, being willing to explain it, and noticing when a polished draft says something you would never defend in a conversation.
When a post this workflow produces goes live, give it its first hour with aaas.market. Start free on aaas.market.
Otherwise, load your context and run prompt 1. Improving the inputs will make every step after it more useful.