Small Signals, Real Pipeline: A Two-Week Route From Website Intent to Sales Inbox

Most marketing leads we speak to have had the same meeting. Someone from a platform has shown them a slide with a vast, beautiful diagram — CDP in the middle, twelve arrows pointing at it, a number at the bottom with six figures in it. The promise: sales will know exactly who is interested and when. The reality: eighteen months, a change of CRM, and a project that never quite reaches the point where a rep actually changes what they do on a Tuesday morning.

It doesn't have to be that hard. The commercial value of website intent sits in a handful of behaviours, and most UK businesses can get them into a CRM in a fortnight with the tools they already own. Small, useful automation beats a grand programme almost every time — because it ships, and because someone actually uses it.

Intent is a behaviour, not a persona

We tend to talk about intent as though it's a quality people possess. It isn't. It's a pattern of behaviour over a short window, and the useful version is narrow: someone is comparing options, checking cost, or re-reading the same page for the third time in a week.

The signals worth treating as intent are the ones where a human would reasonably infer buying behaviour. Everything else is interest, curiosity or a student doing research. Keep those separate. A single blog visit is not a lead. A pricing page view followed by a returning session on the same service page and a second download is a person with a problem and a budget conversation ahead of them.

The three signals worth scoring

Pricing and commercial page visits. Not just any page with a number on it — your actual pricing page, your packages page, your 'how much does it cost' content. A second visit within seven days is a much stronger signal than the first.

Repeat content downloads. The same guide, PDF or comparison sheet downloaded twice, or two related assets in a short window, suggests someone building a case internally. That's the person who has to convince a colleague, and that's a person worth a phone call.

Returning visitors with depth. A visitor on their third session who has read three or more pages on a single service line, and hasn't filled in a form, is the single most under-worked segment on most B2B sites. They know who you are. They're deciding.

Score these in a simple, explainable way — say 10 points for a revisit, 15 for a pricing view, 25 for a repeated download, capped at 100. Resist the urge to build a forty-factor model. If a salesperson asks why someone scored 65, you should be able to answer in one sentence.

What your CRM actually needs

Four fields will do most of the work:

• Intent band — cold, warm, hot. Bands age better than raw scores because nobody argues about whether 61 is different from 64.
• Last high-intent action — a short label plus a date. 'Viewed pricing page, 4 Nov' is all a rep needs.
• Topic — which service line or product the behaviour relates to, so the alert routes to the right person rather than a general inbox.
• Consent and source status — what you know, how you know it, and whether the person has opted out of marketing.

Everything else is nice to have. Job title enrichment is lovely when it's accurate and actively misleading when it isn't, and a half-populated field is worse than no field because people stop trusting the record.

Alerts sales will actually read

One alert. One reason. One link.

If your reps are getting five notifications per lead, they're getting none. Pick a threshold that fires perhaps ten to twenty times a week, not two hundred. Route it to a channel they already inhabit — Teams or Slack rather than email, if that's where they live — and name the account owner where you have one. Where you don't, route by topic or by region.

Wording matters more than people expect. 'Acme Ltd hit 75: viewed pricing twice and downloaded the migration guide, 4 Nov' gets read. 'New lead score update' does not.

Staying on the right side of UK GDPR

This is where a lot of well-meaning setups come unstuck, so be deliberate.

Decide your lawful basis before you build anything. For most B2B intent tracking, legitimate interests is the realistic answer — but that means a documented legitimate interests assessment, not a sentence in a Notion page. Write down what you're tracking, why, what the individual would reasonably expect, and what safeguards you've applied. It takes an hour and it will save you an uncomfortable conversation later.

Cookie and analytics consent falls under PECR, which sits alongside GDPR rather than inside it. If your analytics or tracking depends on non-essential cookies, those need consent first. Configure your tag manager so that any intent event only fires after the appropriate consent state — and make sure the CRM sync respects it too.

Keep data minimisation honest. You don't need a full behavioural history; you need enough to justify an alert. Set a retention rule — twelve months on intent events is a reasonable starting default for most B2B — and make sure it actually deletes.

Finally, remember PECR treats sole traders and partnerships differently from limited companies when it comes to electronic marketing. B2B email to corporate subscribers is generally permitted with an opt-out, but 'generally' is doing a lot of work in that sentence. If your audience includes a lot of sole traders, check your approach with someone who knows your specific case rather than copying a template off the internet.

The two-week build

Week one is decisions, not development. Agree the three signals, tag the pages, confirm your consent states, map the four fields, and get one salesperson to agree the alert wording. Week two is plumbing: build the automation, test it with a handful of known contacts, send three alerts internally before going live, then turn it on.

Then measure the only thing that matters: did the alert change what a rep did? If nobody acted on twenty alerts in a month, the problem isn't the integration. It's the routing, the wording, or the fact that sales doesn't believe the data. Fix that before you add a fourth signal.

Intent data is not a dashboard. It's a nudge in the right place at roughly the right moment — and that's a much smaller engineering problem than most vendors would have you believe.