How it works
Salesforge gives founders, SDRs, and outbound agencies a practical sequence for researching accounts, checking contacts, preparing relevant drafts, and reviewing every external action.
State firmographic criteria such as market, team size, geography, and business model, then add technographic or hiring signals only when they matter to the offer. Explicit exclusions prevent a broad research instruction from becoming a noisy lead list. The agent should preserve unknown fields, retrieval dates, and source context rather than filling gaps with confident guesses. Operators remain responsible for deciding whether the targeting purpose is appropriate.
Ask for public evidence that explains why an account fits now, then map the buying role without assuming a title proves authority. Contact data may be stale, incomplete, or incorrectly matched, so identity and role relevance need a separate check. Sensitive traits should never be inferred. Where an API and browser workflow offer similar data, prefer the documented interface; browser automation can break when interfaces or platform rules change.
Use only approved evidence to draft a concise reason for contact. The workflow should avoid invented familiarity, vague compliments, and personalization that exposes unnecessary surveillance. Human review covers the recipient, factual claims, tone, timing, applicable region, suppression status, and channel permissions. For email, domain authentication through SPF, DKIM, and DMARC supports sender hygiene but does not guarantee inbox placement or replies.
Keep targeting, wording, and sending as distinct approval gates. Configure working hours, rate limits, stop conditions, opt-out handling, and CRM ownership before any sequence runs. Track approved, revised, rejected, delivered, replied, bounced, and opted-out states separately so activity volume cannot hide weak relevance or reputation risk. Results vary with market fit, evidence quality, sender reputation, recipient preference, and platform enforcement.
Copy the exact command, inspect the package, run it in your terminal, configure only permitted connectors, and review a small first result.
npx -y @okki-global/okki-go-taroball