# Claude Code for sales outreach
> Use Claude Code as a terminal operator on Omentir. Diff My Product against the repo. Draft in the session. Send from the workspace. Close the terminal and the job stops.
- HTML: https://omentir.com/claude-code-sales-outreach
- Markdown: https://omentir.com/claude-code-sales-outreach.md

## The job

[Claude Code](https://claude.com/product/claude-code) is a repo session, not an overnight Bot. The same terminal that is editing the landing page can read Omentir over MCP, score a batch, and leave drafts.

- Diff: compare My Product with the README you just changed.
- Read: get_context, then list_agents, before create.
- Draft: up to 30 people, fit notes, two sentences that cite a real trigger.
- Stop: do not send, do not enroll, do not sign into LinkedIn.

## Who does what

Claude Code owns the repo-native check and the first scored list. You own the review, the campaign, and the meeting. Auth is a revocable API key, not the Claude chat connector.

## Paste this into Claude Code

Finish Omentir first. Put the key in the environment Claude Code already uses for secrets. Point it at https://omentir.com/api/agent/v1/mcp with Bearer auth. Fetch [agents.md](https://omentir.com/agents.md). Replace the brackets. Keep the last two sentences.

```
You are the sales outreach operator for my company. You work from this repo through Omentir.

My product helps [buyer] get [result]. Best-fit accounts are [company type, size, region]. Strong signals: [signal]. Skip [bad fit].

Work only through Omentir MCP or REST. Read https://omentir.com/agents.md if you have not. Start with get_context, then list_agents. If no finder matches this ICP, show me a create_agent config and wait for a yes.

Pull up to 30 people. For each one write fit 1-5, the evidence, any risk, and a two-sentence draft that cites a real trigger. If a note could fit two buyers, rewrite it.

Do not send. Do not enroll. Do not sign into LinkedIn.
Do not create, delete, or reply unless I ask in this session.
```

## Related

- [Claude Code outbound](https://omentir.com/use-cases/claude-code-outbound.md)
- [Claude Code integration](https://omentir.com/integrations/claude-code.md)
- [Claude Code for LinkedIn outreach](https://omentir.com/blogs/claude-code-linkedin-outreach.md)

## Common questions

**Does Claude Code keep working after I close the terminal?**

No. That is [Grok Bot](/help/what-is-the-difference-between-grok-bot-and-grok-com). Claude Code is a session in the repo.

**Is this the same as Claude on claude.com?**

No. Chat Claude uses Settings, Connectors, and workspace approval. Claude Code uses a Bearer key. See [Claude Code or Claude chat](/help/should-i-use-claude-code-or-claude-chat-for-sales).

**Can Claude Code send LinkedIn messages?**

It can call Omentir tools under your campaign and safety settings. It should not type in LinkedIn. Keep send behind review.

**Should I pick Cursor instead?**

Pick the window you already live in. Cursor is the editor. Claude Code is the terminal. Same key pattern. See [Claude Code versus Cursor](/blogs/claude-code-vs-cursor-for-outbound).

**Do I need Claude Code if I already use Omentir?**

No. Overview already finds people and drafts notes. Add Claude Code if that terminal is already open.

[Create an Omentir account](https://omentir.com/signup). Pro is $49/month.