Sales reps are overwhelmed with accounts to work. Without a clear prioritization framework,
they fall back on gut feel, recency bias, or whoever shouted loudest in the last marketing email.
Some reps focus on large accounts regardless of intent, others chase every new account
showing activity, still others work existing relationships exclusively while ignoring net-new
opportunities. This inconsistency leads to predictable problems: missed revenue when high-
intent accounts don’t get attention, and wasted effort when reps spend time on accounts that
aren’t ready to buy.
The Prioritize Accounts use case solves this by giving reps a clear, shared framework for
deciding which accounts to work when, based on criteria everyone agrees on. This means
establishing explicit prioritization criteria that combine:
- ICP fit
- Buying stage
- Intent signals
- Existing relationship status
This framework should then be built into filtered lists and workflows that reps actually use.
The maturity progression breaks down like this
Crawl
Reps understand the customer buying journey and prioritize accounts based on established
criteria, even if it’s relatively simple like “in-ICP + showing intent = high priority.” You’ve moved
beyond MQL language to using shared terminology like 6QA (6sense Qualified Account).
You’ve created saved filtered lists that surface these priority accounts, and everyone’s working
from the same definitions rather than each rep using their own mental model.
Walk
You’ve built prioritization through the platform. Reps are building and saving lists based on
specific criteria, not just working from a single “hot accounts” dashboard that marketing
provides. They’re using the platform to identify which accounts are showing intent, what specific
topics they’re researching, and what buying stage they’re in. You’ve established SLAs for how
quickly reps should engage hot accounts and managers are tracking adherence in their one-on-
ones.
Run
You’ve achieved true strategic alignment where prioritization is baked into GTM workflows.
Marketing’s campaign targeting aligns with sales’ account prioritization and they’re working the
same accounts. RevOps measures KPIs like average time to first touch on flagged priority
accounts (6QAs for 6sense users), percentage of flagged accounts receiving outreach within
SLA, and conversion rates by priority level. Sellers create their own lists for strategic in-market
accounts based on territory-specific insights, going beyond just the lists marketing provides.
Watch out for these common traps
You can build a beautiful prioritization framework with perfect logic, deploy it to the CRM, and
watch sales continue working accounts exactly as they always have. Adoption requires sales
leadership buy-in, clear communication about why the framework matters, training on how to
use the tools, and accountability for following the system.
Keep the framework simple. If reps need to check seven different fields and apply a mental
algorithm to figure out whether an account is priority, they won’t do it. The best frameworks are
simple enough to internalize.
You also need SLAs with teeth. If there’s no expectation for how quickly reps should engage a
flagged account, the prioritization framework is optional rather than mandatory. Some reps will
respond immediately while others ignore it, leading to missed opportunities and inconsistent
results.
What you’ll need to make this work
- Platform integrated with CRM so account-level data (ICP fit, intent signals, buying stage)
flows to where sales reps work - Dashboards that surface priority accounts as actionable lists, not just data fields
- Ability for reps to build and save their own lists based on criteria relevant to their territory
- Sales engagement platforms that integrate with prioritization data for filtering
- Alerting that notifies reps when accounts in their territory show new intent or change
buying stages
Measuring success
At Crawl, focus on adoption metrics:
- Percentage of sellers using sales intelligence tools
- Average time to first touch on 6QAs
- Number of sellers actively working 6QAs versus ignoring prioritization
Sales leadership owns this use case because they’re accountable for team adoption and
results. Marketing supports by ensuring data is accurate and accessible. RevOps handles
technical implementation and reporting. But if the VP of Sales isn’t actively reinforcing the
prioritization framework in team meetings and one-on-ones, it will fail regardless of how well it’s
built.
