account qualificationsignal attribution engine
account qualification · signal attribution engine

one honest icp verdict
for every company.

raw company lists and linkedin engagement go in. one shared company table, one dev-signal score, one ai verdict, and a safety layer that refuses to guess. out comes a funnel, buckets and exports.

the icp in one line: a company whose product or service is mainly used by engineers — the people who build, ship, run, observe or secure software. using software for a business job (marketing, hr, finance, sales) does not count.

01what it is

a classifier and decision layer for account qualification. it turns messy company evidence into one defensible verdict, then hands the maybes to a human.

a classifier

two input flows — company lists and linkedin engagement — land in one shared company table and go through the same classifier.

not a crm

it answers “is this company worth a rep’s time?” it does not manage deals, sequences or relationships.

a decision layer

dev-signal evidence, an ai verdict, then the safety layer that can only push toward review — never a silent no.

02system at a glance

evidence goes in; a verdict and a funnel come out; the maybes go to a human. the strictness is the feature.

INPUT
messy company evidence
csv lists, linkedin engagement, profile lists, enrichment sources.
IDENTITY
one company table
strict domain matching, source ownership, duplicates parked for a human.
VERDICT
signals → ai → rules
a dev-signal score, an ai classification, then the safety layer and a policy override.
OUTPUT
funnel + buckets
funnel gates, gtm segments, exports and a review queue.

03the decisions that matter

the rules are the product. these are the ones that keep the verdict defensible.

evidence before verdict

the dev-signal score is evidence for the ai, not the answer itself. the rules decide after the model speaks.

a false no is the worst mistake

weak evidence becomes review, never no. a review costs 30 seconds; a wrong no deletes a real prospect.

never guess identity

no invented domains, no weak auto-merges, no guessing between two companies with the same name.

policy lives in code

the ai suggests, the rules decide, and the admin-editable policy list has the final say — backwards too.

one owner per column

each source owns its fields. every write is logged and every upload can be undone safely.

gaps must be visible

seen-vs-stored counts, unresolved people reported, failures flagged instead of silently dropped.