ICP boundaries
State company profile, geography, seniority, exclusions, and the business reason for contacting each segment.
LinkedIn and multichannel workflow analysis
Examine Expandi outreach before you automate it
Map audience selection, connection steps, follow-ups, reply handling, and human approval in one evidence-led workflow. Install the agent skill to evaluate a campaign brief without confusing a copied command, a configured workspace, and a live sequence.
Open the installation runbookCompare the operating method
Checked 21 July 2026. Unknown means public material did not confirm the behavior; it is not a negative score.
| Dimension | Expandi-oriented workflow | Generic seat platform |
|---|---|---|
| Setup path | Agent skill installed by explicit npx command | Browser account and workspace configuration |
| Campaign model | LinkedIn and multichannel task brief with review gates | Sequence builder; exact behavior varies |
| Data provenance | Connected-source dependent; inspect each output | Provider dependent; Unknown without documentation |
| Human control | Approve targeting and messages before activation | Varies by permissions and campaign settings |
| Cost model | Installer is visible; third-party fees remain separate | Usually seat, usage, or credit based |
| Safety disclosure | Configuration-dependent and tested locally | Review current vendor documentation |
Four states, kept deliberately separate
01Command copied
02Installer run
03Connections configured
04First campaign reviewed
These are workflow states, not performance claims. Results depend on targeting criteria, LinkedIn account conditions, connected channels, message quality, limits, consent context, and operator judgment.
Six checks before a sequence becomes active
Profile verification
Confirm that a LinkedIn profile and company match the intended person rather than trusting a name or title alone.
Channel order
Document when LinkedIn, email, and manual tasks enter the sequence, including stop conditions between channels.
Message review
Keep researched facts distinct from inference, remove unsupported personalization, and approve every reusable message pattern.
Reply classification
Route positive, negative, ambiguous, and opt-out responses without allowing automation to overrule a person.
Account protection
Respect platform limits, sender reputation, suppression lists, regional rules, and any connected provider restrictions.
Copy, run, configure, first result
1. Copy
npx -y @okki-global/okki-go-taroballSuccess means the exact text is in your clipboard; nothing has been installed yet.
2. Run
Use a supported terminal, inspect package identity and prompts, then wait for a completed installer response.
3. Configure
Connect only approved accounts, grant minimum permissions, and keep credentials in the runtime's protected secret store.
4. First result
Use a small known cohort. Review profile matches, exclusions, sequence logic, reply routing, and every proposed message before activation.
Data and security ledger
LinkedIn and connected sources
Config-dependent. Availability, freshness, and permitted use follow the accounts and providers an operator connects. Validate current terms before collection or automation.
Credentials
Verify locally. Inspect where tokens are stored, which processes can read them, how access is revoked, and whether logs redact secrets.
Runtime behavior
Not assumed. Test network requests, rate handling, retries, generated files, and destinations in a disposable environment before production use.
Retention and deletion
Config-dependent. Record where prospect data, campaign drafts, replies, and audit events persist, then test deletion across every connected system.
No SOC 2, ISO 27001, GDPR compliance, deliverability rate, or LinkedIn safety claim is implied here. Procurement teams should request current evidence and counsel should assess their actual use.