Reps ignore buying signals? Give each AE a weekly account list

Why do reps ignore buying signal alerts?

Reps ignore buying signal alerts because each one hands them 2 decisions nobody has made: whether the account deserves their time and what to do next. A rep with a full week of deals makes both decisions the quick way, by skipping the alert.

The pattern is old. About 70% of the leads marketing generates are never pursued by sales, the “sales lead black hole” named in a Journal of Marketing study.^↗ The study used data from 461 reps at 4 firms.^↗ It ties follow-up to lead volume, how well leads are prequalified and whether managers track follow-up.^↗ The more experienced the rep, the more the quality of prequalification counted and the less tracking and volume did.^↗ A fit gate is prequalification, and a weekly review is tracking: a weekly list builds in both.

The signals in a typical alert feed get the least action. In a September 2026 survey of 300 software GTM leaders, 52% said their teams act on content engagement.^↗ Only 24% act on leadership changes, 17% on company events and 14% on tech changes.^↗

Skipping has a cost: 94% of B2B buyers rank their preferred vendors before they first contact a seller.^↗ An account nobody worked this month may have a favourite by next month.

Signal guides list dozens of types, from funding and new executives to competitor changes and expansion. For a weekly list, the type matters less than 2 facts about each signal: which account it lands on and how long its window stays open.

Filter every buying signal through the target account list first

A signal earns a place on the weekly list only if it lands on a tier 1 or tier 2 account on your target account list. Everything else is logged against the account, where it counts when you re-tier, and goes no further. Run this gate the day a signal arrives, so every signal that passes has an owner and an action that day.

Fit works as a gate here: no signal, however loud, can outweigh it. A weighted account score can let a funding round lift a poor-fit account above a quiet tier 1 account. It can happen whenever signal strength and recency together carry more weight than fit. A Forrester analyst warns against letting intent signals stand in for qualification.^↗ Your target account list is the team’s qualification decision; the weekly list only decides the order.

In our experience, stacking rules, which wait for 2 or 3 signals before anyone acts, suit noisy web signals. On a tier 1 or 2 account, a single grant agreement or end-of-support notice is enough for an entry, and later signals join it.

Some signals skip the list. A signal on an account with an open deal goes to the deal owner as a note. A hand-raise, such as a demo request, an RFP or a reply, goes to its owner the same day. So does any signal whose window closes within the week.

The step most alert feeds skip is naming the next contact. A typical buying decision involves 13 internal stakeholders and 9 external influencers, by Forrester’s 2026 count.^↗ “Contact the account” gives a rep nothing to do. Name the buying group role the signal opens that nobody has engaged yet. A funding award opens the budget owner. A new leader opens their own seat. A vendor’s end-of-life notice opens whoever runs the system it retires.

Each entry then carries 4 fields: one owner, the next contact by role and name, this week’s action with its day and the date the window closes. Link the research brief if you have one; the entry itself should fit on one line of a CRM view.

How many target accounts should each AE work a week?

Each AE should get as many target accounts as the hours they keep for new accounts allow, and no more. Work the cap out from capacity; how many signals came in doesn’t matter.

In this illustration, an AE keeps 6 hours a week for list work. Each entry takes about 45 minutes: 15 to read the account, its buying group map and the signal, then 30 for the action and the CRM note. That gives 6 × 60 ÷ 45 = 8 accounts. If 3 entries from last week are still in progress inside their window, they keep their slots, so 5 new accounts join this week. Put in your own hours and minutes; the arithmetic stays the same.

The cap makes a hidden choice visible. In the same illustration, if 60 alerts a week reach 4 AEs as a feed, each AE sees 15 and can work 8. The other 7 get skipped, and nobody chose which. With a list, they wait in a queue ranked by the date their window closes, where the manager can see them.

Revisit the cap after 4 weeks. If most entries are done by Wednesday, raise it; if entries keep rolling over, lower it.

Measure target accounts acted on against a baseline

Track one number every week: the share of listed accounts whose action got done, against the same share for alerts before the list existed. Without that baseline, any acted-on rate looks like progress.

Take the baseline first. Pull the last 8 weeks of alerts on tier 1 and 2 accounts, or all alerts if the tiers are new, and count how many were followed by a logged activity within 7 days. In our audits we score this measure from 1 to 5.^↗ Under 10% acted on scores 1; over 75%, with a named owner and a weekly review, scores 5.^↗

The manager reviews each AE’s list and queue on Monday, and every entry closes on Friday with one of 4 outcomes:

• Engaged: the next contact replied, took a call or met. The account now counts as qualified: open an opportunity or keep the entry and name the next contact.
• Touched, no reply: the action was done, and the entry stays while its window is open.
• Not done: the reason goes in the note. After 2 weeks not done, the entry goes back to the queue.
• Window closed: the entry leaves the list and counts as a miss.

Engaged is the bar because at this deal size one contact rarely carries the decision. In Gong’s analysis of 1.8M deals, multi-threading lifted win rates 130% on deals over $50k.^↗ An email sent is activity. A reply from someone in the buying group is progress.

Report at least one miss every week, by name: an entry not done, a window that closed or an account that moved while it sat outside the list. An illustrative report line: “Week 3: 13 of 16 entries acted on, against a baseline of 14%; 4 engaged; missed: 2 new-GM intros (both AEs in renewals) and a tier 3 account that signed with a competitor after a grant agreement we logged.” A miss like the last one tells you the tiers need another look.

One list for new grant agreements, new GMs and end-of-life notices

For a vendor selling to ISPs, all 3 alerts fit one weekly list once each has a window and a next contact. Grant agreements go on first, new GMs next and a competitor’s end-of-life notice is spread over several weeks.

The grant alerts are arriving fast. By 3 November 2026, NTIA’s dashboard showed all 56 US states and territories with approved final proposals and signed award agreements for BEAD, the federal broadband grant programme.^↗ Each state then signs agreements with its subgrantees, and every signing can trigger an alert. The list of buyers is finite: NTCA alone represents about 850 independent, community-based providers.^↗

By Panelhop’s estimate, a BEAD subgrant agreement opens a window of 1–6 months.^↗ A new general manager or CFO reviews vendors in their first 3–6 months.^↗ A billing or OSS end of support gives operators 6–18 months to switch.^↗ All 3 windows are Panelhop estimates from public research. The grant goes first because its window can close soonest and it brings new subscribers, construction and reporting duties. At a rural telco the general manager usually runs the evaluation and the board signs.^↗ By the same estimate, 5–8 people plus the board decide.^↗

Here is one week for a billing software vendor with 2 AEs and a target account list of 400 ISPs and rural telcos, as an illustration. In that week, 7 grant agreements, 3 new GMs and 1 end-of-life notice make 44 account alerts. The notice alone hits 34 accounts running the retiring product. The gate passes 22 on tier 1 or 2 accounts: 5 grants, 2 new GMs and 15 end-of-life accounts. Of those, 2 end-of-life accounts have open deals and go to their owners. A single account has both a grant and the notice, which leaves 19 accounts. The 2 AEs have 8 slots each; 5 are still taken from last week, so 11 are free. The 5 grant accounts and 2 new GMs go on first. The 4 end-of-life accounts whose contracts end soonest fill the rest. The other 8 wait, ranked; with a window of months, a short wait in the queue costs them little.

A buying signal is a start line, not an action

We think a buying signal only tells you where to start: the action has to be decided before the alert reaches a rep. Reps who ignore alerts are making a sensible call about a broken process. An alert asks a rep to decide which accounts deserve effort and what the next move is. In our experience, nobody upstream has decided either. That is a routing and process gap, and buying more signals only adds to the pile.

So we make those decisions before the alert. We let the target account list decide who qualifies. In our experience, a shorter list scored strictly on fit gets more out of the same signals than a long, loose one. Each entry has a single owner, because a shared queue spreads the responsibility and nobody notices when it stalls. And an account counts as qualified only once someone in its buying group engages; a sent email doesn’t count.

We don’t say intent data is useless, or that signals alone predict a purchase. We do think the weekly report should name at least one miss. A report with none usually means the gate is hiding them, and the misses tell you whether the tiers, the cap or the actions are wrong.