Market brief
Name the business model, geography, company characteristics, buyer role, purpose, and exclusions. Include existing customers and suppressed accounts.
Prospecting playbooks
A helpful playbook makes the brief falsifiable, shows why a prospect fits, names uncertainty, and identifies exactly where external action stops for human review. The contrast below is procedural: move from “find and message everyone” to a scoped ICP, dated evidence, an editable draft, and a named approver.
Interactive calculator layout, repurposed
This guided builder demonstrates what an operator should decide before research begins. It does not calculate an audience size or promise an outcome. Each field reduces ambiguity and gives the reviewer a reason to accept, revise, or reject the resulting record.
Name the business model, geography, company characteristics, buyer role, purpose, and exclusions. Include existing customers and suppressed accounts.
Request recent public firmographic, technographic, hiring, or operational signals with source timing. Tell the agent to preserve unknown values.
Ask for a concise cold email based only on approved context. Prohibit sensitive inference, invented familiarity, automatic sending, and unsupported urgency.
Name who checks identity, relevance, suppression, regional requirements, sender authority, opt-out language, pacing, and every external action.
Find ten B2B software companies in the selected geography that match the approved ICP and show two recent public signals. Exclude agencies, customers, and suppressed accounts. Identify a likely operations leader, label uncertain identity, and prepare a short draft for review. Do not send or export.
Founder
Use a small authorized sample while the market thesis is changing. Compare accepted and rejected accounts, research effort, evidence quality, and meaningful replies rather than treating connection volume as validation. Keep channel actions manual until exclusions and buyer roles stabilize.
Review: fit, source dates, role, exclusionsSDR manager
Require provenance, identity confidence, suppression status, and one evidence-backed reason for contact. Separate approval of the target, wording, export, and send. Set working hours, rate limits, sender authentication, reply ownership, and stop conditions before a sequence is authorized.
Review: relevance, tone, pacing, opt-outAgency operator
Use only the client’s ICP, credentials, sources, approved channels, and suppression records. Keep evidence and reports separated by client. Document authorization and the named approver; distinguish researched, approved, sent, delivered, replied, bounced, and opted-out states.
Review: authorization, separation, retentionThese examples are operating patterns, not customer case studies or performance claims. Current platform terms, regional obligations, data-source behavior, and sender infrastructure must be reviewed for the actual workflow.
Copying the command is the first state. Run it in an approved environment, configure narrow permissions, then review a small first result before any external action.
npx -y @okki-global/okki-go-taroball