targeting-fact-with-sourcelisted

# One fact, with its source, or no message Every first touch carries at least one fact about the person or company that anyone could verify. A fact without a stored source does not exist. A lead with no fact is removed from the batch. ## Why A claim without its ground reads like a fact and leads to decisions nobody can defend later. In our own reporting we once explained a drop in accepts with two messages that turned out to be sent after all the invites had gone out. The cause came after the effect, and the real cause sat in the same log, unused. The same failure in outreach is worse, because the reader can check. When someone asks "where did you get that?", the thread is over. Duplicates hide here too. In our own sending, 44 people received two separate first touches (an invite note and a first message after accept) built on the same fact. For 17 of them the gap was under six hours, and in 29 of the 44 both texts opened with the same word. Each text looked unique on its own. ## How to apply 1. Collect facts from a named source: LinkedIn profile or post, company site, a data provider record, a news article, a job post. 2. Store each fact with `source_url`, `seen_at` and the exact wording. 3. Pick one fact that relates to what you sell. Decoration ("love your posts") does not count. 4. Check dates: a cause must come before the effect you connect it to. 5. If the fact does not fit in the message, shorten your conclusion, and keep the ground. 6. If a note with a fact alrea