What Is CLAUDE.md and How to Write One for Your Sales Methodology
CLAUDE.md is the file that turns Claude Code from a general AI assistant into a specialist that knows your sales process, ICP and messaging. Here is how to write one.
If you are using Claude Code without a CLAUDE.md file, every session starts from scratch. The AI does not know your business, your customers or your sales process. You re-explain everything, every time.
CLAUDE.md fixes this. It is a single file that sits in your project root and gives Claude Code persistent context about who you are, what you sell and how you sell it. Think of it as a constitution for your AI assistant.
For B2B sales teams, this is the difference between an AI that writes generic outreach and one that sounds like your best salesperson on their best day.
What is CLAUDE.md and why every sales team needs one
CLAUDE.md is a markdown file that Claude Code reads automatically at the start of every session. It contains your business context, rules and preferences in a structured format.
According to best practices published in March 2026, a well-written CLAUDE.md runs about 120 lines. Enough to encode your entire sales methodology without overwhelming the AI's context window.
Without one, you are starting cold every session. You tell Claude about your ICP. You explain your pricing. You describe your tone. Then tomorrow you do it all again.
With CLAUDE.md, Claude already knows your ideal customer profile, your signal triggers, your messaging framework, your AU compliance requirements, your quality gates and your folder structure.
The six sections every sales CLAUDE.md needs
Here is the structure we use at Njin when building CLAUDE.md files for our clients' sales playbooks.
1. Business context (10-15 lines)
Who you are and what you do. Company name, what you sell, your market position and your value proposition. Include your revenue model and average deal size so Claude understands the stakes of every interaction.
2. Ideal customer profile (15-20 lines)
Revenue range, team size, industry, job titles you target and the problems they face. Include your disqualification criteria too. Tell Claude who you do not want to sell to.
3. Signal trigger taxonomy (10-15 lines)
The events that indicate a prospect is likely to buy. Leadership changes, funding rounds, hiring patterns, technology adoption signals. Rank them by strength so Claude knows which deserve immediate action.
4. Messaging framework (20-30 lines)
Your positioning statement, key value propositions, proof points and call-to-action patterns. Specify your tone of voice. Include the top 5-10 objections and your preferred responses.
5. AU compliance constraints (15-20 lines)
Spam Act 2003 requirements, DNCR rules, consent management and any industry-specific regulations. AI does not automatically know AU law. You have to tell it. Once it is in the file, it applies every time.
6. Folder structure and tools (10-15 lines)
Where everything lives. Templates, case studies, pricing docs. Which MCP servers are available. CIO.com called MCP "the USB-C of AI" because it standardises how AI tools connect to external systems.
CLAUDE.md vs a system prompt
A system prompt is temporary. It exists for one conversation. CLAUDE.md lives in the project, is version-controlled, editable by the team and read automatically at the start of every session.
For sales teams with complex methodologies, CLAUDE.md is far more reliable. It cannot be forgotten, overwritten or left out by accident.
How Njin uses CLAUDE.md
Every Njin client gets a custom CLAUDE.md as part of their sales playbook. It is built from their ICP, their messaging, their compliance requirements and their qualification criteria.
When their team uses Claude, it follows their methodology. And when connected to their CRM, the AI knows how to interpret what it finds there.
This approach draws directly from our complete sales AI playbook and the CRM integration guide.
Common mistakes to avoid
- Too long - Over 200 lines means Claude spends too much context on instructions. Edit ruthlessly.
- Too vague - "We sell to businesses" is useless. "$2M-$20M ARR SaaS companies with 10-100 employees" is useful.
- Missing compliance - AU businesses must include Spam Act and DNCR rules.
- No examples - Show Claude what good and bad output looks like. Examples beat instructions.
- Never updated - Your ICP changes. Review your CLAUDE.md monthly.
Getting started today
You do not need to be a developer to write a CLAUDE.md. It is just a text file in markdown. If you can write a sales brief, you can write a CLAUDE.md.
Start with the six sections above. Spend 30 minutes on your first draft. Use it for a week, notice where Claude gets things wrong, and refine. Most teams get to a solid version within 2-3 iterations.
