Write a LinkedIn Post
Turn your real insight or story into a LinkedIn post with a mobile-optimized hook, saveable substance, and three labeled versions.
Write a LinkedIn post from my raw material below. What happened / what I know: [THE STORY OR INSIGHT, real specifics: numbers, tools, exact phrases, what changed] Why I'm credible on this: [YOUR ROLE OR EXPERIENCE] Goal: [START DISCUSSIONS / GET SAVES / ATTRACT CLIENTS] Format requirements: - Hook (first line): under 140 characters, that's what shows on mobile before "…see more". It must create an open loop or tension, not summarize the post. No "I'm excited to announce", no "Unpopular opinion:" unless the opinion is actually unpopular. - Body: 1,300-1,900 characters. Short paragraphs, one idea per line, generous white space. - Include something worth SAVING: a framework, checklist, or specific numbers. Saves outrank likes. - Concrete specifics beat lessons: name the tool, quote the phrase, give the number. - End with one earned takeaway. Add a question only if my goal is discussions, and make it answerable in one line. - 0-3 hashtags, at the end, or none. Write 3 versions, labeled: (1) story-led, (2) contrarian-take-led, (3) framework/list-led. Use only the material I gave you. If the story is missing a key beat, mark it [MISSING: what] instead of inventing details; a fabricated anecdote on LinkedIn is worse than no post.
How to use
The quality ceiling is your raw material, not the prompt: a real number and a named tool will outperform any generic insight. LinkedIn's feed now favors knowledge-and-advice posts from people with real expertise, so the credibility line isn't decoration; it shapes the voice.
More writing prompts
Rewrite the text below in plain language for [AUDIENCE, e.g. "patients with no medical background" / "customers reading a policy update" / "new hires on day one"]. Target reading level: [e.g. "8th grade" / "as simple as the content allows"]. How to rewrite: - Lead with what the reader must DO or what happens to them. Background comes af
Plain Language Rewrite
Rewrite dense policy, legal, medical, or technical text at a target reading level without losing a single obligation or number.
Write a comparison article for the query: [e.g. "Notion vs Obsidian" / "best Mailchimp alternatives"]. Options to compare: [LIST 2-8 OPTIONS] Who is searching this: [READER + WHAT THEY ARE TRYING TO DECIDE] My relationship to these products: [e.g. "I make one of them" / "I use two of them daily" / "none, I am researching"] Facts I can su
Comparison Article
Write an honest X vs Y or best alternatives article: real differentiators, a decision table, and a clear pick for each type of reader.
Build an FAQ page for [PRODUCT/SERVICE/TOPIC]. Real questions people ask me: """ [PASTE SUPPORT TICKETS, SALES CALL NOTES, SEARCH QUERIES, OR COMMENTS. RAW IS FINE.] """ Facts I can state as true: [PRICING, POLICIES, LIMITS, TIMELINES] Do this: 1. **Cluster** the raw questions into distinct questions people actually ask. Merge duplicat
FAQ Page From Real Questions
Turn support tickets and sales objections into an FAQ page that answers in the first sentence and is structured for AI search engines.