Skip to content

Overview

Start

Documentation

How the Revenue System is put together, and the shortest path to a first shortlist.

/docs01 / 20

Arvyn is a Revenue System, not a cold email platform. Most outbound software is built to answer “How can we send 1,000 more emails?”. This one is built to answer “Which 20 companies should we contact today?”, and to show you the evidence behind the answer.

That difference decides how the documentation is shaped. There is very little here about sending mechanics and a great deal about how an account gets qualified, what counts as evidence, and how the system argues with itself before it commits to a decision.

Start here#

Three routes through the docs, depending on what you came for. All three assume a workspace at console.arvyn.io.

Set it upGetting startedDescribe your buyer, connect a mailbox, review the first shortlist, approve a campaign.Understand itCore conceptsICP, signals, evidence, the buying window, and how the four tiers allocate effort.Send wellDeliverabilityWarmup, send windows, volume ramp, and why open and click tracking defaults to off.Build on itThe APIRead accounts, decisions and evidence; subscribe to webhooks; sync to your CRM.

The three products#

One system, three surfaces. They share an account graph, an evidence store and a single workspace, so a fact learned in one is available to the others.

NexusRevenue Intelligence

Decides which companies to contact today, and proves why

ScoutResearch Intelligence

Researches a company deeply before you ever speak to them

SonarMeeting Intelligence

Coaches you live on the call, and lets you rehearse it first

The link worth knowing about is the one between the last two. Scout hands its dossier to Sonar, which turns the research into a practice room. You can rehearse a specific call, against a buyer built from that specific company’s public record, before you take it.

How these docs are organised#

SectionWhat it coversRead it when
StartSetup, in order, from an empty workspace.Day one.
Core conceptsThe vocabulary: ICP, signal, evidence, buying window, tier.Before you argue with a decision the system made.
NexusQualification, scoring, campaigns, sending.When you want to change what gets contacted, or how.
ScoutDossiers and their sourcing rules.Before a first call with a company you do not know.
SonarThe live coach and the practice room.Before and during calls.
Sending infrastructureMailbox connection and deliverability.Once, properly, at the start — and again if replies drop.
DevelopersREST API, webhooks, CRM integrations.When something else in your stack needs the decisions.

Conventions#

A few things mean something specific throughout these pages.

  • Monospace marks anything the system emits or accepts literally: routes, field names, record locators like DEC-4417, header names, source URLs and timestamps. If it is in mono, you can type it or click it.
  • Defaults are stated as defaults. Where a page says a cap is 50 messages per mailbox per day, that is the shipped default and it is editable in workspace settings. Where a page says something is not supported, it is not a default — it is absent.
  • Every external claim carries its source. The one research finding these docs lean on is cited inline, with a link, on the deliverability page. That is the same rule the product applies to itself.
  • Examples use fictional companies. Northwind Freight, Halden Systems and similar names in these pages are illustrative. They are not customers.