The growth budget is moving from acquisition to retention

September 22, 2026

The September US marketing retention roundtable included a proposal to give retention a larger share of attention and budget than acquisition. That is a useful signal for vendors, with an essential qualification: the suggested rebalance was a position expressed within the discussion, not a verified movement of budgets across the enterprise market.

The commercial interest lies in what sat behind it. The summaries describe concerns about customer friction, the transition towards subscriptions, the timing of cross-sell offers and the difficulty of recognising customers at risk. July’s discussion adds onboarding, expectations set before purchase and gaps between marketing and customer support. Together, the accounts show why retention can become a technology and operating priority.

For vendors, the question is which part of that problem an offer can actually solve. A platform described as supporting customer lifetime value still needs to demonstrate how it will help the organisation understand a customer, act on a relevant signal or improve an experience. The label alone does little to explain why the investment deserves funding.

Read the budget signal at the right scale

September’s retention discussion records support for giving retention greater emphasis, including a suggested 60/40 orientation towards retention and acquisition respectively. The document presents this as a proposed approach. It does not establish completed budget transfers, a cross-market average or a ratio that every business should adopt.

Vendors should use the signal to open a conversation about priorities. Ask which customer relationships the organisation wants to protect and where the current process falls short. Establish whether the buyer is seeking a new capability, better use of an existing system or coordination between teams. The answer should determine the proposal more than the headline category of retention technology.

The discussion also shows that the meaning of customer value varies. Contributions addressed risk management, subscription models, upsell and cross-sell, and long-term partnerships. Those are different commercial settings. A vendor should avoid forcing them into one standard lifetime value model simply because the product dashboard offers one.

The Leadership Board’s interpretation is that retention can provide a route into a broader conversation about how an organisation delivers value after purchase. The opportunity for a supplier depends on the buyer’s specific obstacle. It should be established through discovery and evidence rather than inferred from a general belief that retaining customers is desirable.

Define the customer relationship before defining churn

The September summary explicitly describes work to redefine what counts as churn. That detail should matter to vendors selling analytics or predictive capabilities. An apparently precise churn figure is only useful when the organisation agrees what event or pattern it represents and what action could follow.

A recommended discovery process would ask how the relationship begins, what continued participation looks like and when the organisation considers it at risk. A subscription renewal differs from a purchasing pattern or a long-term partnership. These are illustrative distinctions grounded in the different business models discussed, rather than a claim that one definition can cover them all.

The buyer may also need to distinguish reduced activity from departure. A change can be worth investigating without proving that the customer intends to leave. The vendor should explain the evidence behind any signal and how the receiving team can assess it. Otherwise, a predictive score can become an instruction that no one knows how to use.

This work should happen before a demonstration is treated as proof of fit. Show how the product can reflect the organisation’s agreed definitions and identify where custom work is required. If the definition remains unsettled, propose a bounded discovery stage. A clear dependency is preferable to a retention promise built around an ambiguous measure.

Retention starts with the promise made before purchase

July’s retention discussion emphasised understanding why customers bought and managing expectations during implementation. It also linked retention with onboarding and early value. That extends the vendor conversation beyond campaigns sent shortly before a renewal. The experience can be shaped by the commitments made earlier in the relationship.

For suppliers, the recommendation is to examine how the buying rationale reaches the people responsible for implementation and support. Does the organisation know what success means to the customer? Can the team see the promises already made? Where does it record whether those expectations have been met? These questions connect retention with an observable operating process.

A technology proposal should show how it supports that hand-off rather than assuming the information already exists in a usable form. The customer may need to change a process or establish an owner as well as configure software. Make that work explicit, especially where different teams control sales records, onboarding and ongoing communication.

There is also a lesson for the vendor’s own sales approach. A retention product sold through exaggerated promises risks reproducing the very problem it is meant to address. Define the use case and implementation conditions carefully. Give the buyer a realistic account of when the proposed capability will become usable and what evidence will indicate progress.

Connect marketing with what service teams know

One of July’s clearest examples concerns promotional messages reaching customers while their existing problems or repair requests were invisible to marketing. The issue was disconnected data across touchpoints. It is a concrete illustration of why a retention proposition should include coordination with service, rather than focus exclusively on campaign sophistication.

A vendor could use a similar scenario in discovery without presenting it as the prospect’s current situation. Ask how the organisation handles an active service problem when another team plans a promotional contact. Who can see the issue? Can the communication be changed or postponed? What happens if the information arrives late?

The useful demonstration follows the information through to an action. Displaying a service record in a customer profile is one step. Showing how an authorised team uses it to change the experience is another. The buyer needs to understand the integration, the permissions and the people responsible for the response.

September’s journey discussion adds continuing difficulty with coherent messaging between marketing and support. This reinforces the value of examining the hand-offs. It does not establish that a single platform will remove every organisational silo. Vendors should describe which connections they can provide and which working agreements the customer must establish.

Make early warning signals actionable

Both source documents include interest in identifying customers at risk before they leave. July’s predictive analytics discussion described monitoring utilisation and listening to customer-facing teams. September’s retention session considered analytics to identify risk earlier. These are useful directions for discovery, but the summaries do not provide a validated predictive model for general use.

For vendors, a responsible proposal should explain how a proposed signal relates to the buyer’s own customer relationship. Identify the information needed, its limitations and the action the organisation could take. A risk alert without a suitable response process can create another queue of work rather than a better experience.

The response also needs an owner. If marketing sees the alert but service must resolve the underlying issue, agree how that hand-off will happen. If the concern relates to implementation, involve the team able to address it. This is a recommended operating design derived from the source’s repeated coordination problems, not a reported common practice.

Evaluate the quality of the resulting action as well as the signal. Did the team understand the issue? Was the contact appropriate? Was the problem resolved? These questions help the buyer distinguish useful intervention from additional messaging. They also give a vendor a more credible evaluation than counting the number of alerts generated.

Use customer feedback alongside behavioural data

July’s retention discussion includes an account of a loyalty measure associated with renewal and expansion risk. It also records the importance of customer-facing judgement and early feedback. The material supports examining different kinds of evidence; it does not establish one survey score as a universal predictor of retention.

A vendor should ask what the organisation already learns from conversations, support interactions and feedback programmes. Then examine where those insights are available and whether they influence action. There may be a valuable opportunity to connect existing information before adding another data source or another scoring system.

Where feedback and observed behaviour disagree, the workflow should allow investigation. A positive survey answer does not settle every question about the relationship, just as reduced activity does not explain its own cause. The buyer needs enough context to decide what to do. Vendors should show how the product supports that judgement.

This approach also keeps measurement connected to customer experience. The purpose of collecting more signals should be to help the organisation respond appropriately. A proposal that describes only the volume of data collected leaves the buyer to work out the practical benefit. Make the connection between information and action explicit.

Put cross-sell in the context of the relationship

September’s retention discussion includes work on the timing and targeting of upsell and cross-sell offers. It also describes an emphasis on making relationships more durable rather than relying solely on lifetime value calculations. The vendor opportunity is to support relevant expansion while recognising the state of the existing relationship.

A recommended discovery question is what makes an offer appropriate at a particular moment. The answer may involve a customer need, an expressed interest or a change in the relationship. The source does not provide a universal trigger. Vendors should investigate the buyer’s evidence and avoid assuming that additional available data automatically justifies another contact.

Service context belongs in that decision. If the customer is struggling to realise value from the original purchase, an expansion message may be poorly timed. Show how the proposed workflow can use the information the organisation is authorised to share, and how a team can withhold an offer when the context is unsuitable.

The evaluation should distinguish increased activity from a better relationship. More messages or more suggested offers do not, by themselves, show that cross-sell has improved. Agree what outcome matters and how the organisation will observe it. Retain enough context to understand whether the proposed capability contributed to that outcome.

Avoid making incentives the whole proposition

The source discussions contain different experiences of loyalty programmes and incentives. July’s retention session considered the challenge of competing on value when financial offers changed. September included scepticism about traditional loyalty mechanisms in some B2B relationships, alongside examples of referral and purchasing arrangements. There is no single model endorsed across the documents.

Vendors should therefore ask what customers value about the relationship beyond the incentive itself. That may require the buyer to gather more evidence rather than choose from a preset campaign menu. The proposal should leave room for service quality, communication and delivery of the original promise, all of which appear in the retention discussions.

If incentives are part of the proposed solution, make their role clear. What behaviour are they intended to support, and how will the buyer judge whether the relationship becomes more durable? The summaries do not substantiate a general return from discounting or referral rewards. Any financial case must be developed for the particular programme.

This keeps the sales conversation commercially grounded. The buyer may have a retention problem that an incentive platform can address, or a service problem that requires different work. Establishing that distinction early helps the vendor scope an offer it can deliver and avoids treating every form of customer departure as the same issue.

Build the case around a manageable customer journey

A credible retention proposal should choose a specific part of the relationship and define the change sought. Onboarding, service coordination or renewal communication may offer a bounded starting point. These are recommended options derived from the source themes, not a prescribed sequence for every organisation.

Document the current process, the information available and the team responsible for acting. Agree the meaning of the retention outcome and the period over which it can sensibly be observed. Include implementation effort and ongoing operational work in the business case. If the result depends on another team’s participation, secure that involvement within the project design.

The September budget discussion should be used as a reason to investigate these opportunities, rather than as proof that funding is waiting. A vendor earns a stronger place in the conversation by showing which customer problem it can help resolve and how the buyer will know whether the investment was useful.

The practical message from July and September is that retention involves connected experiences and delivery of value after the sale. Vendors should bring a proposition that reaches those operating details. That is where a broad ambition to protect growth becomes work an enterprise team can evaluate and fund.