LinkedIn post templates

Good posts repeat shapes, not sentences. This library names the structures that keep working on LinkedIn, twenty-four of them across eight categories, each with the skeleton marked up for copying, a line on when it is the right choice, and a complete example so you can see the shape carry real weight before you trust it with yours.

The turn

Story

You removed or changed something everyone considered untouchable, and the result surprised you.

We [did the scary thing] and [the metric] went [the unexpected direction].

For [time period], [the old way] was sacred. [One line on why nobody questioned it.]

It was [the honest diagnosis].

[What you did instead, in two or three plain sentences.]

[What happened next, with the numbers you actually have.]

The lesson took me too long to learn: [the principle, one sentence].

[A question that invites the reader's version of the story.]
See it filled in

We killed our weekly status meeting and alignment went up. For two years it was sacred. Ten people, an hour, every Monday, because that is what serious teams do. It was theater. Half the room rehearsed their update instead of listening to anyone else's. Six weeks ago we replaced it with a written Friday summary. Five bullet points per person, posted in one thread, read when convenient. Decisions started referencing other teams' work again. Two duplicated projects surfaced in the first month, caught from reading, not reporting. The lesson took me too long to learn: a meeting is one expensive way to communicate, and for status it is the worst one. Which meeting on your calendar exists so nobody can say you did not communicate?

The expensive mistake

Story

You got something wrong, paid for it, and can name exactly what you changed.

[The mistake, stated plainly, with the cost.]

Here is how it happened.

[The decision that seemed reasonable at the time, and why.]

[The moment you realised, concretely: the email, the number, the call.]

[What it actually cost: money, time, trust, in real terms.]

What we changed: [the specific new rule or habit, one or two sentences].

[The transferable warning for the reader, without preaching.]
See it filled in

We shipped a pricing page that cost us around forty demos before anyone noticed. Here is how it happened. During a redesign we moved the pricing table behind a "Talk to sales" gate. It felt strategic. Every competitor with big logos did it. Three weeks later a founder replied to our outreach: "I would have signed up already, but I could not find a price, so I assumed I could not afford you." Demo requests had dropped by a third. Not because the product got worse, because we made buyers do work they refused to do. What we changed: prices went back on the page the same day, and no page ships now without one person outside the project trying to buy from it cold. If your pricing is hidden, you are not being strategic. You are being skipped.

The specific moment

Story

One concrete scene taught you something a summary never could.

[The scene, one or two lines: time, place, what happened. No context yet.]

[The context the reader now needs, briefly.]

[What you thought would happen vs what actually happened.]

[The realisation, anchored to the scene.]

[How it changed what you do, concretely.]

[One closing line that returns to the scene.]
See it filled in

A customer once shared her screen to show me a bug, and I watched her open our product from a bookmark folder named "chores". We were three months into a redesign meant to make the product delightful. I expected the call to be about the bug. It ended up being about the folder. She used us every day, got real value, and still filed us next to expense reports. That is when it landed: nobody wants to use our product. They want to be done with the problem it solves. Delight was our goal, not hers. We rewrote the roadmap around time-to-done. Session length went down, retention went up, and I have never trusted an engagement metric the same way since. I think about that folder name more than any dashboard we own.

Then vs now

Story

The distance between where you started and where you are carries the lesson.

[Year or time marker]: [the old situation, unvarnished].
[Now]: [the current situation, stated just as plainly].

The gap was not [the thing people assume].

It was [the actual lever].

[Two or three short lines on what that lever looked like in practice.]

[One honest line about what it cost or what still is not solved.]

[The takeaway for someone standing where you stood.]
See it filled in

Two years ago: 11 clients, all hourly, every January a panic. Now: 6 clients, all retainer, next quarter already booked. The gap was not working harder. I worked less this year than any year of my career. It was firing the clients that paid by the task. Task clients buy your hours and negotiate each one. Retainer clients buy an outcome and hold you to it. Same skills, completely different business. Honest part: the switch cost me four months of thin income and two relationships I still miss. If you are stuck at capacity, the answer is probably not more clients. It is fewer, structured differently.

The numbered process

How-to

You have a repeatable process that fits in five to seven concrete steps.

[The outcome the process delivers, with a number if you have one.]

Here is the exact process:

1. [Step, starting with a verb, one line of detail.]
2. [Step. Include the specific tool, time, or threshold where it matters.]
3. [Step.]
4. [Step.]
5. [Step. The one people skip; say so.]

[The one mistake that breaks the whole process.]

[Closing line: what to do this week.]
See it filled in

Our churn interviews recover about one cancelling customer in five. Not with discounts, with listening. Here is the exact process: 1. Trigger the ask the moment someone cancels, while the reason is fresh. Ours is one plain email from a founder, not a survey. 2. Offer 20 minutes, on their calendar link or ours, whichever is less friction. 3. Open with "walk me through the week you decided to leave". Never "what could we do better". 4. Shut up for the first ten minutes. The reason they give first is rarely the real one; the real one shows up around minute eight. 5. End by asking what they moved to and what it does that we did not. This is the step people skip because the answer stings. The mistake that breaks it: pitching a fix on the call. The moment you defend the product, the honesty stops. Book two of these this week. Two is enough to hear a pattern.

The pre-flight checklist

How-to

Quality in your field comes from checking the same few things every time.

[The activity] goes wrong in the same [number] ways every time.

The checklist I run before [the moment of commitment]:

[Check 1, phrased as a question you answer yes or no.]
[Check 2.]
[Check 3.]
[Check 4.]
[Check 5.]

[Which check catches the most problems, and a one-line story about it.]

Steal the list. Adjust [the one item that is specific to you].
See it filled in

Proposals lose in the same five ways every time. The checklist I run before any proposal goes out: Does the first paragraph describe their problem in their words, from the discovery call notes? Is there exactly one recommended option, with the alternatives framed around it? Can they find the price without scrolling? Does every deliverable have a date attached to it? Is there one thing in it they did not ask for but clearly need? The first check catches the most. Proposals that open with our history instead of their problem lose before page two, and rereading the call notes fixes it in ten minutes. Steal the list. Adjust the one-option rule if your work genuinely prices three ways, but be honest about whether it does.

One tactic, all the way down

How-to

One narrow technique deserves the full treatment instead of a listicle mention.

[The tactic, in one line, with the result it produced for you.]

Most people [the shallow version everyone already does].

The version that works has [number] parts:

[Part one: the setup detail nobody mentions.]

[Part two: the actual execution, specific enough to copy.]

[Part three: the follow-through where the value actually lives.]

[The honest constraint: when this does not work.]

[Closing line: the smallest version someone could try today.]
See it filled in

One saved reply earns us more replies on cold outreach than any personalisation tool we have paid for. Most people personalise the first line and pitch in the second, which reads exactly like what it is. The version that works has three parts: The setup: we only message people who posted something in the last week. Not liked, posted. That single filter removes ninety percent of the list and all of the awkwardness. The message: two sentences about their post with an actual opinion in them, then one question about how they handle the problem we solve. No link, no pitch, no calendar. The follow-through: whatever they answer, the next message is still not a pitch. We share how we handle the same thing. The demo request comes from them or it does not come. The constraint: this does not scale past about twenty conversations a week per person, and pretending otherwise is how it turns back into spam. The smallest version: find one prospect who posted today and reply with an opinion. That is the whole tactic at size one.

The sacred cow

Contrarian

A widely worshipped practice quietly fails, and you have evidence, not just attitude.

[The revered practice] is [the plain negative verdict].

Everyone says [the standard advice]. [One line on why it sounds right.]

Here is what actually happens: [the mechanism of failure, concretely].

[Your evidence: the numbers, the story, the pattern you observed.]

[The exception, stated honestly: when the practice does work.]

[What to do instead.]
See it filled in

The company blog, as most B2B companies run it, is a content graveyard with a publishing schedule. Everyone says consistency wins: two posts a week, every week. It sounds right because consistency does win in channels where anyone is watching. Here is what actually happens: posts written to hit a calendar answer no real question, rank for nothing, and get shared by nobody. The metric becomes "published on time", which no customer has ever cared about. We cut our blog from eight posts a month to two and traffic went up within a quarter. The two remaining posts each answered a question sales actually gets asked, at real depth. The exception: if you have genuine search demand mapped and writers with real expertise, volume compounds. Most teams have neither and copy the cadence anyway. Write the next post when you have something to say that a buyer would forward. That is the whole calendar.

Stop doing X

Contrarian

The best advice you can give is subtraction, and you can name what to do with the freed time.

Stop [the common activity].

Not "do it better". Stop.

[What it actually costs, in terms the reader will recognise.]

[Why people keep doing it anyway: the fear or habit underneath, named kindly.]

We stopped [time period] ago. [What happened, plainly.]

[What to do with the reclaimed time or budget instead.]

[One line acknowledging who should ignore this advice.]
See it filled in

Stop sending a monthly newsletter nobody asked you to send. Not "improve the open rate". Stop. Every month it eats two working days, interrupts a designer, and goes out to a list where half the addresses came from a lead magnet in 2023. The reply rate is zero. You know it is zero. Teams keep it because stopping feels like admitting the list is dead, and because "we have a newsletter" sounds like marketing is happening. We stopped eight months ago. Nobody unsubscribed from the silence. Nobody noticed. That non-reaction was the most useful data the newsletter ever produced. The two days go into one genuinely useful piece per month, sent only to people who engaged in the last quarter. Smaller list, actual replies. If your newsletter gets real replies from real buyers, ignore all of this. You are the exception and you know it.

What the polite silence costs

Contrarian

An uncomfortable truth in your industry goes unsaid because saying it is awkward.

Nobody in [your field] wants to say this out loud, so here it is:

[The uncomfortable truth, one sentence.]

We all pretend otherwise because [the social reason, honestly].

[Two or three lines of evidence the reader will recognise from their own experience.]

[What the silence costs, and who pays it.]

[The more honest alternative, even though it is harder.]
See it filled in

Nobody in consulting wants to say this out loud, so here it is: Most discovery workshops produce a deck the client could have written themselves, priced as if it were research. We all pretend otherwise because the workshop is the easiest thing to sell. It has a fixed price, a fixed length, and it postpones the scary part where we commit to an outcome. You have seen the pattern: two days of sticky notes, a synthesis full of things the client's own team said, three "strategic pillars" that fit any company in the industry. The cost lands on the client's budget first, but eventually on us: buyers who have been through two of these stop trusting the whole category, and the consultants doing real work inherit that suspicion. The harder alternative is charging for the first real deliverable instead, and letting discovery be the unglamorous week of homework it actually is. It sells worse. It renews better.

The numbers teardown

Proof

You can open the books on one decision and let the numbers argue.

[The headline number or comparison, no context yet.]

Context: [what was changed and when, two lines].

The numbers:
- [Before metric]: [value]
- [After metric]: [value]
- [The cost of the change]: [value]
- [The number that surprised you]: [value]

[What the numbers hide or overstate, honestly.]

[The decision you would make differently with hindsight.]

[The one number the reader should go check in their own business.]
See it filled in

We spent 6,300 dollars rewriting onboarding emails and it outperformed the 40,000 we spent on ads the same quarter. Context: in March we rewrote our 11-email onboarding sequence down to 4, each answering one question new users actually ask. The ads ran as usual. The numbers: - Activation, before: 31% of signups reached the first key action - Activation, after: 40% - Cost: one contractor, 6,300 dollars, three weeks - The surprise: reply rate to email two went from zero to about 4%, and those replies became our best sales conversations What the numbers hide: activation was already trending up about a point a quarter, so the emails do not own the whole jump. With hindsight I would have rewritten emails first and paused the ads entirely for the quarter to get a clean read. The number to check in your own business: what percentage of your onboarding emails could a new user actually act on? Count them. Ours was 3 of 11.

The anonymised client walkthrough

Proof

A client result proves your method and you can share the mechanics without naming names.

A [client description, no name] came to us with [the problem, in their words].

[What they had already tried, respectfully.]

What we actually did, in order:
[Move one, and why that first.]
[Move two.]
[Move three.]

Result: [the outcome, with the timeframe and the honest caveats].

[The part of the result you cannot take credit for.]

[The generalisable principle, one sentence.]
See it filled in

A 30-person logistics SaaS came to us with, in their words, "a sales team that demos brilliantly and closes nothing". They had already tried the usual: new deck, more discovery training, a CRM migration that ate a quarter. What we actually did, in order: Sat in on ten recorded demos before touching anything, because the diagnosis matters more than the cure. Found the pattern: every demo covered eleven features; every closed-won deal from history had hinged on the same two. Rebuilt the demo around those two, with the other nine available on request and never volunteered. Result: close rate on demos went from 12% to 19% inside two quarters. Not 3x, not a miracle, a fifth more revenue from the same pipeline. The part we cannot take credit for: their head of sales enforced the new format on every rep, including the top performer who hated it. Without that, the deck change changes nothing. The principle: buyers do not buy the product that does the most. They buy the one whose demo matched their problem.

The honest experiment

Proof

You tested something properly and are willing to report the result either way.

For [time period] we tested [the thing]. Here is what happened, including the part that did not work.

The setup: [what you changed, what you held constant, what you measured].

What worked: [result, with the number].

What did not: [result, with the number, given equal billing].

What we cannot conclude: [the limits of the test, honestly].

Verdict: [keep, kill, or keep testing, and why].
See it filled in

For 90 days we posted on LinkedIn every weekday. Here is what happened, including the part that did not work. The setup: one post per weekday instead of our usual two per week. Same author, same topics, engagement pass unchanged. We measured followers, profile views, inbound calls booked. What worked: profile views roughly doubled, and follower growth went from about 80 to about 210 a month. What did not: inbound calls stayed flat. Eleven the quarter before, twelve during. The metric we actually run the business on did not move. What we cannot conclude: whether quality suffered. Daily posting forced thinner posts, and thinner posts may cost trust that shows up on a longer lag than 90 days. Verdict: back to three a week. The follower curve was flattering, but we are not in the follower business, and the extra two posts a week were costing better work.

Lessons with receipts

List

A milestone gives you licence to compress hard-won lessons, each with proof attached.

[The milestone or timeframe]. [Number] lessons, each with the receipt:

1. [Lesson, one line.]
The receipt: [the specific moment or number that taught it].

2. [Lesson.]
The receipt: [proof].

3. [Lesson.]
The receipt: [proof].

4. [Lesson.]
The receipt: [proof].

[Closing line: the lesson you suspect you have not learned yet.]
See it filled in

Five years running an agency. Four lessons, each with the receipt: 1. The client who negotiates hardest on price will also be the hardest on everything else. The receipt: our three worst engagements all started with a discount. Our best client has never once asked for one. 2. Write the case study while the project is live, not after. The receipt: we have 9 finished projects with no case study, because "after" never comes. The two studies that win us work were both written mid-project. 3. A niche is a moat you dig one refusal at a time. The receipt: revenue got predictable the year we started saying no to work outside logistics. Not the year we niched the website copy. The year we actually declined the projects. 4. Your calendar is your strategy; everything else is the newsletter version. The receipt: the quarter I audited my own hours, 60% went to internal meetings for a team of eight. No strategy deck survives that. The lesson I suspect I have not learned yet: which of these I only believe because five years is still a small sample.

The stack, with reasons

List

People keep asking what you use, and the honest answer includes what each tool replaced.

[The context: your team size, what you do.] The actual stack:

[Tool or practice 1]: [what job it does], replacing [what you used before and why you switched].

[Tool 2]: [job], replacing [predecessor].

[Tool 3]: [job], replacing [predecessor].

[Tool 4]: [job], replacing [predecessor].

What we deliberately do not have: [the absent tool everyone assumes you need, and why].

[Closing: the rule you use for adding anything new.]
See it filled in

We are a six-person B2B services firm. The actual stack: A shared inbox: every client email visible to everyone on the account, replacing the CC chains that let things fall between two people who each assumed the other had it. One spreadsheet as CRM: forty client relationships do not need pipeline software, replacing a real CRM we paid 200 a month to update out of guilt. Loom before meetings: any topic that is one person explaining something becomes a recording, replacing roughly a third of our calls. A Friday written summary: five bullets per person, replacing the Monday status meeting, and the reason our Mondays are now for actual work. What we deliberately do not have: project management software. For our size, the shared inbox plus one board per client covers it, and every PM tool we tried became a second job. The rule for adding anything: it has to replace something. Tools that only add go on a list we revisit quarterly, where most of them die.

The genuine fork

Question

You face a real decision, both options defensible, and the answers will actually inform it.

Real decision, genuinely torn. [The situation in two lines.]

Option A: [the case for it, made properly].

Option B: [the case for it, made just as properly].

The complication: [the constraint that makes it interesting].

Where I lean: [your honest current lean and why it feels weak].

If you have made this call, what did you learn after it was too late to change?
See it filled in

Real decision, genuinely torn. Our two biggest clients both want us on retainer next year, and together they would be 70% of revenue. Option A: take both. Guaranteed base, deeper work, the kind of compounding client knowledge that makes the work genuinely better each quarter. Option B: cap any client at 25% and keep hunting. Slower, more sales effort forever, but no single phone call can take half the company away. The complication: the team. Retainers would let me hire the senior person we need; the diversified version keeps us stretched for at least another year. Where I lean: taking both, with a hard one-year rebalancing plan. It feels weak because every agency horror story I know starts with exactly this reasoning. If you have made this call, what did you learn after it was too late to change?

The poll with a stake

Question

You want a real read on a split practice, and you will publish what you do with the answer.

[The debate, framed in one line the reader has an opinion about.]

[Why it matters more than it looks: two lines.]

[Your own practice, disclosed first, so the ask is fair.]

The question: [the specific question].

[What you will do with the answers: the follow-up post, the decision it feeds.]
See it filled in

Do you tell candidates the salary range before the first interview? It looks like an admin detail. It is actually a filter: whoever holds the number longest holds the leverage, and both sides know it. Disclosure first: we publish the range in the job ad. It costs us some negotiating room and it has never once cost us a candidate we wanted. The question, for anyone who hires: range in the ad, range on request, or range at offer, and what has it actually done to your pipeline? I will compile whatever lands here into a follow-up with the patterns, anonymised. The comments on this one interest me more than the votes.

The say-do gap

Observation

Your industry preaches one thing and visibly practices another.

Every [role or company type] says [the pious claim]. [The observable behaviour] says otherwise.

Look at [where the gap shows: the artifact anyone can check].

[Two or three concrete examples of the gap, no names needed.]

The gap is not hypocrisy, it is [the structural reason underneath].

[What the gap tells you that the claims never will.]

[How to use this as a reader: the practical takeaway.]
See it filled in

Every B2B company says they compete on customer relationships. Their org charts say otherwise. Look at where the headcount is. Ten in sales, six in marketing, and customer success is one person who also runs onboarding, renewals, and the help centre. The pattern repeats in the budget: conference sponsorships approved in a day, a second support hire debated for two quarters. And in the metrics: pipeline reviewed weekly, churn reviewed when it spikes. The gap is not hypocrisy, it is accounting. New revenue has an owner, a target, and a dashboard. Kept revenue is everyone's job, which makes it no one's. The gap tells you what a company actually believes its growth engine is, far more reliably than the About page does. The takeaway: if retention matters to your model, give it what sales has. An owner, a number, and a standing meeting. Beliefs without headcount are decorations.

The pattern across N

Observation

Repeated exposure (clients, interviews, audits) has shown you the same thing enough times to name it.

I have [seen the sample: number and thing] in the last [period]. The same pattern shows up in almost every one:

[The pattern, one line.]

What it looks like in practice: [two or three concrete variants of the same pattern].

Why it happens: [the underlying cause, sympathetically].

The fix that actually works: [what you have seen break the pattern].

[Closing line: how the reader can check themselves for it.]
See it filled in

I have reviewed 31 SaaS onboarding flows in the last year. The same pattern shows up in almost every one: The product asks for setup before it has shown value. What it looks like in practice: invite your team before you have seen the dashboard. Connect your data before one example exists to explain why. Configure notifications for events you do not understand yet. Why it happens: every team that ships onboarding knows the product too well. To them, setup is obvious prep. To a new user, it is homework assigned by a stranger. The fix that actually works: one example, preloaded, interactive, before any ask. The products that show a fake-data dashboard first get the data connection later at double the rate. Check yourself in one minute: open your own signup flow and count the asks before the first thing a user would screenshot. More than one is the pattern.

The accountable prediction

Observation

You see something coming in your field and are willing to be wrong in public.

Prediction: [the specific claim, with a timeframe].

The reasoning: [two or three lines of mechanism, not vibes].

What I am seeing already: [the early evidence, concretely].

What would prove me wrong: [the honest falsifier].

[What to do differently now if this is even half right.]

Bookmark this. [One line inviting the future check-in.]
See it filled in

Prediction: within two years, "we respond within 24 hours" will read the way "check back during office hours" reads now, in most of B2B services. The reasoning: response-time expectations are set by the best experience anywhere, not the best in your category. Buyers who get instant, competent answers from software all day will not grade agencies on a curve. What I am seeing already: in our last dozen lost-deal interviews, three mentioned speed of first answer as the deciding factor. Two years ago that number was zero. What would prove me wrong: if buyers start treating slow, considered responses as a signal of seniority. There is a version of this where scarcity wins. If this is half right, the move is not hiring for coverage. It is building the answer library: the twenty questions every prospect asks, answered so well that speed and depth stop being a trade-off. Bookmark this. If I am wrong in August 2028, say so loudly.

The open books post

Behind the scenes

Sharing a real internal number, with context, teaches more than any advice post.

[The number, stated cold.]

That is [what the number is, precisely, and the period].

Context that makes it meaningful: [comparisons, history, or denominators].

What is behind the good part: [honest attribution].

What is behind the bad part: [equally honest].

Why I am sharing it: [the genuine reason, briefly].

[One question you are still trying to answer about your own number.]
See it filled in

41%. That is the share of our revenue last quarter that came from clients we have worked with for over two years. Context: three years ago that number was 12%. We were a churn machine with a good sales team, which looks like growth until you price the treadmill. Behind the good part: mostly one decision. We started running quarterly roadmap reviews with every client, unbilled. Renewals stopped being a conversation because they stopped being a decision point. Behind the bad part: 41% also means our new-business muscle has atrophied. Two proposals last quarter. Two. Why I am sharing it: every agency dashboard I ever saw as an employee was secret, and I learned the economics of this business embarrassingly late because of it. The question I cannot yet answer: what the right ceiling for that number is before comfort becomes fragility.

The quarterly self-review

Behind the scenes

A period just ended, and reviewing your own calls in public keeps them honest.

[Period] review, the version without the highlight reel.

Called it right: [one thing, with what you did about it].

Called it wrong: [one thing, with what it cost].

Got lucky: [one good outcome you cannot honestly take credit for].

Still unclear: [one open question the period did not settle].

The one change for next [period]: [specific and small].
See it filled in

Q2 review, the version without the highlight reel. Called it right: we froze hiring in April when two deals wobbled. Both wobbled into July. Payroll never got scary, and the freeze cost us nothing but patience. Called it wrong: I priced our biggest proposal of the quarter to win it rather than to do it well. We won it. Every hour on it since has been a reminder that a discount is a decision you pay for monthly. Got lucky: our best hire of the year applied cold the same week a client doubled their retainer. I would love to claim a system produced that timing. Still unclear: whether our new positioning is working or whether the market just warmed up. The inbound lift coincides with both. The one change for Q3: every proposal gets a second price from someone who did not scope it. My optimism needs a reviewer.

The unglamorous routine

Behind the scenes

The boring habit behind your results deserves the spotlight the results usually get.

People ask [the impressive-sounding question]. The honest answer is [the boring routine].

Every [frequency]: [the routine, in mundane detail].

It takes [the real time cost]. [What it replaced or prevents.]

[One concrete example of the routine catching something.]

There is no [the fancy thing people expect]. [One line on why the boring version wins.]

[Closing: the smallest version of the habit a reader could start.]
See it filled in

People ask how we keep clients for years. The honest answer is a fifteen-minute Friday ritual nobody would put on a conference slide. Every Friday: I open each client's file and write three lines. What moved this week, what is stuck, and what they might be worrying about that they have not said. It takes about ninety minutes for all six clients. It replaced the quarterly panic of preparing for review meetings by remembering a whole quarter at once. Last month the "worrying but unsaid" line caught one: a client had gone quiet on a project that was, by every metric, going well. The three-line habit surfaced the silence itself as the signal. One call later: their board was questioning the spend. We built the case together before the board meeting instead of after it. There is no client health dashboard. Dashboards show you the numbers clients generate; the Friday lines force me to think like each client for two minutes, which is the part no tool does. Smallest version: one client, three lines, this Friday. If nothing surfaces in a month, your clients are either very happy or very quiet, and it is worth knowing which.

The no we are glad about

Behind the scenes

A refusal shaped your business more than most yeses, and the reasoning transfers.

We said no to [the tempting thing]. [What it was worth, so the temptation is clear.]

Why it was tempting: [the honest appeal, including the flattering part].

Why we said no: [the actual reasoning, specific to your strategy].

What saying no cost: [the real price, not waved away].

What it protected: [what stayed possible because of the no].

[The rule you extracted, one sentence, and its limits.]
See it filled in

We said no to a 200k project last year. For a company our size, that was a fifth of annual revenue in one signature. Why it was tempting: beyond the number, the logo. A brand everyone knows, the kind that ends the "never heard of you" problem in sales calls forever. Why we said no: the work was a full replatforming, and we are a conversion optimisation firm. We would have spent a year becoming mediocre at someone else's specialty, with our best people unavailable for the work we actually sell. What it cost: the founder pain of watching a competitor take it, plus a genuinely thin Q1 where 200k would have felt very good. What it protected: the two best case studies we have ever produced, both shipped that year by the team that would otherwise have been buried in the replatform. The rule: revenue that makes you worse at your specialty is expensive money. The limit: this rule is easy to quote and brutal to follow in a thin quarter, and anyone who says otherwise has not had one.

The same editor

You have been using our editor without the account.

The toolbar above is the one inside Depost AI: same styles, same bullets, same counter, same preview. What the free version cannot do is the hard part, which is knowing what to write in the first place.

It reads your analytics first

The draft starts from what has already worked on your audience: your hooks, your pillars, your posting patterns. This page can tell you a post is 240 characters. It cannot tell you the opening is one you have used four times.

Ask AI, and rewrite in place

Select a line and rewrite it, in your voice rather than in the flat register every generator defaults to. Accept, try again, or discard, without losing the draft you had.

The graphic comes with the post

Images, video, documents, and polls attach in the same editor, and the infographic is designed against the post rather than picked from a stock library afterwards.

It schedules itself into the gaps

Send a finished draft to the queue or to the next free slot, published through LinkedIn’s official API. Nothing goes out until you approve it.

Comments, reviewers, and a first comment

Leave a note on a selection, assign a reviewer, and have the first comment written with the post so it is ready the moment the post goes live.

Every revision is kept

Undo here lasts as long as the tab does. In the product, the version you had on Tuesday is still there on Friday.

Connect LinkedIn and you have a strategy, your pillars, and your first post ideas in about fifteen minutes.

Structure is the part worth stealing

Every writer in every medium works from shapes: the cold open, the reversal, the numbered argument. Feeds are no different, and pretending otherwise just means reinventing the same structures badly under deadline. What a template cannot supply is the load: the number from your dashboard, the mistake that actually stung, the client moment you keep retelling. Structure plus your material reads as craft. Structure plus generic filler reads as the content everyone scrolls past, and no library can fix that half.

The honest way to use this page is backwards: collect material first, in a running note of moments, numbers, and opinions from your working week, then come here to find the shape that fits the strongest item. The "when to use it" line on each card exists for exactly that matching step.

From skeleton to published

Once a template is filled, two checks pay for themselves. The hook generator on this site will pressure-test your first line against five alternatives, because the template's opening slot is a suggestion, not a ceiling. And the post preview shows where the “see more” cut lands, which matters because several of these shapes stake everything on the lines above the fold. Fill, sharpen the opening, check the cut, publish.

Questions

What is in this template library?
24 post structures across eight categories: story shapes, how-tos, contrarian takes, proof posts, lists, questions, observations, and behind-the-scenes formats. Each one has the pattern as a copyable skeleton with the slots marked, one line on when to use it, and a complete example filled in so you can see the shape working.
How do I actually use a template?
Copy the skeleton, paste it into your editor, and replace the bracketed slots with your material. The line breaks are part of the template: they carry the rhythm that makes the shape work in the feed. When you are done, nothing bracketed should survive, and ideally a reader should not be able to tell a template was involved.
Will not everyone's posts look the same if we all use templates?
The structures were already everywhere; this page just names them. What makes posts identical is not shared structure, it is shared emptiness: the same shape filled with the same platitudes. A template filled with your specific numbers, your specific mistake, your specific client walks and talks like no one else's post.
Which template should I start with?
The one whose "when to use it" line matches something that actually happened to you this month. Templates fail when chosen first and filled second. Read your own recent weeks for the material, then pick the shape that fits it. If nothing fits, the observation and question shapes run on attention rather than events.
Why do the examples use invented companies?
Because putting real companies' numbers in illustrative examples would mean either leaking or lying. The examples are plausible by design and fictional by policy: they show each shape at full strength without borrowing anyone's actual story. Your fill-in should do the opposite, which is exactly why it will outperform the example.
Is it free?
Yes, all of it, without an account. Copy whatever you want; no attribution needed. The library grows as we find and name more shapes that hold up.

Make LinkedIn your
best-performing channel.

Brief your team once. It studies, plans, writes, designs, and schedules. You approve.

Your brief comes with you: once you're set up, it's the team's first job.

7 days free · Strategy in your first 15 minutes · Cancel anytime