Core concepts - OneShot

Term	Meaning	What to do
ICP	Ideal customer profile: the people and organizations your product can help.	Write roles and relevant needs, not just a broad industry.
Finder	A source-specific discovery routine, such as GitHub stars or funding announcements.	Choose a source that carries evidence of your audience’s needs.
Trigger	A finder’s saved configuration and schedule.	Check its readiness, interval and spend limit.
Queue	Candidates waiting for review or execution.	Inspect the evidence before approving a person.
Play	A named outreach strategy and its target inputs.	Match the play to the reason for contacting someone.
Drain	Process approved queue rows for a selected play.	Preview with dry-run; a live drain can draft and send.
Cadence	The scheduled sequence of touches for one prospect.	Review follow-ups and stop when the conversation changes.
Breakup	A final follow-up that closes an unanswered sequence.	Give the recipient room to decline or defer.
Receipt	A signed record of a OneShot action and its cost.	Use it to inspect what was paid for and why.
Dedupe key	A stable identifier connecting a candidate to its queue row and draft.	Let retries reuse recorded state instead of creating a second first touch.

Two ICP gates

The topic gate judges the source, such as a repository or event, before further paid work. The person gate judges the individual’s role using available text and, when needed, enrichment. A relevant event does not automatically make every attendee a suitable prospect.

A score is not permission to send

Shadow scores summarize evidence for review. They are not conversion probabilities. Eligibility checks, review approval, sender capacity and suppression rules remain separate. Soft gates advise on scaling decisions. RoCS compares confirmed attributed value with action spend.