From Signal to Sales-Ready: A Research-Backed Framework for B2B Pipeline Readiness

What the research says before the framework starts

The evidence behind this publication points in the same direction: B2B teams should be careful about treating one visible action as proof that a buying process is ready for sales. Preferences form early, content consumption can lag form submission, hidden stakeholders influence decisions, and ABM is increasingly converging with demand generation.

The IVRIS Pipeline Readiness Framework

The six dimensions deliberately answer different questions. A strong score in one dimension should not erase a weakness in another.

Why pipeline readiness is hard

The Buyer Readiness Gap

B2B revenue teams often compress several different events into a single label such as “hot lead.” That compression creates avoidable friction.

What the labels conceal

• An identified account may be attractive but inactive.
• An intent signal may reflect learning, competitor research or an existing customer’s activity.
• A content response may reflect interest in an idea rather than interest in a vendor.
• A qualified contact may be relevant but not empowered.
• A booked meeting may be poorly contextualized, rescheduled or unattended.
• An opportunity may exist in the CRM without a validated buying process.

The readiness gap appears when the strength of the evidence is lower than the urgency of the action.

A better question

Do not ask only, “Is this a lead?” Ask:

What do we know, how do we know it, how current is it, and what action is proportionate to that evidence?

A mature system protects the buyer from premature outreach and protects sales from context-poor handoffs.

Four principles for a defensible readiness system

Principle 1 – Treat readiness as multidimensional

No single signal should carry the full decision. Fit without timing creates wasted effort. Intent without fit creates false urgency. Engagement without validation creates operational noise.

Principle 2 – Separate evidence from interpretation

A page visit is evidence. “The account is ready to buy” is an interpretation. Record both separately so the interpretation can be challenged and improved.

Principle 3 – Match action to evidence strength

A newsletter click may justify nurture. A repeat visit from multiple stakeholders may justify account research. A direct request, verified need and agreed next step may justify immediate sales action.

Principle 4 – Make every handoff teach the system

Sales acceptance, rejection, contact, meeting and opportunity outcomes should flow back into targeting and qualification. Without feedback, the same errors repeat at higher volume.

Readiness is not a permanent property of an account. It is a time-sensitive operating decision.

The practical test

Before routing anything to sales, a team should be able to state:

1. Why this account?
2. Why this person or buying group?
3. Why now?
4. Why this action?
5. What happens if the evidence is incomplete?

Shared definitions before shared dashboards

Terminology varies across companies, providers and technology platforms. The labels matter less than the written entry and exit criteria behind them.

In this research, these labels are treated as operational categories rather than universal market standards. Each organization should define the entry criteria, required evidence, permitted unknowns, owner and exit condition for every stage it uses.

Important: HQL is not a universally standardized market category. Define it contractually and operationally before using it in reporting.

The IVRIS Pipeline Readiness Framework

The framework is a decision architecture, not a fixed algorithm. Each dimension answers a different question.

How to apply it

1. Capture raw evidence.
2. Score or categorize each dimension.
3. Identify missing information.
4. Select the least aggressive action that can still advance learning.
5. Record the outcome.
6. Update the criteria based on real progression.

The six dimensions of pipeline readiness

1. Account fit: should this organization buy from us?

Account fit establishes whether the company belongs in the addressable market. It is primarily a structural assessment and should be kept distinct from current buying activity.

Fit inputs

• industry and sub-industry;
• employee and revenue bands;
• geography and serviceability;
• business model;
• technology environment;
• regulatory or operational requirements;
• known use case;
• product complexity and contract value;
• similarity to successful customer profiles;
• exclusion criteria.

Recommended fit tiers

Questions to resolve

• Is the ICP written as observable criteria rather than adjectives?
• Are exclusions as explicit as inclusions?
• Can sales explain why a recently won account fit?
• Are current customers automatically assumed to be ideal, even when they were hard to serve?

Fit tells you where to invest attention. It does not tell you when to sell.

The core framework intentionally uses fit tiers rather than a universal numeric fit score. If your organization already uses a numeric model, calibrate its thresholds against your own won, lost and disqualified accounts instead of importing vendor cut-points.

2. Buyer intent: is research activity changing?

Intent data is most useful when it changes a decision. It should help a team identify a pattern that deserves monitoring, personalization, validation or faster action.

Evaluate intent across five qualities

1. Relevance – does the topic map to a real buying problem?
2. Recency – how recently did activity change?
3. Intensity – how strong is the increase relative to normal behavior?
4. Breadth – are several related topics active?
5. Corroboration – is there supporting first-party or human evidence?

Intent interpretation ladder

Guardrails

• Do not equate anonymous account activity with one individual’s intent.
• Review topic quality; generic topics create generic signals.
• Use intent as a prioritization input, not a legal basis for intrusive personalization.
• Record the date of the signal. Old intent should decay.

Intent answers “why now?” only when it is relevant, recent and corroborated.

3. Engagement: what did the buyer actually do?

Engagement should be assessed by depth, recency, repetition and context, not counted as a flat list of clicks.

A practical engagement hierarchy

Do not flatten content formats

A playbook, research report, checklist, case study, technical guide and pricing page serve different jobs. The asset’s role in the buying journey should influence the next action.

NetLine’s 2026 research reported a 47.7-hour average delay between content request and consumption. ^R2 This supports a two-stage response to a content registration:

• confirm delivery and offer help immediately;
• delay hard-sell outreach until the buyer has had a reasonable opportunity to engage, unless stronger signals justify speed.

Account-level view

One download may be a person learning. Three relevant contacts engaging with different evaluation assets may indicate organizational momentum. Track both contact activity and account aggregation.

4. Data validity: can the record be trusted and used?

Qualification built on unreliable data creates false precision. Data validity should be a formal stage, not an invisible back-office task.

Minimum validation controls

• business email status;
• telephone availability and verification where required;
• current company and role;
• job function and seniority normalization;
• company domain and account match;
• geography and time zone;
• duplicate and suppression checks;
• campaign-source integrity;
• applicable consent, notice and processing rules;
• timestamp and freshness.

A usable record should answer

1. Who is the person?
2. Which account do they belong to?
3. What source or action created the record?
4. When did the event occur?
5. Which criteria were verified?
6. Which criteria remain unknown?
7. What communication is permitted?

Data quality states

A high score cannot rescue a low-trust record.

5. Human qualification: what has the buyer confirmed?

Human qualification converts signals into context. Its purpose is not to interrogate every respondent. Its purpose is to reduce uncertainty enough to choose the right next step.

Progressive qualification

Early-stage confirmation

• role and responsibility;
• relevance of the topic;
• current priority or learning objective;
• preferred content or next resource.

Mid-stage confirmation

• problem or initiative;
• current approach;
• impact of the problem;
• stakeholders involved;
• evaluation stage.

Late-stage confirmation

• decision process;
• implementation window;
• commercial constraints;
• authority and influence;
• agreed meeting purpose and next step.

Qualification quality rules

• Record the buyer’s words, not only a score.
• Preserve “unknown” as a valid answer.
• Separate confirmed facts from rep inference.
• Avoid forcing budget disclosure before value is established.
• Use consistent questions while allowing natural conversation.
• Capture disqualifying information without treating it as failure.

When BANT helps – and when it harms

BANT can structure late-stage information, but applying it rigidly at first touch can reject legitimate buyers who have not yet built a budget or formal timeline. Use it as a diagnostic lens, not a script that every early-stage buyer must pass.

6. Sales action: what should happen next?

Readiness should culminate in an explicit action. “Send to sales” is too vague to operate or measure.

Action categories

Action design principles

• Define the owner and service-level expectation.
• Attach the evidence that triggered the action.
• Specify the objective of the next touch.
• Identify the next-best action if there is no response.
• Set a review or expiry date.

A sales action should answer:

What should this person do, by when, with what context, to learn or advance what?

The action layer is deliberately explicit: scoring matters only when it changes ownership, timing, context or the next-best action.

Decision logic, timing and buying groups

The Fit-Intent-Engagement decision matrix

Use this matrix as a starting point, then refine it with your own outcomes.

High fit + strong intent + meaningful engagement

Default action: rapid human validation or sales engagement. Confirm the trigger, buying group and meeting purpose.

High fit + strong intent + weak engagement

Default action: account-level personalization, targeted content and selective outreach. Do not assume the anonymous signal belongs to a known contact.

High fit + weak intent + meaningful engagement

Default action: nurture around the engaged topic and monitor for additional account activity. The account may be strategically valuable but not in market.

Lower fit + strong intent + meaningful engagement

Default action: review the ICP and the signal. This may reveal a new segment, a partner use case or misleading intent.

Lower fit + weak intent + weak engagement

Default action: deprioritize. Do not use expensive human follow-up merely because the record exists.

The matrix prevents two common errors: overreacting to weak evidence and ignoring strong combinations because no single field crossed a threshold.

The two-clock model for content-generated leads

A content response starts two different clocks.

Clock 1 – the buyer’s consumption clock

The buyer needs time to open, read, share or evaluate the asset. NetLine’s 2026 research places the average request-to-consumption gap at 47.7 hours. ^R2

Clock 2 – the revenue team’s responsiveness clock

The company must still acknowledge the action quickly, preserve context and be available when the buyer is ready.

Recommended starting policy

Immediately

• deliver the asset;
• confirm the request;
• provide one related resource;
• state that help is available without forcing a meeting.

After approximately 48 hours

• use a contextual, low-pressure follow-up for long-form content;
• ask one relevant question;
• reference the problem, not merely the download.

Accelerate when stronger evidence exists

Move faster when the buyer requested contact, visited high-intent pages, engaged repeatedly, matched a high-priority account or directly confirmed a current initiative.

Speed should be proportional to expressed intent, not merely to lead capture.

Read the account, not only the form fill

6sense’s research describes typical B2B buying groups of more than 10 people in substantial purchases and finds that much of vendor selection occurs before seller engagement. ^R1 Edelman and LinkedIn’s 2025 work highlights hidden buyers whose influence may not be visible in early seller interactions. ^R4

Common buying-group roles

• business champion;
• day-to-day user or practitioner;
• technical evaluator;
• security, legal or compliance reviewer;
• procurement;
• financial approver;
• executive sponsor;
• implementation owner;
• blocker or risk owner.

Account-readiness indicators

• more than one relevant contact engaging;
• different roles consuming complementary assets;
• repeated activity over a short period;
• engagement moving from education to evaluation;
• internal sharing or referral patterns;
• direct questions from risk, finance or implementation stakeholders.

Operating response

Do not ask one contact to represent the entire committee. Equip the champion with materials that help internal alignment: business cases, technical validation, risk responses, implementation plans and role-specific summaries.

A lead becomes more valuable when it helps reveal the buying system around it.

Match content to the buyer’s readiness task

Content should help the buyer complete the next decision task – not simply describe the vendor.

CMI’s 2026 study found that nearly all surveyed B2B marketers produce thought leadership, but few operate mature programs. ^R3 Edelman and LinkedIn emphasize that strong, perspective-shifting content can influence hidden buyers and help less familiar brands gain advocacy. ^R4

Content-readiness test

For every asset, document:

• target role;
• buyer task;
• stage assumption;
• next-best action;
• evidence that would justify escalation.

Qualification, handoff and routing

MQL, HQL and BANT: a qualification continuum

These categories should describe increasing information depth, not automatically increasing deal probability.

Design rules

1. Define each category in one page of operational criteria.
2. List required fields and permitted unknowns.
3. Separate lead delivery from sales acceptance.
4. Track progression by source and category.
5. Do not use the labels as substitutes for buyer context.

The labels are useful only when they describe a real difference in evidence depth, operating ownership or next action. Avoid treating them as interchangeable lead-quality badges.

Progressive qualification question bank

Use the fewest questions required to choose the next action. Do not ask every question in one conversation.

Relevance and role

• What prompted your interest in this topic?
• Which part of the issue sits within your responsibility?
• Who else is affected by the problem?

Current state and impact

• How are you handling this today?
• Where does the current approach create cost, delay, risk or missed opportunity?
• What happens if the issue remains unchanged?

Priority and trigger

• Has anything changed that makes this more important now?
• Is this exploratory research or part of an active initiative?
• What would make the project move forward?

Buying process

• Which teams need to evaluate or approve a change?
• What information will those stakeholders require?
• Is there an existing decision process or procurement path?

Timing and commercial context

• Is there a target window for evaluating or implementing a solution?
• Has funding been allocated, planned or not yet discussed?
• Which constraints are most likely to affect the decision?

Next step

• What would be the most useful next conversation or resource?
• Who should participate?
• What should be true at the end of that next step?

Good qualification helps the buyer clarify the decision; poor qualification merely extracts fields.

The minimum viable sales handoff packet

A salesperson should not need to reconstruct the lead’s history from multiple tools before deciding whether to act.

Required handoff fields

Quality standard

The handoff should distinguish:

• observed evidence;
• buyer-confirmed information;
• system-generated inference;
• rep interpretation;
• unknown information.

Acceptance workflow

Sales should accept, reject or recycle the handoff using standardized reasons. Silence is not a valid status.

A complete handoff reduces sales research time and makes rejection data more useful.

Lead and account routing decision tree

Route to direct sales engagement when

• fit is strong;
• contact data is valid;
• the buyer has requested interaction or confirmed a meaningful initiative;
• the account shows corroborating intent or engagement;
• the sales objective is clear.

Route to human validation when

• signals are strong but need, role, timing or account context remains uncertain;
• the contact is relevant but not clearly part of the buying process;
• anonymous account activity needs a known-contact bridge.

Route to nurture when

• fit is strong but readiness evidence is limited;
• the buyer is educating themselves;
• timing is future-dated;
• the account is strategic but not yet active.

Route to enrichment or hold when

• data is incomplete, conflicted or stale;
• the account match is uncertain;
• compliance or suppression status is unresolved.

Disqualify when

• the account fails non-negotiable ICP or serviceability criteria;
• the record is invalid or prohibited;
• the use case is outside the offer;
• the buyer explicitly declines further contact.

Response policy, measurement and feedback

Design a response policy, not one universal speed rule

The right response time depends on the action that created the lead.

SLA fields

• trigger type;
• priority tier;
• owner;
• response window;
• first-touch objective;
• maximum attempts;
• recycling rule;
• escalation path;
• accepted and rejected outcomes.

Avoid the false choice between speed and patience

Responsiveness can be immediate without being aggressive. Confirm delivery quickly. Make help available. Reserve hard-sell sequences for evidence that warrants them.

Measure progression, not only production

Core metrics and formulas

Reporting principles

• Report counts with percentages.
• Separate booked from held meetings.
• Segment by program, source, account tier and signal combination.
• Track contacts and accounts separately.
• Use consistent outcome windows.
• Do not claim revenue impact where attribution is incomplete.

Turn rejection into operating intelligence

A rejected lead is not automatically a bad lead. It may reveal a targeting, timing, data, handoff, capacity or sales-execution problem.

Recommended rejection taxonomy

Monthly feedback review

1. Review top rejection reasons by volume and value.
2. Sample accepted and rejected records for quality.
3. Compare reasons across sales teams and regions.
4. Identify criteria that need clarification.
5. Publish changes to the data dictionary and routing rules.
6. Measure whether the change improves downstream progression.

The goal is not to eliminate rejection. It is to make every rejection specific, learnable and actionable.

Maturity and self-assessment

Pipeline readiness maturity model

Level 1 – Volume-led

Primary question: How many leads were delivered?
Risk: quantity obscures validity, acceptance and progression.

Level 2 – Definition-led

Primary question: Do marketing and sales use documented stages?
Capability: shared terms, required fields and rejection reasons.

Level 3 – Signal-led

Primary question: How do fit, intent and engagement change priority?
Capability: account scoring, signal recency and tiered actions.

Level 4 – Qualification-led

Primary question: What has the buyer confirmed, and what remains unknown?
Capability: progressive qualification, contextual handoffs and stage entry criteria.

Level 5 – Pipeline-orchestrated

Primary question: Which combinations of accounts, signals, content and actions create sustainable progression?
Capability: contact and account measurement, closed feedback loops, governance and continuous refinement.

Maturity is not the amount of technology deployed. It is the consistency with which evidence becomes action and outcomes become learning.

Pipeline readiness self-assessment

Score each statement: 0 = no, 1 = partly or inconsistently, 2 = yes and consistently.

Score interpretation

• 0-9: Volume-led
• 10-18: Definition-led
• 19-27: Signal-led
• 28-32: Qualification-led
• 33-36: Pipeline-orchestrated

Implementation roadmap and operating checklists

A 90-day implementation roadmap

Days 1-30 – Define and baseline

• appoint an executive sponsor and operating owner;
• document ICP inclusion and exclusion criteria;
• define lifecycle stages and required fields;
• create a data dictionary;
• standardize acceptance, rejection and recycle reasons;
• baseline current volumes and progression where available;
• identify privacy, consent and system constraints.

Days 31-60 – Build and pilot

• configure fit, intent and engagement categories;
• create progressive qualification questions;
• design handoff packets and routing rules;
• set response policies by trigger;
• build nurture and recycle paths;
• instrument contact and account-level metrics;
• train a pilot marketing and sales team.

Days 61-90 – Learn and scale

• review accepted, rejected and stalled records;
• compare outcomes by signal combination;
• refine thresholds and questions;
• remove fields that do not change decisions;
• publish version-controlled operating rules;
• expand to additional programs or teams;
• establish a monthly governance meeting.

Day-90 deliverable

A one-page operating policy that states: stages, evidence, owners, response times, handoff requirements, outcomes and review cadence.

Pipeline readiness operating checklist

Strategy and definitions

• [ ] ICP and exclusion criteria are documented.
• [ ] Contact and account stages are separately defined.
• [ ] MQL, HQL, BANT, SAL, SQL and opportunity criteria are approved.
• [ ] Each stage has required fields, owner and exit criteria.

Signals and data

• [ ] Intent topics map to real buyer problems.
• [ ] Signal recency and decay rules are documented.
• [ ] Engagement is classified by depth and format.
• [ ] Duplicate, stale, conflicted and invalid records have handling rules.
• [ ] Consent, suppression and communication status are visible.

Qualification and handoff

• [ ] Qualification questions are progressive.
• [ ] Confirmed facts are separated from inference.
• [ ] Unknowns are preserved rather than guessed.
• [ ] Every sales handoff includes account, contact, source, signals and context.
• [ ] The recommended next action and objective are explicit.

Routing and follow-up

• [ ] Response policies vary by trigger.
• [ ] Content downloads are not treated like direct contact requests.
• [ ] Every routed item has an owner and service-level expectation.
• [ ] Nurture, recycle, enrichment and disqualification paths exist.

Measurement and governance

• [ ] Booked and held meetings are reported separately.
• [ ] Sales acceptance and rejection reasons are mandatory.
• [ ] Contact and account metrics are both reported.
• [ ] Outcome windows and attribution rules are documented.
• [ ] A monthly review changes rules based on evidence.

Demand-generation partner evaluation checklist

Use this checklist when assessing a content syndication, lead-generation, intent, ABM or qualification partner.

Targeting and methodology

• [ ] Can the provider explain how accounts and contacts are selected?
• [ ] Are fit, intent and engagement inputs distinguishable?
• [ ] Are data sources, validation steps and freshness standards documented?
• [ ] Can the provider support account-level and buying-group views?

Qualification

• [ ] Are MQL, HQL and BANT definitions written into the campaign agreement?
• [ ] Are required questions, permitted unknowns and disqualifiers explicit?
• [ ] Is human qualification recorded as structured data and notes?
• [ ] Can qualification scripts be adapted to the buyer’s stage?

Delivery and operations

• [ ] Are lead fields mapped to the CRM or marketing automation platform?
• [ ] Does each record include source, timestamp and campaign context?
• [ ] Is there a clear replacement, rejection and dispute process?
• [ ] Are service levels and delivery timing documented?

Privacy and governance

• [ ] Can the provider explain applicable consent and notice practices?
• [ ] Are suppression, opt-out and data-subject processes supported?
• [ ] Are data retention and security responsibilities defined?

Measurement

• [ ] Will the provider accept downstream feedback?
• [ ] Can performance be reviewed beyond cost per lead?
• [ ] Are booked and held meetings separated?
• [ ] Can reporting be segmented by source, account tier and qualification type?

Choose the partner that can explain its operating system, not only its volume.

Putting pipeline readiness into practice

Putting pipeline readiness into practice

The framework is most useful when it changes a real operating decision. Do not begin by rebuilding the entire funnel or replacing every existing score. Start with one high-friction handoff, one routing rule or one source of disagreement between marketing and sales.

A practical implementation sequence is:

1. Choose one decision to improve. For example: when a content-generated lead should move from nurture to human validation.
2. Write the evidence required for that decision. Separate fit, intent, engagement, data validity and buyer-confirmed information.
3. Run the framework in shadow mode. Score or categorize records without changing live routing at first.
4. Compare the recommendation with the actual outcome. Review acceptance, contact, meeting, progression, recycle and rejection reasons.
5. Adjust cut-points, not the principles. Keep the evidence categories stable while calibrating thresholds to your sales motion.
6. Document the rule and owner. A working system needs written definitions, response windows, exception logic and feedback.

The goal is not a more complicated lead score. It is a more explainable decision about where human attention should go next.

Research application note

The models, thresholds and examples in this publication are starting points. They should be adapted to the organization’s market, average contract value, buying cycle, sales capacity, data quality, consent requirements and observed progression.

The Pipeline Readiness Score in Appendix A is intentionally designed so that teams can test it alongside an existing routing model before replacing anything. The most useful calibration data will come from your own accepted, rejected, recycled and progressed records.

About IVRIS Tech Research

IVRIS Tech publishes practical B2B marketing research, frameworks and operating guidance designed to connect demand generation, content, lifecycle systems, CRM, analytics and sales execution.

For teams that need implementation support, IVRIS Tech’s work spans B2B marketing automation and CRM, marketing analytics and attribution, content strategy, lifecycle marketing and related growth systems.

Publisher: IVRIS Tech
Website: ivristech.com
Next step: Explore IVRIS Tech services if you need implementation support adapting the framework to your operating model.

Methodology and references

Research methodology and references

Methodology

This research was prepared through desk research completed in August 2026 and editorially revised for IVRIS Tech in September 2026. It prioritizes primary studies and official source material published or updated in 2025-2026. No proprietary IVRIS Tech client dataset, original survey or customer performance benchmark is presented. The framework, score and recommended thresholds are operating hypotheses and starting points that should be validated against each organization’s market, sales cycle, systems, legal obligations and observed outcomes.

References

R1. 6sense. 2025 B2B Buyer Experience Report: How AI Is (and Isn’t) Disrupting Buying Journeys. Nearly 4,000 B2B buyer responses across regions; accessed August 22, 2026.
https://6sense.com/science-of-b2b/buyer-experience-report-2025/

R2. NetLine. Consumption Is Changing: Navigating AI and the Widening 48-Hour Consumption Gap, introducing the 2026 State of B2B Content Consumption and Demand Report. Published April 7, 2026; accessed August 22, 2026.
https://blog.netline.com/consumption-is-changing-introducing-the-2026-report/

R3. Content Marketing Institute. B2B Content and Marketing Trends: Insights for 2026. Research covering more than 1,000 B2B marketers. Published October 8, 2025; accessed August 22, 2026.
https://contentmarketinginstitute.com/b2b-research/b2b-content-marketing-trends-research

R4. Edelman and LinkedIn. 2025 B2B Thought Leadership Impact Report: Invisible Influence – Unlocking the Power of Hidden Buyers. Nearly 2,000 global professionals; published June 26, 2025; accessed August 22, 2026.
https://www.edelman.com/expertise/Business-Marketing/2025-b2b-thought-leadership-report

R5. Demand Gen Report. 2025 Account-Based Marketing Benchmark Survey. Published 2025; accessed August 22, 2026.
https://www.demandgenreport.com/resources/2025-account-based-marketing-benchmark-survey/50610/

Publication note

This document provides general marketing and revenue-operations guidance. It is not legal, privacy, financial or compliance advice. Organizations should obtain appropriate professional review for their specific obligations.

Appendix A: Pipeline Readiness Score

The Pipeline Readiness Score

This appendix specifies the method behind step 2 of the framework on page 8. Every input is drawn from criteria already defined in this research, and the model can be applied manually before it is automated.

Pipeline Readiness Score (PRS):

(Account fit + Buyer intent + Engagement + Human qualification) × Data validity = PRS (0-100)

Each scored dimension contributes up to 25 points. Data validity acts as a multiplier rather than a fifth scored dimension.

Gate 1 – Serviceability

Fit tier D (out of profile) → Disqualify. Do not score.

Gate 2 – Permission

Consent, suppression or an explicit decline prohibits contact → Suppress.

Data validity multiplier

Validity is a multiplier, not a scored dimension. That makes the rule on page 12 operational: a high score cannot rescue a low-trust record.

Account fit – 25 points

These point values are illustrative. Calibrate the fit model against your own won, lost and disqualified accounts before adopting it.

Buyer intent – 25 points

Score the five intent qualities from page 10 at up to five points each.

Corroboration is the load-bearing input. Breadth and intensity describe a pattern; corroboration asks whether a real person at the account did something you can point to.

Applying the score

1. Score the account, then the record. Fit and intent are account-level. Engagement and qualification are contact-level. Keep them visible separately.
2. Write down what you assumed. Record assumptions about tier, data state and attribution beside the number.
3. Ship the breakdown, not the total. “PRS 68” is less useful than “68 – fit 18, intent 23, engagement 8, qualification 19; impact and timing unknown.”
4. Recompute weekly. Recency should decay so an untouched record loses ground without a manual deprioritization decision.

Scoring engagement and qualification

Engagement – 25 points

Score depth once, not cumulatively

Take the single highest interaction, not the sum. An account that opened six emails has not out-engaged an account that requested a consultation. Repetition already rewards volume; rewarding it twice quietly inflates engagement scores.

Spread counts contacts who have engaged, not contacts merely present in the CRM. A fully verified buying committee that has done nothing scores zero here.

Human qualification – 25 points

Award points only for what the buyer confirmed. Unknown scores zero, is recorded and is never inferred.

Why “unknown” must score zero

Partial credit for reasonable inference destroys the distinction between buyer-confirmed information and rep interpretation. The number then becomes difficult to audit when the opportunity stalls or is lost.

The seven items map directly to the question bank on page 20. You do not need to ask them all in one conversation; you need to know which are still unanswered.

What the gaps are telling you

A qualification score is more useful as a gap list than as a total.

Bands, thresholds and override rules

A note on commercial impact

This research does not publish conversion benchmarks, so the bands are expressed as cost authorized, not revenue predicted. The score’s job is to decide how much human time an account has earned. After sufficient live use, replace the final column with your own observed progression rates by band.

Override rules

1. Corroboration cap. If intent corroboration scores 0-2, PRS is capped at 59. Third-party intent alone can never reach Engage.
2. Buyer-request floor. If the buyer asked to be contacted – demo, consultation or pricing – PRS floors at 65. The buyer asked; the score does not get a veto.
3. Validity ceiling. Anything below Verified cannot route past Validate. Enrich first.
4. Single-thread flag. PRS ≥65 with a group spread of 0 routes to Engage and Multi-thread in parallel. Never ask one contact to represent the committee.
5. Decay. Recompute weekly. Recency scores step down on their own.
6. Disqualify wins. Fit tier D, prohibited contact or an explicit decline overrides every other input.

Run the model alongside your current routing for one quarter, then move the cut-points – not the rubric. The rubric encodes the framework; the cut-points encode your sales motion.

Two calibration checks are especially useful. First, compare each record’s band with what actually happened to it. Second, review where overrides fired. If the corroboration cap affects a large share of records, the issue may be an intent feed that is not being supported by first-party evidence.

Appendix B: Worked account scenarios

Account 1: the third-party-only account

Northwind Logistics. Tier B core fit. Third-party intent is active across five related topics at roughly 4× the account’s baseline. There is no recent website activity. Two contacts are on file from the correct buying committee; one registered for a playbook 31 days ago. Contact data is verified.

Scoring assumptions used for this example: Tier B, Verified, and the month-old registration belongs to one of the two committee contacts. Write assumptions down because they are the first thing to revisit when a score turns out to be wrong.

The answer: Validate

Not Engage. Not merely Monitor.

Why not Engage: the case rests mainly on third-party topic data. Five concurrent topics raise the probability of evaluation; they do not establish one.

Why not Monitor: five live topics, two role-correct reachable contacts and a prior registration justify human validation. The next unit of information has to come from a person.

The action, specifically

What moves it – and by how much

The account is one confirmed fact away from a sales conversation, and the model names which fact.

Accounts 2 and 3: qualified, and stopped

ABC Manufacturing Group – the qualified account

Tier A strategic fit. Intent is active across three related topics, with activity in the last 10 days at 3× baseline. Two contacts engaged: a Director of Operations attended a webinar 5 days ago; a VP Supply Chain downloaded a comparison guide 12 days ago. An SDR reached the Director, who confirmed her role and current priority, described a specific problem – manual reconciliation across three systems causing month-end delays – and named the VP as decision-maker. She did not know the budget position, timeline or whether a formal process had started. Data is verified.

The answer: Discovery – at the floor of the band

Landing at 80 rather than a near-perfect score is useful. Impact, evaluation stage and timing are still unknown, and they are exactly what the AE needs next.

• Book a discovery, not a demo.
• Fix the agenda in advance: impact, evaluation stage, timing.
• Multi-thread the VP beforehand with a business-case asset, not a product asset.
• If those items cannot be established, return the account to Validate.

Without the qualification call, the account would sit at 64 – Validate. With the call, it reaches 80 – Discovery. The example shows why human qualification can change ownership and the next-best action without pretending that every confirmed fact predicts revenue.

Meridian Health Systems – the account the gate stops

Tier A strategic fit. Four topics are live at 4× baseline, including a de-anonymized visit to a pricing page. Two contacts have three interactions, most recent 3 days ago. But two data sources disagree on the contact’s employer, and the email domain does not match the account record.

The answer: Hold and enrich

This is the data-validity rule made arithmetic. On raw signal it is the strongest account of the three, and it goes nowhere until the record is trustworthy.

Record the raw 63 anyway. That keeps it near the top of the enrichment queue. Once the conflict resolves, it is a 63 and routes straight to Validate. A record held at zero with no raw score is easy to forget.

Frequently asked questions