Write one LinkedIn post from my perspective using the material below. Topic or experience: [TOPIC OR EXPERIENCE] My point of view: [CORE POINT] Who I want to reach: [TARGET READER] My voice samples or voice notes: [VOICE NOTES] Evidence, details, or examples I can support: [SUPPORTING DETAILS] Desired action after reading: [CALL TO ACTION]
First, identify the single reader takeaway in one sentence. Then write the post in this format: 1. An opening of one or two lines that creates genuine tension, contrast, or specificity without using a bait-and-switch question. 2. A short story, observation, or argument with concrete details from my supporting material. 3. The lesson or recommendation, stated plainly and tied to the target reader's work. 4. A restrained ending that invites the requested action or a useful discussion. Keep the body between 180 and 280 words. Use short paragraphs designed for a mobile feed. Preserve my stated level of certainty: do not turn an opinion into a fact, invent a result, add a client name, or claim I did something not in my notes. Do not use hashtags unless I explicitly include them in the voice notes. Avoid generic opening lines, inflated claims, engagement bait, and a list of unrelated tips. Before answering, run two checks: confirm every factual claim is supported by my details, and confirm the opening, body, and ending all support the same core point. After the post, provide three alternate opening lines only. Ask up to three clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [TOPIC OR EXPERIENCE] | Describe the event, idea, result, or observation the post is about. | Our customer-support team stopped measuring first-response time as its main success metric. |
| [CORE POINT] | State the one conclusion you want readers to remember. | Fast replies matter less than resolving the customer’s real problem without handoffs. |
| [TARGET READER] | Name the professional audience you want the post to reach. | Support leaders at B2B software companies with teams of 10 to 50 people. |
| [VOICE NOTES] | Paste a few writing traits or examples that show how you normally sound. | Practical, calm, first person; short sentences; no motivational language; use one specific operational example. |
| [SUPPORTING DETAILS] | List facts, numbers, anecdotes, and examples that can safely appear in the post. | After routing billing and technical questions to mixed pods, repeat contacts fell from 22% to 14% over eight weeks; QA reviews found fewer transfers. |
| [CALL TO ACTION] | State the discussion, comment, or next step you want to invite. | Ask readers which support metric their team has outgrown. |
How to use
- Paste your notes into every bracket, especially the facts you can defend.
- Keep the requested reader narrow; a post for product leaders needs different examples than one for job seekers.
- Check the draft against your voice notes and remove any claim that sounds stronger than your evidence.
- Send this follow-up: “Give me two versions: one more story-led and one more analytical. Keep all facts unchanged.”
Variations
Thought leadership
Use this when you have a point of view but no personal story to anchor it.
Write a 220-word LinkedIn thought-leadership post for [AUDIENCE] arguing that [THESIS]. Build the argument from [EVIDENCE OR OBSERVATIONS], including one concrete implication for the reader’s work. Use this voice: [VOICE NOTES]. Start with a specific assertion, not a question. End with [DISCUSSION PROMPT]. Do not invent research, customer examples, or consensus. Check that each claim is either supported by the inputs or clearly framed as my opinion. Ask up to three questions only if required inputs are missing.
Career update
Use this when announcing a new role, promotion, or professional milestone.
Draft a LinkedIn career-update post of 150 to 220 words about [CHANGE OR MILESTONE]. Thank [PEOPLE OR GROUPS] only where I explicitly name them, explain what I learned in [PRIOR EXPERIENCE], and state what I will focus on in [NEW ROLE OR NEXT STEP]. Write in this voice: [VOICE NOTES]. Include no confidential details, salary information, or claims about company plans. End with [CLOSING SENTIMENT]. Verify that the post does not overstate my title, responsibilities, or results. Ask up to three questions only if needed.
Document post
Use this when a carousel or PDF is the main asset and the caption needs to earn the click.
Write a LinkedIn caption introducing a document about [DOCUMENT TOPIC] for [TARGET READER]. The document contains [THREE KEY POINTS]. In 120 to 170 words, name the problem it solves, preview the most useful insight without giving away every slide, and tell readers what to do with the document. Use [VOICE NOTES]. End with [CALL TO ACTION]. Do not claim the document includes data, templates, or outcomes it does not include. Check that the caption and document topic match exactly. Ask up to three questions only if required inputs are missing.
Tips
- A good LinkedIn post usually has one argument; split a broad set of lessons into separate posts instead of forcing them into one caption.
- Use exact operational details such as a decision, constraint, or before-and-after metric when you can substantiate them; they carry more weight than broad claims.
- Keep line breaks purposeful: each paragraph should advance the story or argument, not simply make a sentence look dramatic.
- If a post mentions an employer, client, or project, remove confidential numbers and confirm you are allowed to share the named example.
FAQ
How long should a LinkedIn post be?
For a single idea, 180 to 280 words is often enough to provide substance without burying the point. Use the length the material needs rather than padding it.
Should I ask ChatGPT to add hashtags?
Only if hashtags are already part of your posting practice. They rarely fix a vague post and can make a voice feel borrowed.
Can AI write in my LinkedIn voice?
It can approximate patterns you provide, but you should supply actual samples or clear voice notes and make the final edit yourself.