LinkedIn for founder-led service firms: posts buyers reply to
LinkedIn for founder-led service firms: how the owner writes posts for buyers, three formats, one idea and one ask per post, what not to post and what to measure.
How do you write on LinkedIn as the owner of a service firm so that buyers reply, not just people you know from your industry? Write for buyers: start every post with one client problem from your ICP, the description of the companies you want to sell to. Use three formats: a lesson from a project, an opinion, and a teardown of a common mistake. Fit one idea into each post and end it with one ask: a question about the reader’s situation or an invitation. Don’t post bragging with no substance or generic takes on AI. Track replies and conversations with people who fit your ICP, not likes.
In this post I’ll show where to get topics, how to build a post, what not to post, what to measure and what to do when someone replies.
B2B marketers rate LinkedIn highest, and buyers turn to expert content
In the Content Marketing Institute’s research for 2025, 85% of B2B marketers said LinkedIn was the social media platform that delivers the best value for their organization; 28% named Facebook.
Buyers use expert content when choosing a vendor. According to a write-up of the 2025 LinkedIn and Edelman report (a survey of 1,934 executives worldwide), 56% of target buyers, the people sales and marketing usually aim at, do so when putting together a vendor shortlist. Among people who influence the decision but whom sales and marketing usually leave out (the report calls them hidden buyers), the figure is 55%.
In my view, though, it’s easy for a service firm owner to slip into writing for people in their own industry: about trends, tools and conferences. Industry peers will like a post like that, but a client won’t find their problem in it and has no reason to reply.
Every post starts with a client problem from your ICP
Before you write a post, list five problems your ICP clients come to you with, in their own words, taken from requests for proposals, emails and sales call notes: “we don’t know what maintaining the system really costs”, “the agency sends reports, but we don’t know what they tell us”. In a post, generalize them so they don’t point to a specific client. Each problem is a topic for several posts. I showed how to describe your ICP in the post on the ICP for a service firm.
Before writing a post, note four things: the buyer’s question, your take on it, what you’ll back it with, and what the reader should do after reading. From a title alone, it’s easy to write a generic post.
Three formats: a lesson from a project, an opinion, a teardown of a common mistake
| Format | What’s in it | Example first sentence |
|---|---|---|
| Lesson from a project | the client’s situation, what you did, what you learned | “In our last migration project, what took longest wasn’t moving the data, it was working out who on the client’s side signs it off.” |
| Opinion | your position on something clients ask about, with your reasons | “I wouldn’t start by choosing a reporting tool until it’s clear who is supposed to make decisions based on the reports.” |
| Teardown of a common mistake | a mistake you see at clients, and what to change | “The requests for proposals we receive include a budget for building the system, but rarely one for maintaining it.” |
A lesson from a project is, in my view, the most valuable format for a buyer, because it shows you’ve solved their problem before. You can describe a client’s result in a post only if the client agreed to public use; their name and a quote are separate permissions, and numbers must be confirmed. I covered how to ask for permissions in the post on anonymous case studies, and how to collect results in the post on the proof library.
One post, one idea, one ask
A post has one idea that can be summed up in a single sentence. I recommend this form: 150–250 words (at most about 300), one sentence per line, no bullet lists or headings, in the first person, with 2–3 hashtags and an ask at the end. According to the same write-up of the LinkedIn and Edelman report, 65% of hidden buyers prefer a more human, less formal tone, so write the way you talk to a client.
The ask at the end is either one concrete question about the reader’s situation (“how do you hand a project over to maintenance?”) or an invitation instead of a question (“if you’d like the checklist, send me a message”). I think a question anyone can answer tends to pull in industry peers rather than clients. With two asks, the reader has to choose, so keep one.
What not to post
- bragging with no substance: “we’re delighted to welcome a new client”, logos and thank-yous that tell a buyer nothing,
- generic takes on AI that anyone could write, unrelated to your clients’ problems,
- descriptions of projects and results of clients who didn’t agree to public use, even without their name; you can describe a general lesson from such a project without its details.
Track replies and conversations, not likes
The number of likes doesn’t tell you whether buyers or industry peers are reacting. Keep a simple spreadsheet instead: one row per post, with columns for the problem, the format and three numbers: how many people who fit your ICP commented or replied, how many sent you a message, and how many of those contacts led to a conversation about their problem. You check whether someone fits on their profile: by their company (ICP) and job title (persona). You’ll see the first signals after a month, but you can only compare formats and problems after a quarter, once you have a dozen or so posts.
What to do when someone from your ICP replies
Reply in the comments or in a message with one question about their situation, without an offer. If they describe a problem you solve, suggest a short call about that problem. In my view, an offer sent in your first reply can easily end the conversation before it starts.
Example: a post by a software house owner
This is an illustration, not a real post: the owner of a software house whose ICP clients ask about the cost of maintaining systems. Before writing, they noted four things:
| Field | Content (illustration) |
|---|---|
| Buyer’s question | “what does maintaining the system really cost?” |
| Take | maintenance costs need to be calculated before the contract is signed, not after the first invoice |
| What backs it up | how the firm breaks down its proposals (no client names or numbers) |
| What the reader should do | check whether their budget has a separate line for maintenance |
Format: a teardown of a common mistake.
The requests for proposals we receive include a budget for building the system, but rarely one for maintaining it.
Then, a year later, invoices arrive that nobody planned for.
Maintenance isn’t just fixing bugs.
It’s library and operating system updates, security patches, backups and monitoring.
It’s also the changes the company itself will force: a new department, a new report, a new integration.
None of this is visible on the day the project is handed over, but all of it shows up in the budget in year two.
That’s why every proposal we send breaks down the cost of building and the cost of the first year of maintenance separately.
We also show which items depend on the client’s decisions and which are fixed.
We talk about maintenance from the first meeting, not only at handover.
It’s a harder conversation about money at the start, but later nobody is surprised by an invoice.
The client sees the whole picture before signing the contract, not after the first maintenance invoice.
If you’re planning a budget for a new system: does it have a separate line for maintenance after handover?
#ITbudget #systemmaintenance #ITprocurement
The post has one idea and one ask at the end, about 190 words in English (the Polish original has about 150, the lower end of the range from the paragraph on length), and no client names or numbers. The hashtags describe the topic from the buyer’s side, not the author’s profession.
Frequently asked questions
How often should I post?
Consistency matters more than volume, in my view. One post a week for a quarter will give you better data than posting daily for two weeks and then stopping: you get a similar number of posts, but you see what happens over three months.
The owner’s profile or the company page?
In my view, in a service firm the client buys people and their knowledge, so the posts in this article go out from the owner’s own profile. The company page can share them.
Where do I find the time to write?
If you don’t have time to write, record a short conversation about one or several problems from your list and hand it over for editing. Read the finished post under your name in full before it goes out. I described this in the post on expert content without writing.
Summary
If you post on LinkedIn and only industry peers write to you, list five problems your ICP clients have, write a first post for each, with one idea and one ask at the end, and post once a week. For a quarter, track replies and conversations with people who fit your ICP. In our open repo (files and instructions for an AI agent such as Claude Code), the LinkedIn post skill writes from the buyer’s question and the description of the service, ICP and persona, not from a title alone (open source).
Every method on this blog also runs as a skill in the open-source B2BForce repo. About the repo