Skip to content

Features

Twelve modules. Two of them are the product.

Discovery, enrichment and sending are table stakes — every competitor has them. What nobody else sells is a market’s complaints in its own words, and a fact about each company that makes the email worth opening.

10 workflows·16 LLM agents·only 2 of them run per prospect

The shape of it

One line, from a URL to a reply

Numbers from a real run: a single SEO-agency segment, first fortnight. Watch where the volume falls away — and which step is a person.

  1. A

    Product & ICP

    1 URL in

  2. B

    Discovery

    2,400 found

  3. C

    Enrichment

    780 verified

  4. D

    Signal scan

    190 signalled

  5. E

    Pain mining

    3 themes

  6. G

    Drafting

    190 drafts

  7. ▲

    You approve

    50 read by you

  8. H·I

    Send & learn

    replies in

The two that make it workWhere you take over

The inventory

Everything in the box

No module here exists to pad a comparison table. If it is listed, it is load-bearing for one of the eight steps above.

01

Product & ICP

Paste a URL. Get positioning, named competitors and three to five candidate segments — as a proposal you edit, not a decision made for you.

  • Landing + pricing + docs crawl
  • Competitor resolution
  • Segment versioning
  • Human edits stay sticky
02

Prospect discovery

Seven source adapters fan out in parallel and checkpoint as they go, so a restart never redoes work and one failing source never takes the run down.

  • OSM
  • Clutch
  • Job boards
  • GitHub
  • G2 / Capterra
  • CSV in and out
  • Chain exclusion
03

Contact enrichment

Finds the address, checks it is real, and records the attempt so the same contact is never scraped twice.

  • Role vs named person
  • valid / risky / invalid
  • Headcount, funding, stack
  • Monthly budget cap
04

Signal engine

What is true about this specific company, right now — and a URL that proves it.

  • Tech detectors
  • Hiring signals
  • Review signals
  • evidence_url + detected_at
  • Recency decay
Deep dive
05

Pain intelligence

What the whole market is angry about, verbatim, attributed and sourced. The flagship, and sellable on its own.

  • Competitor reviews
  • Community mining
  • Theme clustering
  • Verbatim quote bank
  • Monthly diffing
Deep dive
06

Message studio

Drafts composed from this prospect’s signal, this segment’s verbatim pain and your product’s value props. Prospects with no citable fact are routed aside, never blended into a batch.

  • Angle selection
  • Email · LinkedIn · community
  • Opener + 2–3 follow-ups
  • Template library
  • Fallback bucket
07

Batch approval

Fifty drafts, their evidence beside them, and a person reading every one. There is no send-all button and no setting that removes this step.

  • Inline editing
  • Evidence sidebar
  • Reject by rule
  • Reject-rate warning
Deep dive
08

Compliance

Rules that reject rather than rewrite. Suppression is re-checked inside the same transaction as the send, because time passes between drafting and sending.

  • CAN-SPAM address + opt-out
  • CASL hard block on CA bulk
  • Unsubscribe injection
  • Org-wide cooldown
  • Contactability record
09

Sending

Approved batches go out through your own Instantly or Smartlead account. We deliberately do not own your domain reputation.

  • Throttled dispatch
  • Stop on reply
  • Reply classification
  • Auto-suppression
  • In-app inbox
10

Analytics

Reply rate, positive rate and cost per booked meeting. Open rate is omitted by design — Apple’s privacy proxy turned it into noise.

  • Full funnel
  • segment × theme × template
  • Template auto-retire
  • Signal efficacy
  • Cost per meeting
Soon11

Community & content

Where your buyers actually post, ranked by density, pain volume and how hard the moderators are. For segments where cold email is the wrong channel, this is the answer instead.

  • Subreddits, forums, Slacks
  • Per-channel norms
  • Non-email playbooks
12

Platform

Multi-tenant from the first commit. Isolation is enforced by Postgres itself, not by remembering to add a WHERE clause.

  • Row-level security
  • Cross-tenant test in CI
  • Usage metering
  • Job monitoring
  • Audit log
  • /health/ready

Enforcement

Two rules, written into the system

Every outreach tool claims personalisation. Two of ours are constraints rather than intentions, which means they hold on the worst day as well as the best.

No fact, no draft

-- drafts table

cited_signal_id bigint NOT NULL

  REFERENCES signals (id)

A draft that cannot point at a real, dated, sourced observation about that prospect cannot be saved — let alone sent. It is a foreign key, not a prompt and a good intention.

No send without a person

-- draft generation, final node

compliance_gate → END

  no send path exists here

Drafting ends at the approval queue. Sending is a separate workflow that only an approved batch can trigger, so there is no toggle anywhere that turns you into an auto-blaster.

Full mechanics in the how it works walkthrough.

Start with the dossier.

Tell us your product and we'll mine your market's public complaints — ranked, quoted and sourced. Useful whether or not you ever send an email.

Free · no card · yours to keep