The Revenue Engine

The Revenue Engine finds companies worth writing to, writes to them, reads what comes back, and keeps a record of every touch. You hold the switches: nothing reaches a stranger’s inbox without a person agreeing to it, and nothing a machine reads is beyond your correction.

What it is for: Writing to companies worth writing to, and reading what comes back.
Who uses it: Whoever runs outbound, and the agents that draft and read.
Where in the UI: The Revenue section: Overview, Leads, Pipeline, Inbox, Approvals, Reports, Fleet.
What it writes: A touch row for every letter out and reply in, on one timeline.
Which gate governs it: Send approval, decided by the reviewer ladder.

Full map: Map of Neutron Core

This section is written for someone who has never used it. You do not need to know what a domain is, what a sequencer does, or what any of the agents are called. Start with the first journey and work down.

Every screenshot here is fictional. The companies, people, addresses and figures come from a demonstration instance called Meridian Supply. No real prospect, customer, address or price appears anywhere in this section.

The whole journey, in one picture

    flowchart LR
  A["A list of companies"] --> B["A person at each one"]
  B --> C["A letter, waiting for you"]
  C -->|you approve| D["It sends"]
  D --> E["A reply comes back"]
  E --> F["It is read and labelled"]
  F -->|interested| G["A deal opens"]
  F -->|away, or not now| H["The follow-up waits"]
  F -->|leave me alone| I["They are never written to again"]

Four things are worth knowing before anything else.

The engine keeps time, not just data. A letter is not sent because you clicked; it is sent because a date arrived, a domain was healthy, and nobody had replied yet. Silence is a state the engine tracks.

Every touch is a row. Each letter out and each reply in is recorded on the person, on one timeline. When a screen disagrees with your memory, the timeline is what settles it.

A reply acts on its own. Somebody asking to be left alone is suppressed within seconds of writing, whether or not anyone reads their message that day.

A person holds the last switch. First letters wait for approval. Drafted answers wait for approval. An agent may write, and may never send.

Everything on this screen is also reachable from a keyboard somewhere else. Agents and MCP is the endpoint an agent connects to, the tools it gets, and the rules those tools keep.

Where to start

The journeys

Fifteen walkthroughs, in the order you will need them. Start at the first.

How it works underneath

For the curious: the ledger, the spine, the seams, and what keeps time.

Glossary

Every word this section uses that does not mean what you would guess.

Last updated on 17 September 2026