Signals in, meetings out, a human gate in the middle.

This page is the machine, stage by stage, including the part our competitors do not have and cannot copy without rebuilding their business model.

Signals, described in plain English

You tell us the moment a rep wishes they knew about: "manufacturers hiring three engineers in the UK", "alt-nets entering operate phase". We compile it into monitors across hiring, funding, tech and news sources. Ten starter signal types, unlimited custom ones.

A strict qualifier gates everything

Every ICP carries one hard condition. Without it an account is held, whatever its score: a 0.9 fit with no qualifier never gets drafted. Then fit and intent are computed with recency decay, so a sixty-day-old signal cannot masquerade as timing.

Drafts arrive with their evidence

One hypothesis per message, written in your voice, with banned phrases enforced in the pipeline itself. Every draft carries its reasoning trace: which signals fired, and the verified sources behind them.

A named human approves every send

The approval queue is the product. Evidence chips, the draft, approve or reject, keyboard-first. The block is not a policy: it is a database trigger. A forged automated approval is rejected at the storage layer.

Sends go out inside the rules

Warmed domains, paced waves, 20-30 sends per mailbox per day. UK PECR and EU tiers executed as code: restricted countries suppressed, sole traders screened, legitimate interest on file, retention purges on schedule.

The ledger closes the loop

Every send, reply and meeting on the record. Replies override models. The weekly brief reads straight off the ledger in ten minutes, and outcomes sync to your CRM as notes.

Try it: click the stations.

Never-auto-send · enforced by schema, not policy

A named human approves every single send, reviewing the evidence, not a checkbox. The block lives in the database schema itself: an automated approval is rejected at the storage layer.

The guarantee, as schema.

This trigger ships in our database. It is why "never auto-sends" is a fact, not a promise: even our own code cannot create a send without a valid human approval.

CREATE TRIGGER sends_require_human_approval
BEFORE INSERT ON sends
WHEN (SELECT decision FROM approvals WHERE id = NEW.approval_id)
       NOT IN ('approved','edited')
   OR (SELECT decided_by FROM approvals WHERE id = NEW.approval_id)
       IN ('system','agent','auto')
BEGIN
  SELECT RAISE(ABORT, 'send blocked: no valid human approval');
END;

See it running on your ICP.

The scoping call takes thirty minutes and ends with the first custom signal defined. Leave your email and we will book it when your cohort slot opens.