A buying signal is anything a prospect does that shows they’re getting closer to a decision, without actually telling you. Nobody emails a supplier to say “I’m three weeks from picking a vendor.” They just start behaving like it: revisiting the pricing page, opening the same email a second and third time, going quiet for two months and then reappearing right as their budget cycle opens. None of that arrives as a phone call. All of it is data, if anyone’s actually watching for it.

The Two Kinds of Buying Signal

Explicit signals are the ones that need no interpretation. A demo request. A direct pricing enquiry. A reply to an email. Someone is telling you outright that they’re interested and most sales teams already know to jump on these.

Implicit signals are the ones that matter just as much and get missed almost every time. A contact revisiting the pricing page for the third time this month. Opening the same email three separate times over two weeks. A contact’s job title changing on LinkedIn, which often means new budget authority they didn’t have last quarter. Their company announcing a funding round, or hiring for a role that maps directly to what you sell. None of these come with a notification saying “this one matters.” They just sit in the data, waiting for someone to notice.

Why Your CRM Sees the Signal but Doesn’t Act on It

Most CRMs are already logging every one of these events. The problem isn’t visibility, it’s that logging something and acting on it are two different jobs and most systems stop at the first one. A contact’s third pricing-page visit gets recorded exactly the same way as their first: no flag, no priority, no difference in how they’re treated the next morning. The signal is sitting right there in the system. Nothing happens because of it.

What Acting on a Signal Actually Looks Like

Not a mass email to everyone who touched the pricing page this quarter. It’s a specific trigger, say, a second pricing-page visit within seven days, generating an alert routed to the right person on the sales team, who follows up with something that actually reflects what that behaviour indicates, not a generic “just checking in.”

That’s the real difference between a system that reads signals and one that doesn’t: a rep following up because a monthly report happened to mention a name, versus a rep following up because they know specifically what that prospect is thinking about right now.

Why This Matters More Than It Sounds

Chasing cold leads costs money every single time. New ads, new outbound, new names, the acquisition cost resets with each one. Acting on a warm signal costs comparatively little, because the pipeline already exists, it just needs to be read properly. Most of the “new pipeline” a sales team spends its time chasing is often already sitting in the CRM, quietly signalling, completely unread.

If you want to see what this looks like end to end, from a first signal through to a closed deal, that’s the subject of the next post in this series, out this Friday.

In the meantime, if you’re not sure whether your own CRM already has this kind of data sitting unused, the Buyer’s Cycle Diagnostic will show you exactly what’s already there and what it’s telling you. Get your  diagnostic.