Rep Onboarding

IntuBlade Outbound Setup

Set up Claude to research fire and EMS departments and write personalized cold emails. It finds the contacts, the signals, and writes the email in your voice. No coding. Follow the steps.

20 minutes total
1
Get a Claude account
2 minutes
  1. Go to claude.ai and create an account (or sign in if you have one)
  2. Upgrade to Pro ($20/month). Click your name in the bottom-left, then "Upgrade to Pro"
i You need Pro for Claude Code access. The free plan won't work.
2
Install Claude Code
3 minutes

Open your terminal app. On Mac that's Terminal (search for it in Spotlight). On Windows, open PowerShell.

Copy and paste this command, then hit Enter:

terminal
npm install -g @anthropic-ai/claude-code
Don't have npm? Install Node.js first

Go to nodejs.org and download the LTS version. Install it (just click Next through the installer). Then come back and run the command above.

To check if you already have it, run:

terminal
node --version

If it shows a version number (like v22.x.x), you're good. If it says "command not found," install Node.js first.

Getting a "permission denied" error on Mac?

Run it with sudo instead:

terminal
sudo npm install -g @anthropic-ai/claude-code

It will ask for your computer password. Type it (nothing will appear as you type, that's normal) and hit Enter.

3
Download the outbound kit
2 minutes

This downloads the sales playbook, the AI advisors, and all the reference materials Claude needs.

Copy and paste this into your terminal:

terminal
git clone https://github.com/napiermd/outbound-council.git ~/outbound-council
Don't have git?

Mac: Open Terminal and type git. If it's not installed, your Mac will prompt you to install the Xcode command line tools. Click "Install" and wait.

Windows: Go to git-scm.com and download the installer. Run it with default settings.

i This creates a folder called outbound-council in your home directory. That's where you'll work from.
4
Set up your CLAUDE.md
1 minute

Copy the rep instructions into the right place so Claude reads them automatically:

cp ~/outbound-council/rep-kit/CLAUDE.md ~/outbound-council/CLAUDE.md
copy $HOME\outbound-council\rep-kit\CLAUDE.md $HOME\outbound-council\CLAUDE.md
5
Create your voice profile
5 minutes

This is the most important step. Your voice profile teaches Claude to write like you, not like a robot.

  1. Open the file ~/outbound-council/voices/voice-template.md in any text editor (TextEdit, Notepad, VS Code, whatever you have)
  2. Fill out every section. Be honest. If you're casual, say so. If you never say "synergy," put it in the "never say" list.
  3. Save it as your name: ~/outbound-council/voices/danny.md (use your actual name)
! Don't skip this. Without your voice file, Claude writes generic corporate AI output. With it, emails sound like you.
How to open the file on Mac

Paste this in Terminal to open it in TextEdit:

terminal
open -a TextEdit ~/outbound-council/voices/voice-template.md

After editing, use File > Save As and save it as your name (e.g., danny.md) in the same voices folder.

How to open the file on Windows

Paste this in PowerShell:

powershell
notepad $env:USERPROFILE\outbound-council\voices\voice-template.md
6
Add your API key
1 minute. Andrew gives you the key.

Andrew will give you an API key. Create a file called .env in your outbound-council folder with this content:

terminal
echo "SUPABASE_ANON_KEY=your_key_here" > ~/outbound-council/.env

Replace your_key_here with the key Andrew gives you. This connects Claude to HubSpot and the IntuBlade database so your research and emails get tracked automatically.

! Don't share this key or commit it to git. It stays in your local .env file only.
7
Sign in to Claude Code
1 minute. First time only.

The first time you run Claude Code, it needs to connect to your Claude account. Run this in your terminal:

terminal
cd ~/outbound-council && claude

Your browser will open and ask you to sign in with your Claude account. Sign in, click "Allow," and come back to the terminal. You'll see a chat interface. Type /quit to exit for now. We have one more setup step.

i This only happens once. After you sign in the first time, Claude Code remembers your account.
8
Connect your Gmail
So Claude can create drafts directly in your inbox. No copy-pasting.

When you first run Claude Code, it will ask you to sign in. After that:

  1. Go to claude.ai/settings/integrations
  2. Find Gmail and click Connect
  3. Sign in with your work Gmail account (the one you send outreach from)
  4. Grant the permissions it asks for (read and create drafts)
i This is a one-time setup. Once connected, Claude can create email drafts directly in your Gmail. You still review and hit send yourself.
What permissions does Claude get?

Claude can read your emails (to find reply threads) and create drafts (to put outreach emails in your Drafts folder). It cannot send emails on your behalf. You always hit send.

What if I don't want to connect Gmail?

That's fine. Claude will show you the finished email in the terminal and you copy-paste it into Gmail. It works, it's just an extra step per email.

9
Start Claude
You're done with setup. This is how you work every day.

Every time you sit down to do outreach, run these two commands:

terminal
cd ~/outbound-council && claude

That's it. Claude opens in your terminal with the full IntuBlade playbook loaded. Start typing.

Claude automatically reads all the reference files, the sales council, the anti-AI rules, and your accumulated learnings. You don't need to upload or configure anything each time.
Daily Workflow

Two things Claude does for you

Research departments and write emails. Here's how both work.

1
Research a department
Just give Claude a department name. It finds everything.

You don't need to Google anything first. Just tell Claude the department name and state. It will find the chief, medical director, training officer, fleet data, and recent news.

Example: Research
You

Research Parma Fire Department in Ohio. Find me everyone I should contact and any recent news.

Claude

Claude searches the web and comes back with a structured report:

Parma Fire Department — Research Summary People Found | Role | Name | Email | Source | | Chief | Michael Lasky | firechief@cityofparma-oh.gov | cityofparma-oh.gov staff directory | | Medical Director | Dr. Christopher Dussel | christopher.dussel@uhhospitals.org | UH Hospitals EMS page | | Deputy Chief | Mark Brickman | — | Department website | Department Profile - 7 stations, 11 apparatus, ALS - ~5,500 EMS runs/year, ~108 intubations/year - Serves City of Parma (pop. 81,000) Signals 1. SAFER grant for 12 firefighters (Jan 2026) — FEMA awards database 2. Record call volume in 2025 — Parma Observer article Confidence Notes - Chief email verified from city staff directory - MD email verified deliverable (SMTP check score: 100) - Training officer: NOT FOUND

You

Can you also find their training officer? And check if Dr. Dussel covers any other departments nearby.

Claude

Claude digs deeper and reports back with what it found (or didn't find).

i Claude will tell you what it verified vs. what it couldn't confirm. Always check the "Confidence Notes" section before using any contact info.
1b
Research prompts you can use
Copy any of these. Replace brackets with real info.
full research
Research [department name] in [state]. Find the chief, medical director, training officer, fleet info, and any recent news I can use in an email.
find contacts
Who are the key contacts at [department name]? I need the chief, medical director, and anyone involved in equipment decisions.
find medical director
Find the medical director for [department name] in [city], [state]. Check hospital system EMS pages and NPI registry.
find recent news
What recent news, grants, or events has [department name] had in the last 6 months? I need something current for a cold email opener.
verify an email
Verify this email address before I use it: [email]. Check the city staff directory or department website to confirm it actually exists.
2
Write the email
After research, tell Claude to write the email. It uses everything it found.
Example: Research then Email
You

Good research. Now write me a cold email to Chief Lasky. CC Dr. Dussel.

Claude

Claude writes the email in your voice, scores it against all 6 sales advisors, checks for AI slop, and shows you the result with scores. If anything scores below 6, it rewrites automatically.

You

The opening is too generic. Use the SAFER grant. And make it shorter.

Claude

Claude rewrites with your feedback, re-scores, and shows the updated version.

You

Looks good. Create the draft.

Claude

Draft created in your Gmail.

To: firechief@cityofparma-oh.gov
CC: christopher.dussel@uhhospitals.org
Subject: Video laryngoscopy for Parma Fire - no cost

Open Gmail, check your Drafts folder, review one more time, then hit send. Want to move to the next department?

2b
Email prompts you can use
Copy any of these after you've done the research step.
write email from research
Write a cold email to the chief using the research above. CC the medical director if we have a verified email.
score your own email
Score this email against the council:

[paste your email here]
iterate
Make it shorter. Under 120 words.
create gmail draft
Looks good. Create the draft in my Gmail.
no signal found
No recent news on this department. Write a generic deployment kit email using the fleet data from the research.
check for replies
Check my inbox for replies to outreach emails I've sent in the last 3 days.
handle a reply
The chief of [department] replied and said "[their reply]". Help me write a response.
save a learning
Save this to learnings: Dr. Dussel covers Parma Fire, Seven Hills Fire, and Brooklyn Fire.
Know the Rules

What makes a good email

Claude enforces these automatically, but you should know them too.

!
Never use these
These words and phrases scream "AI wrote this." Recipients notice.

Banned sign-offs:

Best regards
Kind regards
Warm regards
Best

Banned openers:

I hope this finds you well
I wanted to reach out
I'm reaching out because
Just following up

Banned words:

delve
seamless
innovative
leverage
robust
cutting-edge
game-changer
synergy
groundbreaking
transformative

Banned punctuation:

Em dashes -- the long dash. Use periods or commas instead.
Bold text in email prose
"Additionally," / "Furthermore," / "Moreover," to start sentences
See the full list

The complete list is in references/anti-ai-slop.md in your outbound-council folder. Claude reads this file automatically, but you should read it once to know what it catches.

What good emails look like
Short. Specific. Opens with their world.
Troubleshooting

Common issues

"command not found: claude"

Claude Code isn't installed. Go back to Step 2 and run the install command. If you just installed Node.js, close your terminal and open a new one first.

"command not found: npm"

Node.js isn't installed. Go to nodejs.org, download the LTS version, install it, then close and reopen your terminal.

Claude isn't using my voice

Make sure your voice file is saved in the voices/ folder inside the outbound-council directory. The file name should be your name (e.g., danny.md). If Claude still isn't picking it up, type: "Read my voice file from the voices folder and use it."

Claude is writing generic emails

You probably didn't give it enough research. The more specific details you paste in (chief name, station count, recent news), the more specific the email will be. If you just say "write an email to a fire department," you'll get garbage.

Claude used a banned word

Tell it: "That email has banned words from the anti-AI-slop list. Rewrite it." If it keeps happening, start a new conversation. Long conversations can drift.

How do I update to the latest version?

When Andrew updates the playbook or references, pull the latest:

terminal
cd ~/outbound-council && git pull
IntuBlade Outbound Kit · Questions? Ask Andrew.