Six steps, in the order the work actually happens.
Not a feature list arranged by menu order. This is the path one lead takes from a search term to a reply in your inbox, with the point where you have to make a decision marked clearly.
No payment method. No recurring charge. Your own SMTP, your own data.
- Steps
- 6, in pipeline order
- Your decision
- Step 03, approval
- Sending
- Your own mailboxes
- Format
- Static illustrations
Before anything is written, let alone sent.
The first half of an outbound programme is not writing. It is deciding who is worth writing to, and knowing enough about them that the first line is not a guess.
A list appears, and stops there
You set a niche and a location, or you import a CSV of up to 20,000 rows. Scout finds matching businesses, looks for email addresses, checks that they resolve, and scores each one. Then it stops: discovery is human-gated, so nothing is researched or written automatically.
- Search by niche and location, or bring your own CSV
- Results cached for seven days so the same search is not paid for twice
- Every lead carries a score before it enters the pipeline
- Saved searches can run daily, weekly or monthly on their own
Each company becomes a paragraph, not a row
Research crawls the site and analyses it, pulling out industry, technology signals and recent changes. Strategist then chooses the angle for that specific company, drawing on a knowledge base that grows with every campaign you run.
- Crawls the real site, with a browser fallback for JavaScript-heavy pages
- No successful first-party crawl means no profile, rather than a guess
- Strategist picks the approach, the tone and the type of ask
- The Analyst writes weekly findings back into the knowledge base
The part where most tools stop asking you.
This is the centre of the product. An AI-written sequence does not reach a recipient until a person has read it, and delivery happens from a mailbox you own rather than a pool you share.
Drafts queue up and wait for you
Writer composes the sequence from the research and the chosen angle: subject lines, body copy and follow-ups. Every AI-written message lands in a review queue where you read it, edit it, approve it or throw it away.
- One to five steps per sequence, with merge tags
- Read, edit, approve or reject each draft individually
- Rewrite and alternative-version helpers when a draft is close but wrong
- Template campaigns are different, and the page says so plainly
Sending happens on your domain, at your pace
Approved messages go out through the SMTP accounts you connected. Warmup governs how much each mailbox may send, authentication records are checked, and an account that crosses the bounce or spam threshold is paused rather than warned about.
- Bring your own SMTP: no shared IP pool, no platform sending domain
- Credentials encrypted with AES-256-GCM before they reach the database
- Gradual daily ramp per mailbox, with SPF, DKIM and DMARC checks
- Automatic pause when bounce or spam rates cross a safe threshold
What comes back, and who it belongs to.
A reply is only useful if it finds its way back to the right lead, the right sequence and the right client. That is the last third of the pipeline, and it runs without anyone watching an inbox.
Replies match themselves to the conversation
IMAP is polled every five minutes. Each reply is matched to its lead and sequence using the original message identifier, then classified so an objection is not filed next to a meeting request. Bounces update the lead, and opt-outs become permanent.
- Matched by message identifier, not by guessing at the subject line
- Classified as interested, objection, meeting request or unsubscribe
- Hard bounces stop further sends to that address
- Opt-outs join an organisation-wide suppression list checked before every send
Several clients, one login, no bleed
An organisation contains projects, and a project is one client. Leads, campaigns, mailboxes and analytics are scoped to the project, and a campaign can only send from accounts belonging to that same project. Four roles decide who may do what.
- Every query filters by organisation, with no trusted exceptions
- Sending for one client never rotates onto another client's domain
- Owner, admin, member and viewer, with viewer read-only
- Switching organisation clears the cached view entirely
What this tour is, and is not
Every panel above is a hand-built illustration of a real screen, labelled as such on the frame. It is not a live sandbox and it is not a recorded demo, and pretending otherwise on a page about honest outreach would be a poor start.
Illustrations, not screenshots
The panels show the shape and vocabulary of the real interface. The values in them are generic on purpose: no invented customer names, no invented performance figures.
No interactive sandbox
There is no click-through demo environment yet. The nearest thing to trying it is early access, which is granted per invitation.
Six steps, not every screen
The application has more surfaces than this: analytics, agent logs, health, knowledge base, suppression management. The tour follows one lead rather than cataloguing the menu.
The order is the argument
Most tools cover steps four and five. The reason the tour starts at step one and stops at step three is that those are the parts a sending tool leaves to you.
Get started
The pipeline is only useful with your list in it.
Tell us what you sell and who you sell it to, and we will say plainly whether this shape of pipeline fits it.
No payment method or recurring charge during early access.