GTMGTM

Find · ICP

Every contact is in your ICP by construction

The gate runs on an Opus-class model and makes two judgements in one pass: a binary in-or-out call on ICP membership, and a 1–5 intent score for the ones that pass. Rejects never become contacts. That is why the flame on the contacts grid means heat, not fit.

Outbound14,208

Outbound row · pre-send evaluation

JurisdictionUS · CAN-SPAM
Entity typeBusiness contact
Lawful basisLegitimate interest, documented
SuppressionNo match at workspace or platform scope
Unsubscribe URLInjected by the transport
Postal addressInjected by the transport
Verdict: allow. Written to the row before the send.

messages_outbound_sent_was_gated. A row cannot reach sent without a verdict and an unsubscribe URL.

What is actually going on

Every claim below is followed by the mechanism under it, because a claim without a mechanism is a slide.

01

The bar is within the ICP, not a literal match on every attribute

Most leads arrive from a targeted search and are expected to pass. Clear mismatches are rejected. Only high-precision mode rejects on remaining doubt. The old reject-almost-everything prompt produced empty workspaces from correct searches.

02

Sourced facts outrank judged ones, per field

The gate parses title, company and country out of a Classic headline because Classic returns none of them. Where the hiring path read a real company name and domain off the company profile, the sourced value wins the merge.

03

Every decision is logged without a name

The ops screen shows the headline and the reasons for each candidate, accepted or rejected, so the accept rate is a number you can tune against. Contacts stay the accept list; rejects live in ops.

04

A human overrule trains the same telemetry

Disqualifying a contact takes a categorised reason. Incorrect-ICP and not-qualified write to the same judgement log the gate is measured on, so your correction is a data point rather than a deletion.

Step by step

How icp & the fit gate runs

  1. 1

    Plan

    Your ICP and keywords become the vendor's filter vocabulary, cached per signal against a fingerprint of its inputs.

  2. 2

    Judge

    Each candidate gets one pass: in-ICP or not, and if in, how warm.

  3. 3

    Merge

    Sourced fields win where they exist; judged fields fill the rest.

  4. 4

    Write

    Rejects are discarded before the contact write. Nothing out-of-ICP reaches your list.

The numbers

Facts, not adjectives

Every figure here is a real value from the running product. A cadence from the scheduler, a price from the credit table, a limit from the ramp. A marketing page that invents a limit is a support ticket with a delay on it.

FindICP
Model
Opus-class, not the economy default
Metered as
ai.classify.fit, 3 action credits
Returns
inIcp (binary) + intentScore (1–5)
Target shape
A precise accept rate, not a big one
Audit
Per-candidate reasons on /settings/ops

ICP & the fit gate, honestly

Why is a cold contact in my list at all?

Because ICP membership and intent are different questions. A perfect-fit buyer who has done nothing yet is exactly who you want sitting there when they finally engage a monitored keyword.

Can I make the gate stricter?

Yes. High-precision matching mode rejects on remaining doubt instead of accepting it. Expect a smaller list and a higher reply rate.

ICP & the fit gate is one part of it. The rest runs too.

Sourcing, enrichment, intent, copy, sending, replies and reporting are one product with one bill and one gate. Connect a channel and the whole motion starts.

Start with sales. $2,000 or $5,000 onboarding, then at least $250 monthly credit funding.