6sense Configuration
The signal backbone for marketing and SDR — account scoring, in-market buying signals, and segment activation. This page tracks the configuration from purchase to full adoption.
What it is
The account-intelligence platform the signal engine runs on: account scoring, in-market buying signals, and segment activation. One platform, one account view — marketing aims campaigns with it, SDRs work the scored accounts it surfaces. It joined the budget switch as the signal backbone: funded inside the engine, no incremental ask.
Status (Sep 1): approved; purchase moving through the Zip workflow. Three confirmed uses to start: in-market account visibility at subregional / regional / territory level, MQA, and automated campaign triggering — starting small. Integration with the inbound agent endpoint (Andy + Keith's team) is worked out, which makes the Lead Agent the trigger mechanism for what 6sense surfaces. The orchestration playbook is a Nash + Reet + GTM effort with Josh, expanding to AEs and CSMs as it proves out; day-to-day ownership lands with the Growth Sr Manager backfill.
How configuration runs
Verto designs and operates the configuration (SOW §3.4/§3.5): signal intake normalized into one scoring model, trigger thresholds per persona and stage, and integration across every ad platform plus Salesforce. Running sequences, calls, and emails stays with Redis on the Apollo + Pocus + Outreach stack. The checklist below is the working state — update `content/sixsense.csv` as items land; statuses are To do · In progress · To discuss · Done.