What belongs in a lead brief?
The source, the change, the timing, and the unanswered question. A small brief that makes an outbound decision easier to review.
By leadleadlead
Make the decision easy to inspect
A name, a job title, and a company domain tell you who a person is. They do not explain why you should contact them now. A useful lead brief connects an account to a specific observation and makes that connection easy to check.
The goal is not to collect every available detail. It is to give the reviewer enough context to decide whether there is a relevant conversation to have.
Record the change and the source
Describe the event in one plain sentence. ‘The company posted an opening for its first revenue operations hire’ is more useful than ‘Strong growth signals.’ Follow it with the original source URL and a short excerpt that supports the statement.
Keep the publication date separate from the date you discovered the page. If the publication date is unknown, say so. Finding a page today does not mean the event happened today.
Explain the fit without inventing the need
Connect the observation to your offering as a hypothesis. For example, a revenue operations hire might make a conversation about workflow ownership relevant. It still does not tell you which workflow needs attention.
Include the claim limit next to that hypothesis, where the reviewer will see it. Then write the question you would ask to learn whether your interpretation is useful.
Leave a clear next step
End the brief with a decision: review the source, research further, draft a message, or pass. A pass is a useful outcome when the evidence is thin or the connection is weak.
Before drafting, ask whether someone else could open the source and reach the same factual conclusion. If the answer is no, the brief needs more work before the copy does.