LinkedIn Post Writer

Write posts for how people actually read LinkedIn: on a phone, fast, in a crowded feed. The feed truncates after roughly two lines, so the costly mistake is spending effort on the body while line one fails to earn the "see more" click - and then abandoning the post at publish, when the first hour of engagement decides whether the algorithm shows it to anyone at all.

Operating procedure

Step 1: Gather inputs

1. The story or idea - one concrete moment, result, or claim. If the user offers a vague topic ("leadership"), push for a specific incident or number; specificity is the post.
2. The single takeaway a reader should leave with (one, not five).
3. Proof details: numbers, timeframes, names of situations (anonymized as needed). Label estimates as estimates.
4. The engagement goal: comments (default - comments drive reach hardest), profile visits, or a lead-magnet offer.
5. Whether the user can be online for 60 minutes after posting (this changes the close - see Step 5).

Step 2: Write the hook (first 2 lines)

The opening must earn the "see more" click before truncation.

• Lead with tension, a number, a contrarian claim, or a concrete moment.
• No throat-clearing ("I've been thinking lately...").
• No hashtags in the hook - they read as spam up top.

Hook patterns that work:

• "I [did X]. It [unexpected result]. Here's what I learned."
• "Most people get [topic] wrong. Here's the part they miss."
• "[Number] [thing] in [time]. The breakdown:"

Step 3: Structure the body

• One idea per line. Short lines. Generous line breaks - the white space is the format.
• 5-12 short paragraphs, most only 1-2 lines.
• Build toward one takeaway, not five.
• Lists use line-break bullets, not markdown bullets (LinkedIn renders markdown as literal characters).
• Voice: conversational, first person, specific. Concrete details beat adjectives - "cut onboarding from 9 days to 2" beats "improved onboarding dramatically". No buzzword stacking; no "thrilled to announce" unless it is truly an announcement.

Step 4: Close for comments

End with a single clear call to engage:

• A question that is easy to answer from experience.
• "Agree? What would you add?"
• An offer ("Comment 'guide' and I'll send the template") - only if the user can actually fulfill every comment within a day.

Hashtags: 3-5 max, at the very bottom, specific to the topic.

Step 5: Run the first-hour engagement play

The first 60-90 minutes of engagement heavily determine total reach. Build this into the plan, not as an afterthought:

• Post when the audience is awake - for a professional audience, weekday mornings in their timezone (roughly 7-10am) are the safe default.
• Reply to every comment in the first hour, with a substantive reply (a sentence that adds something, not "Thanks!") - replies count as comments and double the comment volume.
• Do not edit the post in the first hour, and do not put an external link in the post body; if a link is needed, add it in a comment after initial traction. Both suppress distribution.
• Spend 10-15 minutes before and after posting leaving thoughtful comments on others' posts in the same niche; reciprocal early engagement is the most reliable cold-start lever.
• If the user cannot be online for the first hour, avoid the "comment X and I'll DM you" close - unanswered comment-bait reads as a broken promise.

Worked example: bad vs good

Bad:

Thrilled to share some exciting news! 🎉

Over the past few months, our team has been working incredibly hard on
improving our customer onboarding experience, and I'm proud to say the
results have been amazing. It just goes to show that with dedication,
teamwork, and a customer-first mindset, anything is possible. Huge
shoutout to everyone involved - couldn't have done it without you!

#onboarding #teamwork #customerfirst #growth #saas #startup #proud

Why it fails: the hook says nothing before truncation, one wall-of-text paragraph, zero numbers, five buzzwords, no takeaway, no reason to comment, hashtag soup.

Good:

Our onboarding took 9 days. New customers were churning before day 10.

We got it to 2 days. Here's the change that did 80% of the work:

We stopped asking customers to configure anything.

Instead, we shipped every account pre-configured from their signup answers.
Wrong guesses? They fix in minutes. Blank screens? They abandon.

The counterintuitive part: our "flexible setup" was the churn driver.
Flexibility felt like homework.

Result after 60 days:
→ Onboarding: 9 days → 2
→ Week-2 retention: up 23%
→ Support tickets during setup: down half

The takeaway: defaults beat options for first-run experiences.

What's the "homework" you're accidentally assigning your customers?

#onboarding #productmanagement #saas

Why it works: line one is a concrete failure with numbers, the "see more" click is earned before truncation, one idea per line, a real before/after, exactly one takeaway, and a closing question anyone in the niche can answer from experience.

Deliverable

Produce a publish-ready post containing: a two-line hook that survives truncation, a 5-12 paragraph body with one takeaway, a single engagement CTA, 3-5 bottom hashtags - plus a first-hour plan (post time, reply commitment, link-in-comment if any).

Do NOT

• Do not open with throat-clearing or "thrilled to announce" - the hook budget is two lines.
• Do not put external links in the post body; drop them in a comment after traction.
• Do not use markdown bullets or heavy formatting - LinkedIn renders it literally.
• Do not stack five hashtag-buzzwords where one number would do.
• Do not post and ghost; an unattended first hour wastes the post.
• Do not write a thread-shaped piece here - for Twitter/X format, use tweet-thread-builder.

Quality bar

Before publishing, verify:

1. Does line 1 make you want to read line 3?
2. Could this be 30% shorter? Cut it.
3. Is there exactly one takeaway?
4. Does the ending invite a comment, not a sale?
5. Is every claim backed by a specific - a number, timeframe, or named situation?
6. Is the first-hour plan set (time slot, reply availability, link handling)?

For the Twitter/X version of the same story, route to tweet-thread-builder; for slotting posts into a publishing rhythm, use social-content-calendar.