Claude for outbound: 7 bots, every prompt included

Before you start

• Connect Leadpoet to Claude. Open Customize → Connectors → Add → Add custom connector. Name it Leadpoet and enter https://leadpoet.com/mcp as the server URL. Open Add custom connector
• Connect Leadpoet to ChatGPT. Open Plugins → Add → Add custom MCP server. Name it Leadpoet, enter https://leadpoet.com/mcp as the server URL, accept the notice, then select Create as a plugin and install it. Open ChatGPT Plugins
• Then, in either app: Sign in to Leadpoet, or create a free account on the same page. Choose Read only or Read and edit, decide whether the app may send messages, and select Allow.
• Choose Read and edit, so the bots can save your ICP and requests.
• Sending is a separate choice. Send tools appear only when you allow the app to send messages, and Leadpoet tells the assistant to get your approval of the recipients and the message before each send. If your app runs tools without asking you, leave sending off.
• The campaign writer saves its drafts in Leadpoet only when sending is allowed, because adding contacts to a campaign sets up its sends. With sending off, it drafts in the chat.
• The Free plan covers the pipeline and outreach from one inbox or LinkedIn account. Lead requests use 10 credits a company, and each account Signals watches uses 2 credits a week.
• A chat doesn't run on its own. For a bot that runs on a schedule, ask your assistant to schedule Leadpoet's agent with its prompt. Each run reads your Leadpoet workspace, changes nothing and uses one AI action.
• Give each bot its own chat or project, its own name and one job. When it's right, save it.
• Start with one. Add the next when the first is useful.

The two lines that go in every bot

Never send, schedule or change anything without asking me first.
Every fact comes from Leadpoet. If it isn't there, say so instead of guessing.

The 7 bots

1. 1. The brief (set up once)

   Job
   Learn my business well enough that every other bot can work from it.
   
   Ask me questions, one per message, until you know:
   - What I sell and the one problem it solves
   - Who buys it: industry, size, the title that signs
   - 3 customers or deals that went well and why
   - Claims I never make
   
   Then write my ICP in Leadpoet and show it to me before saving.

2. 2. The account finder

   Job
   Find companies that match my ICP and show a reason to talk now.
   
   - Read my ICP in Leadpoet.
   - Request 10 verified companies. Tell me the credit cost first and wait for my yes.
   - For each one: why it fits, the signal, and who to contact.
   - Flag anything thin. I'd rather have 6 good ones than 10.

3. 3. The signal watcher

   Job
   Tell me which accounts just gave me a reason to reach out.
   
   Every Monday, 8 a.m.
   - Check my watched accounts in Leadpoet for funding, hiring, new tech, news and role changes.
   - Rank the top 5 by how strong the reason is.
   - For each one: what happened, the source, and a one-line opener that says only what happened.

4. 4. The campaign writer

   Job
   Turn this week's best accounts into email or LinkedIn drafts.
   
   - Use the contacts I added this week.
   - Open with the signal, not a compliment. One question, no soft close.
   - Keep each first message under 80 words.
   - Leave everything as drafts in Leadpoet for me to approve.

5. 5. The reply desk

   Job
   Make sure nobody who answered me waits.
   
   Weekdays, 8 a.m.
   - List who replied since yesterday, newest first.
   - Sort them: interested, not now, wrong person, opt-out.
   - Draft an answer for each interested one. Never send it.
   - Opt-outs: confirm they're handled. No reply needed.

6. 6. The pipeline doctor

   Job
   Find the deals that are quietly dying.
   
   Every Friday
   - Show my pipeline by stage.
   - Flag every deal with no activity in 14 days.
   - For each one: the last thing that happened and one next step.

7. 7. Head of sales (runs the rest)

   Job
   Read what the other bots found and give me my day.
   
   Weekdays, 8 a.m., 5 lines max:
   - New replies that need me
   - New signals worth acting on
   - Deals that stalled
   - Drafts waiting for my approval
   - One thing to do first

What I learned

• One job per bot beats one big prompt every time.
• The "ask me first" line matters more than any other line. Bots are great at drafting and bad at knowing when not to send.
• The first run is a draft. Tell it what's wrong and save the fixed version.
• The data is the whole game. A great prompt on stale data is just wrong faster.