Signals, not lists: the order in which you should work your accounts
A list tells you who exists. A signal tells you who to contact today. How to rank accounts by signals, with approval and memory.
By lapersona team
Your accounts aren't a list. They're a set of companies that keep changing
A prospecting list is built once and starts aging on day one. Someone filters by industry, headcount and title, exports two thousand rows and splits them up. The rep starts with A, or with the account whose name rings a bell. It doesn't matter what happened at those companies this week: the order was set by a filter three months ago.
A signal is the opposite. It's an observable change at an account that justifies a conversation now: a funding round, a hire, a website visit, an inbound request or a change in the CRM. A signal doesn't say "this account fits". It says "this account just moved".
That shift in the question, from "who are they" to "who do I contact today", is the whole difference between a list and a live account queue.
A list answers "who are they". A signal answers "who do I contact today"
You need the list to define the universe. It isn't enough to order the work. Two accounts can both fit your ICP perfectly and sit in completely different moments: one just opened a new office, the other hasn't moved in two years. Sending both the same message wastes one of the two conversations.
Signal-based prospecting doesn't delete the list. It sorts it by what just happened. And because the order changes, the message changes too: the signal is the reason you're writing, not a decorative detail at the top of the email.
What signal-based prospecting actually is
It's a method that ranks your accounts by what just changed at each one (funding, hiring, website visits, inbound requests or CRM changes) and turns each change into a play with context, approval and memory. It doesn't order a list. It decides who to contact today and why.
The four signals you already have without buying another tool
You don't need a new vendor to start. Most teams already have access to these four families of signals.
- Funding and capacity. A round, an acquisition, a new business line or an expansion. The account has new budget or a new priority.
- Hiring. A company opening five roles on the same team is changing something. Hiring is one of the few signals you see before the company announces it.
- Website visits. An ICP account coming back to the product or pricing page is researching. They're not always buying, but they're always looking.
- CRM movement or an inbound request. An opportunity changing stage, a note that mentions a competitor, an email asking for details. It's the cheapest signal because it's already in your house.
A signal is worth what it lets you do: build the why before the message.
From signal to play: the why comes before the message
The sequence matters. Most teams start with the message: pick a template, personalise it with the name and the industry, drop it into a sequence. The result is an email that could have gone to anyone and, in practice, went to everyone.
The right sequence is different.
- Signal. What changed at the account, and when.
- Context. Who the person is, what the relationship is, what was said last time, what's still open.
- Play. What action makes sense: a message, a call, a letter, an invite, a meeting request.
- Approval. Who reviews it and who answers for it.
- Memory. What happened next and what the system learns for the next one.
The why is what turns a signal into a play. Without it, a signal only produces urgency. With it, a signal produces a conversation with context.
What you learn when a play is approved or rejected
An approval isn't just a control. It's information. When a rep approves a message, they're saying the angle fits the account. When they reject it, they're saying the system misread the context, the tone or the timing.
The same goes for replies, meetings and deal outcomes. If none of that goes back into the system, the team starts from scratch every Monday. If it does, the playbook improves: angles that work get repeated, angles that don't get fixed, and signals that never convert stop being prioritised.
That loop is the difference between automation that sends more and a system that executes better. Memory isn't a report. It's the reason tomorrow's play beats today's.
An account book worked by signals
In an anonymised case of our own in private banking, with 120 advisors, 2,100 accounts were reviewed by signal and 180 meetings arrived prepared. The number doesn't describe a prospecting trick. It describes a change of order. Instead of handing out a list and hoping each advisor found the moment, the system put the accounts that had moved up front and prepared the context for each conversation.
It's an example of the process, not a named reference and not a guarantee of results. What you can copy isn't the figure. It's the sequence: signal, context, play, approval, memory.
If your team is still working accounts alphabetically, you don't need a longer list. You need a way to decide which account deserves the next hour. The CRM stores the accounts. The tools flag the changes. lapersona turns those changes into executed work.
Create account → https://app.lapersona.ai/register
What we do → https://lapersona.ai/en#product