Multi-agent SDR fleets, with the record nobody else has.
When intake, enrichment, routing, and booking are separate agents handing off to each other, per-agent logs answer per-agent questions. The questions worth asking are at the fleet level — and v2.spot is the record that answers them.
Page in development
Specimen Quorum entries (the canonical northwind.co headcount disagreement) and Chronicle dossier samples will be added as production deployments expand.
The shape of the problem.
A goal — "qualify and book the inbound demo lead" — touches four agents over thirty minutes. Each agent makes a confident call, some of which contradict each other. The final outcome is an email and a calendar invite. When the customer asks why their account got routed where it did, no single agent's log answers.
What v2.spot produces.
- Ensemble — per-goal dossier: every agent that touched the goal, in order, with their contribution.
- Quorum — inter-agent disagreement on record: who claimed what, with what confidence, from which source, and how the resolution was decided.
- Chronicle — content-addressed provenance: for the outbound email, which agent produced the subject line, which produced the body opener, which checked the recipient.
What lives elsewhere.
Sales metrics, conversion rates, pipeline analytics, lead scoring. v2.spot's job is the audit-grade record of the fleet's behaviour — not a sales operations product.