Customer conversations are unusually strong source material because they contain real language and real stakes. They also require care. The goal is not to turn customers into content. It is to extract a broadly useful lesson from your own experience while protecting the relationship that produced it.

Capture immediately, publish deliberately

After a call, record the question that stayed with you and why it mattered. Include your own response and anything you would answer differently now. This private capture can be detailed because it is source material, not the final public draft.

Before writing, decide whether the post needs the customer at all. Many useful lessons can be framed as ‘A question I heard this week’ or as a direct explanation of the underlying tradeoff. If removing the identity does not reduce the lesson, remove it.

Use a privacy filter

Anonymity is more than deleting a company name. Industry, location, team size, job title, timing, and a distinctive problem can identify someone when combined. Generalize details that do not affect the argument and omit internal numbers unless they are already public or explicitly approved.

  • Could the customer recognize themselves?
  • Could a colleague or competitor identify them from combined details?
  • Does the post reveal commercial, personal, or security-sensitive information?
  • Would the relationship remain comfortable if the customer read it today?

Keep observation and interpretation distinct

A customer’s question is an observation. Your explanation of why they asked is an interpretation. Good writing makes that boundary clear. Phrases such as ‘I think the deeper issue was’ are more honest than presenting your inference as the customer’s stated belief.

This distinction also improves the post. It lets you move from one conversation to a broader pattern without claiming that one person represents an entire market. Add evidence from repeated conversations when you have it, and qualify the conclusion when you do not.

Make the reader the beneficiary

The final post should help the reader recognize a decision, risk, or tradeoff in their own work. Give enough context to understand the lesson, then spend more space on the reasoning than on the anecdote. Avoid using a customer as a prop for a self-congratulatory story.

If the customer’s identity, quote, or measured outcome is central, ask for written permission and show them the relevant wording. Trust compounds more slowly than content reach, but it is worth considerably more to a B2B founder.