← Guides

Glossary

Words we use.

The terms the guides lean on, in plain words. Some are our own names for the parts of our own system. The rest are common trade terms, spelled out.

Ring
A list of job titles that count as the same signal, with a weight. Ring 1 is the strongest.
The map
One table of companies, keyed on domain, with a status, a segment, a tier and a reason for each. Nothing is deleted from it. A status changes when a fact does.
Signal
Something a company or a person did that gives a reason to reach out now: a job posting, a funding round, a visit to your site, a click on an ad, a contract award, a compliance date, an expansion, a comment on a post, a form, a reply.
Fit and timing
Two separate numbers. Fit is how well a company matches who we sell to, and it belongs to the account. Timing is how fresh the signal is, and it fades.
Tier
The rank a company holds on the map because of its fit. A signal moves a company up inside its tier and never changes the tier.
Check
One question asked of a company or a person, with three possible answers: pass, fail or unknown. Every check keeps the evidence behind its answer.
Unknown
The answer a check gives when it cannot tell. An unknown is never counted as a pass. It waits for a person or for a missing fact.
Verdict
What a workflow decides after its checks, with the reasons. A person can always see why.
Routine
A job that runs itself on a schedule in the cloud. Nothing depends on a laptop being open.
Broker
One small service that holds the API keys and the spending caps, so a routine cannot spend past them.
Cap
A spending limit per day or per month. Over the cap, the routine stops and says so.
Receipt
The written record of a run: what it checked, what it decided, what it spent.
Ledger
The place the receipts are read. One row per run, read by a person every morning.
Router
The one step every signal passes through. It matches the signal to a company and a person and puts it in one shape before anything acts on it.
Queue
The one ordered list a rep works from, with a score and a reason to call beside each name.
Sender
A tool that delivers messages or calls on one channel: email, LinkedIn or the phone.
Blocklist
The companies and people we must never contact. One tool writes it, and every sender reads the same copy.
Layer
One of four jobs in the stack: decide, remember, record, touch.
No provider credits
A source that answers without drawing down a data provider's paid credits. It is not the same as free: it can still use a search quota or an allowance.
Play
What we do when a signal fires: the call, the message, the ad. A play is something we run for a client, not a how-to to copy.
Signal play
One signal and its play, together on one page. It names the signal, says who gets reached and shows the first line of the call.
Guide
A long how-to write-up of a system we run, with the parts, the order and the reasons.
Recipe
A short how-to: the trigger, the steps and the tools. It sits on the same shelf as the guides.
Target accounts
The companies you want to sell to. In your tools and in your name are different things: those are the logins and subscriptions you own.
GTM (go-to-market)
How a company gets its product in front of buyers and turns interest into meetings and sales: who to reach, when, and through which channel.
BDR (business development rep)
The person who makes the first calls and sends the first messages to companies that have not talked to you yet. Our BDR is our own rep, working for you. Your own person is your salesperson.
SDR (sales development rep)
A close cousin of the BDR: the person who follows up on interest and sets the meeting for a salesperson. The two titles are often used for the same job.
RevOps (revenue operations)
The work of keeping the systems behind sales running cleanly: the CRM, its fields, its reports and the way leads move through it.
ICP (ideal customer profile)
A short description of the kind of company that is the best fit for what you sell. It is how the list of target accounts gets built.
Clay
The data tool we build in. The lists, the checks and the routing live in tables in a Clay workspace in your name.