Customer Service Integration After a Merger: The Finance Side of the Decision

A case: what finance needs to know before two customer service models are merged

Customer service integration after a merger is one of the decisions where a cost saving can quietly destroy revenue. This case follows a common situation: an acquirer assessing the acquired company’s customer service model, segment by segment, before deciding what to integrate. The operational assessment covers the service model, customer journeys, contact data and processes. This article follows the same sequence from the finance side: which numbers each step needs, how cost to serve was built, how savings estimates were tested against revenue at risk, and what finance put in front of the acquirer’s decision makers. The case is representative, not a named company. NEO Expertise supports finance teams through the finance side of integration decisions like this one.

The Situation

A financial services group has acquired a smaller competitor. Both run their own customer service operations: contact centres, relationship managers, quality assurance teams and complaint handling. The acquired company is known for its service to high-net-worth (HNW) clients, who generate a large share of its revenue.

The deal model assumed savings from combining the two service operations. Before any decision is made, the acquirer wants to understand how the acquired company’s service model actually works, whether it fits the group’s strategy, and what combining it would do to customers and to revenue. Operations leads the assessment. Finance is asked to make sure every option has a number attached.

Step 1: Segments and the Service Model

The assessment began with how customer service is structured and which capabilities it depends on. Customers were grouped into segments, and service requirements were documented for each: channels, response times, dedicated contacts, and the products each segment holds.

For finance, the segmentation had to match the revenue data. Service segments defined by operations and revenue segments defined in the ledger rarely match on the first attempt. In this case, operations classified clients by assets held, while the ledger reported revenue by product line. Building a customer-level bridge between the two was the first finance task, because every later calculation depends on it.

Customer journeys were mapped end to end, including every touchpoint across products and services. The differences between segments were the key output: HNW clients relied on a named relationship manager, while other segments used the contact centre and digital channels.

Step 2: Service Data and Cost to Serve

The service data review covered contact volumes, quality assurance scores and samples of recorded interactions. Finance combined those volumes with the cost of each channel to build cost to serve by segment. Call recordings and customer records are personal data, so their use in the assessment, and any later transfer between the two companies, had to follow the General Data Protection Regulation.

Illustrative cost to serve for the acquired business:

Segment	Customers	Contacts per customer per year	Cost per contact (€)	Annual cost to serve (€m)	Annual revenue (€m)
Mass	180,000	1.2	6.50	1.40	27.0
Affluent	40,000	3.0	9.00	1.08	32.0
HNW	2,500	14.0	38.00	1.33	41.0

The HNW segment costs almost as much to serve as the mass segment with 1.4% of the customers. Read alone, that looks like the obvious place to cut. Read next to the revenue column, it is the segment that pays for the business: €41.0 million of revenue on €1.33 million of service cost, a ratio of roughly 31 to 1, against about 19 to 1 for the mass segment.

The strengths and weaknesses of each process were documented through stakeholder interviews with service managers and front-line staff. Finance used the interviews for one specific purpose: to find costs that sit outside the service budget, such as complaint compensation, fee waivers and write-offs agreed by relationship managers.

Step 3: Integration Options and Customer Impact

Integration planning set out which processes to keep, which to change and which to standardise with the acquirer’s model. For each option, finance modelled the one-off cost (systems, training, redundancy, dual running), the recurring saving, and the effect on revenue.

The customer impact assessment was the step that changed the plan. Moving HNW clients from named relationship managers to the group’s shared contact centre produced the largest cost saving in the deal model. It also put at risk the relationships that generated about 41% of the acquired company’s revenue, the largest share of any segment.

Step 4: Testing the Savings Case

Illustrative: combining the HNW service into the group contact centre would save about €0.6 million a year. If that change caused just 2% of HNW revenue to leave, the business would lose €0.82 million a year, more than the saving. The saving only works if HNW attrition stays below about 1.5%, and nothing in the service data suggested it would. Quality scores for relationship-managed clients were the highest in the business, which is exactly the service the change would remove.

There is also a balance sheet angle. In a business combination under IFRS 3, as endorsed in the EU in Regulation (EC) No 1126/2008, customer relationships are usually recognised as an intangible asset separate from goodwill, valued on assumptions about customer retention. A service change that raises attrition above those assumptions is an impairment indicator, not just a revenue problem.

The analysis did find genuine savings elsewhere: combining the mass-segment contact centres, standardising quality assurance, and shared complaint handling. Revenue opportunities were identified too, mainly offering the acquirer’s products to the acquired company’s affluent segment.

Step 5: Decision Support for the Acquirer

The findings went to the acquirer as one decision paper: the customer journeys and service capabilities found, cost to serve and revenue by segment, the options with their costs, savings and revenue effects, and a recommendation.

The recommendation kept the HNW service model intact, combined the mass-segment operations, and set a tracking routine for both realised savings and HNW client retention, reported monthly for the first year. Finance owned the tracker, because savings claimed in a deal model and never measured afterwards are how integration plans lose credibility with the board.

Customer data quality underpins all of this. The checks in our post-acquisition data check and the accounts receivable review after an acquisition apply directly, and the timing fits the first 100 days finance integration roadmap.

Where Service Integration Numbers Go Wrong

• Cost per contact without revenue per customer. It makes the most valuable segment look like the least efficient one.
• Missing costs outside the service budget. Fee waivers and goodwill payments often sit in revenue or other expenses, so cost to serve is understated.
• Savings without a tracker. Savings in the deal model are assumed, not measured, until someone reports them against actuals.

This approach assumes finance can link service data to revenue at customer level. Where the acquired company’s systems cannot identify customers consistently across products, start with a customer master data cleanup, and treat any segment-level figures as estimates until it is done.

The Finance Checklist for Service Integration

Use this as a working checklist. Each item is a check to complete, not a topic to consider.

Data foundations

• ☐ Bridge operational service segments to ledger revenue at customer level
• ☐ Confirm the data protection basis for using call recordings and customer records

Cost to serve

• ☐ Multiply contact volumes per channel by cost per contact
• ☐ Add dedicated costs such as relationship managers
• ☐ Add costs held outside the service budget: fee waivers, compensation, write-offs
• ☐ Compare cost to serve with revenue for each segment

Options and testing

• ☐ Model one-off cost, recurring saving and revenue effect for each option
• ☐ Calculate the attrition rate at which each saving breaks even
• ☐ Check the retention assumptions behind acquired customer relationship assets

Decision and tracking

• ☐ Put every option in front of decision makers with a number attached
• ☐ Track realised savings against the plan monthly
• ☐ Track customer retention by segment for at least twelve months

Frequently Asked Questions

What is finance’s role in customer service integration after a merger?

Finance puts numbers on each integration option: cost to serve by segment, one-off integration costs, recurring savings, revenue at risk from service changes, and the effect on acquired customer relationship assets. It also tracks realised savings and customer retention after the decision, so the plan can be tested against actual results.

How do you calculate cost to serve by customer segment?

Multiply contact volumes per channel by the cost per contact for that channel, add dedicated costs such as relationship managers, then add related costs held elsewhere, such as fee waivers and complaint compensation. Divide by customers in each segment and compare the result with revenue per customer.

Can merging customer service operations reduce revenue?

Yes. If a change removes service that high-value customers rely on, attrition can cost more than the saving. Finance should calculate the attrition rate at which the saving breaks even and compare it with realistic retention assumptions before the decision is made.