The most common revenue conversation in B2B technology goes like this. Marketing presents MQL volume. Sales presents pipeline coverage. Customer success presents churn rate. The CEO asks what the company's net revenue retention is and nobody can answer without a spreadsheet pull that takes two days.
Each function is measuring the part of the revenue model it owns. Nobody is measuring the revenue model itself.
This is not a motivation problem. It is not a communication problem. It is a structural problem. The functions are organized to optimize for their own metrics, and the systems they operate are designed to produce data for those metrics, not for the shared revenue model that connects all three.
This post covers how to close that gap: what structural changes make shared revenue accountability possible, what the data architecture requires, and what the governance process looks like that keeps the alignment from drifting back to silos within six months.
Most B2B technology companies attempt alignment through meetings and shared goals. They create a revenue team meeting where marketing, sales, and CS present their metrics together. They add a shared OKR that references revenue growth. They publish a customer journey map that shows how all three functions contribute.
None of that produces alignment. It produces coordination theater.
The reason is that the underlying incentive structures, data systems, and accountability models are still function-specific. The marketing leader is evaluated on MQL volume and marketing-sourced pipeline. The sales leader is evaluated on quota attainment. The CS leader is evaluated on churn rate and customer health scores. The shared revenue meeting gives them a venue to report their individual numbers to each other. It does not give any of them a reason to make decisions that optimize for the shared revenue outcome at the cost of their own metric.
Genuine alignment requires three changes that are organizational and structural, not behavioral.
The most powerful alignment mechanism available to a revenue leadership team is shared metrics. Not shared awareness of each function's metrics. Shared accountability for the same metrics.
The five metrics that, when owned jointly by marketing, sales, and CS, produce genuine revenue alignment:
Marketing-sourced pipeline as a percentage of total pipeline. Marketing owns the programs that generate it. Sales owns the criteria that qualify it. CS owns the expansion programs that make the customer base a source of new pipeline. When all three functions are accountable to this number, their individual decisions become interdependent.
Win rate on marketing-sourced pipeline. Marketing is accountable for the quality of the leads it sends to sales. Sales is accountable for its conversion rate on those leads. When both functions are accountable to this number together, the lead quality argument that occupies so many marketing and sales relationships becomes a shared problem to solve rather than a blame assignment exercise.
Time to close. Every function contributes to sales cycle length. Marketing contributes through the quality of buyer education before the sales conversation. Sales contributes through qualification rigor and process execution. CS contributes through reference availability and case study production. When all three are accountable to cycle length, each function has an incentive to invest in the parts of the buyer journey it owns.
Net revenue retention. NRR above 100% requires CS to deliver adoption and value realization, marketing to run expansion programs for the existing customer base, and sales to execute expansion opportunities when CS identifies them. No single function can move NRR materially without the others. That interdependence is what makes NRR the ideal shared accountability metric.
Expansion pipeline contribution. The percentage of total pipeline generated from the existing customer base. Marketing generates awareness and demand for expansion. CS identifies the accounts ready for expansion conversations. Sales executes the expansion opportunity. All three need to be accountable to the outcome.
Getting these five metrics agreed upon and signed off by the CMO, CRO, and VP of Customer Success before any process or system changes are made is the first and most important step. Everything else in this post depends on that agreement existing.
Shared accountability requires shared visibility. If marketing can only see MAP data, sales can only see CRM data, and CS can only see CS platform data, each function will optimize for the metrics that their data system is designed to measure. The shared accountability metrics will be aspirational rather than operational.
The data architecture changes required for genuine alignment:
CS health score data in CRM. Every account in CRM should have the CS platform's health score, adoption data, and expansion signal data visible on the account record. Sales reps calling into an account should know the customer's health score before they dial. Marketing teams building expansion programs should be able to segment the customer base by health score and adoption signal. This requires a reliable integration between the CS platform and CRM that most B2B technology companies have not built.
Marketing attribution data visible to sales. When a sales rep opens an account record in CRM, they should be able to see every marketing touchpoint that contact has had: emails opened, content downloaded, events attended, pages visited. Sales reps who know what a contact has already engaged with have more relevant first conversations. This requires the MAP-to-CRM integration to be configured to write touchpoint data to the contact timeline in CRM, not just the attribution fields.
Pipeline data visible to CS. Customer success leaders should be able to see the expansion pipeline that exists for their accounts, which sales reps are working it, and what the current stage is. CS teams that do not have pipeline visibility cannot coordinate their customer engagement with the sales motion. This requires pipeline data to be shared from CRM to the CS platform, either through a native integration or through a shared reporting layer.
Unified revenue reporting. A single dashboard that shows the five shared accountability metrics, updated automatically from MAP, CRM, and CS platform data, that all three commercial function leaders review from the same source. Not marketing's version of the revenue report, sales's version, and CS's version. One version.
Shared metrics and shared data enable alignment. Governance structure sustains it.
The governance failure mode is universal: cross-functional alignment is established at the beginning of a planning cycle, each function returns to its operational reality, the shared metrics drift back to being aspirational, and by the next planning cycle the alignment has to be rebuilt from scratch.
Preventing that failure requires a governance structure with three components.
Weekly revenue operations review. A 60-minute meeting with representatives from marketing ops, sales ops, and CS ops (or the individuals who own those functions at smaller organizations) that reviews the RevOps dashboard, identifies any metric that is trending in the wrong direction, and assigns an owner and a resolution timeline for each issue. This meeting is operational, not strategic. It is a data review and issue assignment process.
Monthly revenue leadership review. A 90-minute meeting with the CMO, CRO, and VP of CS that reviews the five shared accountability metrics for the month, discusses any organizational or investment decisions that the metric trends indicate, and confirms priorities for the next 30 days. This meeting is where the shared accountability is operationalized at the leadership level.
Quarterly alignment review. An annual planning session divided into four quarterly reviews where the ICP definition, the lead management process design, and the customer lifecycle process are reviewed against current performance data and updated to reflect ICP evolution, product changes, and market changes. The definition documents from the initial alignment process need to be living documents, not artifacts.
The governance structure only works if the meetings happen consistently and if the data is available for each meeting without manual assembly. RevOps functions that spend the day before each governance meeting pulling data are not governing. They are reporting. The data infrastructure should be producing the dashboard automatically so that governance meetings are spent discussing what the data means, not assembling it.
Every alignment initiative starts with the ICP, because the ICP is the document that all three functions depend on but that most organizations have not agreed on in writing.
Marketing's ICP determines which companies and contacts to target with demand generation programs. Sales's ICP determines which leads to qualify and which deals to invest time in. CS's ICP determines which customers are likely to renew and expand. When those three ICPs are different, the misalignment is structural and will not be fixed by a better attribution model or a more capable CRM.
The ICP definition workshop is a facilitated session with representatives from marketing, sales, and CS that produces a single document defining: the firmographic criteria for an ideal account, the technographic signals that indicate a good fit, the behavioral signals that indicate an account is in an active buying cycle, the job titles and personas involved in the buying committee, the common business problems that create urgency for the solution, and the disqualifying signals that indicate an account is not a fit regardless of firmographic profile.
That document should be reviewed and signed by the CMO, CRO, and VP of Customer Success. It should be used to configure lead scoring in the MAP, qualification criteria in the CRM, and customer health scoring criteria in the CS platform. It should be reviewed quarterly against win/loss data and NRR cohort data to validate that it reflects current reality.
An ICP that exists only in the marketing team's targeting parameters or only in the sales team's qualification checklist is not an ICP. It is a functional definition masquerading as a shared one.
A B2B technology company with genuine marketing, sales, and CS alignment around a shared revenue model looks like this in practice.
The marketing team runs demand generation programs designed against the agreed ICP. Every campaign produces leads that are scored against criteria that sales has reviewed and agreed to. The MQL-to-SQL conversion rate is 18 to 22% because the scoring model reflects actual buying signals that the sales team recognizes as valuable.
The sales team receives MQL notifications in CRM and can see the marketing touchpoint history for every contact before they make their first call. They follow up within the SLA window because the RevOps governance process surfaces SLA compliance data weekly and the CRO reviews it. They update deal stage criteria accurately because those criteria were designed with their input and they trust that the pipeline report their CRO presents to the board reflects the pipeline they are actually working.
The CS team has expansion signal data in their platform that was configured from the same ICP criteria that marketing and sales are using. When an account shows an expansion signal, the CS platform notifies the sales rep with the relevant account context. Marketing runs expansion programs targeting customer segments identified by CS as high expansion potential. The expansion pipeline metric is tracked and reviewed in the monthly revenue leadership meeting.
The monthly revenue leadership meeting reviews five numbers that all three function leaders helped define, that all three functions contribute to, and that all three functions are evaluated against. When the numbers are on track, the meeting is 45 minutes. When a metric is trending in the wrong direction, the meeting is 90 minutes with a structured diagnosis and an action plan. The conversation is about the revenue model, not about whose metric is and is not performing.
That is not an ideal state. It is a practical operational reality that B2B technology companies at every stage from Series B through public can build. The ingredients are shared metrics, shared data, and a governance structure that keeps the alignment operational rather than aspirational.
How long does it take to build genuine marketing, sales, and CS alignment? The ICP definition and shared metrics agreement takes 2 to 4 weeks if the leadership team is engaged. The data architecture changes take 60 to 90 days. The governance structure takes one full quarter to establish as a consistent operating cadence. Full alignment, where the shared metrics are driving resource allocation decisions rather than just being reviewed in meetings, typically requires 6 to 9 months from the initial ICP definition workshop.
What do you do when the CMO and CRO will not agree on the ICP? Escalate to the CEO. ICP misalignment between marketing and sales is a CEO-level organizational problem. The CEO is the only person in the organizational structure with authority over both functions. Frame the escalation as a revenue model question: the company cannot optimize its revenue growth if marketing and sales are targeting different buyers. The CEO's role in the alignment process is to make the ICP decision when marketing and sales leadership cannot reach consensus.
How do you maintain alignment when the ICP changes after a product pivot or market shift? The quarterly alignment review exists for exactly this reason. When the product changes, the target market shifts, or win/loss data indicates that the ICP has drifted from the buyers who actually convert and retain, the quarterly review is the process for updating the shared definition documents and propagating those updates to the MAP scoring model, the CRM qualification criteria, and the CS health scoring criteria. Organizations that skip the quarterly review end up with an ICP that was accurate 18 months ago and an alignment structure built on an outdated foundation.
What is the most common reason alignment initiatives fail after initial success? Leadership turnover. When a new CMO, CRO, or VP of CS joins and is not onboarded into the shared metrics framework and governance process, they typically revert to optimizing for their own function's metrics within 30 to 60 days. The governance documentation and the quarterly alignment review process need to survive leadership transitions. Organizations that treat alignment as a leadership team initiative rather than an organizational process lose their alignment every time a commercial function leader changes.
The Pedowitz Group has been building revenue marketing and revenue operations alignment infrastructure for B2B technology organizations since 2007. If you want to understand where your current cross-functional alignment stands, the RM6 diagnostic assesses the people, process, and technology dimensions of your revenue model and identifies the specific gaps to close. Talk to TPG.