Copilot at Bluestone Assurance: the first 75 days

Developers using Copilot

497

71% of 700 seats

Plan progress

56%

5 of 9 milestones

Developers learning

on a learning path

Challenges completed

hands-on, with official docs

Summary

Copilot is now part of daily work across most of Bluestone's engineering org, with 497 of 700 developers active. Policy admin and data and analytics have made it a weekly habit on nearly every seat, and the first monthly update reached the CIO on schedule. Claims platform adoption has dipped, so the next quarter focuses on a tailored plan for that team and its legacy Java modernization.

Goals

Modernize the legacy claims system
A claims modernization pilot with agent mode is planned, and custom instructions for the claims repo are under way.
In progress
Adoption across the whole engineering org
497 of 700 seats are active (71%), and two teams are above 90%.
On track
A monthly adoption update for the CIO
The first monthly update was delivered on schedule.
Achieved

Wins

Every seat assigned in week one
All 700 seats went out by team, so adoption can be followed team by team.
Security questions settled early
The public code filter and IP questions were resolved within the first two weeks.
Two teams set the standard
Policy admin and data and analytics use Copilot weekly across nearly every seat, a model for the rest of the org.

Adoption highlights

The next 90 days

Hands-on session for the claims team
Claims platform team lead · Next two weeks
A working session on their own legacy Java, using Chat and repository instructions.
Repository instructions for every team
Platform team · This month
Start with the claims repo, then roll the pattern out org-wide.
Claims modernization pilot with agent mode
Elena Ruiz · Within 45 days
Small, tested refactors of legacy Java, measured against today's baseline.
Results review with leadership
Your GitHub account team · Next quarter
Progress against each goal, with the numbers from your portal.

How you can help

Help us find a Copilot advocate inside claims or platform engineering
Join the kickoff for the claims modernization pilot
Share the monthly update with the wider engineering leadership team

Prepared by your GitHub account team with help from Claude. Numbers come from your Copilot usage and your onboarding plan.

Summary

Goals

Modernize the legacy claims system

A claims modernization pilot with agent mode is planned, and custom instructions for the claims repo are under way.

In progress

Adoption across the whole engineering org

497 of 700 seats are active (71%), and two teams are above 90%.

On track

A monthly adoption update for the CIO

The first monthly update was delivered on schedule.

Achieved

Wins

Every seat assigned in week one

All 700 seats went out by team, so adoption can be followed team by team.

Security questions settled early

The public code filter and IP questions were resolved within the first two weeks.

Two teams set the standard

Policy admin and data and analytics use Copilot weekly across nearly every seat, a model for the rest of the org.

The next 90 days

Hands-on session for the claims team

Claims platform team lead · Next two weeks

A working session on their own legacy Java, using Chat and repository instructions.

Repository instructions for every team

Platform team · This month

Start with the claims repo, then roll the pattern out org-wide.

Claims modernization pilot with agent mode

Elena Ruiz · Within 45 days

Small, tested refactors of legacy Java, measured against today's baseline.

Results review with leadership

Your GitHub account team · Next quarter

Progress against each goal, with the numbers from your portal.