LEON BASIN.

GTM Systems / Live demo

Signal Architect.

A raw lead list goes in. A prioritized attack list comes out.

This page runs the real Basin Priority Logic from the open source Signal Architect tool, ported line for line into your browser. Load the sample list, read exactly why each row earned its priority, then flip a signal off or on and watch the tier move. Nothing is uploaded: the scoring happens on this page.

The sample list is synthetic. Twelve invented companies, invented people, written to carry the signals the logic reads. No real company or contact appears anywhere in the demo.

Run it.

Synthetic data. Real logic.
No list loaded yet. Load the sample list and every row is scored on the spot: a Friction score from the Friction Filter, a DNA read from DNA Analysis, and a P0 to P3 priority from the combined rule.

How the logic works.

Three steps, exactly as the tool runs them. The scan is a plain substring match over the full row text (company, contact, title, and notes combined, lowercased). It matches letters, not intent, and each keyword counts once per row no matter how often it appears. That rawness is deliberate: the logic is the filter, and a human still reviews the queue it produces.

Step 1

Friction Filter

Counts how many of these hiring keywords appear in the row: sales, account executive, ae (the letters ae followed by a space, catching AE as a standalone title), sdr, bdr, business development, revenue. One point per keyword found. A company hiring for sales roles is showing intent to build sales infrastructure, and that friction is the buying signal.

Step 2

DNA Analysis

Counts two keyword families. Technical: engineer, cto, vp engineering, developer, technical founder, phd, security, infosec. Sales: vp sales, cro, chief revenue, sales leader, head of sales. More technical matches means Technical DNA, more sales matches means Sales DNA, and an even count means Mixed DNA. Confidence is the winning count times 20, capped at 100; a tie is always 50.

Step 3

Priority

P0 when friction is 3 or more, the DNA is Technical, and confidence is 60 or more. P1 when friction is 2 or more and the DNA is Technical. P2 when friction is 2 or more, or the DNA is Technical. Everything else is P3. The queue is worked top down: P0 first, P3 only when the top of the list is clear.

Inspect the real thing.

The code

The full Python tool, friction filter, DNA analysis, and outreach drafting included, is public on GitHub.

Read the code

The system

Signal Architect is one build inside a wider GTM operating system: qualification, routing, scoring, and human review.

See GTM Systems

The essay

Why the tool exists: fifteen years of fighting bad data, and the weekend the filter got built instead of bought.

Read the essay

Architecture > Activity.