A practical framework for aligning sales, marketing, and customer success around shared intelligence.
Why are some campaigns successful in generating revenue while others aren’t? The simplest answer is a lack of individual direction and information.
Back in the day, psychologist Dmitry Davidoff created a game called Mafia at Moscow State University- its key insight is that a coordinated minority with more shared information can overpower a larger but poorly informed group.
In most cases, your buyers are the coordinated minority and your disconnected teams are a poorly informed group. Successful campaigns just flip the script.
Let’s see how.
Revenue Enablement is where the good shit’s at
Salesforce defines revenue enablement as: “Revenue enablement is a strategic approach that equips all customer-facing teams, including sales, marketing, and customer success, with the tools, content, coaching, and data they need to engage buyers effectively and drive predictable revenue growth. While traditional sales enablement focuses on the sales team, revenue enablement expands the scope to align all functions involved in the customer journey around a common goal: revenue.
In practice, that means making sure a rep heading into a discovery call has the same context as the marketer who nurtured that lead, and customer success has what they need to grow the account after the deal closes.”
However, this is an incomplete, or rather misleading, definition. First, they are essentially saying that revenue enablement is sales enablement at scale, and thus, the advice they give is of coaching, content strategy, cross-functional alignment, technology + data, feedback loops, etc.
The problem here is that this will produce more content, demand more productivity tools, and increase the noise inside the teams’ heads- which is what often happens anyway.
The insight here is that information should not be words on a sheet but rather an action built into the operations.
But first, it would be unwise to get into operations without setting a definition that is more aligned with revenue enablement.
So, what is revenue enablement?
Revenue enablement is the system through which customer-facing teams build, preserve, and apply shared knowledge across the customer journey, so every interaction helps the buyer make a better decision, and the business generate more predictable revenue.
Information Is Useless Until It Becomes Coordinated Action
Revenue teams rarely suffer from an absolute lack of information. More often, the information is fragmented across departments, people, and platforms.
Marketing knows which message attracted the account. Sales knows which problem the buyer admitted to. A subject-matter expert knows where implementation can fail. Customer success knows what happens once the promise meets reality.
The information exists. The coordination does not.
Build Common Knowledge Across Revenue Teams
Shared information only tells us that several people possess the same facts. Common knowledge means everyone also knows that the relevant people possess and accept those facts. That difference creates confidence for interdependent action. Research on common knowledge and coordination shows that people are more willing to coordinate when the information behind the decision is commonly known.
For revenue teams, this means an account insight should not merely be entered into a CRM. The team must know:
- Where the information came from
- Whether it has been verified
- Who has accepted it as relevant
- Which decision it should change
- Who is expected to act on it
A field marked “security concern” is information. A verified security concern that alerts the appropriate expert, changes the next conversation, and follows the account into onboarding is enablement.
Create a Shared Mental Model of the Account
Teams perform better when members have compatible understandings of the objective, environment, roles, and likely sequence of action. These are called shared mental models. Research on shared mental models connects them with stronger coordination and team performance.
Marketing, sales, and customer success do not need identical knowledge. They need the same map.
At minimum, that map should answer:
- What problem is the buying group trying to solve?
- Why has it become important now?
- Which outcomes matter to each stakeholder?
- Which risks could stop the decision?
- What evidence does the buyer require?
- What has the seller promised?
- What should happen next?
This account narrative should become more accurate as the buyer moves through the journey. It should not restart every time ownership moves to another team.
Know Who Knows What
Daniel Wegner’s idea of transactive memory is useful here. A coordinated group does not require everyone to remember everything. It requires people to know who knows what, trust that expertise, and retrieve it when required. Wegner’s research on transactive memory breaks the system into specialization, credibility, and coordination.
This gives revenue leaders a practical test:
- Specialization: Is it clear where different kinds of expertise live?
- Credibility: Does the team trust the source and quality of that expertise?
- Coordination: Can the right expert be brought into the account before the information loses value?
Research also suggests that transactive memory affects performance through routines and patterns of interaction-not simply because knowledge exists. Research on transactive memory and routines
So, the objective is not to build another knowledge repository. It is to create reliable paths between a signal and the person who can do something about it.
Coaching Cannot Fix an Implementation Gap.
Coaching can improve discovery, interpretation, objection handling, and judgment. But it cannot repair missing information, broken handoffs, contradictory incentives, unreliable systems, or absent decision rights.
Organizations often use coaching to individualize an operational failure. When teams do not share information, employees are taught to communicate better. When incentives conflict, they are taught to collaborate. When workflows make the desired behavior difficult, they are given another framework to remember.
Then everyone returns to the same environment that produced the old behavior.
Before introducing coaching, ask:
| If the person knew exactly what to do tomorrow, would the surrounding system allow and reward them for doing it? |
If yes, coaching may help. If no, redesign the system first.
Make Coaching Part of the Workflow
When coaching is necessary, connect it to an observable action:
1. Define the behavior that should change.
2. Identify where that behavior occurs in the workflow.
3. Give the person a real opportunity to practise it.
4. Capture the result, not merely completion of the training.
5. Reinforce the behavior through management, incentives and feedback.
For example, do not coach sales on stakeholder discovery and measure attendance. Coach the skill, require an updated stakeholder map on active accounts, review its quality, and track whether previously hidden stakeholders are engaged.
Coaching transfers knowledge to an individual. Revenue enablement must transfer knowledge into the operation.
Gather Buyer Intelligence Legally and Ethically
If “information infiltration” sounds too close to espionage, that is because it does. More useful terms are ethical competitive intelligence, market sensing, customer intelligence, and boundary spanning.
The practical boundary is simple: information should be public, permissioned or properly licensed-not private, deceptive or improperly obtained. SCIP’s ethical-intelligence guidance rejects misrepresentation, hacking and inducing people to violate confidentiality.
Legal and ethical sources can include:
- Public filings, procurement documents and company websites
- Product documentation, job postings and earnings calls
- Conferences, public communities and customer reviews
- Consented customer interviews and customer-advisory boards
- Win–loss interviews and sales calls used with appropriate permission
- Support and product-usage data the company is entitled to use
- Partner and distributor feedback
- Post-sale adoption and outcome data
The process should not stop at collection. Revenue teams need boundary spanners who can find outside information, interpret it, translate it into the team’s language, and route it to the people who can act.
A salesperson can be a boundary spanner between the buyer and product. Customer success can carry implementation reality back to marketing. Partner teams can expose market dynamics the direct organization cannot see. The role matters less than the movement of intelligence.
Information Asymmetry Runs in Both Directions
The seller knows more about product limitations, implementation demands, and actual performance. The buyer knows more about internal urgency, budget, politics, competing priorities and decision criteria.
Both sides reveal information selectively because information affects leverage.
George Akerlof’s “Market for Lemons” shows what happens when buyers cannot distinguish high quality from low quality: they discount the entire market. In B2B, this is why every vendor begins to look similar. Everyone claims expertise, ease, transformation, and measurable results. More messaging can increase uncertainty rather than reduce it.
Use Credible Signals to Make Quality Observable
Michael Spence’s signaling theory explains how an informed party can reveal hidden quality through observable evidence.
Useful B2B signals include:
- Independent audits and certifications
- Reference customers
- Verifiable outcomes
- Transparent implementation requirements
- Product trials
- Performance guarantees
- Public documentation
- A clear explanation of when the product is not a fit
The signal should be costly, verifiable, or consequential. Generic claims are weak because almost any competitor can reproduce them.
Use Screening to Reveal Hidden Information
Screening works in the other direction: the less-informed party creates a test.
Buyers screen sellers through RFPs, security reviews, technical evaluations, references, trials and proof-of-concept projects. Sellers screen buyers through discovery, stakeholder mapping, readiness assessments, mutual action plans and implementation workshops.
A mature revenue-enablement system should define:
- Which evidence is available at each buying stage
- Which buyer questions require specialist involvement
- Which tests demonstrate real product fit
- Which commitments indicate genuine buyer participation
- Which account-specific work should not begin without reciprocity
Revenue enablement does not eliminate information asymmetry. It helps the organization decide what to learn, what to reveal, what to protect, and how to verify claims.
Buyers Will Extract as Much Value as They Can
Buyers do not gather information passively. They use sellers to understand the problem, learn the market’s language, establish comparison criteria, reduce implementation risk, build an internal case, and improve their negotiating position.
A buyer may use one seller’s expertise to evaluate another. They may request a custom recommendation and use the logic internally. They may collect multiple proposals to negotiate with a provider they already prefer.
This is not necessarily bad faith. It is rational behavior under uncertainty. No seller can prevent it by gating everything without also becoming invisible.
The better approach is to use the buyer’s information gathering to learn how the decision is being made.
Treat Buyer Behavior as Intelligence
Every attempt to extract information can reveal something:
- Requested information reveals evaluation criteria.
- Repeated questions reveal unresolved risk.
- New stakeholders reveal how the decision is organized.
- Competitor comparisons reveal the category in which the buyer has placed you.
- Requests for customization can reveal a genuine need for proof-or low commitment.
- Pricing pressure can reveal budget constraints, perceived substitutability, or negotiation strategy.
- Ghosting can indicate lost urgency, internal disagreement, or a preferred alternative.
These are signals, not conclusions. A pricing objection does not prove the price is too high. A content download does not prove purchase intent. Stated preferences should be tested against observable behavior and multiple sources.
For every meaningful signal, record:
1. What happened: The observable behavior or direct statement
2. What it might mean: The working interpretation
3. How confident the team is: Confirmed, probable, or speculative
4. What would validate it: Another stakeholder, behavior or source
5. What action it should trigger: The next practical step
This keeps useful interpretation from becoming institutional fiction.
Shape the Buyer’s Reference Frame
Sellers cannot control the buyer’s entire research process. Buyers will consult competitors, peers, analysts, communities, review platforms and AI.
The stronger position is to shape the criteria through which all of that information is interpreted.
If your content teaches buyers which questions matter, which risks are overlooked, and how alternatives should be evaluated, competitors may be assessed using standards you helped establish.
Instead of saying, “Here are the benefits of our solution,” show:
- The conditions required for any solution in the category to work
- The hidden costs buyers should include in the comparison
- The risks that appear after implementation
- The questions weaker providers avoid
- The evidence required to distinguish claims from capability
The seller that defines the problem and establishes credible evaluation criteria can influence the decision without controlling every source the buyer consults.
Use Progressive Information Reciprocity
This does not mean giving away unlimited expertise.
The seller should make information more specific as the buyer provides more context and commitment.
Public Value: Educate the Market
Offer frameworks, research, benchmarks, and general diagnostic tools. This knowledge scales and helps shape the buyer’s mental model.
Contextual Value: Exchange Insight for Context
Provide tailored interpretation after the buyer shares meaningful information about the organization, problem, stakeholders, or evaluation process.
Bespoke Value: Require Commitment for Custom Expertise
Reserve custom analysis, technical design, and substantial consulting for buyers who provide access, relevant data, stakeholder participation, agreed next steps, or commercial commitment.
| Do not gate basic knowledge. Require reciprocity for expensive specificity. |
This lets the seller remain useful during buyer research without becoming an unlimited source of free consulting.
Build Revenue Enablement Around Four Actions
A practical system should acquire, validate, route, and embed customer and market intelligence.
1. Acquire the Right Information
Start with the decisions each team needs to make. Do not collect information simply because the CRM has an empty field.
Ask:
- What must marketing know to improve the campaign?
- What must sales know before the next interaction?
- What must a subject-matter expert know before joining?
- What must customer success know before implementation?
- What must product know about recurring friction?
2. Validate the Signal
Separate evidence from assumptions, stale data, isolated anecdotes, and negotiation tactics.
Capture the source, date, and level of confidence. Distinguish what the buyer said from what the team inferred. Where possible, corroborate material claims through another stakeholder or observable behavior.
3. Route It to the Right Person
Send the information to the person with the expertise and authority to act while it can still affect the outcome.
Define:
- Who needs to know?
- At what stage?
- In which workflow?
- What should the information trigger?
- Who confirms that the action occurred?
A technical concern sent to everyone is noise. The same concern sent to the right specialist before the next meeting is coordination.
4. Embed It Into the Workflow
Information should change the next action and survive the next handoff.
For example:
- Marketing captures a recurring concern and updates campaign framing.
- Sales records the buyer’s actual evaluation criteria rather than generic notes.
- A specialist is introduced when a material risk appears.
- Customer success receives the original business case, stakeholder context, and promises made.
- Post-sale outcomes return to marketing and sales as evidence and learning.
This creates a closed information loop rather than a sequence of disconnected departments.
Predictable Revenue Comes From Coordinated Learning
The winning organization is not necessarily the one with the most information. It is the one that can convert information into the right action with the least friction.
The buyer will continue to research, compare, negotiate, and extract value. But every attempt to reduce their information disadvantage also produces information for the seller.
Revenue enablement captures that exchange, validates what it means, distributes it across customer-facing teams and turns it into coordinated action.
