Built from your codebase, not from a template.
A hands-on AI engineering programme for software teams, delivered on-site in small cohorts. Participants work on code they recognise as their own, which is why the habits survive contact with real sprints.
Teams finish with working, AI-assisted code they built themselves, not a certificate.
Licences already bought. No shared practice around them.
Software developers and QA engineers on teams that have AI tooling in place but no agreed way of working with it.
Adoption is uneven: a few developers are far ahead and the rest have barely started.
Senior engineers are sceptical, and their scepticism is mostly well founded.
Output quality is inconsistent, and nobody agrees on what good looks like yet.
The exercises are written after we read your code.
Every engagement starts with discovery. Nothing is delivered from a shelf.
Stack, tooling configuration, and what leadership needs the team to be able to do afterwards.
Participants describe where the friction actually is, in their own words. Anonymity is what makes the answers usable.
A read of the team’s real patterns and conventions. Exercises get built from this, not from a template.
Scoped to the team, not to a calendar.
Length follows what the team needs. The curriculum below is shared across all three.
Discovery and assessment
The pre-engagement work, sold on its own. Useful when you want to know where the team stands before committing to anything longer.
Team programme
On-site, hands-on, small cohorts of developers and QA engineers working through the full curriculum against your own code.
Individual coaching
One developer at a time, on their own tickets. Fits either side of a team programme, or on its own for a specific gap.
Three areas, taught against your stack.
Depth and pace vary by format. The shape does not.
capstone build · full UI, API and database application, built by the teams · included in longer engagements
Four things, all of them yours.
Built by the team during the engagement, running against your own stack.
Shared, reusable, and owned by the team after everyone goes home.
Agreed up front so impact can be assessed against something real later.
Review expectations and conventions for AI-assisted work, written down.
Worth saying plainly.
Nobody leaves with a certificate. They leave with code they wrote and standards they agreed to.
We work with the licences you already hold and configure them properly. Nothing here depends on buying more.
Anyone quoting one before reading your codebase is guessing. The baseline is established during the engagement so you can judge for yourself.