Embracing Copilot: Crimson Goes First
Copilot readiness
Build secure foundations for Microsoft Copilot.
Our Readiness Assessment reviews your permissions, data governance and security before rollout.
How first-hand adoption of Microsoft Copilot is changing the way Crimson works, delivers and advises clients
Crimson is acting as Customer Zero: deliberately using its own organisation as the proving ground for Microsoft Copilot before taking those lessons to clients. Six months of sustained use has delivered clear productivity benefits, informed a more AI-enabled delivery model and given Crimson first-hand experience to bring to client transformation.
If Crimson was going to help clients navigate AI transformation, it first needed to experience that transformation itself.
The goal was not simply to introduce another productivity tool. Crimson wanted to understand where AI creates genuine value, what adoption requires in practice and how it could change the way the business operates and delivers for clients.
This follows Microsoft’s Customer Zero approach: use the technology internally, learn from real work and turn that experience into practical customer guidance. For Crimson, Copilot is the starting point, with agents and automation forming the next stage of that internal journey.
What began as an individual productivity initiative is now influencing how Crimson’s people develop solutions, create content, prepare for client conversations and deliver projects.
How work changed
Crimson’s journey began with familiar use cases. Colleagues used Copilot to summarise meetings, research topics, draft communications and create documents.
The more significant change came when people stopped treating Copilot as a separate application and incorporated it into their everyday work.
Developers now use Copilot to examine code, investigate issues and explore potential solutions. Consultants use it to bring together technical information, research and discovery findings before applying their expertise to the final recommendation. Sales teams use it to prepare for client conversations and develop bids. Marketing uses it to turn interviews into articles, research sectors, optimise content and improve campaign ideas.
For one technical colleague, Copilot connects research with delivery. They use it to bring together Microsoft Learn content, DevOps tickets, code and working notes, then convert completed work into structured guidance for clients or colleagues. They report faster coding and support in learning a new programming language.
In Sales, one colleague estimates saving 3 to 5 hours on producing professional bid and presentation content, plus approximately another hour on drafting emails. A technical colleague compares Copilot to having a junior developer available for clearly defined tasks, creating more space to concentrate on the bigger picture.
Another colleague captured the wider behavioural shift simply: “I generally use Copilot alongside me as my teammate.”
Copilot provides a starting point, helps people explore options and accelerates routine work. Crimson’s specialists remain responsible for checking the evidence, applying client context and making the final decision.
01
The impact at a glance
An estimated 1,900 to 5,800 hours of potential annual capacity
-
100% of surveyed colleagues say Copilot makes them more productive.
-
100% say Copilot helps them complete tasks faster.
- 82% say Copilot improves the quality of their work, with the remaining 18% neutral.
- The estimate is based on more than 58,000 Copilot actions recorded over six months of recurring use across Crimson.
- £76,000 per month saving in time-equivalent prompt output value.
The annual capacity range is modelled rather than directly measured. It annualises six months of observed activity and assumes that each recorded action releases between one and three minutes. It represents potential working capacity, not a confirmed cash saving. Meeting-related benefits have not been added separately to avoid potential double-counting.
For clients, this everyday use provides practical insight rather than generic demonstrations. Crimson is learning where AI genuinely helps, where human expertise remains essential and how adoption differs by role. Those lessons can shape the advice, enablement and role-based use cases it brings to each client.
The survey results indicate clear perceived benefits in productivity, speed and quality. The telemetry also records recurring activity across leadership, consulting, technical delivery, sales, marketing and operational functions, using Copilot Chat and Copilot experiences across Microsoft 365.
Crimson will build on this baseline by examining selected workflows in greater detail. This will help the business understand where time is released, whether quality or consistency changes and how additional capacity is put to productive use.
Human expertise remains accountable
At Crimson, accountability stays with the person, not the tool.
Colleagues use Copilot to challenge their thinking, develop ideas, explore alternatives and accelerate initial drafts. They interrogate its responses, check the evidence and test proposed designs against their professional knowledge before using an output in a solution, document or client recommendation. This puts responsible, governed AI adoption into practice: people remain accountable, outputs are challenged and professional judgement stays central to delivery. It is consistent with Microsoft’s emphasis on governance and responsible AI as foundations for customer transformation.
The aim is to reduce the time specialists spend searching, summarising, structuring, and documenting, thereby creating more capacity for complex problem-solving, informed decision-making, and client relationships.
From personal productivity to delivery transformation
Once Copilot became part of everyday work, Crimson turned to a bigger opportunity: redesigning how client projects are planned, delivered and supported.
Crimson is now mapping AI across its technology delivery lifecycle, from mobilisation and design through to iterative delivery and service transition. During mobilisation and design, AI can help teams capture discussions, organise discovery findings, analyse requirements and consolidate technical research. Within delivery sprints, it can support analysis, development, testing, troubleshooting and documentation. During service transition, it can help convert project knowledge into technical, functional and operational guidance.
Initial work suggests that the greatest opportunity lies in sprint delivery, where Copilot, Power Apps, and Power Automate could reduce repetitive effort throughout iterative development. Design, planning, and service transition also offer opportunities to improve consistency and reduce administrative effort.
Crimson has established initial internal delivery-efficiency ambitions of 10% for mobilisation, 20% for design and planning, up to 35% for sprint delivery and 20% for service transition. These are targets to test and validate, not realised savings. No target has yet been established for deployment activities such as migrations and integrations, where the potential value and risk require further evaluation.
These ambitions should not be read as automatic reductions in project cost or like-for-like discounts. They target repetitive effort within defined delivery activities, with the aim of improving consistency and releasing capacity. Client value may emerge through faster mobilisation, stronger documentation and testing, reduced rework, improved governance, better knowledge transfer and service transition, and lower delivery risk. Once efficiencies are measurable, repeatable and proven, they can inform future delivery models and commercial approaches.
This distinction reflects Crimson’s measured approach. The business is not assuming that AI improves every activity equally. It is examining where the technology adds value, where further investment is required and where human oversight is especially important.
What Crimson has learned and brings to clients
Crimson’s internal transformation has shown that successful AI adoption is not achieved by allocating licences alone.
People need opportunities to experiment with real work. Different teams require use cases relevant to their roles. Leaders need to use the technology visibly. Employees also need sufficient subject knowledge to question the output, while organisations need to measure outcomes rather than activity alone.
These lessons now strengthen Crimson’s work with clients.
As Customer Zero, Crimson has experienced the challenges of moving from licences and experimentation towards embedded use. Its consultants understand that enthusiasm does not automatically create lasting change, that generic demonstrations rarely address the realities of a particular role and that governance must support responsible use while keeping people accountable.
Clients can draw on that experience for more practical guidance on AI strategy, Copilot adoption, governance, role-based use cases, change management and value measurement. The aim is not to replicate Crimson’s journey in every organisation, but to turn internal learning into approaches clients can adapt: identifying appropriate starting points, establishing realistic measures and avoiding common adoption barriers.
What comes next
Crimson’s next step is to redesign complete workflows, not simply accelerate individual tasks.
This includes extending role-specific use cases, developing capabilities around Copilot Studio and agents, connecting AI with intelligent automation, and measuring the impact on effort, quality, and consistency at specific points in the delivery lifecycle.
Like many consultancies, Crimson must balance working on its own business with delivering client projects. It plans to involve its new Transformation Engineer apprentices in internal AI projects, giving them opportunities to apply AI theory to real operational challenges while developing agents intended to improve Crimson’s efficiency. The aim is a shared benefit: practical learning for apprentices and additional capacity for internal transformation.
The next stage is also about turning tested approaches into repeatable methods, delivery playbooks and customer accelerators. As these are validated, they can help clients move beyond isolated use cases towards governed, scalable adoption, without having to start every workflow from scratch.
This aligns with Microsoft’s Frontier Partner direction: partners transforming their own organisations as Customer Zero, redesigning work around people, Copilot and agents, and building governance and measurement into adoption. Crimson is working towards that model, not claiming that its transformation is complete. Its focus is to turn continuing internal experimentation into practical guidance that helps clients adopt AI responsibly at scale.
A Microsoft partner that goes first
What differentiates Crimson is not access to Microsoft technology. It is the decision to use its own organisation as a proving ground.
Crimson has put Copilot into everyday use across leadership, consulting, technical delivery, sales, marketing and operations. It has gathered feedback, examined activity, identified benefits and confronted limitations. It is now applying those lessons to its delivery model and the advice it brings to clients.
Crimson’s Customer Zero approach makes “goes first” a practical commitment, not simply a claim based on selling or implementing Microsoft technology. By transforming its own ways of working and bringing those lessons to clients, it is working towards Microsoft’s Frontier Partner direction and grounding its advice in experience rather than theory.
Crimson goes first so its clients can move forward with greater confidence, more practical insight and a clearer understanding of how to manage AI risk.
Copilot readiness
Is your organisation ready for Copilot?
Our Microsoft Copilot Readiness Assessment reviews your licensing, permissions, data governance and security, then gives you a practical plan for a controlled rollout.
No obligation | Tailored to your Microsoft 365 environment