Write a LinkedIn post in my voice from the material below. It should earn attention through a specific point of view and useful detail, not manufactured controversy. My voice samples or style notes: [VOICE GUIDANCE] Post topic and point of view: [TOPIC AND ANGLE] Facts, examples, and experience I can truthfully claim: [SOURCE MATERIAL] Target reader and what they care about: [TARGET READER] Goal and desired CTA: [POST GOAL] Boundaries or words to avoid: [CONSTRAINTS]
Ask up to 3 clarifying questions only if a required input is missing. Then write one post of 180-260 words with short, varied paragraphs suitable for LinkedIn. Use this structure: a two-line opening that creates a concrete tension, observation, or outcome; a brief setup grounded in the source material; 3-5 scannable points or a compact story; one practical takeaway the reader can apply; and a low-friction CTA appropriate to the goal. The opening must make sense without a “wait for it” device, false urgency, or unsupported metric. Use first person only for experience I supplied. After the post, provide: - Three alternative opening lines, each using a different angle: contrarian observation, practical lesson, and specific scene. - A brief “fact and tone check” listing any sentence that needs my confirmation. Do not invent clients, results, job titles, conversations, revenue, dates, or personal feelings. Do not turn the post into an article, use excessive line breaks, or include more than three hashtags. Self-check before answering: verify that the hook is supported by the body, and that every stated outcome can be traced to my source material.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [VOICE GUIDANCE] | Paste a few posts you wrote or describe your usual tone, vocabulary, and sentence style. | Plainspoken, analytical, short sentences. I use one concrete example before drawing a lesson. Avoid hype and “thought leadership.” |
| [TOPIC AND ANGLE] | State the topic and the specific lesson, opinion, or observation you want to make. | Why weekly status meetings fail when the underlying work has no named owner |
| [SOURCE MATERIAL] | Provide the true facts, examples, results, notes, or experience the post can use. | I watched a 14-person product team spend 45 minutes reporting blockers; three blockers were duplicates because ownership was unclear. We replaced the meeting with an async board and a 15-minute decision review. |
| [TARGET READER] | Describe the people you want to reach and the problem or interest they share. | Product and operations leads at growing software companies |
| [POST GOAL] | State the outcome you want, such as comments, a resource download, or a conversation. | Start thoughtful comments from managers who have changed their meeting cadence |
| [CONSTRAINTS] | List prohibited claims, sensitive details, formatting rules, or words you do not want used. | Do not name the company, claim productivity gains, or use hashtags |
How to use
- Paste your own posts or clear style notes before asking for a draft; voice cannot be inferred reliably from a job title alone.
- Give the model source material with the details that make the lesson credible, including what changed and what did not.
- Check every first-person statement and outcome against your notes before publishing.
- Follow up with: “Rewrite this for a skeptical operations leader and remove any sentence that sounds like advice without evidence.”
Variations
Founder announcement
Use when announcing a product, hire, partnership, or company milestone.
Draft a LinkedIn announcement in this founder's voice: [VOICE NOTES]. The announcement is [ANNOUNCEMENT]. Verified details are [FACTS]. The audience is [AUDIENCE], and the intended CTA is [CTA]. Write 150-220 words: lead with what changed and why it matters to the audience, give only the essential context, and end with a concrete next step. Include two alternate hooks. Do not invent traction, customer names, excitement, or future commitments. Flag any claim that needs legal, partner, or customer approval.
Case-study post
Use when you have permission to share a customer or project result.
Write a 220-word LinkedIn case-study post using these approved project details: [CASE DETAILS]. My voice is [VOICE]. The reader is [TARGET READER]. Structure it as problem, constraint, decision, implementation, and verified result. Explain one tradeoff or lesson so it does not read like an advertisement. End with a question that invites practitioners to compare approaches, not a generic sales CTA. Do not identify the client or state results beyond the supplied approval language. Add a list of facts I should recheck before publishing.
Comment reply
Use when turning a thoughtful comment into a useful, concise response.
Write three possible LinkedIn replies to this comment: [COMMENT]. My original post was about [POST CONTEXT]. My actual perspective and relevant facts are [MY NOTES]. Make each reply 45-75 words: one should agree and extend the idea, one should respectfully qualify it, and one should ask a concrete follow-up question. Match this voice: [VOICE]. Do not pretend I have experience or data not in my notes, and do not use a reply as a disguised pitch.
Tips
- Use a real operational detail, decision, or observed consequence early; broad claims about leadership or AI are rarely distinctive on their own.
- Make the CTA fit the post's trust level: ask for comparison stories after a lesson, and reserve links or offers for posts that clearly establish their relevance.
- Avoid turning a single internal experience into a universal rule; name the context or constraint that made the lesson apply.
- When a post includes a customer result, keep the approved wording, measurement period, and comparison baseline close to the number.
FAQ
What length works for LinkedIn posts?
A focused 180-260 word post is long enough to make a substantive point while remaining easy to scan. The idea and evidence matter more than reaching a fixed length.
Should I use hashtags?
Use none or a small number only if they serve a real discovery purpose. They should not replace a clear topic in the post itself.
Can I paste a competitor's post as a style example?
Use it to describe structural choices you like, but provide your own voice notes and source material. Do not ask the model to imitate a living writer closely.