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.
Grok is a natural fit for this, because it reads X in real time and can keep your files, instructions, skills and scheduled runs together in one project.
Save this for your next content planning session.
## Before You Run a Single Prompt: Load Your Business Context
Grok 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.
### Where Grok keeps this context
Create one project on grok.com called "LinkedIn" and run every prompt in this article inside it. A Grok project has a config tab for instructions and automations, plus a file tree, so it has three natural homes for this material:
- **Project instructions.** Paste the filled-in context into the instructions field in the project config tab. Every new chat in the project starts from it, so you do not paste it again.
- **Project files.** Upload your 10-20 posts, transcripts and case studies when you create the project, Grok can build a project from several local files and folders at once. If they already live in Google Drive, mount the project from the drive instead of copying them. Ask Grok to store the reference document from the prompt as a project file, then edit it later in the right-hand panel.
- **Memory.** Grok also keeps a memory summary in Settings. Open it after the first session and correct or delete anything it took away wrongly, such as an old job title or a client you no longer name.
When a set of rules stops changing (your banned phrases, your formatting habits), move it into a skill. Grok applies skills across every conversation, and they work inside projects too. If a colleague or editor helps with the content, share the project with them, Grok's share dialog warns that sharing a project includes its conversations, so keep private client chats outside it.
## PART 1: RESEARCH + CONTENT PRODUCTION
Prompts 1-8
## 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 Grok:** run this inside the LinkedIn project so it reads the samples already in the file tree, and say which files count as your strongest writing. Grok's default register comes from X, punchy and a little spiky, so add one line to the guide that describes your LinkedIn register: calmer, more explained, one concrete detail per idea. Once you are happy with the guide, open the Skill Creator at grok.com/skills and turn it into a "my-voice" skill. From then on you can pick it from the composer in any chat, not only in this project.
**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 immediately before they sign.
> 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 Grok:** the raw material usually sits in tools Grok already connects to. Gmail, Outlook, Google Drive, OneDrive, SharePoint and Microsoft Teams are built-in connectors, and Salesforce lets Grok query records. Add the ones you use at grok.com/connectors before you start, if Grok needs one you have not linked, it asks right in the chat. Call recordings from a tool outside the catalog go in as exported transcripts. Ask for the ranked table as a project file, because prompts 5 and 9 read it later. On a Grok Business or Enterprise workspace, connectors appear only after an admin provisions them in the cloud console, so ask for Gmail, Drive and Salesforce before the first run rather than halfway through it.
**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 available X search tools 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 Grok:** this is the prompt Grok was built for. It searches X and the open web in real time, so "available X search tools" means Grok's own search, not an export you have to prepare. Three things make the output sharper:
- List accounts by @handle, and add a floor such as "only posts with at least 5 replies" so Grok looks at arguments people are actually having rather than one-off viral posts.
- Link your X account in the X connector at grok.com/connectors. The connector shows which @handle is linked, so you can see which account Grok is working with.
- Open the sources panel and click through the three ideas you plan to use. A real-time result is not automatically a reliable one, which is exactly why the prompt asks for original sources.
Then make it weekly: in the project config tab, turn this prompt into an automation that runs every Monday morning and sends the digest to your inbox. Use **Run now** once before you trust the schedule.
Two follow-ups work well in the same chat once the digest arrives. First: "Cluster these posts by idea, not keywords, and tell me which angles are already overused and which are still underexplored." Second, for the idea you pick: "Find the strongest arguments against this take and what skeptics would say in the comments, then help me sharpen it without softening it." If you already work with Meltwater, its catalog connector adds news coverage and social metrics to the same research.
**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 Grok:** keep the swipe file as a CSV or spreadsheet in the project, Grok previews CSV and Office files there, and a table pasted from a spreadsheet arrives as a real table, not a wall of text. Ask it to put the median for each author in its own column so you can check the arithmetic, and to say which rows it skipped and why. If the swipe file lives in Google Sheets, the Google Drive connector reads it in place, so the analysis always runs on the current version. For a quick sanity check on a single post, run its numbers through our [LinkedIn engagement rate calculator](/tools/linkedin/engagement-rate-calculator) and compare with what Grok reports.
**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 Grok:** upload the transcript as a file (Grok accepts uploads up to 100 MB) or point it at the copy in Google Drive, and attach your "my-voice" skill from the composer so the three drafts use it. Everything you upload or generate also shows up in the Library page, which makes it easy to find last month's webinar when an idea needs a source. No recording yet? Voice mode works inside project conversations, so you can talk the story through with Grok for ten minutes and run the prompt on that conversation. Image generation now lives inside Projects as well, so when one of the three drafts needs a cover visual, generate it from the same project composer and keep it next to the draft it belongs to.
**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 Grok:** ask for the calendar through the built-in spreadsheet skill so you get a real .xlsx with one row per post, or write it into a Notion database through the Notion connector if that is where you plan. The weekly X digest from prompt 3 is a ready source for the "timely replacement" slot. Choose days and hours with our [best time to post on LinkedIn](/tools/linkedin/best-time-to-post) guide, keep the rhythm steady week to week, and when the brief says "carousel," build the slides in the [LinkedIn carousel maker](/tools/linkedin/carousel-maker). With the Gmail & Google Calendar connector linked, ask Grok to check your calendar first, so no publishing day lands on a conference or a travel day.
**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 Grok 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 Grok:** start a fresh chat in the project for each batch, so the drafts are not shaped by a long research thread, and pick the "my-voice" skill in the composer. If an opening still sounds like a tweet, ask: "rewrite this for LinkedIn, same idea, calmer and more specific, no hype words." The first two lines decide whether anyone taps "see more," so compare Grok's alternatives with a few from our [LinkedIn hook generator](/tools/linkedin/hook-generator) before you choose. Two small rules help Grok on LinkedIn in particular: no emoji unless the brief asks for them, and never open with a greeting or a rhetorical question.
**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.
> Specificity and supporting evidence: 25.
> Strength and clarity of the argument: 20.
> Match with my voice: 20.
> Readability and formatting: 10.
> 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 Grok:** "separate" matters here. Run the review in a new chat in the project, not in the chat that wrote the drafts, and for a second opinion switch to another model in the model picker. Ask for the result through the Word skill, so you get a review document with scores, revision and open questions in one file, and pin that review chat inside the project so you can find every past verdict when you run prompt 12. Before you approve, paste the revision into our [LinkedIn post analyzer](/tools/linkedin/post-analyzer) to check length, line breaks and how the opening reads on a phone.
**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 gives you a revision you approve, and then the post goes live. From here, every other MAXXING technique is the same: in the first, golden hour, get as many reactions on the post as you can.
**Ask the people you can reach.** Colleagues, friends, relatives, clients, anyone you can actually get hold of. A personal message as soon as the post is live is the best source of reactions.
**If there is no one to ask, use a specialized service.** Only one with quality engagement and real moderation.
**Use the engagement groups we checked.** The table in the next section is the list from our other articles. These groups are good ones.
**Use aaas.market.** It is our service, built around real people. It has the highest level of moderation and the highest-quality audience, because that is where we put the most attention. It is a closed community, and you join through verification. It supports every type of engagement. Start free on aaas.market.
**Let Grok request the engagement.** Agents like Grok need MCP to get engagement. aaas.market runs an MCP server at and through it Grok can request any type of engagement for a post you have published. Publishing, comments, connection requests and messages stay with you.
To connect it in Grok:
1. Go to [grok.com/connectors](https://grok.com/connectors).
2. Click **New Connector**, then choose **Custom**.
3. Enter the server URL ` and save.
4. The server uses OAuth, so the first time you connect, Grok opens an aaas.market sign-in page. Log in with your aaas.market account and allow access, there is nothing to copy or paste.
5. Grok discovers the server's tools and offers them in chat like any other connector. After you approve and publish a post, give Grok the post URL and the type of engagement you want.
On Grok Business or Enterprise, a team admin has to provision the connector in the cloud console before it appears for you. If you work in Grok Build, xAI's terminal agent, the same server is one command: `grok mcp add --transport http aaas.market Grok Build opens the same aaas.market sign-in in your browser on first use.
## 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. Want real engagement on your own posts without searching through groups? Start free on aaas.market, and let Grok handle the request after you publish.
| 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 |
## PART 2: PIPELINE + PERFORMANCE
Prompts 9-12
## 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 Grok:** if you run Salesforce, the built-in connector lets Grok explore objects and query opportunity records directly. The same connector can also create and update records, so open the prompt with "read only, change nothing in the CRM." Any other CRM goes in as a CSV export, with names removed before upload if you prefer not to rely on the prompt alone. Keep the five briefs in the project next to the buyer-question table from prompt 2: when the same objection shows up in the two files, that brief goes to the top of next month's calendar.
**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 establish commercial intent.
> 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 commercial intent 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 Grok:** Grok has no LinkedIn connector, so this prompt works on what you paste: copy the comment thread and the messages into the chat, or drop in a screenshot. Replying quickly and usefully to every comment keeps the thread alive, so do this pass the same day the post goes up. Messages that reach you as LinkedIn notification emails can come in through the Gmail or Outlook connector instead of copy-paste: ask Grok to collect last week's notifications into one list before it groups them. You can even turn this into an email-triggered automation that drafts a brief whenever such a notification lands, with every reply still a draft for you. For replies on other people's posts in your niche, which earn you attention before your own post goes live, our [LinkedIn comment generator](/tools/linkedin/comment-generator) gives you starting points to rewrite in your own words.
**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 Grok:** export LinkedIn analytics as a spreadsheet, add your website and inquiry exports, and upload all of them to the project, pull deal stages through the Salesforce connector if you use it. Ask for the report as a spreadsheet plus a one-page summary so the numbers stay checkable, and have the monthly automation email the summary to you and anyone else who reads it. To read reach in context, estimate what a post's impressions should look like with our [LinkedIn impressions calculator](/tools/linkedin/impressions-calculator).
**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 Grok:** the change log maps onto three places. Approved style rules go into the "my-voice" skill, changes to who you write for go into the project instructions, and anything Grok has wrongly remembered about you gets fixed by selecting it in the memory summary in Settings. Keep the change log itself as a dated project file, so next month's run can see what changed and why. If a built-in skill fights your rules, for example on document formatting, write your own version, your skill takes priority over the built-in one.
**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.
Week 2: Build your research backlog. Run prompts 2-4 using a manageable set of customer conversations, market sources, and supplied LinkedIn examples.
Week 3: Produce the first batch. Use prompts 5-7 to turn approved material into a calendar and a small number of drafts.
Week 4: Strengthen the review process. Run prompt 8, publish the posts you approve, run the first hour on each post you publish, and record the changes you make.
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.
Then repeat monthly: Use prompts 11 and 12 to review results, improve the instructions, and choose the next experiment.
For any recurring job, define its inputs, destination, frequency, and owner. Test a run before relying on the schedule, and have Grok report missing access or incomplete work.
In Grok, recurring jobs are Automations. They run your instructions on a schedule or when a matching email arrives in Gmail or Outlook, can use your connectors and skills, and deliver results in the app or to your inbox. A good starting set:
- **Prompt 3, every Monday at 8:00.** The X digest lands in your inbox before you plan the week.
- **Prompt 11, on the first of the month.** Triggered by the analytics export you email to yourself, if you want it fully hands-off.
- **Prompt 12, the day after prompt 11.** It reads the report and proposes the change log.
The instruction for the Monday run can be short, because the project already holds the context:
```
Every Monday at 8:00, run prompt 3 from this project for the last seven days.
Accounts: @handle1, @handle2, @handle3. Topics: [topics].
Only include posts with at least 5 replies. Link every source.
Email me the three recommended ideas first, then the full list.
If X search or a connector fails, say so at the top instead of guessing.
```
Create them in the project config tab so their runs open inside the project, press **Run now** once, then check past runs from time to time, Grok warns you when a connector a trigger depends on needs reconnecting. Publishing stays manual. To be reminded when each planned post is due, put the calendar into our [free social media scheduler](/tools/free-tools/free-social-media-scheduler): we remind you, you publish.
You do not need 12 separate automations on day one.
Start with the job that consumes the most time and produces an output you can reliably evaluate.
## The Real Talk
Grok 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 from this workflow goes live, Grok can bring in its first engagement through the connector you added: start free on aaas.market.
Otherwise, load your context and run prompt 1. Improving the inputs will make every step after it more useful.