Install
$ agentstack add skill-matellez-claude-skills-sales-leader-alignment ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Sales Leader Alignment: Shifting a Skeptical or Adversarial Relationship
This skill addresses the most common and most politically damaging situation a demand gen or RevOps leader faces: a sales leader who does not believe marketing is adding value, will not prioritize marketing-sourced leads, and either actively undermines or passively ignores the programs marketing is building.
This is not a process problem. It is a trust problem that predates most of the operational issues it produces. The MQL definition is contested because the relationship is contested. The pipeline attribution is disputed because the relationship is disputed. Fixing the systems without fixing the relationship produces better-documented friction, not alignment.
This skill does not assume the sales leader is wrong. In many cases the skepticism is earned. Marketing at many B2B SaaS companies has historically generated high-volume, low-quality leads and measured activity rather than pipeline. A sales leader who has been burned by that is not being irrational. The path to alignment starts with acknowledging that, not defending the prior regime.
HOW TO SET UP THIS SKILL
Provide:
- What the sales leader has said or done that indicates the problem
- How long the dynamic has existed
- Whether you are new to the role or have been in it for some time
- What you have already tried
- Whether the sales leader reports to the same person you do, or
is a peer versus a senior stakeholder
- The specific business context: stage of company, whether there
is a shared revenue target, and whether leadership above both of you sees the problem
Diagnosing the Type of Misalignment
The approach differs based on what is actually driving the friction. Most sales-marketing misalignment falls into one of four types.
Type 1: Earned skepticism from prior marketing performance
The sales leader has legitimate reasons to distrust marketing based on historical experience. High lead volume with low conversion. Programs that generated activity metrics but no pipeline. Marketing that could not answer basic questions about pipeline contribution with data.
The signal: the sales leader can cite specific examples. They remember the webinar that generated 200 leads and zero opportunities. They remember the content campaign that produced a surge in newsletter subscribers and nothing else.
The approach: do not defend the prior record. Acknowledge it directly. The most disarming thing a new marketing leader can say to a skeptical sales leader is "I have seen the pipeline data and I understand why you do not trust the MQL number right now. I would not either. Here is what I am going to do differently and here is how we will know if it is working."
What not to do: argue that the prior program was misattributed or that sales did not follow up correctly. Both may be true. Neither is the right first move.
Type 2: Structural misalignment where sales and marketing have different targets
Marketing is measured on MQL volume. Sales is measured on closed revenue. There is no shared metric that creates common ground. Each function is rationally optimizing for its own number, which produces behavior that looks like conflict.
The signal: both sides have data that supports their position. Marketing has MQL volume. Sales has low conversion rates on marketing leads. Neither is wrong. They are measuring different things.
The approach: propose a shared pipeline metric. Marketing pipeline contribution as a percentage of total pipeline, tracked jointly, with a shared definition of what counts. This is not possible to implement without executive support, but proposing it to the sales leader as a concept often shifts the conversation from blame to alignment. "What if we both owned the same pipeline number?" is a more productive conversation than "our leads are better than you think."
Type 3: Political misalignment where the sales leader sees marketing as competition for resources or credit
The sales leader believes that when marketing claims pipeline contribution, it reduces the credit that sales receives for generating revenue. Attribution is a zero-sum political contest, not a measurement exercise.
The signal: the disagreement about lead quality is unusually sharp even when the data is relatively clear. The sales leader pushes back on attribution methodology rather than the outcomes.
The approach: make attribution generous to sales in the short term. Give sales credit wherever there is ambiguity. The goal is not to maximize marketing's pipeline attribution number. The goal is to build a working relationship. Once the relationship exists, the attribution conversation can be had with less friction.
What not to do: win the attribution argument. A marketing leader who is technically right about attribution and politically isolated as a result has won nothing.
Type 4: Personality misalignment or a sales leader who is categorically opposed to marketing functions
Some sales leaders have built their careers in outbound-dominated organizations and genuinely believe that marketing is not required to generate revenue. The skepticism is not about this marketing team's performance. It is philosophical.
The signal: the skepticism predates any data about this marketing program's performance. The sales leader makes statements like "sales doesn't need marketing to hit its number" or dismisses the function categorically.
The approach: this type requires executive alignment before operational alignment is possible. If the CEO or CRO does not believe marketing is a required function, the marketing leader cannot fix that relationship by building better programs or having better conversations with the sales leader. The first move is to get clarity from leadership about what marketing is expected to contribute and what the consequences are for the sales leader who does not engage with the program. Without that clarity, the relationship cannot improve through marketing's effort alone.
The Conversations That Shift the Dynamic
The transparency conversation
Request a one-on-one with the sales leader. Not a sync. Not a pipeline review. A direct conversation with the explicit agenda: "I want to understand what marketing needs to do differently for you to trust the leads we send."
Let the sales leader talk. Take notes. Do not defend. Do not explain. Ask follow-up questions that go deeper: "When you say the leads are not ready, what specifically is missing when a rep gets on a first call?" and "What would a good marketing-sourced lead look like compared to what you are seeing now?"
The goal of this conversation is not to agree on a solution. It is to demonstrate that you are willing to hear the critique and act on it. Most marketing leaders skip this conversation because it is uncomfortable. The ones who have it first get the relationship advantages that make every subsequent operational conversation easier.
The shared problem conversation
After the transparency conversation, come back with one specific change based on what the sales leader said. Not a full program redesign. One thing. Present it as "here is what I heard from you and here is what I am changing because of it."
This establishes the pattern that the feedback loop works. The sales leader says something, marketing responds to it. That pattern is more valuable than any individual program change because it creates a foundation for future feedback that does not require escalation.
The seat at the pipeline review
Most demand gen and RevOps leaders are not in the weekly pipeline review. That absence is both a symptom and a cause of misalignment. Marketing cannot diagnose why leads are not converting if it is not in the room where deals are discussed.
Ask directly for a standing invitation to the pipeline review as an observer. Frame it as: "I want to understand what is happening with the deals marketing sourced so I can improve the quality of what we send you." Do not frame it as accountability or oversight. Frame it as learning.
Once in the room, do not use the time to defend marketing. Use it to understand what sales is seeing and to flag patterns that might indicate a qualification issue upstream. The credibility from being useful in that room compounds quickly.
The win together conversation
When a marketing-sourced deal closes, make it visible in a way that gives sales the credit. "The BuyerForesight deal that closed this week started as a LinkedIn ABM lead, but it closed because of how [rep name] ran the discovery." Marketing sourced it. Sales closed it. Both are true. Leading with the sales contribution builds the relationship.
Most marketing leaders do the opposite: they claim the win for marketing attribution. That is the right move for reporting. It is the wrong move for relationship building.
What Not to Do
These are the most common mistakes demand gen and RevOps leaders make when trying to repair a sales relationship. Each one makes the problem worse.
Going over the sales leader's head first: Escalating to the CEO or CRO before having a direct conversation with the sales leader almost always backfires. Even if leadership sides with marketing, the sales leader knows what happened and the relationship gets harder. Use escalation only after direct conversation has failed and only to clarify shared expectations, not to win an argument.
Sending data to prove marketing is right: A slide deck with pipeline attribution data sent to a skeptical sales leader is not alignment. It is a provocation. Data is useful after trust exists. Before trust exists, data is received as argument.
Making the MQL definition change without sales input: Updating the MQL definition to produce better leads without involving sales in the definition conversation produces better-documented conflict. Sales did not agree to the new definition and will not prioritize leads under it any more than the old one.
Committing to a number without understanding the context: Promising a pipeline contribution number to the sales leader or CEO before you know what the current programs can actually produce creates a credibility problem that takes months to recover from. Commit to a process and a timeline before committing to a number.
Deliver the Alignment Plan
Output in this format:
SALES LEADER ALIGNMENT PLAN
Misalignment type: [one of the four types, or a combination]
Urgency: [how quickly this needs to move based on the situation]
Built: [today's date]
SITUATION ASSESSMENT
[What is driving the friction based on what the user described. Be
direct. If the sales leader has legitimate reasons for skepticism,
say so. If the problem is structural, name the structure. If it is
political, name the politics.]
THE FIRST CONVERSATION
When: [as soon as possible / after X happens first]
Who should be in the room: [one on one or with others present]
How to open it: [specific opening, not generic advice]
What to listen for: [the specific signals that indicate which type
of misalignment is driving the dynamic]
What not to say: [the specific thing the user is probably tempted
to say that would make the situation worse]
THE FIRST CHANGE TO MAKE
[The single most visible, concrete thing to do in the next 30 days
that directly responds to what the sales leader has said or shown
you. Not a program redesign. One thing.]
THE SEAT TO GET
[Whether to seek access to the pipeline review, how to request it,
and what to do when in the room]
ESCALATION TRIGGER
[The specific condition under which going to the CEO or CRO becomes
the right move. Not a timeline. A specific observable event that
indicates direct conversation has failed.]
WHAT WILL NOT WORK IN THIS SITUATION
[Based on the type and context, the one or two things the user is
probably considering that will make the relationship worse, not
better.]
Output Rules
- Do not assume the sales leader is wrong. Diagnose the type of
misalignment before prescribing the approach.
- Be direct about situations where marketing has earned the
skepticism. Telling a user their program is the problem is more useful than validating a grievance that is partly their own making.
- Escalation is a last resort. Do not recommend going to the CEO
or CRO unless the direct conversation has clearly failed and the business impact justifies the political cost.
- The goal is a working relationship that produces shared pipeline.
The goal is not for marketing to be vindicated. If those two objectives conflict, prioritize the relationship.
- No em dashes. Use commas or periods.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: matellez
- Source: matellez/claude-skills
- License: MIT
- Homepage: https://linkedin.com/in/manuelvallestellez
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.