← Agent catalogue
AUCTOR

Preview portrait

Integration

AUCTOR

Commercial pipeline posture alongside execution outputs; not a full external CRM — governed APIs and connectors (e.g. HubSpot) as configured.

LiveCatalogue status
AdvisoryRuntime posture

Sales and pipeline intelligence: tenant-scoped AUCTOR domain agent — pairs with the Sales OS module (Prisma `Sales*` models, `/console/sales`, sales APIs) for accounts, opportunities, and outbound sales campaigns.

  • AUCTOR
  • Sales
  • Pipeline
  • Sales module

Expanded capabilities

  • Observe pipeline, account, and outbound sales posture for entitled tenants
  • Compose opportunity narratives with explicit missing/partial source health
  • Coordinate with MERCURY on demand-to-revenue handoffs
  • Stay CRM-adjacent without inventing HubSpot rows or silent syncs
  • Propose RECORD_ONLY improvements; never auto-send outbound sequences

How they learn & improve

AUCTOR learns from closed-won/lost signals, operator overrides on opportunity priority, and human-approved learning proposals — not from silent CRM writes.

  1. Read sales command surfaces and connector posture with provenance.
  2. Emit advisory findings or learning candidates when patterns look actionable.
  3. Improve next-cycle recommendations only after human review/apply on Autonomy · Learning.

How they work together

AUCTOR partners with MERCURY for inbound context, ATLAS for orchestration, and NUNTIUS/approvals for any human-facing send.

  • MERCURYConsumes marketing handoffs so reps start with campaign context.
  • PROMETHEUSSurfaces expansion opportunities that sales leadership can escalate.
  • CONCORDIAShares account health cues before renewal or expansion motions.
  • ATLASRuns under ATLAS-classified work so sales automation stays policy-bound.
  • Sales OS (AUCTOR module surface)Shares governed context with Sales OS (AUCTOR module surface) so operators see one coherent path instead of conflicting module stories.

Practical benefits

  • Pipeline triage that names gapsIf CRM sync is missing, AUCTOR says so — operators reconnect instead of trusting empty boards.
  • Outbound draft, not auto-sendSuggested sequences stay draft/approval-bound; customers never receive unapproved messages.
  • Shared growth roomGrowth Command shows MERCURY + AUCTOR together so leadership sees one demand-to-revenue posture.

Learning and improvement stay human-visible: candidates are RECORD_ONLY until an operator reviews and applies them. Sensitive sends, publishes, and approvals never run silently.

AUCTOR — AgentIQ Agent Catalogue · AgentIQ Labs