Background Account Triage
Opulent continuously researches accounts in the background, turns weak public context into scored evidence, and surfaces the right companies for deeper sales diligence.
Profile the buyer and connect discovery to the CRM
Connect Apollo and Clay for discovery and enrichment, and HubSpot or Attio as the record store. Triage runs against public signal and lands its verdict on the CRM record, so the pipeline stays the one place you look.
Start with a buyer profile: a playbook (a reusable, named set of steps) that says who you sell to, which signals count as intent, and what disqualifies an account, the standard every company gets held to.
Playbook: !triage-account For each candidate account: 1. Match the buyer profile: [sector], [size], [geo], [buying signal]. 2. Discover context with Apollo and Clay, hiring, funding, tech stack, leadership changes, product launches. 3. Filter the noise: drop accounts with no real signal, keep only those with evidence of intent. 4. Score 0-100 with a cited reason per point. 5. Write the research and score to the HubSpot record. Route only accounts scoring 70+ to the diligence queue.
Give Opulent read-only access to your CRM history so it can weigh an account against deals you already won or lost, instead of scoring every company from a cold start.
Let it run in the background on a schedule
Triage should never wait on a human to start it. Create a schedule, a recurring run on a fixed cadence, and point it at !triage-account so it works the candidate list continuously.
Click path: Settings, then Schedules, then Create schedule. Set the frequency to daily or hourly for high-volume lists, choose the playbook, and route the cleared accounts to a Slack channel your team watches.
The sharp edge: run it against the same list too often and it re-scores unchanged accounts and burns budget. Scope each run to newly discovered or recently changed accounts, not the whole universe every time.
Watch weak public context become scored evidence
Take an account with thin public information the background run picks up:
Opulent filters before it scores, so noise never reaches your diligence queue.
Account: Meridian Analytics (data tooling, ~60 staff) Run actions: - Signal check: posted a "Head of Revenue" role and a "Founding AE" role in the last two weeks, real hiring intent. - Enriched (Apollo, Clay): $9M seed 14 months ago, 40% headcount growth this year, moved onto a modern data stack. - Filtered in: clears the "evidence of go-to-market build-out" bar. - Scored 74/100, "GTM hiring + stack signal, unproven revenue". - Wrote the research to the HubSpot record and routed it to the diligence queue with a "confirm budget" next step.
What lands in the diligence queue
When the run finishes, the accounts that surfaced are ready for a human, each verifiable against its evidence:
Scored account records in HubSpot, each carrying the signal that triggered it, the enrichment behind the score, and a source per claim. A routed queue holding only accounts above the bar, so diligence time goes to real candidates. A running log of what was discovered, filtered out, and why.
Because the noise is filtered before scoring, the queue is short and every entry earns its place, which is what makes background triage worth trusting.
Sharpen what rises
When accounts that clear the bar keep going nowhere, tighten the signal definitions in !triage-account, or write the correction into memory (the notes a run recalls next time), like "seed-stage without a GTM hire is not yet a fit".
Tell Opulent which routed accounts converted; memory learns which signals actually predicted a real deal and weights them higher next cycle.
The natural chain: promote the cleared accounts into Deal Sourcing as a Self-Driving CRM so they move through pipeline stages, or into Self-Evolving Pipeline Operations for ongoing hygiene.