Definition
A buying signal is a checkable event, such as a job post, a relevant public comment, a launch, a leadership change or a tool migration, that makes it reasonable to research whether a company has a problem you can help with.
The event has to be something you can show a colleague. “They feel like a fit” is not a signal. Neither is a purchased score with no source attached.
TWL’s signal pages cover the types this site is willing to explain: competitor engagement, job posts, funding, new hires, keyword posts, stack changes, launches and leadership changes. Each one says how strong it is and how it fails.
Keep the source attached all the way to the TWL Reach draft. If the sender cannot see why the row exists, it is no longer a buying signal. It is a name.
Keep reading
Questions people ask
Are buying signals the same as intent?
People use the words loosely. This glossary keeps intent data as a separate entry. A signal is an event. Intent is often a model on top of events you do not see.
Which signal should we start with?
The one your buyer actually emits in public, and that you can check. Job posts and problem comments are the usual first pair.
Can an agent invent a signal?
No. If the source is missing, the row is not qualified. The system should make that hard to override quietly.
Where is the guide?
The buying signals guide on the blog is the longer practical piece.
Put the next workflow on the stack.
Start with the tool you need. Connect signals, TWL Reach and the rest of the system when the job is real.
Get TWL