Customer data platform teams in North West England: roles and governance

What to take away

Why North West England projects usually start with CRM consolidation

A customer data platform rarely arrives on its own. In the North West it usually follows a CRM problem that has become visible to the board.

A retailer with a mail order heritage may hold customer records across a legacy order system, a call centre tool and a separate email platform. A bank or insurer may hold them across a branch system, a broker feed and a contact centre.

The trigger is the same: nobody can answer a simple question about a customer without joining three systems by hand.

CRM consolidation is the first phase because it produces a visible win. Duplicate records fall, contact preferences become consistent, and the marketing team stops mailing people twice. That win funds the second phase, which is the customer data platform itself.

The sequence matters for headcount. A consolidation project needs data engineers and a business analyst. A customer data platform needs those people plus a segmentation owner and someone accountable for consent. Recruiters who understand the sequence can brief candidates accurately instead of advertising a single vague role.

The platform choice sits alongside that sequence. Adobe Experience Platform, Salesforce Data Cloud, Twilio Segment, Tealium, Treasure Data and Amperity are among the customer data platform products sold into the UK market, and each brings its own expectations about who owns identity resolution, consent and activation.

Regional employers also tend to run the work in-house rather than hand it entirely to a systems integrator. That keeps a permanent team on the payroll and creates the roles this site tracks, including the functions that need an owner before any headcount request goes out.

Budget cycles reinforce the pattern. Many North West businesses plan technology spend on a financial year that starts in spring, so consolidation scoping happens in autumn and platform hiring follows in the new year.

Named Manchester and Liverpool employers running customer data platform work

The Manchester employers most often named in briefs are Co-op, N Brown, JD Sports, boohoo group, AO World and the Manchester Airports Group. Each holds a large consumer base and each has consolidated customer records at some point in the last decade.

Co-op is a useful example because its funeralcare, insurance and retail arms all hold customer data under one brand. Consolidation there is as much about governance as technology.

N Brown and JD Sports are retail cases with different rhythms. N Brown carries a credit and catalogue history. JD Sports runs a store estate alongside ecommerce, so identity resolution across channels is the hard part.

The Liverpool employers cited most often are The Very Group, which grew out of Shop Direct, and the city's insurance and building society operations. Liverpool also has a strong agency and consultancy cluster that supplies contract staff to both cities.

A worked example shows how this lands in practice. A Liverpool retailer with a catalogue history merges three customer tables into one, then adds a platform to score recency and value. The team is four people at the start and six after twelve months.

Manchester and Liverpool employers compete for the same candidates, and the M62 corridor means many staff will commute either way. That has kept salary bands closer together than the two cities' office markets might suggest.

Typical team shapes in retail and finance

Retail team shapes are commercial and lean. A typical structure is a data engineering lead, two engineers, an analytics or segmentation manager, and a CRM or lifecycle marketer who owns the campaigns. Product ownership often sits with a head of digital or ecommerce.

Finance team shapes are larger and more layered. A bank or insurer will usually separate marketing data from risk and compliance data, even when both sit on the same platform. That means a platform owner, a data governance lead, analysts in each business line, and a marketing operations function.

The table below sets out the common shapes. Employment and labour market data from the Office for National Statistics is the usual starting point when a team wants to benchmark its size against the wider regional labour market.

Retail teams tend to hire generalists who can move between engineering and campaign work. Finance teams hire specialists, and the governance role is rarely combined with delivery.

Contractors fill gaps in both. A retail team may bring in a contractor for migration and release them once the platform is live. A finance team is more likely to convert a contractor to permanent staff, because platform knowledge is harder to replace.

Recruiters should note that job titles vary more than the underlying work. A segmentation manager in one Manchester employer is an audience lead in another and a CRM analyst in a third. The operating models set against the manual baseline explain why the same work attracts different titles.

Retail audience segmentation and ONS retail industry data

Retail audience segmentation in the North West leans on a small number of variables: recency, frequency, value, category affinity and channel preference. Most teams start with those five and resist adding more until the first set is stable.

The reason is practical. A segmentation scheme that nobody maintains is worse than a simple one that the CRM team uses every week. North West retailers with catalogue histories often already hold the recency and value data they need.

The ONS retail industry data — the Retail Sales Index, the Office for National Statistics' regular measure of retail sales volumes and values in Great Britain — is the baseline for sizing. Teams use it to check whether their addressable audience, basket patterns and seasonal peaks match what the national statistics show for the sector. The figures are published regularly and are free to use.

A worked example: a Manchester homeware retailer builds five segments, maps them to the ONS seasonal pattern, and finds its peak differs from the national one by several weeks. That single finding changes the campaign calendar.

Segmentation work also has a governance dimension. Every segment that drives a marketing message needs a lawful basis, and the team must be able to explain how a customer entered a segment. That is one reason the segmentation owner sits close to the CRM team rather than in a separate insights function.

Finance teams use segmentation differently. They segment for service and risk as much as for marketing, so the same platform may hold marketing segments and collections segments that must never be mixed.

Finance consent and retention constraints in the region

Finance teams in the North West operate under tighter consent and retention rules than retail teams. UK GDPR and PECR apply to both, but financial services add conduct rules and, for some products, a statutory retention period.

The practical effect is that a finance customer data platform must record consent at a finer grain than a retail one. A customer may consent to marketing by email but not by phone, and that distinction has to survive every system migration.

Retention is the harder problem. A bank may need to keep transaction records for years while deleting marketing data much sooner. The platform has to hold both, with different rules, without leaking one into the other.

This is where the controller and processor split matters. When a finance team buys a platform, the vendor is usually a processor and the firm remains the controller. The ICO's guidance on controllers and processors sets out how those roles divide.

Liverpool and Manchester finance employers also face scrutiny from the Financial Conduct Authority, whose Consumer Duty and the financial promotions rules in its COBS 4 sourcebook sit outside the data protection regime but shape how customer communications are approved. Teams that ignore this find their campaign sign-off slows to a crawl.

A common structure is a marketing operations lead who owns consent capture, a governance lead who owns retention schedules, and a platform owner who makes sure both are enforced in the technology. Splitting those three across one person is a known failure mode.

How the ICO guidance shapes North West team structures

The ICO does not prescribe team structures, but its accountability guidance effectively does. It expects a named owner for data protection compliance and evidence that decisions are recorded.

In practice, North West teams respond by creating a governance role that sits alongside the platform team rather than inside it. That person maintains the record of processing, handles data subject requests, and signs off new data sources before they are connected.

Accountability duties set out in the ICO's accountability framework are the reason many teams keep a decision log. When a segmentation rule changes, the log records who approved it and why.

This shapes hiring. A customer data platform team in a regulated North West employer will usually include someone who has run a data protection impact assessment before, even if that is not their main job.

The guidance also pushes teams toward documented retention schedules. That work is dull and it is the first thing an auditor asks for, so it tends to be owned by the governance lead and reviewed annually.

Smaller retail teams often share the governance role with an existing compliance function. That is workable if the platform team routes every new data source through the same review, and risky if it does not.

The regional consequence is that the people, not systems making the decisions are the ones who carry accountability. Technology choices matter less than who signs the decision log.

What the regional evidence does and does not show

The evidence supports a clear pattern: North West customer data platform work starts with CRM consolidation, is staffed by small retail teams and larger finance teams, and is shaped by ICO accountability expectations.

The evidence does not support precise salary benchmarks or headcount ratios for the region. Public data is too coarse, and employer disclosures are too inconsistent, to justify a number.

It also does not show that every North West employer follows the same sequence. Some buy a platform first and consolidate later, usually because a vendor has bundled the migration into the contract.

What the evidence does show is that the work is durable. Consolidation, segmentation and governance all need permanent owners, and those owners are the roles regional employers keep hiring for.

Common questions

Do North West customer data platform teams report to marketing or technology?

Retail teams usually report to marketing or digital. Finance teams usually report to a data or risk function, with marketing as a stakeholder rather than the owner.

How long does CRM consolidation take before a platform goes live?

Most North West projects run consolidation for six to twelve months before the platform takes on live segmentation. The variance comes from how many legacy systems hold customer records.

Is the ONS retail industry data useful for a single retailer?

It is useful as a baseline for seasonality and sector size, not as a forecast for one business. Teams use it to sanity check their own patterns rather than to set targets.

Who is the controller when a North West firm buys a customer data platform?

The firm buying the platform remains the controller. The vendor is normally a processor acting on the firm's instructions, which is why the contract and the retention schedule matter.

Do Liverpool and Manchester employers hire the same profiles?

Broadly yes. The M62 corridor means candidates move between the two cities, and the main differences are in sector mix rather than in the roles themselves.

What is the first hire for a new customer data platform team?

A data engineer who understands the existing CRM. Without that person, consolidation stalls and the platform has nothing reliable to read from.