How it works

Write rough notes: what happened, what you learned or want to say, and the numbers or names that make it real.
Pick the type of post (lesson, announcement, opinion, how-to, hiring or team shout-out) and a length, then click Write my post.
Read it out loud, change any line that doesn't sound like you, fill in [placeholders], and post it.

Examples

Sample results for the inputs shown, so you can see the format and quality before you try it.

Example 1: input

What's the post about? We spent 3 months building a bulk-edit feature for our scheduling app. After launch, 4% of accounts used it. We'd built it because 3 big customers asked. When we finally watched 10 customers do their weekly scheduling, most of them copy last week's schedule and change 2 or 3 shifts. We built 'copy last week' in 2 weeks and 60% of accounts use it now.

Type of post: Lesson from experience

Length: Medium (100 to 200 words)

Example 1: output

We spent 3 months building a feature that 4% of our customers used. It was bulk editing for schedules. Three of our biggest customers asked for it, so it went to the top of the roadmap. After launch, we finally did what we should have done first: we watched 10 customers do their weekly scheduling. Most of them didn't need to edit a lot of shifts at once. They copied last week's schedule and changed 2 or 3 shifts. So we built "copy last week". It took 2 weeks. 60% of accounts use it now. What I'd do differently: when a customer asks for a feature, ask them to show us the task first. The request tells you where it hurts. Watching tells you what to build. What's the most-requested feature you built that nobody used?

Example 2: input

What's the post about? Starting Monday as Head of Finance at Ridgeline Health. Leaving Oakbridge Capital after 7 years, where I built the FP&A team from scratch. Thank you to my manager Lena.

Type of post: Announcement (launch, new job, milestone)

Length: Short (under 100 words)

Example 2: output

On Monday I start as Head of Finance at Ridgeline Health. It means leaving Oakbridge Capital after 7 years. I got to build the FP&A team there from scratch, and I'm proud of the people and the work we did together. Thank you, Lena, for being the kind of manager who handed me hard problems and trusted me to solve them. On to the next one.

Example 3: input

What's the post about? Hiring a senior backend engineer for our payments team. Remote in US time zones. Go and Postgres. First project: rebuilding how we retry failed card payments. Team of 6. Apply at our careers page.

Type of post: Hiring post

Length: Medium (100 to 200 words)

Example 3: output

We're hiring a senior backend engineer for our payments team. Your first project: rebuild how we retry failed card payments. It's a problem where small decisions (when to retry, how often, when to stop) change how much money our customers actually collect. What you'd work with: - Go and Postgres - A team of 6 engineers - Remote, in US time zones You'd probably like this if you enjoy systems where correctness matters more than speed, and you like owning a problem from design to production. Apply on our careers page: [link]. Questions about the role? Send me a message.

Tips for better results

Give it your real numbers. "4% used it, then 60% used the fix" makes a post; "it didn't go well" doesn't, and the generator won't invent figures.
Put the most surprising fact in your notes first. The first line is what people see before "see more", and it gets built from your best detail.
Cut the last line if it only sums up. Posts read better when they end on the lesson or a specific question.
Post in your own voice. Change a few words to how you'd actually say them; readers notice text that sounds like everyone else's.

FAQ

Is this LinkedIn post generator free?

Yes. Enter your email once to use it (you'll also get Something Big, our free weekly AI newsletter, and you can unsubscribe anytime). There's no account and no credit card.

Will the post sound like AI wrote it?

It's written to avoid the usual tells: no "thrilled to announce", no one-word dramatic lines, no hashtag walls or engagement bait. Still, change a few phrases to your own words before posting.

Does it make up stories or numbers?

No. It uses only the facts in your notes. If the post needs a detail you didn't give, it leaves a [placeholder] for you to fill in.

How long should a LinkedIn post be?

It depends on the post. Announcements work short, under 100 words. Lessons and how-tos usually need 100 to 250 words to include the evidence. Pick the length and the generator sticks to it.

More free AI tools

Related prompts

Prefer to use ChatGPT or Claude directly? These free prompts do similar jobs.