Take your team AI-first
I take software teams from "we tried Copilot" to an agentic workflow that runs on their own stack, with their own people and their legacy code. I've done it at a 52-person software company and at a 12-developer backend startup.
What I set up
- Agentic development pipelines. Agents write the code, and your leads own the process around them.
- Custom skills for your codebase. I build and test them for each stack, so agents follow your conventions.
- Team training. Hands-on help for developers, plus workshops for leads and the CTO.
- Legacy code included. The workflow has to run on the code you already have.
Discovery > pilot > ongoing
See where you stand
A short first stage with a fixed scope: I look at your codebase, your team and your bottlenecks.
- Codebase and workflow review
- Talks with developers and leads
- A staged plan you keep either way
Prove it on real work
A few sprints on a real slice of your product, measured by outcomes rather than hours.
- One agentic workflow, end to end
- Custom skills for your stack
- Hands-on help in the field
Make it stick
Roll it out across teams and keep it working after I step back.
- Rollout to more teams
- Tooling kept current
- Leads coached to run it themselves
What this looks like in practice
Teams that no longer write code by hand
I picked agentic workflows for the gamedev and full-stack teams, built and tested custom skills for each stack, and trained the leads to run them.
One AI-first workflow, end to end
Agents now write the code and manage the tickets. Everyone uses one workflow with quality controls, and the team had workshops to learn it.
To see how I build agent tooling, look at claude-plugins, my open-source Claude Code plugins. More client work is on the work page.
FAQ
Does it work on a legacy codebase?
Yes. I've done it on legacy code as well as greenfield projects, and I test the custom skills against your real stack and conventions before the team depends on them.
Do we have to commit to the whole engagement?
No. The first stage is a short discovery with a fixed scope, and the staged plan from it is yours whether or not we move on to the pilot.
What does my team keep when you step back?
Documented workflows your team owns, custom skills for your stack, and leads who know how to run an AI-first team without me.
Get in touch
Tell me what you're working on and what "better" would look like. I'll reply with whether I can help and how we'd start. The price depends on the scope, so we agree on it once we know what the work is.