How many times have your reps re-explained the same ICP criteria, messaging preferences, and exclusion rules to Claude Code before launching a campaign? A CLAUDE.md file for sales solves this by packaging your entire sales configuration into one file that Claude Code reads automatically. This guide shows you what a CLAUDE.md file is, why it outperforms ad hoc prompting, and provides a complete copyable template you can deploy immediately. Fusse Network executes what Claude Code produces once it reads this file, turning configuration into actual sent emails and booked meetings.
What Is a CLAUDE.md File for Sales?
A CLAUDE.md file for sales is a structured configuration file that Claude Code reads automatically to understand your ICP, messaging guidelines, exclusion criteria, and campaign parameters without requiring manual explanation in every session. The file acts as a persistent context that transforms Claude Code from a general-purpose AI into a specialized sales automation engine configured specifically for your business. Instead of starting from scratch each time, your team references one source of truth that maintains consistency across all campaigns.
The file lives in your project directory where Claude Code can access it. When you start a new campaign, Claude Code pulls the configuration automatically and applies your rules without prompting. This architecture eliminates the friction of repeated explanations and ensures every campaign follows the same quality standards.
Why Claude Sales Automation Needs Persistent Configuration
Ad hoc prompting creates three problems that kill sales productivity. First, every rep explains context differently, leading to inconsistent campaign quality. Second, critical details get dropped between sessions when context doesn’t persist. Third, teams waste hours re-explaining the same ICP criteria, messaging preferences, and operational rules.
Traditional Claude sales implementations require you to provide full context in every conversation. You explain your target company size, then your exclusion criteria, then your messaging tone, then your sending limits. Miss one detail and the campaign quality suffers. Start a new chat session and you’re back to square one.
Configuration files solve this by establishing persistent context that Claude Code references automatically. The configuration exists as a single source of truth. Your ICP definition stays consistent. Your messaging guidelines don’t drift. Your exclusion criteria apply uniformly. New team members use the same configuration as experienced reps, maintaining quality across your entire sales operation.
The efficiency gains are measurable. Campaign setup that traditionally takes 4-6 hours drops to 30-60 minutes when Claude Code works from a properly configured file. Subsequent campaigns using the same configuration launch even faster. The file becomes more valuable over time as you refine it based on campaign results.
Your Complete Template for Sales Teams
Copy this template directly into a file named CLAUDE.md in your project directory. Customize each section with your specific criteria.
# Sales Campaign Configuration
## Ideal Customer Profile
### Target Company Criteria
- **Industry**: B2B SaaS companies
- **Company Size**: 50-500 employees
- **Funding Stage**: Series A through Series C
- **Revenue Threshold**: Minimum $5M ARR
- **Geography**: United States-based headquarters
- **Growth Signals**: Active hiring for sales or revenue roles in last 90 days
### Target Decision Makers
- VP of Sales
- Head of Revenue
- Chief Revenue Officer
- VP of Business Development
- Director of Sales Operations
### Intent Signals to Prioritize
- Recent funding announcements (within last 6 months)
- Job postings for SDR, AE, or sales leadership positions
- Technology stack includes Salesforce, HubSpot, or similar CRM
- Company blog posts about scaling sales operations
- LinkedIn posts from executives about revenue challenges
## Messaging Guidelines
### Brand Voice
- Professional but conversational tone
- Data-driven with specific metrics
- Consultative rather than transactional
- Focus on efficiency gains and ROI
### Key Value Propositions
1. Reduce campaign setup time by 87.5% compared to manual processes
2. Achieve 85-95% email coverage through waterfall enrichment
3. Generate hyper-personalized outreach at scale
4. Lower operational costs versus traditional SDR hiring
### Personalization Requirements
- Reference specific funding rounds with dollar amounts
- Mention relevant job postings by exact title
- Acknowledge company growth trajectory with concrete metrics
- Connect our solution to their specific market segment challenges
### Email Sequence Structure
- **Email 1**: Problem awareness with industry-specific pain point
- **Email 2**: Solution introduction with relevant use case
- **Email 3**: Social proof with similar company case study
- **Email 4**: Direct call-to-action with calendar booking link
- **Timing**: 2-3 days between emails, send Tuesday-Thursday 9 AM - 4 PM local time
## Exclusion Criteria
### Company Exclusions
- Agencies and consulting firms
- Companies with less than $5M ARR
- Non-profit organizations
- Government entities
- Companies outside United States
- Competitors in our category
### Contact Exclusions
- Generic email addresses (info@, contact@, hello@, support@)
- Previously contacted within last 90 days
- Existing customers or active opportunities in CRM
- Contacts who previously opted out
- Job titles below Director level
### Topic Exclusions
- Avoid mentioning competitors by name
- No claims about replacing human sales teams
- No unrealistic ROI promises or guarantees
- Skip technical jargon unless prospect's background indicates understanding
## Tools and Connected Systems
### Data Enrichment
- **Primary**: Fusse Network API for contact enrichment and verification
- **Secondary**: Apollo.io for additional coverage when needed
- **Email Verification**: Minimum 85% confidence score required
### Sending Platform
- **Primary**: Instantly.ai for email sequences
- **Daily Limit**: 50 emails per inbox maximum
- **Warmup**: All new inboxes require 14-day warmup period
### CRM Integration
- **System**: Salesforce
- **Sync Requirements**: Log all sent emails, track opens and clicks, create tasks for replies
- **Lead Status**: Mark as "Outbound - Contacted" upon first send
### Intent Signal Tracking
- Monitor funding announcements via Crunchbase
- Track job postings through LinkedIn and company career pages
- Identify technology stack changes through BuiltWith
## Campaign Rules and Operational Parameters
### Sending Parameters
- Maximum 50 emails per day per inbox
- 2-3 day delay between sequence steps
- Send times: Tuesday-Thursday only, 9 AM - 4 PM recipient local time
- Avoid Monday mornings and Friday afternoons
- Pause all sending on major US holidays
### Data Quality Thresholds
- Require minimum 85% email verification confidence score
- Validate company domain exists and is active
- Confirm LinkedIn profile URL for all contacts
- Verify job title matches target decision-maker criteria
### Response Handling
- Auto-pause sequence immediately upon any reply
- Flag positive responses for same-day follow-up
- Track all opt-outs and update exclusion list within 24 hours
- Log objections with categorization for messaging refinement
- Route meeting requests directly to calendar booking system
### A/B Testing Protocol
- Test subject lines with 10% sample before full send
- Minimum 100 sends required for statistical significance
- Track open rates, reply rates, and meeting booking rates
- Implement winning variation after 48-hour test period
### Approval Requirements
- All new email templates require review before first send
- ICP changes need approval from sales leadership
- Exclusion criteria updates require documentation of reasoning
- Tool integration changes require testing in sandbox environment first
This template covers every component Claude Code needs to execute campaigns consistently. The ICP section defines exactly who to target and which signals indicate buying intent. The messaging guidelines ensure brand voice stays consistent while incorporating required personalization elements. Exclusion criteria prevent wasted outreach and maintain campaign quality. Tool specifications tell Claude Code which systems to query and how to handle the data. Campaign rules establish operational boundaries that protect deliverability and ensure compliance.
Keeping Your Configuration File Current
A configuration file delivers value only when it reflects current reality. Stale configurations lead to poor targeting, outdated messaging, and missed opportunities.
Implement monthly review cycles to analyze campaign performance. Break down results by company size, industry, and funding stage to identify which ICP segments respond best. If Series B companies consistently outperform Series A, adjust your targeting criteria. If certain job titles never engage, remove them from your decision-maker list. The data tells you what works.
Update messaging guidelines based on what resonates. Track which personalization elements drive replies. If mentioning funding rounds generates more engagement than referencing job postings, emphasize funding in your personalization requirements. If certain value propositions fall flat, replace them with messages that perform better.
Refine exclusion criteria as you learn. Some excluded categories might actually be valuable prospects. Some included categories might waste resources. After each campaign, review which contacts engaged positively and which were poor fits. Adjust your exclusions accordingly.
Tool specifications need updates when you add new data sources or change platforms. If you switch from one enrichment provider to another, update the file immediately. If you implement a new intent signal tracking system, add it to your configuration. Keep the file synchronized with your actual tech stack.
Campaign rules should evolve based on deliverability data and response patterns. If certain send times consistently underperform, adjust your timing parameters. If your daily sending limit proves too aggressive for inbox health, lower it. The rules exist to optimize performance, not to stay static.
Version control makes maintenance easier. Treat your configuration file like code. Track changes over time. Document why you made each modification. This creates an audit trail that helps you understand what worked and what didn’t. When you test a new approach, create a variant file and compare results. Keep what performs better.
The best configurations improve continuously based on empirical evidence rather than assumptions. Your file should get sharper with each campaign as you learn which criteria predict success and which waste resources.
Fusse Network Executes What Claude Code Configures
Claude Code reads your configuration file and understands what to do. Fusse Network provides the infrastructure to actually do it.
We’re building the execution layer that turns configurations into real outbound campaigns. The platform provides access to over 800 million verified contacts with 90%+ accuracy for email and phone data. When your file specifies ICP criteria, Fusse Network’s automated lead sourcing identifies matching prospects in real-time. When your configuration requires waterfall enrichment, Fusse Network queries multiple data providers to achieve 85-95% email coverage.
The platform consolidates functions that typically require separate tools. Contact data, enrichment, automation, engagement tracking, and intent signals all operate through one system. Your configuration references Fusse Network as a single integration point rather than managing multiple vendor relationships.
Real-time AI agents provide access to buying signals that match the intent criteria in your configuration. When a target company announces funding or posts a relevant job opening, Fusse Network identifies it immediately. Multi-channel engagement automation executes the sequences defined in your file across email, LinkedIn, and phone.
We’re not claiming to replace your sales team with automation. We’re building for human amplification. Your configuration captures your sales strategy. Fusse Network executes it at scale while your team focuses on high-value conversations with engaged prospects.
The integration between Claude Code and Fusse Network means your configuration flows directly into execution. Planning becomes action without manual data transfers or platform switching. Your file defines what should happen. Fusse Network makes it happen.
Request access to see how Fusse Network executes your sales configurations.
