LinkedIn for lawyers, when the matter never leaves the room.

Start with the line, because everything else on this page depends on it. Sonar reads your week to find things worth posting about. For a lawyer, client meetings sit outside that read entirely. Not summarised, not anonymised, not held for later. Outside it.

The mechanism is duller than a promise. Sonar reads only sources you have connected, one switch each, and meeting transcripts are their own sources. Google Meet, Zoom, Granola, Fireflies and the rest are separate connections you either grant or never grant. Leave them ungranted and there is no transcript in the system to summarise, because we never had one. Nothing joins your calls to listen either: the transcript connectors read what the meeting platform already wrote, through the permission you gave, and no bot appears in your room.

Two rules run underneath all of it, applied twice each. Private individuals are never named in anything publishable, so a draft says "a client's general counsel" or "opposing counsel" or "someone on my team". And where the only honest telling of a moment would identify the person it is about, the moment is dropped rather than softened. Both rules are applied when a moment is pulled out of your week and again when a post is written from it, which is deliberate: one of them alone would be a single point of failure.

Three kinds of name stay named, and you should know all three before you rely on any of this. Genuine public figures, such as an author or a regulator you are quoting. The employers and clients your own credibility answer cites. And anyone you name yourself in a request, because a name you type into the chat is read as a decision rather than a leak.

What is left after transcripts is more than enough to carry a posting habit, because a practice generates material in four other places.

• Your calendar, for shape. Read as the structure of a week rather than its contents: how many of a kind of conversation, what filled the days, which week was unusual. A calendar entry is where something happened and is not itself the story, which is how the extraction step is written. See what Sonar reads from a calendar.
• Slack, in the channels you pick. Picking channels is the whole consent boundary: Sonar reads the ones you choose and nothing else, so business-of-the-firm channels can be in while any channel that carries matter substance stays out.
• Notion, for the pages you wrote. Connected through Notion's own picker, so you grant specific pages. A knowledge base, an internal explainer, a process you wrote up after a hard month: all yours, all publishable in substance.
• The Story Bank, which needs no connection at all. Sonar turns your career into chapters and interviews you about them, and keeps your answers in your own words. For a lawyer this is the richest source on the list, because a career is decades of material that belongs to nobody else. It is never swept by the retention rule.

Microsoft 365 is built and not yet open. Microsoft's publisher verification has not cleared, so no organisation but ours can consent to it today, and the integrations page marks it as coming rather than live. When it does open it connects as your Outlook calendar first, with the Teams transcript permission as a separate ask you can decline. A calendar and one Slack channel is a working setup on its own, which is the question answered here.

The instinct in a regulated practice is to post nothing but law updates, which is why so many firm feeds read identically. A summary of a judgment is available from forty other accounts within a day. What a reader choosing a lawyer wants is how you think about the thing, and that is publishable without a single client fact.

• What the change actually means for the person paying. Not the summary of the new rule. The operational consequence for a buyer: what they will have to do differently in March, what it will cost, what most of them will get wrong first.
• The pattern across enough matters to count. "In nine of the last ten disputes of this kind, the thing that decided it was the paper trail from the first fortnight." Counted from your own work, attached to no one's file.
• The question you ask first. The diagnostic that tells you in ten minutes which kind of problem this is. Giving it away is the strongest advertisement there is for how you work.
• What clients get wrong before they call. The email that should not have been sent, the clause nobody read, the deadline that was already running. This is the most useful post a lawyer can write and it names nobody.
• Your own practice decisions. Why you stopped taking a kind of work, how you price, what you tell people who cannot afford you, what you changed about your process after a year that taught you something. Your business, your facts.
• The career. The first matter you were trusted with, the year you moved practice areas, the case that changed your mind about something. Yours to tell, and the Story Bank exists to get it out of you.

What to leave out

Leave out the matter, obviously, including the version with the details changed, because a disguised matter is still a matter to the client who recognises it. Leave out the reaction post about somebody else's case. Leave out the judgment summary with no view attached to it. And leave out anything that reads as advice to a stranger's situation, which is a problem your regulator cares about more than your audience does.

The practical version. Once a week Sonar reads the last seven days from whatever you connected, keeps the moments worth saying and throws the raw text away. You look at what it found before anything is written, which for a lawyer is the step that matters: the moments are listed in plain words, and anything you would rather did not exist is deleted with one action, by the moment, by the source, by a cutoff date or all of them at once. You can also set a retention rule of 30 days, 90 days or 1 year, and a job sweeps every day to enforce it.

Then five drafts arrive for the week, built from those moments, an answer you gave the Story Bank, a development in your field and a subject you chose. You read them, kill the ones that are wrong, edit one until it says the thing you meant and schedule the rest. Nothing goes out until you schedule it: the job that publishes to LinkedIn only picks up items you have already put a time on.

Two or three posts a week is a working rhythm for a practising lawyer, and the case for holding a small number is in the content strategy guide. If your material is mostly your own reasoning rather than your week, the consultants page covers publishing a method when the client can never be named, and the executives pagecovers posting under a firm's name as well as your own.

A tool that handles your week should be plain about where its guarantees stop, so here they are in one place.

• Sonar is not a privilege-safe system of record and is not sold as one. It has no matter management, no conflicts checking and no ethical wall.
• Nothing on this page is advice about your obligations. Your duty of confidentiality, what privilege covers where you practise, and your regulator's rules on advertising are yours to know, and they are the reason the source decision is yours rather than ours.
• Drafting sends the relevant text to a third-party model provider, Anthropic. Its commercial terms define Customer Content as your inputs together with the outputs generated from them, and say Anthropic may not train models on Customer Content from the services. That is a contractual position and not a claim that the text never leaves our systems, because it does. The terms are linked below so you can read the clause yourself.
• The people rule governs what is written. It is applied at extraction and again at drafting, and it has never been the only thing standing between a client and a post, because you read every draft before it is scheduled.

What gets read, what is kept, for how long, where it is stored and how to delete all of it is set out on the security page, and what happens to a transcript answers the narrower version for anyone who does connect one.

The first decision is yours and it is the one that matters here: which sources Sonar is allowed to read at all. Grant the Story Bank and a Notion page and that is the entire corpus. Grant no transcript connector and no transcript exists to be mishandled. Sonar has no way to reach material you did not hand it, which is a duller guarantee than a policy and a more reliable one.

On whatever you did choose: the last seven days are read about once a week, the moments are kept and the raw text is discarded. Your writing is learned from your own published posts, measured from the real thing rather than described in a briefing, so a draft reads like you and not like a firm newsletter. Private people are written as roles at every step. Five drafts wait each week to approve, edit or kill, and you schedule what survives.

The mechanism in full is on How it works, the writing half is how to write LinkedIn posts, and the practice underneath it is founder-led marketing. One plan, $99 a month, 7 days free.