Buying signals follow up wins when sorted first

Alex Berman's guide on buying signals gives the rule in one line. Then match the sequence to intent, using Digital Sales Pro's cadence: 4 touches over 7 business days for high intent, 4 over 12 days for medium, 3 over 15 days for low. High-intent signals have a short shelf life. They need a same-day reply, ideally within hours. His examples are a pricing page visit and a demo request.

Think about why. A company reading your pricing page is doing a job right now. It's comparing you with someone else. By tomorrow that job may be done, and your message lands after the call has been made.

The same guide carries the uncomfortable number. Two-thirds of B2B buyers already have a shortlist before they surface to sales. A form fill that reaches you late may mean you're already off the list. An earlier, anonymous signal is one of the few ways in before the list closes.

"Within hours" needs two things. The alert has to go where someone looks today, not into a weekly report. And one named owner has to answer it. Pricing alerts with no owner get answered on Friday, and Friday is too late.

Here's where the rule doesn't apply. A company reading one blog post doesn't need a same-day message. A rushed reply to a weak signal reads as pushy, and it trains the company to ignore you. And if nobody can reply within the day, a same-day rule is one you'll break. Cover fewer signals and cover them well.

Do this today. Write down which signals in your business deserve a same-day reply. Put one owner's name next to each.

This guide starts once a signal has fired. To spot the signals in the first place, read identify buying signals.

Digital Sales Pro splits intent signals into four levels: high, medium, low and caution. Each level gets its own sequence length. Sending the same follow-up to every alert is the mistake this split exists to stop.

Here's how the levels read:

• High: a signal close to a buying step, like a pricing page visit or a demo request. Reply the same day, then run 4 touches over 7 business days.
• Medium: real interest, but no buying step yet. Run 4 touches over 12 days.
• Low: general interest. Run 3 touches over 15 days.
• Caution: one alert, such as a new VP hire, with no link to your problem. Verify first. No sequence yet.

The same-day timing comes from Alex Berman. The touch counts and day ranges come from Digital Sales Pro. Two guides, and they fit together without a fight.

Look at how the numbers move. High intent gets the tightest window because the decision is close. Medium keeps 4 touches but stretches them to 12 days. Low drops to 3 touches over 15 days. Less urgency means fewer pushes and more room between them.

What goes inside the touches matters as much as the count. For medium and low signals, a short guide or a checklist beats a meeting request. It gives the company something useful and keeps the door open until it decides to qualify itself. For high intent, be direct and name what the company looked at.

The caution row is the one most teams skip. It has no sequence. It has a check, and the last section covers it.

Where does this not apply? If you talk to a handful of companies a month, four levels is more process than you need. Two buckets are enough: reply now, or reply later. Add levels when alerts start piling up.

Next step: take the alerts you have right now and label each with one of the four levels. If you can't decide, it's probably caution.

Here's the gap in most guides. They list signal types, then list cadences by level, and stop. They rarely say what a rep should send when a known company reads a specific page on your own site, or how the order of pages changes the plan. The answer has four parts: timing, message, sequence and escalation.

Timing comes from the page. A pricing page or a demo form is high intent: reply the same day, ideally within hours, per Alex Berman. A case study view or a repeat visit is medium. A blog read is low. The message comes from the page too, because the company has already told you what it's asking. After a pricing visit, offer a demo or an ROI calculator. After a case study, share a similar customer story. After a blog post, share related content and don't ask for a meeting.

Sequence comes next, using Digital Sales Pro's counts: 4 touches over 7 business days for high, 4 over 12 days for medium, 3 over 15 days for low. Escalation is the part guides leave out. A company that comes back to pricing has told you more than one that came once, so move it up to the high row. A company that only returns to a blog post stays where it is.

Here's a worked example. It's an illustration, not a case from any source. A company reads your comparison page on Monday, then opens pricing on Tuesday. Neither visit says much alone. Together they say the company is choosing. The rep replies on Tuesday, within hours, and mentions the comparison.

• Touch 1: names the comparison page and offers a demo or an ROI calculator.
• Touch 2: adds a similar customer story.
• Touch 3: answers the objection a pricing visit usually raises.
• Touch 4: asks plainly whether the timing is right.

All four land inside the 7 business days. Now take a second company. It reads two blog posts and a case study over a few weeks and never opens pricing. That's medium at best. It gets 4 touches over 12 days, each with something useful and no meeting ask. If it opens pricing later, it jumps to the high row and gets a same-day reply.

What about the US and India? None of the four sources splits advice by country, so timing and cadence stay the same for both. What changes is around it. Quote prices in USD first, with the rupee amount beside it for an Indian reader. Privacy rules differ by country, so check your consent setup with your own legal review. Team size decides how many signals you can own.

Where does this break? On a site with little traffic. A few company visits a month won't show a return pattern, and the same-day rule will rarely fire. Always work at the company level: which companies came back, and what they read.

Chrysales makes a sharp point about where teams look. Most teams only track verbal signals, like a question about price or timelines. They miss the earlier behavioural signals, such as website visits and email engagement, which appear first.

That order matters. A verbal signal needs a conversation to exist already. A behavioural signal doesn't. A company can read several pages, come back, and never say a word to your team. If you only listen for words, it's invisible until it's deep in a decision.

You don't need new software to test this. You need a short list and a rule.

1. List your high-intent pages: pricing, comparison, case studies and the demo form.
2. Pull recent visits by company, and mark every company that reached one of those pages.
3. Mark the ones that came back. A return to pricing is your escalation trigger.
4. Set the same-day rule. When a known company hits a high-intent page, one owner replies within hours with a message that names the page.
5. Start the sequence by level: 4 touches over 7 business days for high, 4 over 12 for medium, 3 over 15 for low.
6. Leave low-intent pages, like blog reads, to automated content, and trigger outreach only from the high ones.

Page order is the part worth watching. A first visit to a blog, then a pricing page a week later, shows growing intent. A single pricing visit might not. Treat any path you spot, like pricing then comparison then docs, as a pattern to check against your own replies. It isn't a finding from any source.

Where does this fail? Little traffic. If only a handful of companies reach your site, there's no pattern to read. Rely on explicit inbound leads until you have enough data. And not every visit can be tied to a company. Some stay unknown, so a missing company isn't proof of low interest.

Run it for a few weeks. Then look at which pages the strongest replies came from, and move those pages up your list.

The B2B Playbook is blunt about this. A single alert, such as a new VP hire, doesn't equal buying intent. Before you reach out, verify what changed and whether it relates to the problem you solve.

Take the VP hire. It tells you the company changed. It doesn't tell you the company needs what you sell. A message that opens with "congrats on the new role, let's talk about our product" is built on nothing. The company can tell.

The check is short. What exactly changed? Does that change touch the problem you solve? Is there a second signal pointing the same way, such as a visit to your pricing page? One alert is a note. Alerts that agree are a reason to write.

A single pricing visit has the same problem. It could be a competitor doing research or a student writing a report. Repeat visits by the same company across several pages over a short period are much stronger.

Over-indexing on weak signals has a cost. You annoy the companies you write to, and you hurt your brand. You also burn effort the strong signals deserved. Verifying costs time too, and some real opportunities will wait a day longer than they should. That's still better than a name for noisy, irrelevant mail.

There's one exception. A demo request doesn't need verifying. It's the company telling you what it wants. Verify the ambiguous signals and answer the explicit ones.

Your move: add one question before any outreach goes out. "What changed, and does it touch what we solve?" If the answer is vague, the alert goes in the caution row and no sequence starts.

PageFox is the wrong choice if all you want is a raw list of companies to export. It gives you AI agents that work your leads: the Visitor Agent knows which companies are on your site, where it can resolve one, and the Chat and Enquiry agents answer every enquiry. With little traffic, the Visitor Agent has little to show; the Research Agent, rolling out now, finds the right people without it. Voice and Booking agents are coming soon.

Decide which pages on your site count as high intent, and name one owner who replies when a company reaches them. Then write the first message for each page before the next alert lands.