ENGAGEMENT · MODE 01 · ENABLEMENT
Make your engineers ten times more productive.
Most engineering teams have access to Claude Code, Cursor, and the same AI tools I use. Few of them ship at the speed I do. The gap is not talent: it is workflow discipline, prompt instincts, and a refusal to accept the old implementation tempo. I work directly with your team to close that gap.
A two-to-four week program that installs the workflow and proves it on your own tasks. The shape most relationships start with — compound from there.
Book a call◆ Who this is for
Engineering teams of 5 to 50 where senior leadership has noticed that AI tools are being used unevenly. CTOs and VPs of engineering who want this to become an organisational capability, not a personal one.
- ◆Your team has Claude Code or Cursor licenses but you cannot tell if they are paying off
- ◆You have watched one engineer ship in a day what others take a week to ship
- ◆You are hiring AI engineers and getting outbid; meanwhile your existing team could be the answer
- ◆You want AI literacy to be a baseline expectation, not a niche skill
◆ Where this sits in the relationship
This is usually how a relationship starts. The team is talented; the AI posture is not. A focused training engagement is low-risk for both sides and gives us real working knowledge of each other. If it works — and it usually does — the next shape tends to surface within a quarter. A pipeline that needs building. An architecture decision that needs ownership. The first engagement becomes the foundation for what comes next.
◆ What we'd do
Week one is diagnosis. I spend time with your engineers: pair sessions, code reviews, tool audits. I observe how they actually work and where the leverage is missing. Most of what I find is invisible to leadership: engineers prompt-engineering inside chat windows when they should be in Claude Code, building from scratch when they should be delegating, treating AI as autocomplete when it should be a peer.
Week two is where we install the workflow and measure the baseline. Hands-on sessions on session structure, design-first discipline, test-first as quality gate, multi-agent decomposition, and where these tools break — run against your stack, on a real task, with the clock on. That measurement becomes the number we hold ourselves to.
The final week is embedding. Habits either stick now or they do not, so I stay in the work: async reviews, unblocking the specific problems your engineers hit, and re-measuring the same kind of task we timed at the start. Each engineer leaves with a workflow they can actually use, not a deck they will forget.
◆ What happens in practice
One typical mid-complexity ticket — a non-trivial bug fix, with the docs and tests it should ship with. Here is what it looks like before the workflow and after, timed end to end.
Those are example numbers, not a promise. In week two we measure your team's actual baseline on a task like this, then re-measure the same kind of task at the end. The ROI you act on is your own data, not mine.
◆ What you get
Diagnostic report
A clear-eyed assessment of your team's current AI tooling posture, where the gaps are, and what to fix first.
Tailored workshop curriculum
Built around your stack, your product, and the specific patterns your team has missed.
Live workshops
Hands-on sessions with your engineers, remote or on-site. Not lecture. Pair work.
Documented workflows
Everything your team learns is codified. They own the workflows after I leave.
Your own ROI numbers
We time a baseline task at the start and re-measure it at the end. The before-and-after is your data — yours to take to your board.
30-day follow-up
Async reviews, check-ins, and unblocking through the month after — the window where habits stick. For most teams it becomes the on-ramp to Sustain.
◆ What this is not
This is not a generic AI for developers course. It is not a slide deck. It is not a webinar series. It is not a one-day session that disappears. If you want training as theatre, plenty of firms will sell you that. This is workflow installation, and it only works if your team actually does the work.
◆ Relevant work
The same workflow that built TraceLayer in 21 days is the workflow your team will be running.
Read the case study◆ What it costs
Price this against what your team costs, not against what I charge. A team of fifteen engineers runs well north of €1M a year in loaded salary. If the workflow returns each of them even one hour a day, the program pays for itself inside the first week — and keeps paying every week after. Against that number, the fees below are a rounding error.
Every engagement can open with the three-day pilot. Stop there and pay nothing if your team does not see the difference; continue, and the pilot fee credits toward your package. The risk is mine to carry — so I carry it.
Every program closes with a 30-day follow-up: async reviews, check-ins, unblocking, while the habits set. For most teams that month is where Sustain begins — the same support, made standing, plus monthly office hours, new-tool rollout, governance, and standards maintenance as the team grows.
Let's talk about this.