New Service

Claude Code Enablement for Engineering Teams

Get your engineers actually using Claude Code — on your codebase, not a demo repo — and make the adoption stick after I leave.

Most teams turn Claude Code on, watch a slick demo, and plateau at a handful of power users while everyone else drifts back to old habits. The problem is never the tool. It's that nobody translated it into your stack, your repos, and your review culture — and nobody built the internal muscle to keep it going.

I do both.

How It Works Book a Readiness Assessment

Why This Works When Generic AI Training Doesn't

Generic training produces awareness. It doesn't produce adoption. The difference comes down to three things I build into every engagement:

🧑‍💻

Taught on Your Codebase, Not Slides

We work in your actual repositories. CLAUDE.md configured for your project conventions, custom skills and slash commands for your real workflows, MCP wired into your internal tools. Engineers leave having done real work, not toy exercises.

🛡️

Guardrails First, So Engineers Can Move Fast

What stalls most rollouts isn't capability — it's nervousness. I set up the permission model, hooks, and security guardrails before broad rollout, and embed Claude Code into your existing SDLC. Engineers get confidence to delegate; leadership gets control they can defend to security and the board.

🏆

Champions, Not Dependency

The goal is that adoption survives my exit. I identify and equip 2–4 internal champions who maintain the plugin and skill library, onboard new hires, and keep momentum after the engagement ends. You stop paying me; the capability stays.

How to Work With Me

Readiness Assessment

Half a day

The front door. I map your stack, repos, and highest-leverage workflows, run a live Claude Code session against your real code, and deliver a short report: where the fastest wins are, which teams to start with, what guardrails you need before you scale, and what "good" adoption looks like for you. You leave with a concrete plan whether or not we go further.

Team Enablement

1–3 days

Hands-on enablement for one or more engineering teams, on your codebase. Security guardrails and permission model set up first, then CLAUDE.md hierarchy, subagents, skills, hooks, and custom commands — tailored to your tools. Every engineer leaves shipping real work with Claude Code, inside boundaries your security team has signed off on.

Adoption & Champions

Ongoing

Light-touch retainer. I equip your internal champions, review adoption, and keep the plugin and skill library evolving. Priced on outcomes — sustained active usage — not workshop hours.

Most teams start with the Readiness Assessment and use it to scope Team Enablement.

What You Get

A Claude Code setup configured for your codebase — CLAUDE.md, skills, commands, MCP — not generic defaults
Security guardrails and a permission model your security team has signed off on — before broad rollout, not after an incident
Engineers who use it on real work, not just the early adopters
Internal champions equipped to sustain it
Adoption that doesn't plateau the moment the consultant leaves

Who I Am

Fractional CTO, 27+ years scaling product-engineering organisations (Culture Amp, SEEK, Rome2rio and Yahoo). I'm currently running a live Claude Code rollout across the engineering teams of an ASX-200 listed company — building the plugins, skills, agents, and security guardrails, and driving actual adoption across multiple teams and tech stacks.

I've done the same at smaller companies, where the constraint isn't governance — it's getting real adoption from a lean team without slowing delivery.

This isn't a methodology I read about. It's one I'm shipping right now, from scale-up to enterprise, this quarter.