Two questions get mixed together in account prioritization. The first is whether an account matches your ideal customer profile. The second is whether something suggests a need now. The first is fit. The second is intent, or timing.
They need different evidence, and they do different jobs in a queue. Fit decides who is on the list at all. Timing decides who goes first.
Each qualified account in Outlevo gets a Readiness Card with separate fit, intent and data quality scores. [[1]](#sources) A single blended score hides which of the two is doing the work.
Why fit is the filter and timing is the sort
Take an account that fits your ICP but shows no timing signal. It is still a reasonable account to contact, just later. Now take an account with a strong-looking signal that does not fit. Contacting it first means working a company you would not want as a customer.
So fit goes first, as a yes-or-no gate. Timing then orders whatever passed the gate. A timing signal can move an account up the queue. It should not let an account into the queue.
This only works if the fit definition is built on evidence. Outlevo learns the ideal customer from the deals you won and lost in HubSpot, which gives the fit side something to stand on. [[2]](#sources)
Small samples limit how far you can trust that definition. Outlevo's win/loss analysis counts companies, not deals. Under 10 won companies is labeled very low confidence. [[3]](#sources) If your fit definition rests on a handful of wins, treat it as a starting guess.
AI-proposed ICP segments are labeled experimental until a person approves them. [[3]](#sources) That label is the right posture for any fit rule you have not tested.
What changed
Several vendors sell timing signals as products. The details below are as read on the dates given, and prices may have moved since.
As read on 2026-11-09, Demandbase describes its product this way: "Demandbase turns signals into coordinated action across your entire GTM to prioritize the right accounts and drive revenue." [[4]](#sources) As read on 2026-10-29, Warmly sells a GTM Signals Package add-on at $10,000/year covering intent data, hiring activity, funding events and competitive intelligence. [[5]](#sources) As checked on 2026-11-06, Amplemarket lists AI intent signals on every plan, and job change alerts for 500 contacts on its Startup plan. [[6]](#sources) RB2B sells website visitor identification software, which is one source of timing signals. [[7]](#sources) As read on 2026-11-09, its free plan gives company-level ID with 150 resolutions a month. [[8]](#sources)
More signal sources mean more reasons to reorder a queue. If nothing sits in front of them, they also mean more ways to put the wrong account on top. You can compare what these tools cost on the intent data tools page.
Signals that look like intent but are not
Some signals feel like timing and carry less than they seem to. These are the ones worth checking before they move an account up.
A visit from a company that does not fit. Website-visitor tracking in Outlevo shows which companies visit, which pages they read and whether they fit your ICP. [[9]](#sources) The fit field is the point. A visit says a company's network loaded your pages. It says nothing about whether you want that company.
A visit treated as a person. Outlevo's visitor tracking never identifies a person or sets a cookie. [[9]](#sources) It tells you about an organization, not about who read the page or why. Do not write "the VP is researching us" from a company-level visit.
A visit count treated as complete. Browsers that send Do Not Track or Global Privacy Control, and automated browsers, send nothing at all. [[9]](#sources) The data is incomplete by design. A quiet account may simply be invisible, so low visit counts are not proof of low interest.
A signal with no date or source. A Readiness Card needs at least three observations, each with a source and a date. [[1]](#sources) Timing is about now. An observation with no date cannot tell you whether it is now.
A guess presented as a finding. Outlevo labels guesses as hypotheses, never as findings. [[1]](#sources) Apply the same rule to your own queue. If a reason for contacting an account is an inference, mark it as one.
A competitor mention on an account that fails fit. Outlevo's competitor tracking adds competitor signals to accounts, based on quoted facts from competitors' public pages. [[10]](#sources) That is useful context. It is still only context for an account that already passed the fit gate.
What to do
Build the rule in four steps. Then write it down so a person can approve it.
1. Define fit from won and lost accounts. Import past deals from your CRM or a CSV and run the win/loss analysis. [[11]](#sources) Read the confidence label before you trust the result. If you have no deal history yet, the free ICP assessment reads up to 5 public pages of your website. It returns facts labeled as verified observations or AI inferences, and up to 5 experimental segment hypotheses. [[12]](#sources)
2. Set the gate. An account that fails fit is not in the queue, whatever its timing signals say. Write the fit criteria as plain conditions a colleague can read.
3. Order by timing. Among accounts that passed, list which signals count, how recent they must be, and what source each needs. Keep data quality as its own check, as the Readiness Card does with its separate data quality score. [[1]](#sources) An account with a good fit score and thin evidence should be marked as thin, not quietly promoted.
4. Feed back what reps decide. In HubSpot, Outlevo writes status, fit and intent scores, reason, next action and due date to fields it owns, so fit and timing stay visible as separate fields. [[2]](#sources) Nothing is written until an owner or admin approves the field mapping. [[2]](#sources) In Salesforce, a rep's Accept or Reject on the Account is read back by the 15-minute sync. [[13]](#sources) A rep rejecting accounts that scored high on fit is a sign the fit definition needs work.
Writing it into a policy a person can approve
A prioritization rule that lives in someone's head cannot be reviewed. In Outlevo, policies set who can be contacted, on which channels, how often and with what budget. Nothing is sent outside a policy that a person approved. [[14]](#sources) Every external action is checked against the approved policy before it runs and is recorded in a ledger. [[14]](#sources)
A rule written for approval might read like this:
- Who is eligible. Accounts that match the approved ICP version. Accounts that do not match are not contacted, whatever their signals.
- Which markets. The countries you tell Outlevo you sell into. Outlevo asks which countries you sell into and never proposes markets. [[3]](#sources)
- What counts as timing. A short list of named signals, each with a required source and date, and a maximum age you choose.
- What does not count. A company-level visit alone, an undated observation, or an unlabeled inference.
- Order. Eligible accounts sort by timing. Ties go to the stronger evidence.
- Channels, frequency and budget. Set per the policy fields above.
- Stop conditions. Kill switches pause a campaign, a channel or the whole workspace at once. [[14]](#sources)
Add a line about law. The FTC states: "The law makes no exception for business-to-business email." [[15]](#sources) A well-fitting B2B list does not exempt a sender from CAN-SPAM. The ICO, for UK rules, says: "You can email or text any corporate body (a company, Scottish partnership, limited liability partnership or government body)." [[16]](#sources) In our reading, that list names corporate bodies only, so it does not cover every business recipient on a B2B list. Those two rules answer different questions, so put the one that applies to your markets in the policy and have the approver read it.
The approver does not need to understand scoring. They need to see who is eligible, what moves an account up, and what stops the work. If they can read the rule in a minute and disagree with a line, it is written well enough.
To go deeper, see how to qualify B2B accounts and lead vs account qualification.
Sources
- Readiness Cards
- HubSpot integration
- ICP from evidence
- Demandbase: positioning
- Warmly: pricing
- Amplemarket pricing
- RB2B: positioning
- RB2B: pricing
- Website visitors integration
- Release 2026-10-19
- Release 2026-10-19
- Free ICP assessment
- Salesforce integration
- How Outlevo works
- FTC: CAN-SPAM Act compliance guide for business
- ICO: Electronic mail marketing (PECR)