LinkedIn for B2B: posting as a person, not a brand

Businesses that take LinkedIn seriously usually start by building a company page and posting to it, and then conclude the platform does not work for them.

The observation behind the standard advice is consistent: on LinkedIn, posts from personal profiles tend to travel considerably further than the same content from a company page. The mechanism is partly about how the platform distributes content and partly about how people behave. A person's post arrives in a feed attached to a face and a name, and LinkedIn's core interaction — someone commenting, which exposes the post to their network — happens far more readily on a person's post than on a company's. Few people want to be seen arguing with a logo.

It is worth being careful about the precise size of the difference, since figures circulate widely without sources attached. The direction is well established and the specific multiple usually is not. The practical conclusion does not depend on the number: if the founder or a named employee is willing to post, that is where the effort belongs.

None of this means the company page should be deleted, and abandoning it entirely creates a different problem.

A page is a reference rather than a channel. When somebody hears about the business and looks it up, the page is what they find, and an empty or clearly abandoned one is a poor answer to a question about whether the business is real and active. It also holds the things a personal profile should not: the description of what the business does, the employee list, the website, and posts recording things a company records, such as launches and hires.

So the sensible arrangement is a page kept current and not expected to distribute, plus personal posting where the actual reach is. Employees' profiles link to the page, which means people arriving from a post find something coherent.

What wastes effort is producing the same content twice into both, which is what most businesses do — and the company version of a post written for a person almost always reads worse.

The single most common LinkedIn mistake is writing in the register of a corporate announcement, and it fails for a reason worth naming.

A press release is written to be unobjectionable. It removes uncertainty, specificity, and anything that could be disagreed with — which is precisely what removes any reason to respond. Nobody comments on a sentence stating that a business is thrilled to announce a strategic partnership, because there is nothing in it to engage with.

The things that make a post worth reading are the things a press release strips out: what was actually difficult, what the business believed and turned out to be wrong about, what a specific number was, what the alternative options were and why they were rejected. Those are all specific, and specificity is what makes a reader think of their own experience — which is what a comment is.

The writing test is simple. If the post could have been published by any business in the sector with the name changed, it will not travel, because there is nothing in it that only this business could say.

Three categories consistently produce discussion, and they have a shared property: each invites a reader to contribute rather than to admire.

Lessons learned. Something the business got wrong, and what it cost. This works because it is genuinely uncommon — most professional posting is a performance of competence — and because a reader who has made the same mistake will say so. It requires the mistake to be real and to have been resolved.

Behind-the-scenes decisions. A choice with defensible options on both sides: how a price was set, why an approach was rejected, how a hire was decided. Readers engage because they have made the same call differently.

Questions. A genuine one, where the poster does not know the answer and has a reason to want it. This fails when it is transparently a device — a question whose answer the post then supplies is not a question.

What unites them is that the reader has somewhere to stand. A post presenting a finished conclusion leaves them with nothing to add.

LinkedIn's own interface shapes how a post should be laid out, in ways that are easy to get wrong.

Only the first few lines appear before a see more link, so the opening carries the same weight it does on any platform that truncates. Lead with the specific claim or the situation rather than context.

Paragraphs should be short — one or two lines with a blank line between — because the feed is read quickly and often on a phone. This produces the somewhat mannered look common to LinkedIn posts. It is worth adopting up to a point; taken to an extreme, where every sentence is its own paragraph, it becomes a style people have learned to distrust.

A link in the post body is generally distributed less well than a post without one, so where a link matters, putting it in the first comment is the usual practice. And length is not the constraint people assume: substantial posts do well when they are specific, and short posts fail when they are empty. Consistency matters more than either — a couple of posts a week, sustained.

The barrier for most business owners is not the platform but the prospect of writing regularly in public, which is a genuine cost and worth planning around.

What works is not writing. It is recording. The material for good LinkedIn posts is generated by ordinary work — a decision made in a meeting, a customer question that revealed a wrong assumption, a supplier problem and how it was solved. Keeping a note of those as they happen turns posting into transcription rather than invention, and the note takes a moment while the memory is fresh.

Batching helps in the same way it does elsewhere: writing two posts in one sitting from a stocked list is far cheaper than producing one from nothing twice a week.

The part to keep personal is the replying, because comments are where LinkedIn's distribution actually happens and a post left unanswered wastes it. A scheduling tool such as Socie can queue drafts across accounts so the cadence holds; the comment thread underneath is where the value is, and that is a person's job.