← All posts

Making AI-generated social media posts sound like you wrote them

You can usually spot an AI-generated LinkedIn post within the first sentence. “Excited to share that…” “Thrilled to announce…” “Proud to be part of…” There’s nothing wrong with any of those words. They’re just not how anyone actually talks.

The bigger problem is a line or two in. The post says something like: “We’ve been working hard to build something that makes a real difference for our customers.” That sentence is true of every company that has ever existed. It’s the kind of thing you write when you’re trying to say something meaningful but don’t want to say the specific meaningful thing — the one that would make someone stop scrolling.

AI doesn’t know what that specific thing is. It knows the category of thing you want to say. It fills in the shape.

Live demo

Try making this post sound human

A launch announcement that could be about almost anything.

Launch demo →

The fix is almost always the same: find the sentence that could be about any company and replace it with the one that is only about yours.

“Months of hard work” — doing what, specifically? What was the hardest part? Was there a week in November when the whole thing nearly fell apart?

“Listened to your feedback” — what did they say? Name the specific complaint that came up fourteen times in support. That’s the sentence.

“The best is yet to come” — if you know what’s next, say it. If you don’t, cut it. That line doesn’t add anything.

“The second paragraph says ‘make a real difference in how you work’ — replace it with the specific thing: the feature customers asked for most was bulk editing, and it’s in this release.”

“The sentence about listening to feedback — replace it with the actual feedback: the top support request for eight months was the ability to export to CSV, and 2.0 ships with that.”

What the AI skips

When you draft something with AI and ask it to write a launch post, it produces a competent draft. But “competent” here means structurally correct, tonally appropriate, and entirely interchangeable. It has no access to the internal history — the sprint that almost broke the team, the customer who kept pushing for this feature, the number that made you realize you had to build it.

Those details aren’t in the brief you gave it. They’re not anywhere in writing. They’re things you carry around and never think to type.

The gap between an AI post and a good post is almost always a gap of specifics. Not more words. Not a different structure. Just: what is the actual thing?

The specific detail is the only thing that lands

Most people reading a launch post are skimming. They’re looking for a reason to stop and read the whole thing. That reason is almost never “this company is thrilled to announce.” It’s a number, a name, a before-and-after, a thing they recognize from their own work.

“We shipped bulk editing after 312 support requests asking for it” stops people.

“We shipped a major update that improves your workflow” doesn’t.

The AI gave you the second version. It had everything it needed to write the first one — except the number. That part was always yours to add.

“The opening ‘couldn’t be more excited’ — replace it with the actual number: it took 312 support requests before we finally built bulk editing, so we built it.”

When you read it back with that sentence at the top, everything that follows feels different. The “months of hard work” has a reason now. The team has something specific they were working toward. The post is still short, still a launch announcement — but it’s about one actual thing instead of the shape of a thing.

That’s the whole edit. One sentence replaced. The post becomes yours.

Editing requires precision.
Redraft keeps the tools where the writing already is.

Open editor →