The craft guide · last lines only

LinkedIn post endings: stop asking "Thoughts?"

Ezekiah Livingston, LinkedIn content strategist for founders
Ezekiah Livingston LinkedIn strategist and ghostwriter. I have deleted the word "Thoughts?" from more drafts than I can count. Find me on LinkedIn.

Published September 6, 2026

TL;DR

An ending does one of three jobs: state a position, name a next step, or close the loop the hook opened. Pick one and land it.

"Thoughts?" asks for a favor with no direction, so it draws "Great post!" or silence. A stated opinion gives people something to argue with, and argument is where comments live.

The last line gets its own paragraph. On a phone the eye stops on the final block, so don't bury the ending inside the one above it.

Test any ending free: the Content Audit grades the ending strong, mixed, or weak and quotes your own last line back.

The hook decides whether the post gets read. The ending decides what the reader does with it: agree, argue, save, reply, or forget you existed by the next scroll. It's the second-most-read line in any post, because an eye that made it to the bottom is an eye that already invested. And what do most founders spend that hard-won attention on? "Thoughts?". One word, one question mark, the writing equivalent of ending a job interview with "so... anything?". This guide is about the last line and nothing else. The first line has its own discipline.

Why "Thoughts?" fails

"Thoughts?" is a request for a favor with no direction. It hands the reader a blank canvas and a deadline: you build the comment, you pick the angle, you do the work, all so my number goes up. Most people politely decline by scrolling. So you get "Great post!" from your usual three supporters (hi, mom) and silence from everyone else. It also pattern-matches to engagement bait and AI filler, which readers now skip on sight, the same reflex that kills a rhetorical-question hook. And it teaches the algorithm nothing useful: a pile of one-word replies is exactly the shallow signal 360Brew has gotten good at pricing down. You're not being penalized for a word. You're being ignored for asking for a reaction instead of earning one.

The three jobs an ending can do (pick one)

State a position. End on the opinion the whole post was building toward, sharpened to one line a reader can nod at or fight. "Consistency wasn't his problem, and it probably isn't yours." A position puts something on the table. People comment on things on tables.

Name a next step. If you genuinely want an action, name exactly one: read the linked piece, reply with your own example, book the call. Vague asks ("let me know if this helps") get vague results, which is to say, none. One clear ask beats three polite ones.

Close the loop. If the hook opened a gap, the last line is where you pay the debt, cleanly, without a summary paragraph loitering in between. The reader came for the answer. Hand it over and stop typing. Yes, even if you have one more good sentence. Especially then.

Trying to do all three at once, position plus CTA plus recap, is how a post ends three times and lands zero. Choose the one this post actually needs.

The last line owns its own paragraph

This is a formatting rule with an outsized effect, and it costs you exactly one keystroke. On a phone, the eye scans down the left edge and stops on the final block of text. If your ending is glued to the end of the paragraph above it, your best line dies in a crowd, and the post trails off instead of landing. Break it out. White space on both sides turns the same sentence from an afterthought into a mic set down gently on a table. The formatting guide covers why phone-screen line breaks change everything; the ending is where that rule earns the most.

8 endings rewritten: before and after

Position endings

✕ Thoughts?✓ Volume was never the problem. Taste was. That's the part no tool fixes.A stated position gives the reader a side to take. "Thoughts?" gives them homework.
✕ Curious to hear what you all think.✓ If your last five posts could carry a competitor's name unchanged, that's the real problem.Ends on a test the reader can run on themselves, right now.
✕ Agree or disagree?✓ I'd rather post twice a week for a year than daily for a month. One of those compounds.Names the trade-off out loud, so agreement and disagreement both have somewhere to go.

Next-step endings

✕ Let me know if you found this helpful.✓ Try it on one post this week: cover the last line and ask if a stranger would know what you think.One concrete action beats fishing for a compliment. The reader can do something with it tonight.
✕ Link in comments, check it out!✓ I broke down the full framework in the first comment. Read it if hooks are where your posts die.Names who the link is for and why, so the click is qualified, not begged.
✕ DM me if interested.✓ If you're staring at a blank feed and a full calendar, reply "extract" and I'll send the one-hour system.A specific, low-friction ask outperforms the generic "DM me" every time.

Loop-close endings

✕ So yeah, that was a big lesson for me. Anyway, hope this helps someone.✓ He was right to fire us. We were writing for other marketers, not for his buyers.Pays the hook's debt in one line. "Hope this helps someone" is how a post shrugs.
✕ In conclusion, consistency and value are what matter most on LinkedIn.✓ The week we cut his posting in half, his reach doubled. That's the whole story.A concrete result closes the loop harder than a recap of the obvious.

The last-line test: read only your final line, alone, with the rest of the post covered. Would a stranger know what you actually think, or what to do next? If that line could be pasted under any post in the feed, it's filler wearing your byline. Rewrite it until it could only belong to this post.

Where the call to action goes

Not every post needs a CTA. Tacking one onto a post that was only ever meant to make a point is the LinkedIn version of ending a wedding toast with your business card. When you do want an action, match the placement to the ask. A soft ask ("what would you add?") belongs in the last line. A link belongs in the first comment, because outbound links in the body are widely observed to draw less distribution, and parking it below keeps the post clean either way. If the link is the entire point of the post, say so plainly in the body and repeat it in the comment. The rule that never changes: one ask per post. Two asks is zero asks, because a reader offered two doors takes the third one, the one marked "keep scrolling".

Test your ending before you post

Grading your own last line is hard, because you know what you meant and the reader wasn't at that meeting. So outsource it. Cover everything above the final paragraph and read the last line cold. If it lands as a position or a clear next step, ship it. If it reads as a plea for engagement, cut it, and here's the good news: your real ending is almost always already written, sitting two paragraphs up, being the strongest sentence in the post and wondering why it didn't get the job. Promote it. And if you'd rather not grade your own homework (nobody grades their own homework honestly, that's the whole point of homework), the free Content Audit scores the ending strong, mixed, or weak alongside your hook, structure, readability, and substance, quoting the exact line back at you. The walkthrough shows what each grade means.

Free · paste, don't upload

Get your endings graded without mercy

Paste your last 3 to 5 posts into the free Content Audit. Every ending comes back strong, mixed, or weak, with your own lines quoted as evidence, next to the hook, structure, readability, and substance. If you signed off with "Thoughts?", it will notice. It always notices.

Audit my posts Fix the first line too

Questions people ask

How should I end a LinkedIn post?
End on one of three things: a position (a stated opinion the reader can agree or argue with), a next step (one clear action), or a closed loop (the payoff the hook promised). Give that line its own paragraph so the eye lands on it. What you want to avoid is the reflex "Thoughts?", which asks for engagement without giving the reader anything to react to.
Why is "Thoughts?" a bad way to end a post?
Because it does the reader's job for them. "Thoughts?" is a request for a favor with no direction, so it mostly draws "Great post!" or silence. A stated position gives people something specific to agree with, add to, or push back on, and disagreement is where the real comments come from. The question ending also pattern-matches to AI and engagement-bait writing, which readers now skip on sight.
Should every LinkedIn post end with a call to action?
No. A call to action fits when you actually want the reader to do one thing: read a linked piece, reply with an example, book a call. If you tack a CTA onto a post that was only ever meant to make a point, it reads as a sales reflex. When in doubt, end on the position and let the comments come to you. One ask per post, at most.
Where should the call to action go, in the post or the comments?
Both work, and it depends on the ask. A soft ask ("what would you add?") belongs in the last line. A link belongs in the first comment, because outbound links in the body are widely observed to get less distribution, and you keep the post clean either way. If the CTA is the whole point of the post, state it plainly in the body and repeat the link below.
How do I test whether my ending works?
Read only the last line and ask whether a stranger would know what you actually think, or what to do next. If it could be pasted under any post in the feed, it is filler. You can also paste the post into the free Content Audit, which grades the ending strong, mixed, or weak alongside the hook, structure, readability, and substance, and quotes the exact line back to you.

Keep going: how to write hooks people stop for (the ending's twin), the formatting guide for why the last line needs its own paragraph, what to post in the first place, or how to audit your posts step by step.