Context Engineering for LinkedIn ABM Using Claude Code: A Beginner’s Guide

Claude is the new cool kid of the block, and context engineering using Claude code is now the differentiator between actually successful AI-powered LinkedIn account-based marketing (ABM) campaigns and bogus ones.

So, if you’re up to ABM, but new to Claude (or have been using Claude without utilising its context engineering capability), this article is the perfect beginner’s guide for you.

Here, I have first discussed the importance of context engineering with data-backed claims, then have briefly touched on some theory, and finally have shared real steps to set up Claude Code for ABM, a Claude.md template, some real ABM examples, and more.

Let’s go!

A Beginner’s Guide to Context Engineering for LinkedIn ABM Using Claude Code: Quick Summary

Short on time?

Here’s a quick overview:

• Most GTM teams are still getting little or no value from AI because they use it like a chatbot instead of building persistent context systems.
• Prompt engineering means re-explaining your company, ICP, brand voice, and standards every time.
• Context engineering means Claude Code already knows that information before the task begins.
• For LinkedIn ABM, that difference matters a lot because better context directly improves personalization quality, outreach relevance, pipeline velocity, and consistency.
• The article breaks context engineering into four practical building blocks: CLAUDE.md for persistent context, Skills for reusable playbooks, MCP for tool access, and Hooks for deterministic quality control.
• CLAUDE.md should stay lean and high-signal. It holds your positioning, ICP, brand voice, competitors, content rules, and quality standards, so Claude starts every session with the right operating context.
• Skills let you turn repeatable ABM workflows into reusable systems, such as account research, outreach generation, LinkedIn post creation, campaign analysis, and competitive battlecards.
• MCP is what makes Claude genuinely useful for GTM work because it can read directly from tools like Clay, HubSpot, Salesforce, Gong, Slack, GA4, Notion, and many others instead of relying on manual copy-paste.
• Hooks solve the “Claude forgot my rules” problem by enforcing checks automatically. They can inject campaign context at session start, run brand voice compliance after file writes, and notify teams when work is done.
• The article’s before-and-after example shows how context engineering transforms a generic “research Acme Corp” prompt into a real ABM research workflow with funding signals, hiring signals, ICP scoring, pain points, and outreach angles.
• The quickstart is intentionally practical: install Claude Code, create a project folder, paste the CLAUDE.md template, run one research task with context, then run the same task without context and compare outputs side by side.
• ZenABM strengthens this setup by offering its own MCP server, which lets you connect LinkedIn ads performance and ABM data directly into Claude Code to build dashboards, combine reporting sources, trigger agents on engagement thresholds, and generate executive-ready reporting from campaign data.

Why 53% of GTM Teams Saw Zero Impact from AI

In February 2026, Maja Voje (GTM Strategist, author of GTM Strategist, Claude partner) and Kyle Poyar (Growth Unhinged) published their 2026 State of AI for GTM report.

The findings were brutal:

• 53% of GTM leaders reported little to no impact from AI. Only 24% said they were seeing real returns. And 47% had zero AI agents running in production.
• The gap between the winners and everyone else wasn’t intelligence, budget, or tools. It was structural.
• The 24% seeing results had built persistent context systems.
• The 53% seeing nothing were treating AI like a chatbot: type a prompt, get a response, start over next time.

Well, the last point is the exact problem that context engineering solves.

And for LinkedIn ABM specifically, where personalization quality directly determines response rates, pipeline velocity, and win rates, the difference between these two approaches is much more than just ‘significant.’

What Context Engineering Actually Means (the Practitioner Definition, Not the Philosophy)

The term ” Context Engineering” went mainstream on June 18, 2025, when Shopify CEO Tobi Lutke posted on X: he preferred “context engineering” over “prompt engineering” because it better described the core skill.

The post hit 2 million views and counting.

A week later, Andrej Karpathy endorsed it, mapping context engineering to the components that fill an LLM’s context window: task descriptions, examples, retrieved data, tools, state, and history.

But the most actionable definition for GTM teams came from Phil Schmid (formerly Hugging Face):

“Context Engineering is the discipline of designing and building dynamic systems that provides the right information and tools, in the right format, at the right time, to give a LLM everything it needs to accomplish a task.”

His critical follow-up: “Most agent failures are not model failures anymore. They are context failures.”

Anthropic’s engineering team published the canonical treatment in September 2025, defining context engineering as the strategies for curating and maintaining the optimal set of tokens during inference.

Their key insight: bigger context windows don’t solve the problem. You need the smallest possible set of high-signal tokens that maximize your desired outcome. Irrelevant context doesn’t just waste space. It actively degrades output quality through what they call “context rot,” where model accuracy drops as token count increases.

Here’s what this means in plain English for ABM practitioners:

• Prompt engineering = you write a clever question every time you need something from AI. The AI knows nothing about your company, your ICP, your brand voice, your competitors, or your campaign history. You re-explain everything from scratch.
• Context engineering = you build a system where the AI already knows your company, ICP, brand voice, competitors, campaign history, and quality standards before you ask it anything. You give it instructions once. It remembers forever.

As Maja Voje frames it in her GTM Guide to AI Context Engineering:

“Prompt engineering is writing a clever brief for every single task. Context engineering is building the team that doesn’t need a brief, because the institutional knowledge, the playbooks, the quality standards, and the tool access are already baked into how the operation runs.”

Context Engineering vs. Prompt Engineering: Side-by-Side with ABM Task Examples

To better understand the difference between prompt engineering and context engineering for account-based marketing, let’s see how they work for a common task.

The task: Research Acme Corp and generate a personalized LinkedIn outreach sequence.

Prompt engineering approach (what most people do):

Research Acme Corp and write a 5-message LinkedIn outreach sequence for their VP of Marketing. We sell an ABM analytics platform.”

What you get back: generic company overview pulled from Wikipedia, bland messages like “I noticed your company is growing” and “Would love to connect about ABM,” no awareness of your brand voice, product positioning, or what makes your solution different from competitors.

Context engineering approach (what the 24% do):

Claude Code reads your CLAUDE.md at session start.

It already knows:

• your product
• your ICP
• your brand voice
• your competitors
• your quality standards.

Now, when you type the same task, Claude Code:

• Searches the web for Acme Corp’s recent funding, product launches, and hiring patterns
• Checks their LinkedIn company page for recent posts about marketing challenges
• Identifies their VP of Marketing’s LinkedIn activity, stated priorities, and pain points.
• Maps their pain points to YOUR specific product features (not generic ABM benefits)
• Generates outreach in YOUR brand voice using YOUR positioning against THEIR specific situation
• Formats each message within LinkedIn’s character limits, following YOUR proven outreach structure

The output references specific details about Acme Corp, uses your exact product language, follows your proven 5-message cadence, and sounds like your best BDR on their best day. Every. Single. Time.

Here’s the comparison in a table:

The Four Components: CLAUDE.md, Skills, MCP, and Hooks

Four components make context engineering work in Claude Code.

Think of them as layers of a system, each one making the next more powerful.

Block 1: CLAUDE.md

CLAUDE.md is a plain text file that Claude Code reads automatically at every session start.

It’s persistent memory.

Whatever you put in this file, Claude knows before you type your first prompt.

For a LinkedIn ABM team, your CLAUDE.md contains:

• Your company’s positioning statement and product description
• Your ICP definition (firmographic, technographic, and psychographic criteria and anything else that you factor in)
• Brand voice rules (10 rules maximum, with examples of good and bad output)
• Competitor names, their positioning, and your counter-positioning angles
• Content format specifications (LinkedIn post character limits, email length guidelines, etc.)
• Quality standards (never fabricate data, always cite sources, banned words list, etc.)

The key insight from the r/ClaudeAI community: keep it under 80 lines. One practitioner reported that reducing from 200 lines to 45 actually improved output quality. The reason is technical: Claude Code’s system prompt already contains ~50 built-in instructions, and frontier models reliably follow approximately 150-200 total instructions. Every CLAUDE.md line competes against that budget.

You’ll find the complete fill-in-the-blank CLAUDE.md template in Section 7 of this article below.

Block 2: Skills (Your Specialist Playbooks)

Skills are SKILL.md files that encode specific marketing workflows into reusable playbooks.

Unlike CLAUDE.md (which is always loaded), Skills activate automatically only when the task matches their description.

This means you can have dozens of specialized playbooks without wasting context space.

For LinkedIn ABM, your Skills library might include:

• Account research skill: given a company name, research firmographics, pain points, buying committee, and output a structured brief
• Outreach generation skill: given an account brief, generate a 5-message LinkedIn sequence following your proven cadence
• LinkedIn post skill: generate posts matching your voice using your examples and hook patterns
  Campaign analysis skill: read campaign data, compare against benchmarks, and output optimization recommendations
• Competitive analysis skill: research a competitor and output a structured battlecard

Skills use a three-level progressive disclosure architecture (documented in Anthropic’s engineering blog on Agent Skills): only the skill name and description load at startup (costing minimal tokens), the full instructions load only when triggered, and reference files load only when needed.

This means zero wasted context.

Anthropic’s insight: “Building a skill is like putting together an onboarding guide for a new hire.”

If you’ve given the same instructions to Claude 3 times, it’s time to turn it into a Skill.

Pro Tip: For a head start, you can install Corey Haines’ open-source marketing skills library (12 skills covering SEO, CRO, copywriting, paid ads, growth engineering) with one command:

npx skillkit install coreyhaines31/marketingskills

Block 3: MCP (Your Tool Connections)

The Model Context Protocol connects Claude Code to your existing tools.

Instead of copy-pasting data between platforms, Claude reads directly from your CRM, enrichment tools, and analytics.

ABM-relevant MCP connections available right now:

ZenABM also provides an MCP server, which allows you to connect your LinkedIn ads performance and ABM data directly to any LLM that supports the Model Context Protocol – most notably, you guessed it right, Claude Code.

This means you can:

• Build bespoke ABM analytics dashboards tailored to your company’s specific needs
• Create custom reporting that combines ZenABM data with other data sources
• Build agents that act on your data automatically (e.g., trigger outreach when accounts reach certain engagement thresholds)
• Generate executive reports and board-ready presentations directly from your campaign data

Block 4: Hooks (Quality Control)

Here’s the critical difference: CLAUDE.md rules are advisory.

Claude can ignore them.

But hooks are deterministic.

They always execute.

No exceptions at all!

Hooks are automated checks that fire at specific points in Claude Code’s lifecycle:

• SessionStart hook: auto-inject today’s campaign brief and priority accounts at every session start
• PostToolUse hook: run a brand voice compliance check every time Claude writes a content file
• Stop hook: send a Slack notification to your team channel when a research task completes

For marketing teams, hooks solve the “Claude forgot my rules” problem permanently.

If your brand voice guide says never use the word “leverage,” a hook will catch it every single time, even when CLAUDE.md instructions get lost in a long session.

The hooks system supports 16+ lifecycle events, including PreToolUse (block or modify actions before they happen), PostToolUse (auto-format after writes), and Notification (desktop alerts).

Configuration lives in .claude/settings.json as a simple JSON structure.

Before and After: The Same Account Research Task, Two Approaches

So, this example is based on GrowthSpree’s documented Claude ABM workflow, one of the most complete production ABM systems built with Claude Code.

Without context engineering (generic prompt):

You type: Research Acme Corp for our ABM campaign.

You get back: a Wikipedia-style company summary, generic industry challenges, no connection to your product, no personalization hooks, no outreach angles. Useful for a school report. Useless for pipeline generation.

With context engineering (CLAUDE.md + Skills + MCP) based on GrowthSpree’s framework:

You type the same thing.

But Claude Code already has your CLAUDE.md (knows your ICP, product, voice), your account research Skill (knows the 6-section brief format), and Brave Search MCP (can access current web data).

What Claude Code actually does:

• Step 1: Searches the web for Acme Corp’s recent funding ($25M Series B, announced 3 weeks ago)
• Step 2: Finds their VP of Marketing’s LinkedIn posts about struggling with ABM attribution on LinkedIn ads
• Step 3: Discovers they’re hiring 3 demand gen roles (signal: scaling marketing spend)
• Step 4: Checks their tech stack via BuiltWith data (HubSpot CRM, running LinkedIn ads, no ABM analytics tool)
• Step 5: Maps all findings to your ICP scoring criteria: 85/100 (Tier 1 account)
• Step 6: Outputs a structured brief with: company snapshot, buying committee map, 4 specific pain points, 3 personalization hooks for outreach, and recommended engagement sequence

GrowthSpree documented this system mining 35+ contacts across 15 companies in a single session, replacing 3-4 hours of manual BDR research.

Here’s their video demonstration (starts at 00:45):

Result?

As per their claims, their personalized outreach sequences achieved 2-3x higher response rates versus generic templates.

The 15-Minute Quickstart: Install Claude Code, Paste the Template, See the Difference

Let’s set this up right now.

You need: a computer with Node.js installed, an Anthropic account (Pro plan at $20/month is sufficient to start), and 15 minutes.

Step 1: Install Claude Code (2 minutes)

Open your terminal (Mac: Terminal app; Windows: PowerShell) and run: npm install -g @anthropic-ai/claude-code

It should return something like this:

If it returns something on the lines of “npm not found”, you haven’t installed Node.js.

You can download it from nodejs.org (choose the LTS version).

Run the installer, then retry the npm command above.

Verify it worked: claude --version

You should get something like this:

Step 2: Create your ABM Project Folder (1 minute)

Run these commands to create the recommended folder structure:

mkdir ~\abm-campaign
mkdir ~\abm-campaign\data
mkdir ~\abm-campaign\research
mkdir ~\abm-campaign\outputs
mkdir ~\abm-campaign\brand
mkdir ~\abm-campaign\templates
mkdir ~\abm-campaign\.claude
mkdir ~\abm-campaign\.claude\skills
mkdir ~\abm-campaign\.claude\agents
mkdir ~\abm-campaign\.claude\commands
cd ~\abm-campaign

You should get something like this:

Step 3: Create your CLAUDE.md (5 minutes)

Create a file called CLAUDE.md in your project root.

You can do that just after the previous step:

Copy the complete template from Section 7 below, then fill in your specific details.

This should take about 5 minutes.

• On Mac/Linux: nano CLAUDE.md
• On Windows (PowerShell): notepad CLAUDE.md

Then, paste the template from Section 7, fill in your details, and save.

Step 4: Run Claude Code and See the Difference (5 minutes)

Start Claude Code from your project directory: claude

Claude Code will authenticate via your browser on first run.

Note: If you get something like “Claude Code on Windows requires git-bash (https://git-scm.com/downloads/win). If installed but not in PATH, set environment variable pointing to your bash.exe, similar to: CLAUDE_CODE_GIT_BASH_PATH=C:\Program Files\Git\bin\bash.exe” like in the result below, it means you need to first install git-bash from: https://git-scm.com/downloads/win

Once you’re in, run this test:

Research [YOUR TARGET COMPANY] as a potential ABM target account. Score them against our ICP criteria. Output a structured brief with pain points and outreach angles.

Replace [YOUR TARGET COMPANY] with an actual company from your prospect list.

Notice how the output references your product, uses your terminology, and scores against your ICP criteria from CLAUDE.md.

Step 5: Run the Same Prompt Without Context (2 minutes)

Now, leave the abm-campaign folder and open Claude outside it, and again run the same test and compare the two outputs side by side, or simply go to a Claude chat and attempt the test there.

The difference is the entire argument for context engineering.

In fact, as our test prompt talks about “score them against our ICP”, Claude, without context, may ask you to give your ICP guidelines,

Well, that’s the whole point of context engineering.

It ensures you don’t have to give detailed context for repetitive tasks ten times a day.

This not only saves you time but also improves output quality, because we often end up producing lazy, low-quality prompts when we have to do it manually repeatedly, but context engineering ensures all your tasks get the original detailed context each and every time, ensuring consistent output.

Checklist before moving on:

☐ Claude Code installed and running (claude –version shows a version number)

☐ Project folder created with the recommended structure

☐ CLAUDE.md written and saved in project root

☐ First research task completed with context

☐ Comparison completed: context vs. no-context output reviewed

The Complete Marketing CLAUDE.md Template (Copy-Paste, Fill In Your Details)

Copy this entire template.

Replace everything in [BRACKETS] with your specific information.

Save as CLAUDE.md in your project root.

# ABM Campaign System

## Identity
You are a senior ABM strategist and content specialist for [YOUR COMPANY NAME].
We sell [ONE SENTENCE: what your product does and who it’s for].
Our positioning: [ONE SENTENCE: why you’re different from alternatives].

## ICP Definition
Primary ICP:
– Company size: [e.g., 50-500 employees]
– Industry: [e.g., B2B SaaS, professional services]
– Tech stack signals: [e.g., uses HubSpot, runs LinkedIn ads]
– Funding stage: [e.g., Series A-C]
– Geography: [e.g., US, UK, DACH]

Anti-persona (do NOT target):
– [e.g., companies under 20 employees]
– [e.g., government agencies]
– [e.g., direct competitors]

## Brand Voice Rules (5 maximum)
1. Write like a practitioner sharing what they learned, not a thought leader pontificating
2. Use short sentences. Be direct. No fluff.
3. Always use specific numbers over vague claims (“3x pipeline” not “significant improvement”)
4. First person. Say “we tested” not “it was determined”
5. Never use these words: [leverage, synergy, revolutionary, game-changer, unlock, delve]

## Competitors
– [Competitor A]: [their angle]. Our counter: [why we’re better for our ICP].
– [Competitor B]: [their angle]. Our counter: [why we’re better for our ICP].

## Content Rules
– LinkedIn posts: max 1,300 characters, hook in first line, one sentence per line
– Emails: subject under 50 characters, body under 120 words, one clear CTA
– Account briefs: use the 6-section format in skills/account-research/SKILL.md

## Quality Standards
– Never fabricate data. Mark unknown fields as “Not Found”
– All factual claims must include source attribution
– ICP scores must include one-line justification per dimension
– Run quality checks before delivering any final output

## Connected Tools
– MCP: Brave Search (web research), [add others as you connect them]
– Skills: see .claude/skills/ for available playbooks
– Outputs: save all deliverables to outputs/ folder

That’s 42 lines.

Well under the 80-line recommended maximum.

You can expand sections later as your system matures, but start lean.

Every line should earn its place.

Self-Assessment: Is Your Team Doing Context Engineering or Just Prompting?

Score yourself on each item. 1 point per “yes.”

1. You have a CLAUDE.md file that Claude Code reads at the session start
2. Your AI outputs consistently match your brand voice without re-explaining it
3. You have at least one Skill file for a repeatable marketing workflow
4. Claude Code can pull live data from at least one external tool (CRM, Clay, etc.) via MCP
5. You have a hook that automatically checks output quality before delivery
6. Your AI system produces better output this month than it did last month (compounding)
7. New team members can use your Claude Code setup and get on-brand output on day 1
8. You have a documented ICP that Claude Code references in every research task
9. Your outreach sequences reference specific prospect pain points, not generic templates
10. You track which AI-generated content performs best and feed winners back into your system

Scoring:

• 0-2: You’re prompting, not engineering. Start with Section 6 (quickstart) above.
• 3-5: You’ve started but aren’t compounding yet. Focus on Skills and MCP connections.
• 6-8: You’re context engineering. Focus on measurement and optimization.
• 9-10: Great. Share your learnings, and read our advanced guides on multi-agent architectures.

Claude Code for Content Engineering for LinkedIn ABM: Final Thoughts

Context engineering is what turns Claude Code from a clever writing assistant into a real operating system for LinkedIn ABM.

Once your positioning, ICP, playbooks, tool access, and quality checks are built into the system, you stop re-briefing AI and start compounding output quality across research, outreach, reporting, and campaign analysis.

And if you want to connect that setup directly to real LinkedIn ads and account engagement data, ZenABM makes the workflow much more powerful through its MCP server, which lets you pull ABM performance into Claude Code, build custom reporting, trigger actions from engagement thresholds, and generate much more useful campaign intelligence.

Book a demo now to know more about how ZenABM can support your LinkedIn or even multi-channel ABM campaigns!