Resource
🟠 The Marketing Operations & Revenue Operations Professional's Guide to Claude
3/2/2026
A practical, copy-paste-ready guide to help marketing operations and revenue operations professionals get ramped up quickly in Claude (the AI assistant from Anthropic).
Please note that Claude and AI in general are transforming at a rapid rate…so this is the best that I have learned in this moment. 🙏 Features, limits, and availability can change quickly across Claude plans and workspaces. Check Anthropic’s documentation for the most current details, before investing too much time in any solution, to make sure it’s right for you.
🤔 But Sara…Why Should Ops People Care About Claude?
Look — I know. You've seen the AI hype cycle. You've watched people on LinkedIn post about how AI "changed their life" while you're still in the trenches trying to figure out why a Salesforce Flow is firing twice. 🫠
Claude is actually useful for ops work. It will do the annoying parts of your job faster so you can focus on the stuff that matters.
The way I like to explain it: Claude is like having a really sharp junior analyst on your team who never tires and can jump from writing SOQL queries to building lifecycle documentation to debugging your Marketo webhook — while you and your team focus on the most important, strategic work for the business.
Where it fits in your day-to-day:
Area | What Claude Does For You |
Data Hygiene | Write normalization formulas, dedupe logic, standardization rules. Paste in messy data, get (well, hopefully) clean outputs. |
Automation Logic | Design lead routing rules, scoring models, lifecycle logic. Plain English first, then translated to your platform. |
Reporting | Build SOQL/SQL queries, attribution models, funnel analyses. Question → query quickly. |
Documentation | Generate runbooks, SOPs, field dictionaries, technical specs. |
Troubleshooting | Paste in error messages and get context-specific fixes. Often faster than Googling. |
💡 Claude.ai vs. Cowork vs. Claude Code — Which One Do I Need?
Think of it like three levels of delegation: talking through a problem with a consultant, handing someone a file and saying "clean this up" — or giving a developer a full project to build independently.
ㅤ | Claude.ai (Chat) | Cowork (Desktop) | Claude Code (Terminal) |
What it is | Web/mobile chat interface | Desktop agent that reads and edits your local files | A command-line tool that writes and runs code on your machine |
Best for ops | Strategy, logic design, writing queries, brainstorming, documentation | Processing files, organizing data, creating docs and reports from local files | Building scripts, processing massive datasets, building API integrations |
Skill level | None — just type like you're Slacking a coworker | None — point it at a folder and describe what you need | Comfort with the command line; basic coding understanding helps |
File access | Upload files into the conversation (file size limits vary by plan). | Reads and writes to folders on your computer directly | Full access to your local filesystem and can run scripts |
Skills support | Enable built-in and custom Skills in Customize > Skills. Claude loads them automatically when relevant. | Same Skills from your account apply here too | Place Skill folders in ~/.claude/skills/ or install from the plugin marketplace. |
Where to start | Start here. This is your 80/20. | Graduate to this when you want Claude to work with your actual files | For developers or when you need scripts, APIs, and automation |
Pro Tip: 80-90% of the value for MOPs and RevOps people comes from Claude.ai (the chat). Start there, get comfortable, then try Cowork when you want Claude to work directly with files on your machine. Claude Code is the power-user tier for folks who are comfortable in a command line. Also, admittedly…even though I pride myself as being a great technologist, I am still personally learning how to use Claude Code. It helps that I have a partner who is a software engineer, which not everyone has. SO basically, ramp up over time — you don't need to learn it all at once.
One more thing worth knowing about up front: Skills. All three surfaces — Claude.ai, Cowork, and Claude Code — support something called Skills. These are reusable instruction packages that teach Claude specific workflows so you don't have to re-explain yourself every session. Anthropic ships a set of built-in Skills (for creating Excel spreadsheets, Word documents, PowerPoint presentations, and PDFs), and you can build your own custom Skills for anything ops-related. I cover Skills in depth in Section 6 — they are a serious force multiplier once you're comfortable with the basics.
🧠 The Right Mental Model (TBH This Is the Most Important Section)
The biggest mistake people make with Claude is treating it like a search engine. You type something vague, get something vague back.
The trick is treating Claude like a smart new team member who needs context and, in many cases, training + guidance.
Step 1: Set the context. Tell Claude your role and your stack. "I'm a marketing ops manager running Marketo + Salesforce + 6sense. I need to…" is 10x better than "How do I score leads?"
Step 2: Provide specifics. Paste in your actual data, field names, object schemas, or current logic.
Pro Tip: Please make sure you work with your Infosec/Legal teams — I think adoption of tools like Claude and ChatGPT are inevitable across businesses, but we do need to care about protecting PII and following policy to protect the business. So get clarity if you are inputting any sensitive data, especially financial and PII. Some companies will be okay with this if they have a Pro or Enterprise license and can ensure that data is not retained or trained on.
Step 3: Ask for the format you need. "Give me this as a Marketo smart list setup" or "Write this as a Salesforce validation rule" or "Format this as a RACI matrix."
Step 4: Iterate. Claude remembers context within a conversation. Push back, ask follow-ups, say "actually, I forgot to mention we also use Qualified for chat."
Step 5: Package what works into a Skill. Once you've refined a prompt and workflow to the point where it reliably produces great output, don't let it live only in one chat. Turn it into a custom Skill so Claude follows those exact instructions automatically every time you (or your team) do that kind of task. More on how in Section 6.
SECTION 1: EXAMPLE MOPS USE CASES
🎯 Lead Scoring Logic
Lead scoring is one of Claude's sweet spots because it requires combining business logic with data architecture and platform-specific implementation — exactly the kind of multi-layered thinking where it does its best work.
Prompt template (copy + paste this):
Why this works: It gives Claude the full picture — your role, your platform, your ICP, and your business context. It also asks for a specific deliverable (a table), which prevents Claude from writing a generic essay about lead scoring best practices. The "flag false positives" ask is especially useful — Claude is great at spotting edge cases, like a competitor's employee racking up behavioral points.
Pro Tip: ask it to mock up some example leads and their corresponding example scores. This will help you visualize how it'll work and make any tweaks.
🧹 Data Normalization
If you've ever stared at a CRM field where "United States" appears as "US", "U.S.", "USA", "United States of America", "us", and "united states" — Claude is about to become your best friend.
Prompt template:
Pro tip: Upload a CSV export of the dirty data directly to Claude. It handles moderately sized files well (a few hundred to a couple thousand rows) and can generate the full mapping table. For very large datasets (tens of thousands of rows or more), use Cowork or Claude Code instead — both can process files locally and can handle significantly larger files than the chat interface. Either way, this saves you an entire afternoon of VLOOKUP hell. Seriously. Btw, a way to help do this without exposing PII is to only include non-PII fields, like country, state, title, without identifying accompanying fields like FN/LN/email.
📤 Campaign Operations
Every campaign launch involves a ridiculous amount of operational setup — UTM structures, program templates, smart lists, token logic, and QA checklists. Claude can build all of this from scratch or audit what you have.
Use Case | What to Ask Claude |
UTM Taxonomy | Describe your campaign types and channels. Claude generates a standardized UTM naming convention with documentation and examples. |
Program Templates | Outline your campaign type → Claude maps out the full Marketo program: smart campaigns, flow steps, tokens, status progressions, reporting tags. |
Email QA | Paste your email HTML → Claude reviews the code for common rendering pitfalls, accessibility problems, broken tokens, deliverability red flags. (Note: it reads the HTML — it doesn't render or test across email clients.) |
Lifecycle Design | Describe your funnel → Claude creates the full lifecycle model with stage definitions, transition rules, SLA recommendations. |
📊 Reporting & Attribution
Claude is really good at writing SQL and SOQL — I'd argue it's often better than fumbling through the Salesforce report builder. Just describe what you want in plain English. Of course, be sure to sanity check it — but it can save you time, especially from a blank canvas.
Prompt template — SOQL query builder:
Prompt template — attribution analysis:
SECTION 2: REVOPS USE CASES
🔀 Territory & Lead Routing
Territory and routing logic is one of those areas where the business rules are always way more complex than anyone admits. Claude is excellent at helping you think through edge cases.
Prompt template:
📈 Funnel Analysis
Give Claude your pipeline data and ask it to find the story.
Prompt template:
📄 Process Documentation
Nobody likes writing SOPs. Claude doesn't care either way. 🤷♀️ And it does it shockingly well when you give it enough context.
Prompt template:
Pro Tip: Record a Loom of yourself walking through the process. Grab the transcript and paste it into Claude. Ask it to turn that into a structured SOP. That way, you go from zero documentation to a polished runbook in about 15 minutes.
🔗 Integration Mapping
When you're implementing a new tool or auditing your tech stack, Claude can help you think through the data flow and field mappings — the stuff that usually lives only in one person's head (and that person is probably you).
Prompt template:
SECTION 3: COPY-PASTE PROMPT LIBRARY
Copy these, customize the brackets, then go.
🧹 Data & Hygiene Prompts
Deduplicate a list and create merge rules:
Enrich and standardize company names:
Audit email deliverability hygiene:
⚡ Automation Logic Prompts
Design a lead lifecycle model:
Build a Salesforce Flow (step-by-step):
📈 Analysis & Insights Prompts
Pipeline velocity analysis:
Campaign performance teardown:
📖 Documentation Prompts
Generate a CRM field dictionary:
Write a technical requirements doc for a vendor:
SECTION 4: BEYOND THE CHAT — COWORK & CLAUDE CODE
But Sara, What If I Want File Access Without Having to Know Code?
This is where Cowork comes in. Anthropic has been introducing agentic desktop features like Cowork (availability may vary by plan and workspace), and it's basically Claude Code's power in a friendly desktop wrapper.
Cowork is available within the Claude Desktop experience. Open the app and navigate to the Cowork section to connect a folder and describe your task. It reads your files, creates new ones, and edits existing ones. It also keeps you in the loop on its progress throughout.
Why this matters for ops people: The chat is great for brainstorming and writing queries, but it can't touch your files. And Claude Code is powerful but intimidating if you've never used a terminal.
What Cowork can do for you:
Use Case | How It Works |
Process a folder of exported CSVs | Point it at your exports folder. Ask it to merge, deduplicate, standardize across files, then save a clean output. |
Create formatted docs from raw data | Give it a data export and ask for a Word doc, PDF, or slide deck summarizing the findings. |
Organize messy file structures | Point it at a cluttered project folder. It proposes categories, renames files, sorts everything — after you approve the plan. |
Audit a batch of documents | Drop your Marketo email templates or campaign briefs into a folder and ask it to flag inconsistencies or missing elements. |
Scheduled recurring tasks | Type /schedule in Cowork to set up tasks that run daily, weekly, or monthly (like pulling a report every Monday morning) |
Connectors make it even more useful. Cowork can connect to external tools (like Google Drive, Slack, or Notion) through Anthropic’s connectors and partner-built skills ecosystem, depending on your workspace setup. So instead of the old download-clean-reupload cycle, you can have Claude pull context directly from your tools.
Getting started with Cowork:
- Download the Claude Desktop app from claude.com/download
- Requires a paid plan (Pro at $20/mo, Max, Team, or Enterprise)
- Open the app, click the "Cowork" tab, select a folder, then describe your task
- Cowork is still in research preview, so expect it to get better over time
⚠️ Heads up: Cowork can make real changes to your files — reading, editing, creating, even deleting. I'd recommend pointing it at a copy of your folder (not the originals) until you're comfortable with how it works. Also avoid giving it access to folders with sensitive financial or personal data while it's still in preview.
P.S. Claude also has a handy Chrome app, for local Chrome work — worth checking out too!
⌨️ Claude Code — The Developer Tier
For most ops folks, the chat interface plus Cowork will cover 95% of your needs. But here's when Claude Code (the command-line tool) starts to make sense:
Task | Claude.ai Chat | Cowork | Claude Code |
Clean up a 50-row CSV | ✅ Paste it right in | ✅ Works great | Overkill |
Clean up a 50,000-row CSV | ❌ Too large | ✅ Can handle it locally | ✅ Processes locally with scripts |
Write a SOQL query | ✅ Perfect for this | Overkill | Overkill |
Build a Python script to pull API data nightly | Can write it, can't test it | Can write it to a file | ✅ Writes, tests, and debugs it |
Design lead routing logic | ✅ Ideal for strategy | Overkill | Overkill |
Process 200 Marketo email templates for audit | ❌ Too many files | ✅ Point it at the folder | ✅ Reads and analyzes all files |
Getting started: Claude Code requires a paid Claude plan (Pro, Max, Team, or Enterprise). Install it using the latest instructions in Anthropic’s official documentation, as setup steps may change.
Then run
claude in your terminal to authenticate. You can also use it through the Claude Desktop app without touching the terminal. Check Anthropic's docs for full setup details.Example — bulk CSV cleanup:
Example — API data pull:
SECTION 5: WORKFLOW TIPS & COMMON MISTAKES
Avoid These Mistakes
- Use Projects to organize context. In Claude.ai (requires a paid plan — Pro, Max, Team, or Enterprise), create a Project for each major system or workstream — like "Salesforce Admin" or "Marketo Programs." Upload your field dictionaries and process docs. Claude will reference them in every conversation within that Project.
- Always ask for edge cases. After Claude gives you any logic or automation design, follow up with: "What edge cases or failure modes might I be missing?" This is consistently where Claude delivers insights you wouldn't have caught on your own.
- Use it for meeting prep. Before your weekly marketing-sales alignment call, paste in your pipeline data and ask Claude to generate a few talking points plus risk flags for the quarter. Walk into meetings prepared, not reactive.
- Paste error messages directly. Getting cryptic Salesforce errors? Marketo sync failures? Paste the exact error message. Claude can reason about your specific context and suggest a fix — often faster than Googling.
- Record a Loom, paste the transcript. Any process you can walk through on video, Claude can turn into structured documentation. Zero to SOP in 15 minutes.
- Turn your best prompts into Skills. If you've built a prompt that consistently produces great lead scoring audits or data normalization outputs, package it as a custom Skill. Claude will automatically follow those instructions every time the task comes up — no re-prompting required.
❌ Common Pitfalls (and What to Do Instead)
Pitfall | Do This Instead |
Trusting output blindly. Running Claude's SOQL in production without reviewing. | Always review and test in a sandbox before deploying. Claude is a draft machine, not a deployment pipeline. |
Not providing your schema. "Write me a query" without field names. | Paste your actual field API names and object relationships. Claude can't guess custom field names. |
One-and-done prompting. Accepting the first response. | Iterate. "This is close but we also need to handle [case]" or "Simplify this." The 3rd or 4th refinement is usually the best. |
Using it for real-time data. "What's our pipeline this quarter?" | Claude doesn't have access to your live systems. Export → Paste → Analyze. |
Sharing sensitive data without thinking. | Be mindful of PII. Anonymize where possible. Check your org's AI usage policy. |
SECTION 6: SKILLS — TEACH CLAUDE YOUR PLAYBOOK
This is the section that turns Claude from a helpful chat assistant into something closer to a trained teammate. Skills launched in October 2025, and they are genuinely one of the most underrated features for ops professionals.
🧩 What Are Skills, Really?
Skills are reusable instruction packages — folders containing a markdown file (called
SKILL.md) and optionally some scripts or reference files — that teach Claude how to perform a specific task. Think of a Skill like an onboarding doc you'd hand to a new analyst: "Here's how we structure UTMs. Here are the fields we care about. Here's the format the output should always be in."The key difference between a Skill and a really good prompt: a Skill persists. You don't re-paste it each conversation. Once a Skill is enabled, Claude automatically detects when it's relevant and loads those instructions behind the scenes. You'll even see it in Claude's chain of thought when it kicks in.
🏗️ Anthropic's Built-In Skills vs. Custom Skills
Anthropic ships four built-in Skills out of the box. These power the document creation features you may have already used in Claude.ai:
Built-In Skill | What It Does |
xlsx | Creates and edits Excel spreadsheets — with formulas, formatting, and charts |
docx | Creates and edits Word documents — with headers, tables of contents, page numbers, tracked changes |
pptx | Creates and edits PowerPoint presentations — with layouts, speaker notes, and branded formatting |
pdf | Creates, fills, merges, and extracts data from PDF files |
These activate automatically when relevant. You don't need to do anything special — just ask Claude to "create a spreadsheet of our lead scoring model" or "make a one-pager on our lifecycle stages" and the appropriate Skill fires.
Custom Skills are where it gets interesting for ops. You write a
SKILL.md file describing your workflow, your formatting preferences, your field naming conventions, your org's specific rules — whatever institutional knowledge currently lives in your head or a dusty Confluence page. Then Claude follows those instructions automatically any time the task matches.📂 How Skills Work Across Surfaces
Skills are portable — they use the same format everywhere:
Surface | How to Add Skills |
Claude.ai | Built-in Skills are already there. Upload custom Skills as a ZIP file. |
Cowork | Same as Claude.ai — Skills you've enabled in your account apply to Cowork sessions too. |
Claude Code | Place Skill folders in ~/.claude/skills/ or install from the plugin marketplace. Claude discovers them automatically. |
API | Use the /v1/skills endpoint to upload and manage Skills programmatically. |
Pro Tip: Skills need the "Code Execution and File Creation" feature enabled in your settings to work. Built-in Skills (the document creation ones) fire automatically on paid plans. Custom Skill uploads are available on Pro, Max, Team, and Enterprise. Anthropic's docs suggest some Skills functionality may be accessible on the free tier, but for the full experience — especially custom Skills — a paid plan is the way to go.
🛠️ The Skills Directory (Partner Skills)
Beyond the built-in document Skills, Anthropic has a growing directory of partner-built Skills from companies like Notion, Atlassian, Figma, Canva, Zapier, and more. Browse the directory at claude.com/connectors.
Some that are relevant to ops professionals:
Partner Skill | Why You'd Care |
Atlassian | Turn specs into Jira backlogs, generate status reports from Confluence pages, triage issues — Claude understands Atlassian's teamwork patterns |
Notion | Claude works within your Notion workspace context — pulling from pages, databases, and docs to produce structured output |
Zapier | Skills layered on top of Zapier's automation platform for workflow orchestration |
Canva | Generate on-brand presentations and campaign materials directly through Claude |
To install a partner Skill, visit the directory, download the skill package (usually a ZIP from GitHub), then upload it in Customize.
📝 Building Your First Custom Skill (No Coding Required)
A custom Skill can be as simple as a single markdown file (if you’re unfamiliar with markdown, you can find simple cheat sheets like this one online or ask Claude). Here's the minimum structure:
And the
SKILL.md file looks like this:That's it. Zip the folder, upload it in Customize > Skills, and the next time you ask Claude anything about UTMs or campaign tracking, it will follow your naming convention automatically.
Pro tip: Claude has a built-in "skill-creator" Skill that walks you through building a new Skill interactively. Just tell Claude "I want to create a custom Skill for [task]" and it will ask you questions about your workflow, then generate the SKILL.md for you.
🎯 Custom Skill Ideas for MOPs & RevOps
Here are Skill concepts I think are especially high-value for ops teams. Each of these represents a workflow you'd otherwise re-explain to Claude (or a new team member) every single time.
Data normalization Skill
Encode your org's standardization rules — official country mappings, job title hierarchies, industry taxonomy, company name corrections. Claude follows your rules automatically any time it touches a CSV or data cleanup task.
Lead scoring auditor Skill
Package your ICP definition, current scoring model, platform (Marketo / HubSpot / Pardot), and the format you want the audit output in. Claude consistently produces the same structured analysis without you re-prompting each time.
SOQL / SQL query writer Skill
Include your Salesforce object schema, custom field API names, and common join patterns. Claude writes queries against your actual data model instead of generic examples.
Campaign brief → ops checklist Skill
Describe the steps that every campaign launch requires at your org — UTM creation, program setup, smart list logic, QA steps, token configuration, reporting tag assignment. Claude takes any campaign brief and spits out the full operational checklist tailored to your stack.
SOP generator Skill
Embed your preferred SOP format (including your standard headers, your RACI template, your escalation path structure) so every SOP Claude writes matches your org's documentation style.
Weekly pipeline prep Skill
Include the format your leadership expects for pipeline reviews — specific metrics, visualizations, risk flags, talking points. Upload your pipeline data each week and get a formatted briefing doc.
Integration mapping Skill
Encode your standard field mapping template, sync direction conventions, and conflict resolution rules so Claude can produce integration specs that match how your team actually documents these.
🏢 Skills for Teams (Admin Features)
If you're on a Claude Team or Enterprise plan, admins can provision Skills organization-wide. This is a big deal for ops teams because it means you can:
- Deploy a "Salesforce Query Writer" Skill that includes your org's object schema to every team member
- Ensure everyone on the RevOps team gets the same SOP template, the same UTM conventions, the same pipeline analysis format
- Manage Skills centrally from admin settings — enable, disable, or update Skills for the whole org from one place
Users can still toggle individual Skills off if they prefer, but admin-provisioned Skills are enabled by default for everyone. This is how you scale consistency across a team without relying on everyone having the same prompting habits.
⚠️ Skills Security & Best Practices
A few things to keep in mind:
- Only install Skills from sources you trust. Skills can include executable code, so treat them with the same care you'd give a browser extension or a Zapier integration. Stick to Anthropic's built-in Skills, partner Skills from the directory, and custom Skills your team builds internally.
- Audit before you install. If someone shares a Skill with you, open the SKILL.md and any bundled scripts before uploading. Look for anything unexpected — network calls, file access patterns, or instructions that don't match what the Skill claims to do.
- Skills don't persist data between sessions. They execute in a sandboxed environment. Nothing is saved from one conversation to the next beyond what's in the Skill's files themselves.
- Custom Skills are private by default. Skills you upload are only visible to your own account. They're not shared with other users unless an admin provisions them org-wide (Team/Enterprise plans only).
🚀 Getting Started with Skills — Quick Checklist
Step | Action |
1. Check your settings | Go to Settings > Features (or Settings > Capabilities > Skills) and confirm Code Execution is enabled. |
2. Explore built-in Skills | Ask Claude to create a spreadsheet, Word doc, or slide deck — the built-in Skills fire automatically. |
3. Browse the directory | Visit claude.com/connectors and see if any partner Skills match your stack (Atlassian, Notion, Zapier, etc.). |
4. Build your first custom Skill | Pick your most-repeated workflow — UTM generation, data cleanup rules, or SOP formatting. Write a SKILL.md, zip the folder, upload it. |
5. Ask Claude to help you build it | Tell Claude "I want to create a custom Skill for [workflow]" and let the skill-creator Skill walk you through it. |
6. Test and iterate | Run a few tasks with the Skill enabled. Refine the instructions based on what Claude gets right and what needs adjusting. |
7. Scale to your team | If you're on Team or Enterprise, work with your admin to provision high-value Skills org-wide. |
SECTION 7: PUTTING IT ALL TOGETHER
☑️ Your First Week with Claude — A Checklist
Don't try to boil the ocean (LOL). Here's how to get value in your first five days:
Day | Task | Why |
Setup | Sign up at claude.ai (free tier works for basic chat; Pro at $20/mo is worth it for Projects, Skills, and heavier use) | Get access |
Day 1 | Paste a messy data sample and ask Claude to clean + standardize it | See the magic instantly |
Day 2 | Take a SOQL query you've been meaning to write — describe it in plain English | Save 30+ mins |
Day 3 | Describe a process you own but haven't documented; ask for an SOP | Create something you've been putting off |
Day 4 | Paste your lead scoring model and ask Claude to audit it for gaps | Get fresh eyes on stale logic |
Day 5 | Upload a campaign performance CSV and ask for a full analysis | See how Claude handles real analysis |
Bonus | Create a Claude Project for your primary platform and upload key docs (requires Pro or above) | Set yourself up for speed going forward |
Bonus | Download the Claude Desktop app and try Cowork — point it at a folder of exports and ask it to organize or clean the files | See what "agentic" actually feels like |
Bonus | Enable Skills, browse the partner directory, and build your first custom Skill for a repeatable workflow | Go from "I use Claude" to "Claude knows how we work" |
The bottom line: Claude won't replace your expertise — you still need to know your systems and your data. And even more importantly, strategy and stakeholder management. But Claude can and likely will make the execution side of your job significantly faster. The stuff that used to take you a full afternoon — writing documentation, building queries, cleaning data — can now happen in 20 minutes. And that means you actually have time for the strategic work that moves the needle (instead of just saying you'll get to it next quarter).
P.S. I'm going to keep updating this as I find more use cases and better prompts. If you've found a killer prompt for ops work — or built a custom Skill worth sharing — reply to the newsletter. I read every response and I'll add the best ones (with credit). 🙂
🗣️ Have feedback? Email me at sara@saramcnamara.com — this is a living resource for all of us.
Related Guides
📑 AI Learning Roadmap
🚨 Ops Signals: A Practical Guide for GTM Teams
The Marketing Operations Strategist Newsletter
Join 3,500+ operations professionals. Get actionable MOPs tips every month.