Why departmental revenue targets can weaken customer relationships

Customers experience one relationship, even when teams operate separately

Imagine a customer receiving three unrelated emails from marketing, customer support and product in the same week, then having to explain the same problem to four people. Leaders may see a coordination failure, but they should also ask whether their performance measures helped create it. Requiring every department to claim its own revenue can encourage teams to pursue separate goals within the same customer relationship.

Those separate goals show up in ordinary interactions. A customer success manager, or CSM, knows nothing about a commitment made by support, while marketing promotes a webinar about a feature the customer already uses. Sales then introduces an “expansion opportunity” without connecting it to the customer’s priorities. In this illustrative situation, the customer might select “unsubscribe”; repeated irrelevant or inconsistent contact can also weaken trust and lower expectations of the brand.

The customer’s response makes internal coordination a service issue. Management may treat processes, ownership, systems and teamwork as internal concerns, but IT, reporting structures, handoffs and information sharing affect what customers must do to get help. Customers experience one relationship with the company, so departmental evaluations can shape the service they receive. Leaders therefore need to ask whether those evaluations encourage teams to improve that relationship together.

Requiring every department to claim revenue can reward the wrong work

A hypothetical renewal shows why separate revenue claims can misrepresent how customer value develops. Imagine an enterprise customer worth $500,000 approaching its renewal decision after six functions have helped sustain the relationship over the preceding year. Each function has a contribution to explain, but the renewal depends on how their contributions have built on one another across the account.

Their contributions address different customer needs. Customer success has helped the customer manage an organizational restructuring, while customer marketing has introduced additional stakeholders to capabilities they were underusing. The community has helped users solve problems and build peer connections, and support has fixed a persistent technical issue. Product has delivered an essential feature, while an executive sponsor has strengthened relationships with the customer’s leadership team.

When the customer renews, several departments can therefore credibly claim a role. Customer success points to its responsibility for the account; customer marketing reports engagement and influenced revenue, meaning revenue associated with customers its programs reached. Community points to active participation, while product and support identify improvements that changed the customer’s experience. Each claim describes a contribution, but none establishes that the function independently produced the renewal.

These contributions also reinforce one another, which makes dividing the result more difficult. Broader stakeholder engagement can make a product improvement more useful, while effective support helps users keep benefiting from it. Executive relationships can strengthen organizational support for continuing the purchase. Because the customer decides whether to renew the combined relationship, a departmental percentage of revenue gives an incomplete account of how that decision became possible.

Yet requiring separate revenue claims can push teams to behave as though value develops independently. Performance measures define the results employees must defend, so they influence which customers and activities receive attention. When budget protection depends on a visible revenue number, work with a clear, near-term commercial result becomes easier to fund. Preventive work faces a harder test even when it addresses a serious business risk.

Two hypothetical customer marketing programs show how this funding preference develops. Program A targets customers who have already shown purchasing intent and generates 20 opportunities, followed by $1 million in closed-won expansion revenue: completed sales that increase spending by existing customers. The team can connect its activity to an identifiable sales result, giving it a straightforward case to present during a funding review.

Program B addresses a different need: dependence on a single champion, the person inside a customer organization who strongly supports the product. It reaches additional stakeholders, develops executive relationships and builds wider organizational support. If the champion leaves, those relationships could help prevent churn, or the loss of the customer’s business. The program could therefore protect millions of dollars in future revenue, although that protection depends on what happens to the accounts.

The time required for that protection to matter makes Program B harder to defend. A renewal it helps protect might be 18 months away, and customer success, product, support and account management would also contribute to the result. Customer marketing would struggle to separate its financial share from everyone else’s work. Its contribution could be important while fitting poorly within a short attribution window, the period during which a team connects an activity to a revenue outcome.

Program A’s clear result still deserves scrutiny, including whether it created additional value beyond what would have happened anyway. Its measurable revenue total does not establish that it generated more of that additional value than Program B. Treating ease of measurement as evidence of superior value creates measurability bias. This bias gives immediate expansion activity an advantage over work intended to make customer relationships more durable.

The advantage can redirect effort before the next budget meeting. Teams evaluated on revenue have a reason to concentrate on customers already likely to buy, because those customers offer a more defensible result. Short measurement periods further weaken the case for long-term prevention. Customer marketing and community are particularly exposed when their work depends on sustained participation, broader relationships or benefits produced jointly with other functions.

Competition for defensible results can also turn shared customer work into a contest for credit. Functions may duplicate activity, withhold information to protect their claims, or miss opportunities that require cooperation. Communications then become fragmented as each team prioritizes the activity it expects to report, allowing departmental metrics to improve while customers receive less relevant contact. Better reporting will leave this incentive in place if every function must still defend an independent claim on shared revenue.

Keep teams accountable for execution and contribution

Changing that incentive starts with a different question about team performance. Attribution asks how much revenue a function can claim; contribution asks what change the function was responsible for making, whether that change occurred and why it matters to the business. Leaders must define the expected change before judging success. This gives teams a specific responsibility within the shared customer result.

For a CSM, that responsibility includes account planning, coverage of relevant stakeholders, identification of risks and progress toward the customer’s goals. These duties remain demanding when renewal revenue is assessed across the teams involved. An account can renew despite weak account management, while strong account management can still help a difficult relationship. Evaluation must therefore examine the work performed and its consequences within the account.

Customer marketing needs equally explicit responsibilities so leaders can assess its contribution on its own terms. They can examine whether programs improve product adoption, customer knowledge, stakeholder engagement or advocacy readiness, meaning the customer’s preparedness to recommend or publicly support the product. Each change has commercial relevance, but reaching a customer does not entitle marketing to claim all of that customer’s revenue. The team should explain what improved and how that improvement supports the relationship.

Community’s responsibilities should likewise reflect the help it provides. Its contribution can include helping customers resolve problems, become more proficient and form useful peer relationships. Assigning community an arbitrary percentage of customer lifetime value, the value associated with the customer over the relationship, would obscure those duties. Evaluation should examine whether participation produced meaningful help and whether the team performed its role effectively.

These functional responsibilities fit into three separate assessments. Controllable performance concerns how effectively a team carried out its assigned work. Demonstrated contribution concerns meaningful change resulting from that work, while shared economic outcomes concern whether the customer portfolio retains business, grows and creates value. Assessing each separately lets leaders examine execution, change and financial results without treating them as interchangeable.

Financial results remain essential because well-executed activity can still fail to create useful business value. Portfolio retention and growth belong in the evaluation at the level where multiple contributions combine. Team-level measures then help explain what each function did within that result. Leaders can use both levels to connect operational work to economics and decide whether an activity deserves continued investment.

Shared outcomes nevertheless create a risk that weak teams will escape scrutiny. The unnamed author of Can Your Customers See Your Org Chart in Every Interaction? captures that risk with the hypothetical defense, “We all contributed”. Leaders should require each team to demonstrate effective execution and meaningful change before awarding credit. Activities that consistently fail to produce useful results should lose funding, even when their intended purpose sounds valuable.

Requiring evidence also means examining whether a team’s work caused the claimed change. Separating execution, contribution and economic outcomes helps leaders identify the questions they must answer, but establishing cause can remain difficult. Attribution can still have legitimate uses here. Leaders need to judge the evidence behind each contribution alongside the conditions in which the team worked.

Retention results need context before they become performance judgments

Those working conditions can change what a result reveals about performance. Consider two hypothetical CSMs, each managing $5 million in annual recurring revenue, or revenue expected to recur each year. Their portfolios have equal financial size, but their assignments can differ substantially in difficulty. A useful comparison starts with what each person inherited.

The first CSM receives mature customers with strong adoption, stable budgets and established executive relationships, while the second receives customers with weak adoption, unresolved product issues and substantial organizational turnover. At year-end, the first records 95% gross revenue retention and the second 85%. Gross revenue retention measures how much existing revenue remains after losses and reductions, excluding expansion. It shows the financial result, but the starting conditions affect what that result reveals about either employee’s effectiveness.

For example, the lower-retention CSM may have prevented several additional cancellations through strong work. The higher-retention CSM may have benefited from accounts already likely to stay while doing little to strengthen them. These possible explanations leave a management question unanswered: what did each employee change relative to the conditions they faced?

Answering that question requires examining inherited conditions, risks identified and changes achieved within the accounts. The evaluation must also consider the resources and authority available to the CSM, because those determine which responses were possible. Leaders can then distinguish outcomes the person controlled, outcomes they could influence and outcomes determined elsewhere. Retention remains important, while this context helps explain what it says about performance.

Capacity is one condition that can limit what a CSM achieves. If account loads prevent adequate stakeholder coverage, penalties will not create the time needed to do the work. Account management and functional leaders must determine whether an employee failed to carry out an achievable responsibility or faced a workload that made it unattainable. The distinction determines whether the useful intervention concerns execution, staffing or the assignment itself.

Product limitations can similarly constrain customer marketing. If essential capabilities are missing, replacing the marketing leader will leave the adoption barrier in place. Product and engineering leaders therefore belong in the diagnosis when customer difficulties arise from what the product cannot do. Strong execution in one team can coexist with poor customer results caused elsewhere, so personnel decisions should follow an examination of what is limiting progress.

Allocate the next dollar according to customer risk

Understanding those conditions also gives leaders a better starting point for budgeting. Department-led discussions begin with separate requests: customer success seeks headcount, customer marketing proposes programs, and community requests another platform or team member. Each functional leader, including the marketing leader, builds a return-on-investment, or ROI, case explaining the expected financial benefit relative to cost. This creates a risk that the most persuasive attribution claim will receive funding ahead of the most important customer need.

A discussion organized around customer risk begins by asking which relationships are exposed and what capabilities would improve their position. It also considers opportunities to increase customer value, giving leaders a basis for assessing both prevention and growth. The problem or opportunity comes first. Leaders then decide which functions need resources to address it.

Suppose, hypothetically, that $20 million in recurring revenue depends heavily on accounts with a single champion. Support for each relationship is concentrated in one person, whose departure or changing role could weaken the company’s position within the account. This diagnosis establishes a need to broaden and strengthen relationships across those customers. Choosing the response then requires comparing what different teams could do.

Additional CSM capacity might enable more direct engagement with stakeholders. Customer marketing programs that reach many accounts could involve a wider set of people, while executive engagement could focus on a smaller number of strategically important relationships. The appropriate response may combine these capabilities. Comparing customer success and customer marketing solely through their historical ROI would make that combined response harder to assess.

The next funding decision should therefore turn on which investment has the best chance of reducing the identified risk. Leaders can compare proposed capabilities against the customer conditions they need to change, including the reach and attention each approach provides. Departments must explain their specific roles within that response. This keeps the decision focused on portfolio needs and makes funding across departments a practical option.

Funding against risk still requires follow-through after resources are allocated. Leaders should examine execution and demonstrated contribution, including whether stakeholder access and organizational support actually improve. Activities that consistently fail to produce useful results should stop receiving support. The reason for selecting an investment changes, while the obligation to demonstrate results remains.

Make coordination part of everyday accountability

The same approach to responsibilities should address the disconnected contacts and repeated explanations in the opening scenario. To coordinate those interactions, teams need shared customer information, dependable transfers and clear ownership of unresolved work. Internal IT and reporting arrangements affect whether those practices are possible, so leaders must examine them alongside performance measures. A team’s evaluation should include how effectively it helps the next team serve the customer.

Leaders can make that responsibility concrete by connecting each operating gap to the customer experience it creates. The comparison below pairs each gap with an action leaders can examine in daily work. These responsibilities make coordination part of what teams are expected to deliver.

Key takeaways for decision-makers

• Customer experience reflects internal coordination: Department heads need shared customer information and coordinated outreach. Customers experience one relationship, and disconnected messages or repeated explanations increase their effort and weaken trust.
• Revenue targets shape investment choices: Separate departmental revenue claims favor near-term sales activity with clear attribution. Budget reviews need to examine the value created by preventive work, including broader stakeholder relationships that protect future renewals.
• Shared outcomes require specific accountability: Functional leaders need to define each team’s responsibilities, assess execution and verify meaningful customer improvements. Evaluate retention and growth where those contributions combine, and withdraw funding from activities that consistently fail to produce useful results.
• Retention results need operating context: Customer success managers’ evaluations need to account for inherited account health, workload, product limitations and available authority. These conditions help distinguish strong performance from favorable assignments and identify where intervention will help.
• Customer risk should guide funding: Budget owners need to identify exposed relationships and compare the capabilities required to strengthen them. Accounts dependent on a single champion may benefit from a combined investment in customer success capacity, marketing programs and executive engagement.
• Handoffs need clear ownership: Functional leaders need to assign responsibility for unresolved issues and make transfers between teams dependable. Include coordination in performance evaluations so customers receive consistent help across departmental boundaries.