We're aware of a phishing scam and of illegitimate communications from individuals falsely representing themselves as employees of Eames Consulting. If you have any doubts about the legitimacy of any communication you receive from us, please contact us. Please note that we would never charge candidates for our services.

How to build a data team to drive better outcomes in insurance: Securing top data specialists

by James Freeman

AI and automation are transforming how UK insurers use data. Many are responding by building project-based data teams that scale up when the work demands it and scale back when it doesn't. 

Strategic insurers engage delivery partners early to scope requirements, ensuring that they can access qualified data specialists with niche skillsets precisely when they need them most.  

Explore insights drawn from experience in building mid-senior project delivery teams, covering how insurers can secure the strongest data teams for building long-term advantage.

How data governance is driving demand for data specialists  

The platform work is largely done for many larger insurers, with many running mature environments on Databricks or Snowflake.  

Although adoption is uneven and there are still leaders and laggards in digital transformation, the priority now is making sure that data flows effectively and that the accuracy, availability, reliability and security of business- and compliance-critical data is consistent.  

This puts data integration, governance and remediation firmly on the agenda, as ECMS, the managed solutions arm of Eames Group, explores in this case study.

What insurers need from a modern data team now 

Across the insurance industry, the goals are broadly the same:

  • Strengthening technical data foundations and data interoperability
  • Making organisations AI ready so that automation ambitions can be realised
  • Securing strong specialists who can sit between technology and commercial teams and ensure data informs better decision-making and drives profitability 

In practice, this means that technical data professionals in insurance need to be commercially minded and capable of working closely with underwriting and actuarial colleagues.

What to include when briefing a data project delivery partner

A detailed brief makes the difference between building a data team that fills seats and one that delivers outcomes. Be sure to outline:

  1. The why. What is the long-term business benefit a data initiative brings, and what happens if the project isn't delivered? This will help your partner price the work according to precise benchmarks.

  2. Milestones and deliverables. Define what success looks like at each stage, not just what consultants will do day to day.

  3. Specific skills versus domain knowledge. Decide which matters more for each role. A business analyst working alongside a team of Databricks engineers doesn't necessarily need Databricks expertise. They do need to understand the subject matter stakeholders will be discussing.

  4. Project or programme longevity. Explain where you see the project going over the long run, not just over the course of the first contract or statement of work, as this may impact project appeal for data specialists and finding the best fit.

What attracts contract data specialists

When you hire data engineers, scientists or analysts on a contract or consulting basis, compensation often comes first among candidates’ priorities. A good day rate, longevity and roles outside IR35 are the deciding factors for most mid-senior data contractors. 

After rate, what attracts data specialists varies. Some professionals want exposure to new technology or unfamiliar business areas. Others prefer to deepen a niche they already know, so that they're first in line when the next role in that space comes up. 

The environment matters as well. Insurers who attract the best people tend to offer: 

  • A fast-paced culture where change gets implemented quickly
  • Flat structures without layers of sign-off creating roadblocks to progressing initiatives
  • Flexible working, with face-to-face collaboration on an ad hoc basis rather than a constant requirement 

Why timing matters when building data teams

There's no single best month to start building data teams, but there is a best point in the project or programme lifecycle: early.  

As soon as clients know what they want to do, they should be engaging with outcomes-focused partners like Eames Consulting and Eames Group's managed solutions arm, ECMS, for support in defining data initiatives’ scope and requirements. 

How data contract and consulting seasonality impacts the best time to hire data specialists 

Across the UK market, data contracts often run for six months, ending in June or December. 

The seasonality of data contracting and consulting work means that launching a data project delivery team in January may be challenging, as many of the best contractors will have recently renewed.  

Approaching data professionals in October or November, as early in Q4 as possible, means that contractors and consultants are more likely to be considering their next moves.

How to ensure data team structure stays scalable

Most data transformation work in insurance runs for several years, and demand rarely stays level. Adaptable data team structure allows for that from the outset. 

For example, a two-year programme may need around ten people for the first six months, three or four during a quieter phase, then more again as scope grows.  

Sharing a roadmap of planned technology-led initiatives upfront helps your delivery partner scale the team up and down without losing momentum or organisational knowledge. 

Additionally, ensuring that data capability sits where it needs to with clear ownership avoids silos and bottlenecks.

Building data teams that drive results: Three essentials

In my experience building data teams, project delivery runs smoothest when clients: 

  1. Hire consultants who are well referenced. Check with people in your network who have worked with a consultant or ask your delivery partner to do it for you.
  2. Avoid cutting corners on cost. Trying to save money can result in a project running much longer than it needs to. It can also create technical debt that will add cost down the line anyway, due to more needing to be fixed eventually.
  3. Look for data specialists who bridge the business and the technology. Often, the consultants who move the needle most combine technical ability with commercial awareness. They're comfortable sitting close to the business and acting as the conduit between stakeholders and engineering teams.

Eames Consulting has partnered with insurers for 20+ years, building a trusted network of expert data consultants who understand the insurance market.  

If you’re looking to scope a data initiative or build an experienced data team to drive delivery, speak Jim here or contact our team of Technology & Digital Enablement specialists.   

Frequently asked questions

As early in the project as possible. For contractors, October and November are often ideal, as many six-month contracts end in December.

Traditional carriers and insurtechs are looking for much the same people. Insurtechs may present themselves as technology businesses, but ideal candidates will still need knowledge of the insurance market.

Plan for flexibility. Multi-year programmes often need a larger team in some phases and a smaller one in others, so share your forecast with your delivery partner.

Day rate, longevity and outside IR35 status come first. After that, it's exposure to new technology or business areas, or the chance to deepen existing expertise.

The purpose of the project, the cost of not delivering, clear milestones, whether domain knowledge or platform skills matter more, and the long-term roadmap.

Related insights

Live jobs in this field

Search all jobs

How can we help?

Whether you're hiring or looking for your next move, our specialist consultants are here to help.

Accessibility and Languages