LinkedIn post templates by role: founder, engineer, designer, sales

How to use these

A template is a skeleton, not a script. Keep the structure, replace every bracket with something only you could write, and delete any line that doesn't earn its place. If the finished post still reads like the template, the brackets weren't specific enough.

Each role below gets one template, one filled-in example, and the trap people in that role fall into.

Founder: the decision post

Template: “We [decided X] this week. The obvious move was [Y]. We didn't do it because [specific reason]. Here's what we're watching to know if we were wrong: [metric].”

The trap: announcing outcomes without the decision. “We grew 40%” is a press release. “Here's the call we made and why” is a post people learn from.

Engineer: the bug post

Template: “[Symptom] for [duration]. Everyone blamed [usual suspect]. It was actually [real cause]. The fix was [small thing]. Lesson: [one sentence].”

The trap: too much jargon too early. Lead with the symptom anyone can picture, then go technical.

Designer: the before/after post

Template: “Old [screen] did [problem]. Users [behavior we saw]. We changed [one thing]. Result: [observed change]. What I'd do differently: [honest note].”

The trap: posting the pretty after-shot with no before and no reason. The reasoning is the valuable part; the screenshot is just proof.

Sales: the objection post

Template: “The objection I hear most: ‘[exact words].’ I used to answer with [old answer]. Now I ask [question] instead. Here's why that works: [reason].”

The trap: humble-bragging about a closed deal. Prospects read your posts too — teach them something and they'll trust the next call.

Make any template sound like you

Templates flatten voice. After you fill one in, read it out loud and fix anything you'd never say. Or paste three of your own posts into the free generator and let it match your length, line breaks, and endings.