Customer story / Gully Cricket
Getting Gully Cricket's teambuilding with Claude.
The engagement started with mapping and an audit, brought leadership into alignment, and moved into workshops and team education. A hackathon marked the finish of Gully Cricket's Claude Code and Cowork rollout.
- 01 Map & audit
- 02 Align leadership
- 03 Educate & deploy
- 04 Close with a hackathon
01 / Mapping & audit
Start with the work.
Gully Cricket brought in Practical Intelligence to enable and deploy Claude Code and Cowork. We began by mapping the work and carrying out an audit, giving the rollout a starting point in the team's workflows.
The audit grounded the engagement in how Gully Cricket operated. It gave the leadership conversation a practical foundation: the team's work, its starting point, and where Claude could fit.
02 / Leadership alignment
Bring leadership into the plan.
We then worked with Gully Cricket's leadership to align on the engagement. Bringing the people setting direction into the rollout meant the team education that followed sat within a shared plan for adopting Claude.
03 / Workshops & education
Make room to learn by doing.
With leadership aligned, the engagement moved to the team. Practical Intelligence ran workshops and education sessions alongside the enablement and deployment of Claude Code and Cowork.
The aim was to make the tools familiar and useful: give people time to learn, ask questions, and build an understanding they could carry into their work. The programme then gave that learning a place to be applied.
Claude Code
AI assistance for software development, enabled and deployed for Gully Cricket.
Cowork
AI assistance for knowledge work, enabled and deployed alongside Claude Code.
04 / The closing hackathon
The finish was hands-on.
The engagement closed with a hackathon, giving Gully Cricket's team a dedicated occasion to put the workshop learning into practice. Building and experimentation with Claude became the final activity of the programme.
It provided a clear completion milestone: Claude Code and Cowork were enabled and deployed, leadership alignment was complete, and the education programme ended with the team getting hands-on.
Engineering impact
More tasks completed. More features shipped.
Engineering output across task completion, monthly features shipped, and time from starting a feature to releasing it.
+50%
Engineering tasks completed
60 → 90per month
More engineering work completed each month.
+75%
Features shipped
4 → 7per month
A higher monthly feature delivery cadence.
-30%
Feature delivery lead time
10 → 7days
Less time between starting and shipping a feature.