
Your prospective client needs to recognize a problem, understand how you approach it, and decide whether a conversation is worthwhile. A stream of motivational statements gives them little help with those decisions. Show the work in a form that respects client privacy and makes your service easier to evaluate.
This playbook proposes two substantial posts and one short question each week. Reduce that workload if you cannot also respond thoughtfully. The aim is a repeatable route from useful explanation to an appropriate inquiry, not a daily performance of expertise.
Name one client situation
Choose a situation narrow enough to recognize in a conversation. A consultant might help small agencies improve project handoffs. A coach might work with people preparing for their first management role. Those audiences need different examples even if both care about communication.
Write down the triggering moment: a handoff repeatedly loses information, or a new manager needs to prepare a difficult meeting. Then identify what you can explain publicly and what requires individual work.
Keep the service description beside that note. If you sell a diagnostic workshop, the content should help someone understand when a diagnostic is useful, what it includes, and what happens afterward. Avoid implying that a short post can resolve every version of the problem.
Turn recurring questions into an editorial list
Review your own notes for questions that repeat before a sale or at the start of an engagement. Remove identifying details before using them. Group questions by decision: recognizing the issue, trying an initial step, choosing support, and understanding the engagement.
For the handoff consultant, possible topics include which information a brief needs, how to identify an owner, and what a kickoff can realistically settle. A post answering one of those questions can be more useful than a broad claim about improving productivity.
Keep a separate list of questions you cannot answer responsibly without context. You can explain why more information is needed and how your assessment works without giving a premature recommendation.
Teach with an artifact
Use a worksheet, a short decision tree, an annotated agenda, or a before-and-after example you created yourself. Label fictional material clearly. Readers should know whether they are seeing a real case, an anonymized case with permission, or a teaching example.
An invented agenda could show three fields: decision required, information missing, and person responsible for the next step. Explain how someone would use each field during a meeting. That gives the reader something to test.
Include the limitation. An agenda does not solve a disagreement about authority, for example. Naming that boundary makes your explanation more accurate and tells a prospect what additional work an engagement might involve.
Show your process without exposing clients
Describe a sequence such as intake, diagnosis, working session, and written next steps. State what the client supplies and what you deliver. Use the terms from your actual offer rather than inventing a more impressive process for social media.
If you use a testimonial or client example, confirm permission and scope. Avoid posting screenshots of private messages simply because the feedback is positive. A client may consent to a sentence on your website without consenting to a public account tag.
Do not promise revenue, career, health, or personal outcomes you cannot substantiate. An example can explain what happened in that specific engagement while acknowledging conditions. It should not quietly become a typical-results claim.
Write an example that earns the next sentence
An illustrative post might open: “Your project brief lists six deliverables but nobody owns the final sign-off. Add an owner before adding another meeting.” Follow with a small example showing where that field belongs and how it changes the next action.
Then explain when the suggestion is insufficient: “If two departments disagree about authority, settle that decision separately.” Close with a question about the reader’s process or a relevant service link, depending on the post’s purpose.
Avoid making every post a consultation pitch. Some pieces can simply help someone make a better decision. A useful explanation remains useful even when the reader is not ready to buy.
Make the service post specific
Once a week or less, explain an actual offer. State who it is for, the question it addresses, the format, required preparation, and the next step. Include exclusions that prevent an inappropriate inquiry.
For a fictional workshop: “A working session for agency owners whose projects stall between sales and delivery. Bring one current brief. We map the handoff and leave with an owner and a checklist. Implementation support is a separate engagement.” Replace the details with your real scope.
Give people a page where they can check the offer without disclosing sensitive details in comments. If pricing depends on scope, explain how you determine scope rather than using vague urgency to push a call.
Pick channels from actual conversations
Choose a main destination based on where appropriate clients already interact with your work. LinkedIn may suit professional discussion; Instagram may suit a visual teaching practice. Neither is automatically right for every coach or consultant.
Postbean supports personal LinkedIn profiles, not company pages. Its other current connections are Instagram, Facebook, TikTok, YouTube, Threads, Bluesky, and DEV. X, Pinterest, and Google Business are coming soon. Match your publishing plan to available destinations rather than assuming every profile can be connected.
Adapt the example to each network. A visual worksheet needs readable labels; a short text post needs enough context to stand alone. Reusing an idea does not require copying the same opening everywhere.
Set a weekly drafting block
Reserve a weekly block to select questions, prepare examples, and draft two posts. Use Postbean’s composer for captions and network-specific wording, then inspect the calendar before scheduling.
Check the offer, link, date, permissions, and selected profile. If a colleague or client must review material, obtain that review through your existing process before scheduling. Postbean does not currently provide an active approval workflow or team invitations from the panel.
Keep a separate reply window. Drafting ahead should not create the impression that you are available for immediate individual advice whenever a scheduled post appears.
Measure the quality of the conversation
Use a simple inquiry log with topic, source, relevance, next step, and outcome. Ask new prospects which explanation helped them decide to contact you. Treat their answer as evidence about that conversation, not perfect attribution.
Illustrative comparison: a broad opinion receives many reactions, while an agenda example brings two inquiries matching your service. That suggests a useful topic to explore. It does not prove that practical posts always sell better or establish a conversion benchmark.
Review repeated misunderstandings too. If readers consistently expect implementation when you sell diagnosis, rewrite the offer page and service post. That correction may matter more than publishing another topic.
Give examples a clear home
Keep your teaching resources in a small, maintained library. Record the question each resource answers, the service it relates to, and when you last checked it. If your offer changes, inspect the resources that still describe the old scope. A worksheet can remain helpful while its closing invitation becomes inaccurate. Save the editable original so you can correct a label without rebuilding the entire asset. This preparation also gives you material for a difficult week, when writing another personal reflection would take time away from serving clients.
Review after a small, complete cycle
Run the routine for four to six weeks, then inspect time spent, useful replies, relevant inquiries, and completed work. Allow for the actual buying cycle; silence after one post is weak evidence about demand.
Keep formats that you can produce accurately without borrowing client confidentiality. Retire topics that attract people you cannot help, and make the service boundary clearer where needed.
Draft your next two explanations in Postbean, then check that each points to the right service and keeps client details private.