LinkedIn maxxing with Grok: 12 prompts from research to reporting

LinkedIn maxxing with Grok means keeping your business context, voice samples and research in one Grok project, then running 12 prompts that research, draft, review and measure your LinkedIn posts. Grok suits the job because it reads X in real time and holds files, instructions, skills and scheduled automations in the same place.

Hand any AI a topic and ask for a LinkedIn post, and it skips the work that makes a post worth reading: knowing your customers, finding an angle, gathering evidence, and knowing which claims you can stand behind. The 12 prompts below turn that work into a system you can repeat, from market research to a content calendar to seeing which posts lead to real business conversations.

By the end you will have:

• A voice guide built from the way you really write and talk.
• A research routine that surfaces useful ideas before the calendar needs them.
• A drafting and review process with clear quality standards.
• A reporting loop that tells you what to write next.

Bookmark this page for your next content planning session.

What context should you give Grok before the first prompt?

A job title and an instruction to "sound human" aren't enough. Grok has to know who you sell to, what you believe and which claims you can back up.

Paste this first:

Treat everything below as the standing context for my LinkedIn content. Store it as a reference document I can reuse, and tell me where you saved it. Business: [company name, website, what we sell, usual length of our sales cycle]. Audience: [customer roles, company sizes, industries, locations]. The problems they face are [problems], the objections they raise most often are [objections], and the moments that push them to look for help are [triggers]. Positioning: we help [audience] get [outcome] through [approach]. What sets us apart most: [differences]. We are the wrong choice for [disqualifiers]. Point of view: my three opinions about our industry are [opinions]. I disagree with [common advice], and here is why: [reason]. Evidence: work only from these approved case studies, results, examples and personal experiences: [sources]. Never make up customers, revenue numbers, stories or quotes. Voice: these [10-20 posts] and [transcripts or writing samples] sound like me. Stay away from [phrases, tones and formatting habits]. Goals: the main thing I want from LinkedIn 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: read connected sources only where you have authorized access. When a source can't be reached, ask me for an export or pasted text. Publishing, comments, connection requests and messages on LinkedIn stay with me. Put drafts in [review destination], keep evidence apart from inference, and flag anything that needs my input.

Update this context whenever your offer, your audience or your opinions change.

Where does Grok keep this context?

Create one project on grok.com named "LinkedIn" and run every prompt from this guide inside it. A Grok project has a config tab for instructions and automations, plus a file tree, which gives the material three natural places to live:

• Project instructions. Paste the completed context into the instructions field on the config tab. Every new chat in the project begins with it, so you never paste it twice.
• Project files. Upload your 10-20 posts, transcripts and case studies when you set up the project; Grok can build a project from several local files and folders in one go. If they already sit in Google Drive, mount the project from there and skip the copying. Ask Grok to save the reference document from the prompt as a project file, which you can edit later in the right-hand panel.
• Memory. Grok also keeps a memory summary in Settings. Open it after the first session and fix or delete anything it picked up wrongly, such as an old job title or a client you no longer mention.

Once a set of rules stops changing (your banned phrases, your formatting habits), move it into a skill. Grok applies skills in every conversation, and inside projects as well. If a colleague or editor works on the content with you, share the project with them. Grok's share dialog warns that sharing a project also shares its conversations, so keep private client chats out of it.

Part 1: research and content production (prompts 1-8)

1. How do you build a voice guide with Grok?

A voice guide earns its keep when it explains the choices behind your writing: how you introduce an argument, how you use examples, how you move from one idea to the next. A label like "conversational and authoritative" gives a writer almost nothing to work with.

Read the posts and transcripts I supplied and turn them into a practical voice guide for LinkedIn. Cover: the way I start a post, explain an idea and finish an argument; my usual vocabulary, sentence and paragraph lengths, and how often I use lists; how I show disagreement, doubt, humour and confidence; phrases that come to me naturally, quoted word for word with their source; and habits that show up in my weaker pieces and shouldn't turn into rules. Add a list of phrases and patterns to avoid, such as needless repetition, forced drama, certainty without support, and too many one-line paragraphs. End with three before-and-after edits that move generic copy into my voice without changing what it means. Make the guide specific enough for another writer to follow.

In Grok: run it inside the LinkedIn project so it reads the samples already in the file tree, and tell it which files are your strongest writing. Grok's default register comes from X, punchy and slightly spiky, so add one line to the guide that describes how you sound on LinkedIn: calmer, with more explanation and one concrete detail per idea. When the guide looks right, open the Skill Creator at grok.com/skills and save it as a "my-voice" skill. From then on you can pick it from the composer in any chat, inside or outside this project.

Why it helps: with a good voice guide, feedback gets reused. You stop correcting the same phrasing every week and improve the instructions behind every draft instead.

2. How do you find the customer questions worth answering?

Sales calls and customer conversations surface questions that no keyword tool will ever show you. The useful ones usually sit around a decision someone is finding hard to make.

Go through the sales calls, support threads, customer interviews and closed-lost notes I supplied for [period]. Sort the questions that keep coming up into five groups: problems customers are trying to make sense of; worries that hold a decision back; alternatives they weigh us against; expectations that end in disappointment; and questions they ask right before they sign. For each theme give an anonymized quote, where it came from, how many separate conversations mention it, the customer's role, and where they were in the decision. Propose two LinkedIn angles per theme, one that helps the reader name the problem and one that helps them judge a solution. Rank the ten strongest by how often they recur, how much they matter commercially and how solid our evidence is. Keep what customers said outright apart from your reading of it.

In Grok: most of this material already lives in tools Grok 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 begin; if Grok needs one you haven't linked, it asks 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 only appear after an admin provisions them in the cloud console, so request Gmail, Google Drive and Salesforce before the first run instead of halfway through it.

Why it helps: you get a backlog built on conversations your business is already having, in words you recognise, with evidence you can check.

3. How do you spot topics moving from X into your market?

A discussion picking up speed on X can become a useful LinkedIn post, as long as you explain why it matters to your customers and add something of your own on top of a rewrite.

With the X search tools and public sources you can reach, review the past [seven days] of conversation about [topics] and from these accounts: [accounts]. Pick up to 10 developments or arguments that matter to [customer]. For each one return: the original source with its author, date and link; a neutral summary of what happened or what people are arguing about; the strongest readings that compete with each other; what it changes for our audience; and an angle we could take that our experience or evidence supports. Mark any reaction counts as a snapshot, don't treat popularity as proof, and check factual claims against the original source where you can. Suggest the three ideas most worth developing, and tell me what I'd have to add before each one becomes a credible LinkedIn post.

In Grok: this is the job Grok was made for. It searches X and the open web in real time, so "the X search tools you can reach" means Grok's own search, with no export to prepare. Three things sharpen the result:

• List accounts by @handle and set a floor such as "only posts with at least 5 replies", so Grok looks at arguments people are really having and skips one-off hits.
• Link your X account in the X connector at grok.com/connectors. The connector displays the linked @handle, so you know which account Grok is reading as.
• Open the sources panel and click through the three ideas you plan to use. A real-time answer can still be a wrong one, which is exactly why the prompt asks for original sources.

Then put it on a weekly schedule: on the project config tab, turn this prompt into an automation that runs every Monday morning and emails the digest to you. Press Run now once before you rely on the schedule.

Two follow-ups work well in the same chat once the digest arrives. First: "Group these posts by idea instead of keywords, and tell me which angles are already worn out and which few people have covered." Second, for the idea you choose: "Find the strongest arguments against this take and what skeptics would write in the comments, then help me make it sharper without making it softer." If you already use Meltwater, its catalog connector adds news coverage and social metrics to the same research.

Why it helps: research hands you a starting point, and your judgment gives readers a reason to follow you. A good adaptation ties the discussion to a decision your readers really face.

4. How do you analyze posts that beat their author's usual results?

If you measure every post against a celebrity account's biggest hit, the research comes out skewed. Compare a post with its author's typical results first, and only then look at what might explain the gap.

Work through this LinkedIn swipe file and the performance data that comes with it: [file]. Where there is enough comparable data, set each post's reactions and comments against the author's median for a similar format and time period. Show the math, and flag thin samples, missing numbers and posts too new to judge. For the clearest outliers, describe: the topic and the reader it was written for; the opening, the argument, the supporting evidence and the ending; the format and rough length; whether the comments point to real customer interest; and other factors that could explain it, such as a launch, a news event or unusually wide distribution. Give me five structural patterns I can reuse, then suggest an original idea for each one based on my own experience. Don't copy distinctive wording, and don't present a pattern you noticed as a rule of the algorithm.

In Grok: keep the swipe file in the project as a CSV or a spreadsheet. Grok previews CSV and Office files there, and a table pasted from a spreadsheet arrives as a real table instead of a wall of text. Ask for each author's median in its own column so you can check the arithmetic, and ask which rows it skipped and why. If the swipe file is in Google Sheets, the Google Drive connector reads it where it is, so the analysis always runs on the latest version. For a quick check on a single post, put its numbers into our LinkedIn engagement rate calculator and compare the answer with Grok's.

Why it helps: you end up with better hypotheses to test, and you stop assuming that copying a successful post's layout will copy its results.

5. How do you turn recorded knowledge into original posts?

A transcript can hide a strong post inside a story, a throwaway explanation, or a disagreement that deserved more airtime than it got in the original conversation.

Read this interview, podcast, webinar or meeting transcript: [source]. Find eight moments that could carry an original LinkedIn post. Look first for decisions, mistakes, surprising observations, practical explanations and opinions grounded in experience. For each moment give: the exact quote with its timestamp or location in the source; the main idea and who it would help; any context needed so the speaker isn't misrepresented; facts we already have that back it up; and one follow-up question that would make the idea stronger. Choose the three best moments and draft a post from each, following my voice guide. Keep the speaker's level of certainty, strip out confidential details, and leave a placeholder anywhere a result or example still needs checking.

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 follow it. Everything you upload or generate also appears on the Library page, which makes last month's webinar easy to find when an idea needs a source. If you have no recording yet, voice mode works inside project conversations: talk the story through with Grok for ten minutes and run the prompt on that conversation. Image generation lives inside Projects too now, so when one of the drafts needs a cover visual, generate it from the same project composer and keep it beside the draft it belongs to.

Why it helps: you turn knowledge you already have into posts, and nobody has to invent a fresh opinion every time the calendar has a gap.

6. How do you build a four-week LinkedIn content calendar?

A calendar has to weigh what customers need to understand against what you have enough evidence to say. When every slot is one more version of your offer, the feed starts to repeat itself.

Plan four weeks of LinkedIn posts at [three posts per week] from the ideas we approved during research. Mix in: practical explanations that help a customer solve a problem; opinions backed by experience or evidence; customer examples we have permission to share; answers to objections and decision questions; and the occasional offer post with a fitting next step. For every post, list the reader, its one goal, the main argument, the source material, a suggested format and what the reader should do afterwards. Check for repeated topics, arguments that overlap, claims without support and too many sales posts. Write full briefs for week one and shorter outlines for weeks two to four. Keep one slot a week open for a timely swap instead of treating the calendar as fixed.

In Grok: ask for the calendar through the built-in spreadsheet skill to get a real .xlsx with one row per post, or have Grok write it into a Notion database through the Notion connector if that's where you plan. The weekly X digest from prompt 3 is a ready source for the "timely swap" slot. Pick days and hours with our best time to post on LinkedIn tool, keep the rhythm the same from week to week, and when a brief says "carousel", build the slides in the LinkedIn carousel maker. With the Gmail & Google Calendar connector linked, ask Grok to look at your calendar first so that no publishing day falls on a conference or a travel day.

Why it helps: a good calendar cuts weekly planning time and still leaves room for better ideas, new evidence and changes in the market.

7. How do you get Grok to draft posts that say something?

Research should settle the argument before Grok starts polishing sentences. Skip that step and you can end up with tidy writing that takes several paragraphs to make an obvious point.

Write three LinkedIn drafts from these approved briefs: [briefs], using my business context and voice guide. In each draft: make one clear argument for one reader; open with a specific observation, tension, result or question that the brief supports; walk through the reasoning with a concrete example; use bullets where parallel points are easier to scan that way; mix sentence and paragraph lengths, with an occasional one-line paragraph for emphasis; and close with a useful implication or a natural next step. Aim for [180-300 words] unless the idea calls for a different length. Leave out repeated endings, made-up personal stories, inflated promises and formula contrasts. Give me two other openings and say in a sentence how each one shifts the emphasis. List missing evidence separately from the copy that is ready to publish.

In Grok: open a new chat in the project for each batch so a long research thread doesn't bend the drafts, and select the "my-voice" skill in the composer. If an opening still reads like a tweet, ask: "rewrite this for LinkedIn, same idea, calmer and more specific, no hype words." The first two lines decide whether anyone clicks "see more", so compare Grok's alternative openings with a few from our LinkedIn hook generator before you pick one. Two small rules help Grok on LinkedIn: no emoji unless the brief asks for them, and never start with a greeting or a rhetorical question.

Why it helps: tight constraints produce drafts that are easier to judge. Your review can focus on how good the argument is instead of cutting filler.

8. How do you set up a separate editorial review?

Give the reviewer one defined job: find the weak spots in the draft and explain how to fix them. A comforting "This is strong" doesn't count as an editorial process.

Check these LinkedIn drafts against the brief, the source material, my business context and my voice guide. Score each one out of 100: relevance to the customer 25, specificity and evidence 25, strength and clarity of the argument 20, match with my voice 20, readability and formatting 10. Show what each score is based on. Verify every factual claim, point out generic passages, and mark repetition, abrupt one-line fragments and paragraphs that would read better as lists. Return a revision ready to publish, a short note on the changes that matter, and any open questions. Invented evidence, leaked confidential information or a misquoted source blocks the draft whatever its score. Keep everything in the review document until I approve it.

In Grok: the word "separate" matters here. Run the review in a new chat inside the project, away from the chat that wrote the drafts, and if you want a second opinion, switch to another model in the model picker. Ask for the output through the Word skill so the scores, the revision and the open questions arrive in one document, and pin that review chat in the project so every past verdict is easy to find when you run prompt 12. Before you approve a post, paste the revision into our LinkedIn post analyzer to check its length, its line breaks and how the opening looks on a phone.

Why it helps: a scoring rubric puts your standards in writing. The score keeps the feedback organised, while the source checks and the editor's judgment decide whether the post is ready.

What should you do in the first hour after publishing?

Prompt 8 ends with a revision you approve, and then the post goes live. From here every LinkedIn maxxing method comes down to the same thing: collect as many reactions as you can in the first hour.

Ask the people you can reach. Colleagues, friends, relatives, clients: anyone you can contact directly. A personal message sent the moment the post is live brings in more reactions than any other source.

Join groups where members support each other's posts. The table in the next section lists free groups from our other guides.

Use LinkedInLikes. It's our community. You paste the link to your post, choose comments or likes, and other members do the action by hand from their own LinkedIn accounts. Comments are written in each member's own words, and if someone confirms an action they didn't do, you can report it within 72 hours. It's free, and you start with 100 starter points. Get first comments on LinkedInLikes.

Grok doesn't publish or request anything on LinkedIn for you, so this step stays in your hands.

Which LinkedIn groups can you join for first reactions?

These are free communities. Member counts are the figures each platform displayed on Oct 21, 2026. Every group is run by its own admins, so read the pinned message before you post for the first time. If you'd rather skip the group search, you can add your post's link on LinkedInLikes once it's published.

Part 2: pipeline and performance (prompts 9-12)

9. How do you build content around deals that went quiet?

Some of your most useful posts may answer a worry that several prospects raised in private. The aim is to explain it well enough that future customers show up better informed.

Go through the CRM records and call notes I supplied for qualified deals that stopped moving during [period]. Find the objections that repeat and sort them into three kinds: objections stated outright in conversations; possible explanations nobody has confirmed; and operational delays that content probably can't fix. For each repeated objection, note the customer's role, the deal stage, the evidence we have, and the question a useful LinkedIn post should answer. Suggest five content briefs. Each one should state the concern fairly, show where our approach fits, admit where it doesn't, and name the proof we'd need. Draft the two strongest posts without naming prospects or exposing deal details. Separately, list approved resources we already have that a salesperson could send during a relevant conversation.

In Grok: if you use Salesforce, the built-in connector lets Grok browse objects and query opportunity records directly. The same connector can also create and update records, so start the prompt with "read only, change nothing in the CRM." Any other CRM goes in as a CSV export; remove names before uploading if you'd prefer not to rely on the prompt alone. Keep the five briefs in the project beside the customer-question table from prompt 2. When the same objection shows up in both files, that brief moves to the top of next month's calendar.

Why it helps: it links marketing to the questions salespeople keep answering, and it stops you from writing persuasive posts about problems your customers don't care about.

10. How do you prepare briefs for conversations that start on LinkedIn?

When someone responds to a post, the right next step depends on what they said and whether a business conversation would be welcome. A like or a comment on its own says nothing about intent to sign.

Read the LinkedIn conversations I've pasted: [comments, inbound messages, or interactions I recorded by hand]. Sort them into: questions that deserve a useful public answer; conversations where a resource would help; clear interest in our offer; and general discussion with no business next step. For each relevant one, sum up the need the person stated, the business context we have, and what we still don't know. Draft a reply that deals with what they actually wrote before bringing up anything else. Where it fits, suggest one follow-up question or a resource we already have. Don't read sales intent into a like, don't pretend we know each other, and don't push a meeting request into a conversation that doesn't call for one. Leave every reply as a draft for me to check 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. Quick, useful replies to every comment keep the thread going, so do this pass on the day the post goes up. Messages that arrive as LinkedIn notification emails can come in through the Gmail or Outlook connector: ask Grok to gather last week's notifications into one list before it groups them. You can even make it an email-triggered automation that drafts a brief whenever one of those notifications lands, with every reply still left as a draft for you. For comments on other people's posts in your niche, which get you noticed before your own post goes live, our LinkedIn comment generator gives you starting points to rewrite in your own words.

Why it helps: preparation makes replies more thoughtful without turning every exchange into a sales sequence. Sometimes the right result is a useful answer and nothing more.

11. How do you report on business results with honest attribution?

Impressions tell you about distribution. They can't tell you whether the right people got interested or whether a post helped close a deal.

Bring together the LinkedIn analytics, tracked website visits, inbound inquiry records and relevant CRM data I've supplied for [period]. Report on: reach, reactions and comments by post, topic and format; qualified inbound conversations; resource sign-ups and demo requests where tracking exists; opportunities with a documented LinkedIn contact point; and the time spent producing and reviewing content. Keep directly tracked conversions, self-reported discovery and possible influence apart. Don't attribute a whole deal to LinkedIn because one contact reacted to a post. Point out posts that drew relevant customers, posts that reached a broad but less relevant crowd, and posts with too little data to judge. End with three findings, three limitations and one experiment you recommend. Where you can, compare posts at the same age so that a new post isn't measured unfairly against older ones.

In Grok: export LinkedIn analytics as a spreadsheet, add your website and inquiry exports, and upload them all to the project; pull deal stages through the Salesforce connector if you have it. Ask for the report as a spreadsheet plus a one-page summary so the numbers stay checkable, and have a 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.

Why it helps: better reporting gives you a reason to repeat an approach or change it. It also keeps uncertainty visible, so patchy tracking doesn't turn into a confident revenue claim.

12. How do you turn your edits into a better system?

Every draft you edit says something about your standards. Write down the lessons that keep repeating, and you'll spend less time fixing the same problems.

Compare the first drafts, my edits, the published versions and the performance data available for [period]. Find: voice corrections I keep making; claims that needed more evidence; ideas that got clearer once the framing changed; formatting changes that made posts easier to read; and topics that started useful conversations with customers. Propose changes to the voice guide, the research briefs and the editorial checklist. For each proposed rule, give an example, explain what it's for, and note when an exception makes sense. Keep style preferences and performance hypotheses apart. Never turn a single post, good or bad, into a permanent rule. Give me a short change log to approve and one controlled experiment for next month.

In Grok: the change log goes to 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 remembers wrongly 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 clashes with your rules, such as on document formatting, write your own version: your skill takes priority over the built-in one.

Why it helps: this is how the workflow gets easier to run over time. Your corrections turn into guidance you can reuse, and ideas about performance stay testable before they harden into superstition.

How should you roll out all 12 prompts?

Add the workflow in stages, so you can inspect what each step produces before you add another recurring job.

For every recurring job, decide its inputs, where the results go, how often it runs and who owns it. Test one run before you trust the schedule, and have Grok report any missing access or unfinished work.

In Grok, recurring jobs are called Automations. They run your instructions on a schedule, or when a matching email lands in Gmail or Outlook, they can use your connectors and skills, and they deliver results in the app or by email. A sensible first set:

• Prompt 3, Mondays at 8:00. The X digest is in your inbox before you plan the week.
• Prompt 11, on the first day of each month. It can be triggered by the analytics export you email to yourself, if you want it to run hands-off.
• Prompt 12, the day after prompt 11. It reads the report and proposes the change log.

The Monday instruction can stay short, since the project already holds the context:

Each Monday at 8:00, run prompt 3 from this project over the past seven days. Accounts: @handle1, @handle2, @handle3. Topics: [topics]. Include only posts with 5 or more 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 and don't guess.

Create automations on the project config tab so their runs open inside the project, press Run now once, and look over past runs now and then. Grok warns you when a connector that a trigger depends on needs reconnecting. Publishing stays manual.

You don't need 12 separate automations on day one. Start with the job that takes the most time and gives you an output you can judge with confidence.

What can Grok do for you, and what stays your job?

Grok can organise research, pull up useful evidence, prepare drafts and learn from your edits. The quality still comes from the experience and judgment you bring into the system.

That means holding a real opinion, being willing to explain it, and catching the moment when a polished draft says something you'd never defend in a conversation.

Next step: load your context and run prompt 1, because better inputs make every later step more useful. When the first post from this workflow is live, join LinkedInLikes and add its link to get the first comments from members.

More articles

• How to build an AI content system for LinkedIn from one empty folder
• The 2027 LinkedIn marketing playbook
• LinkedIn maxxing with Claude