Most people use Claude for one-off tasks and get generic output. These guides fix that. Each edition walks you through setting up a Claude Project with persistent context for your specific role — so every conversation starts with Claude already understanding your business.
Each edition is built for a specific B2B function with role-specific use cases and constraints.
The .txt file has placeholders for your ICP, product, methodology, team, and preferences.
Create a Claude Project, paste the template, and every conversation starts with full context.
For SDRs, BDRs & AEs
For VPs of Marketing, CMOs & Heads of Demand Gen
For VPs of Sales, CROs & Heads of Sales
For Heads of RevOps, Sales Ops & Marketing Ops
When you use Claude without a Project, every conversation starts from zero. Claude does not know your ICP, your product, your methodology, or your team. So it gives you generic output that sounds like it could have been written for anyone.
A Claude Project stores persistent context that Claude reads before every conversation. The difference is immediate: pipeline reviews reference your actual reps, cold emails match your voice, and campaign briefs align with your real brand guidelines.
Without a Project
"Write me a cold email to a VP of Sales at a mid-market SaaS company."
Generic output. No ICP context. No voice. No product specifics.
With a Project
"Write a cold email for the Acme Corp account."
Claude already knows your ICP, product, voice, banned phrases, and email constraints. Output is specific and usable.