The MapDemand GenerationShortlist / Prioritization

Shortlist / Prioritization

Scoring the list down to the accounts worth your outreach.

Workflow

Step 1Prospects with Signals

No playbook note for this step yet — the workflow stands on its own.

Why it matters

  • Capacity is finite. Prioritization decides where reps and sequences go. Without it, effort is spread evenly across a list where 80% of the value sits in 20% of accounts.

Best practices

  • Score two things independently: ICP fit + signal strength.
  • Make thresholds explicit — what is "reach now" vs "nurture later".
  • Keep the model simple enough to explain in one sentence.
  • Review the scoring against outcomes and recalibrate each cycle.

Common mistakes

  • Scoring so many factors the model is unfalsifiable.
  • Letting signal strength override terrible ICP fit.
  • Never recalibrating — the model drifts from reality.

Key questions

  • Does this account fit AND show intent?
  • Is the threshold data-driven or vibes?
  • Where is the boundary between shortlist and nurture?

Agents that drive this

Signals ScoutQualifier

Tools we use · alternates in [ ]

Parallel[ Bombora, 6sense, Common Room ]Clay[ Bitscale, Enrow, Insycle ]Supabase[ Postgres, Firebase ]