Most founders finish a client call with more material than they will produce in a week of staring at an empty composer, and publish none of it. The reason is usually not laziness. It is that the call belongs to somebody else, and the line between your insight and their business is not obvious at four in the afternoon.
The line is clearer than it looks. A client call hands you four things that are yours to publish, and they are yours because they describe your own work rather than theirs.
What a client call gives you that is safe to post
The pattern
The pattern is the thing you have now heard more than once. Three clients this quarter opened with the same complaint. Every mid market buyer asks the same question at the same point in the process. The fourth call in a row stalled on the same internal approval.
A pattern is safe because it belongs to nobody in particular. The instant something is true of several clients, it stops being a client's story and starts being an observation about your market, which is exactly the thing your audience cannot get anywhere else.
The objection
The objection is what they pushed back on, and what you said next. The real exchange, including the part where your first answer was not good enough and you had to find a second one.
Objections make the best posts because the reader is usually holding the same one. When you write "the question I get every time is whether this works with a team of four", you have written the first line of a post for every reader with a team of four.
The number
The number is any figure the call produced that is yours to know. How long the thing took. How many revisions. What the conversion was on the last cohort. How many calls it takes to get to a yes.
Their revenue and their headcount belong to them. Your own operating numbers belong to you, and they are worth spending, because a figure from inside your business is something a reader cannot get from anyone else writing about your category.
The decision
The decision is what you changed because of the call. You dropped a feature. You rewrote the onboarding email. You decided to stop taking projects under a certain size. You said no.
A decision post works because it has a before and an after built into it. There is a thing you used to do, a moment that changed your mind, and a thing you do now. That is a complete story in three sentences and it needs no ending anyone has to invent.
How to write each one without identifying anyone
The rule is short. Keep what happened, drop who it happened to.
In practice that means four substitutions, and they are the same four every time.
Names become roles. "Priya at Northwind" becomes "a client's head of ops". This is the one most people already do.
Companies become categories. "A fintech in Leeds" is still identifying if you only work with three fintechs. "A regulated business" is not.
Single clients become counts. This is the substitution that does the most work. "A client told me" points at one person. "The third client this quarter to tell me" points at a pattern, and is both safer and a better post.
Distinctive details become generic ones. The detail that makes a story good is often the detail that identifies the company. If the anecdote only lands because of the unusual thing about their business, the anecdote is theirs and not yours.
Two things never travel, whatever you do to them. Anything about a named individual's private circumstances, including health, pay, performance and a departure in progress, because in a small company the details identify the person even with the name removed. And anything told to you in confidence, which no rewriting fixes.
If the only honest version of the story identifies someone, the story is not a post. Write a different one. There were four things in the call.
Three worked examples
None of these are customers. They are illustrations, written to show how each shape reads when it comes out right.
A pattern. "Three sales calls this month, three companies that already had the software they were asking me to sell them. Nobody had switched it on. I have started opening with 'what did you buy last year and why is it not running', and the call goes somewhere useful about fifteen minutes earlier than it used to."
An objection. "The question I get on every call now is whether this works for a team of four. My honest answer for a long time was that it probably did. It does not, and I have stopped pretending otherwise. Under about eight people the coordination problem I solve is not yet a problem, and you are better off with a shared document and a standing Friday call. I will tell you that on the first call and it costs me about one deal a month."
A decision. "I dropped the free trial this week. It was cheap enough to run. The problem was that every trial conversation started from a feature tour, and none of them started from the thing the buyer was actually trying to fix. A thirty minute call converts better than fourteen days of self serve, and I would rather have the conversation."
Each one is a complete post. None of them names a person, a company or an industry small enough to be a company. Two of them cost the writer something, which is the part that makes them worth reading.
The template block
Four sentences, in this order, for any of the four shapes.
- 01The observation, stated flat. What you have now seen more than once, or what they pushed back on, or the figure, or what you changed.
- 02Where it came from, de identified. A count, a role, a category. "The third one this quarter." "A client's finance lead." "Two regulated businesses."
- 03What you think it means. This is the post. Everything above it is setup, and everything below it is invitation.
- 04The open end. A question, a caveat, or the thing you are still unsure about. Not a call to action.
Then cut the first sentence you wrote, because it is almost always throat clearing, and check that nothing in the remaining four points at one identifiable company.
The whole thing takes about six minutes if you do it while the call is still warm. It takes about forty if you try to remember the call on Sunday night, which is the real argument for writing it down on the day.
More ways to find material in a week you already worked are in the guide to LinkedIn post ideas from your week. If you publish in two rooms, one voice, two registers covers what changes between them, and how Sonar keeps your colleagues out of your LinkedIn posts is the same de identification rule written into a product. The rest of the writing is on the Sonar blog, the product is at Sonar, and there is one plan on pricing.
Questions
Should I ask the client before posting?
Not for the four shapes above, if you have de identified them properly, because none of them is the client's story. Ask before naming any person or any company, every time, and get it in writing if it is going to read as a case study.
What if my market is small enough that a category still identifies them?
Use a count instead of a category, and wait until you have three examples before you publish the pattern. If a third example never arrives, the material is not a post.
Can I quote what they said on the call?
Paraphrase. A verbatim quote from a private call is the client's words, and a paraphrase of an objection is usually the sharper sentence anyway.
How long should the post be?
Long enough to hold the four sentences in the template and nothing more. LinkedIn shows roughly the first 210 characters before the see more fold, so the observation has to be sentence one.
How does Sonar handle this?
Sonar reads the calls and channels you connect, pulls the moments out and drafts from them, and a standing instruction keeps private people out of both the moment and the draft. You approve every post before it goes anywhere.