TL;DR: The questions buyers ask before they say yes are sitting in your proposal files right now. You can pull them out, build content around them, and not reveal a single client detail in the process. Here’s the 90-minute review that makes it work.
Most firms spend hours creating content they assume buyers want to read – their process, their credentials, their philosophy. Meanwhile, the actual words buyers use when deciding whether to hire someone are buried in proposal folders, read once, and forgotten.
Pull up your last five proposals. Not to review the offer. Look at the questions you were answering.
Every proposal you’ve written responds to something a buyer was worried about, confused by, or needed addressed before they’d commit. Those concerns don’t change much from client to client. The same questions show up in different language, from different people, in different industries. That pattern is telling you something.
What you’re actually looking for
You’re not mining for client data. You’re looking for patterns in buyer thinking.
Go through each section of your proposals and ask: what concern was I responding to here? If you wrote a section on project scope, someone asked about scope creep. If you included a communication cadence section, someone worried about being kept in the dark. If you spelled out what “success looks like,” someone needed that anchor before they’d move forward.
Write down the underlying question for each section. Not the client’s name or situation. Just the question.
After five proposals, you’ll have 15 to 20 questions. Most will cluster into 5 or 6 themes. Those themes are your content calendar.
What’s reusable vs. what stays private
The question is always reusable. The client’s specific situation is not.
“How do you handle a project that changes direction mid-engagement?” is a question you can answer publicly. The story of the specific client whose project changed direction is not yours to tell, unless they’ve said so.
You can write an entire article, LinkedIn post, or FAQ entry around a buyer question without mentioning the client who raised it. The question came from them. The answer is yours. Write the answer.
The same applies to objection language. If a buyer said “we tried something like this before and it didn’t stick,” that’s a pattern you’ve heard before. Write about why implementations fail to stick. What you do differently. What you watch for. None of that reveals anything about the person who first raised the concern.
Outcome language is worth checking too. Pay attention to how buyers described the result they were hoping for. “We need our team to actually use this” is different from “we need measurable time savings.” Those phrases tell you how different buyers frame value. Use that framing in your content. It’s yours the moment you internalize it.
The 90-minute review
Block the time. Open your last five proposals, one at a time, with a notepad beside you.
For each proposal, list every section heading or major point you made. Then write the buyer question that section was designed to answer. If you can’t identify the question a section was answering, it’s probably a section you included out of habit, not because a buyer needed it.
When you’ve gone through all five, group the questions by theme. Flag anything that appeared in three or more proposals. Those are worth writing about first, because they’re not outliers.
You’ve already been asked to explain all of this. The only thing missing is making those explanations available before someone has to ask.