Skip to content
Case studiesDistributed Operations

Staff cost cuts began with one customer record

A services group had a board target on staff cost and no count of its work. The fix started with one record for each customer.

A MetMov engagement. The client is not named.

RoleFinished engagement

Key results

01
The response centre moved to an outsourcing partner and is live.
02
A multi-million yearly saving in staff cost was identified. It is not banked yet.
03
The middle and upper cases meet the board's target; the lower case falls short.
04
One integrated system, built on one customer record, was chosen. Implementation is starting.
The challenge

A services group asked for help with two targets its board set. The first was to fix its response centre, the in-house team that took client calls and requests. The second was to take a double-digit share out of staff cost, across a large client-servicing team spread over several business units and several countries.

We started by asking for the numbers behind the work, and there weren't any. Nobody recorded how many requests came in, how long each one took, or what service level a client had been promised. There were no written procedures either.

The tools showed why. The same client sat in several systems. Requests arrived in personal mailboxes. Incidents had no owner and no due date. Billing ran in a separate system from service, and handovers between teams were tracked by hand.

Each of these problems traced back to one gap: the group had no single record for each customer. Without that record nobody could count the work. Without a count, the staff cost target had nothing to be measured against.

The solution

The work came in three parts:

  • The response centre. We ran a vendor selection with several large outsourcing firms and collected their quotes ourselves. The in-house centre moved to the chosen partner, which added both capacity and capability.
  • Staff cost. We studied the work in every business unit and set a savings range for each unit and for each capability, such as ticketing, billing, incident handling and the response centre. The rollout runs in three stages: pilot, adopt, then scale.
  • The systems. We compared vendor quotes and chose one integrated system built on one customer record. It covers ticketing, incidents, the client lifecycle and billing, and implementation is starting now.

Where It Stands Now

For the first time, the group will record its work one request at a time. The next round of automation depends on that record, because a team can't automate work it has never counted.

What a Smaller Firm Can Use

This group is far larger than most founder-led firms, so the size of the saving doesn't carry over. The order of the work does. A firm that wants to cut a cost first checks whether it can count the work behind that cost. If one customer sits in several systems, the firm builds one customer record before it buys any automation.

Discussion

Discussion

Leave a comment

Next

Ready for a similar transformation?

Install your Operating Spine in 90 days. Start with a short scoping call.

Chat with us!

Pick a time that suits you.