LinkedIn

Verified against Claude · 2026-07-22

Turn a work memory into a story-driven LinkedIn post with a real lesson

Structure a raw, unpolished work anecdote into a hook-setup-turn-lesson post using LinkedIn's actual short-line, high-white-space format, while explicitly protecting the unflattering or uncertain detail that makes the story read as lived rather than as a templated failure-to-growth arc.

ClaudeChatGPTGemini5 fillable variables

The prompt

Ready to copy — highlighted parts are example details you can swap.

RAW STORY, IN YOUR OWN WORDS, UNPOLISHED
I told a client we could hit a deadline we clearly could not, because I was scared of losing the account. We missed it by two weeks and I had to call and admit it. They stayed as a client anyway, and told me later it was the call that made them trust us more, not less.

AUDIENCE
Freelancers and small agency owners who struggle to push back on clients

LESSON YOU WANT IT TO LAND ON, IF YOU HAVE ONE IN MIND
Honesty about a missed deadline builds more trust than a confident lie

LENGTH PREFERENCE
Short — under 150 words

THE DETAIL YOU'RE TEMPTED TO SAND OFF
The part where I nearly didn't make the call at all and drafted an excuse email first

WHY THE BEAT ORDER MATTERS HERE
A story post that gives away its point in the first two lines gets skimmed and scrolled past — the entire value of a personal-story format is a delayed payoff that keeps a reader reading past the point they'd normally bail, which is also exactly what LinkedIn's feed ranking rewards through dwell time. Withhold the lesson until it has been earned by the setup and the turn; do not state it early even if doing so feels clearer while drafting.

BUILD THE POST IN THIS ORDER
1. HOOK (1 line) — the moment of tension or the outcome itself, never "Let me tell you a story about..." or any variant that announces a story is coming instead of just starting it.
2. SETUP (2-4 short lines) — only the context required to understand the stakes: what you were trying to do, what you believed would happen, who else was involved if relevant. Cut anything that doesn't change how the turn lands.
3. TURN (2-4 short lines) — what actually happened, including one specific, slightly uncomfortable detail from The part where I nearly didn't make the call at all and drafted an excuse email first that most people would be tempted to smooth over. That detail is what makes this read as true instead of as a constructed inspirational arc.
4. LESSON (2-3 lines) — the takeaway stated plainly and generalized to something the reader can actually use in their own situation, not a moral handed down from a position of having already figured it out.
5. SOFT CLOSE (1 line) — a genuine question or observation that invites a real comment, not a command ("Comment below if...") and not a rhetorical question nobody would actually answer.

FORMATTING
Keep paragraphs to one or two sentences with a line break between them — the way people actually write on LinkedIn's feed, not dense paragraphs that read like an essay. Avoid starting more than one line in a row with "I" — vary the sentence openings so the rhythm doesn't flatten into a list of things that happened to you.

WHAT NOT TO DO
Do not sand off the specific, slightly embarrassing, or uncertain detail from The part where I nearly didn't make the call at all and drafted an excuse email first — polishing it away is what turns a true story into a generic "I failed, then I learned, then I grew" template readers have become numb to. Do not add a detail, quote, or number that wasn't in I told a client we could hit a deadline we clearly could not, because I was scared of losing the account. We missed it by two weeks and I had to call and admit it. They stayed as a client anyway, and told me later it was the call that made them trust us more, not less. to make the story land harder; if the story genuinely needs a stronger detail to work, say so honestly instead of inventing one.

OUTPUT
The finished post, formatted with line breaks as it would actually appear on LinkedIn, followed by one line noting whether The part where I nearly didn't make the call at all and drafted an excuse email first made it into the final draft and where — if it got cut anyway, say why, and whether the post still works honestly without it.

Customize

Optional — swap in your own details for the highlighted parts above.

Why this works

Withholding the lesson until the turn has landed exploits the same dwell-time mechanic that makes any hook work, but for the whole post instead of just the first line: LinkedIn's feed ranking weights time spent actually reading a post, and a story that gives away its point in line two gives a reader permission to stop reading immediately, while one that only resolves at the lesson beat keeps them reading through the setup and turn to get there. Explicitly protecting the detail named in {{what_you_almost_cut}} targets the actual difference between a story that reads as lived experience and the templated "I failed, then I learned, then I grew" format LinkedIn readers have become measurably fatigued by. The instinct to sand off an unflattering or uncertain detail during editing is completely understandable, but it is also specifically what turns a real memory into an inspirational-quote shape indistinguishable from thousands of others, so naming that detail as a required input rather than trusting it to survive editing is what keeps it in the final draft. The instruction never to invent a stronger detail or number than what appears in {{raw_story}} matters because a fabricated specific is more damaging than a vague true one if it is ever checked — a plausible-sounding "we lost the account" detail that did not happen is discoverable and destroys trust in every other claim in the post the moment it is caught, whereas a true story with a genuinely soft or uncertain ending is still more credible than a punched-up fake one. The formatting rule about line breaks and varied sentence openings is not cosmetic. LinkedIn's feed renders text at a width where dense paragraphs visually read as a wall of text and get skipped before a reader even starts reading the words, while short lines with white space between them signal "this is quick to read" before the content itself is evaluated at all — a real first-impression filter that operates before writing quality has a chance to matter.

What you get back

I told a client we'd hit a deadline I already knew we'd miss. Not because I was optimistic. Because I was scared of losing the account. I actually drafted an excuse email first — something vague about "unforeseen delays" — and sat on it for a day before deleting it and picking up the phone instead. Two weeks later, I made the call I'd been avoiding: we're late, here's why, here's the new date. They stayed. Not despite that call — because of it. They told me later it was the first time a vendor had been straight with them about bad news before it became their problem too. The lesson wasn't "communicate better." It was that the lie I was protecting was smaller than the trust the truth would cost me — I just couldn't see that until after. What's the deadline you're not admitting you'll miss right now?

Verified against

Claude Sonnet 5 · 2026-07-22

ChatGPT GPT-5.1 · 2026-07-23

Changelog

  • 2026-07-23 Initial publish for the rewritten linkedin category, verified against Claude (Sonnet 5) and ChatGPT (GPT-5.1).

Need this built into your business?

If a prompt isn't enough — Google Ads management, built and maintained for you — that's Scult's day job.

EXPLORE GOOGLE ADS MANAGEMENT
All LinkedIn prompts

Check your AI visibility

One URL in, a 0–100 score and the exact fixes out.

RUN THE CHECK

Browse all the tools

15 tools across six categories
13 of them never send your data anywhere

Free · No signup · No trial clock

SEE THE DIRECTORY