Becoming your clients' AI lead
Your clients want AI. Learn to lead the topic, not just code with it.
3-day training for tech freelancers: scale a development process with agents, bring a client's teams on board, and package all of it into a recurring offer.
The symptom
"We want to do AI, we don't know where to start."
It's the sentence a leader says to you one day, often at the end of a meeting, because you're the technical person closest to them.
You already use these tools every day for your own work. Answering that question takes something else: choosing the tools for a whole team, putting practices in place that hold, bringing on board people who never asked for any of it and measuring what it produces.
That's an engagement in its own right, and it gets billed as one.
Today it goes to consultancies and to profiles who know how to name it, while the work itself is very close to what you already do.
The cost of inaction
What it's actually costing you
You stay on development work.
The AI budgets already exist at your clients, and they go to whoever can present a properly built offer.
Your own use of AI stays invisible.
You save time on your own engagements, without it changing anything about what you bill.
You have no answer for the leader asking where to start.
Naming tools isn't enough: they expect a trajectory, a cost, an order for the steps and someone to hold the topic over time.
At your client, every team moves on its own.
AI is already used there individually, with no shared framework, no sharing of practices and nobody to arbitrate.
The window closes.
Once a client has handed the AI topic to someone else, it's gone.
What changes
What you gain
An offer you can sell.
A fractional Lead AI or Chief AI Officer role, with a scope, an engagement rhythm and a price.
A clear view of what exists.
The tools, the ways of assembling them and the practices that hold up today for developing with agents.
A path to scaling.
How a team moves from individual use to a properly tooled development chain, in stages and without stopping delivery.
What you need to bring non-technical teams on board.
Use cases by department, meeting formats that circulate practices and a way of handling resistance.
A rare positioning.
Few tech freelancers can hold both ends: the technical industrialization and the adoption by the teams.
Profile
Who it's for
Developers, tech leads, technical consultants or CTOs.
You will recognize yourself if:
- Your clients talk to you about AI without knowing where to start.
- You use agents for yourself, and you cannot yet roll them out across a team.
- People ask you which tools to choose and you answer case by case.
- Data and confidentiality questions stop projects before they start.
- You see AI engagements go by that you do not know how to price.
You need real software development experience and regular use of AI tools in your own work.
This isn't for you if
you're looking for prompt engineering training or a course on training models. Here, we work on the offer: what you set up at a client, how you bring them on board and how you sell it.
The method
The main steps
What the Lead AI and CAIO roles actually cover
Who buys this kind of engagement today, for what needs and at what level of maturity. We look at real engagements, their scope and their duration.
The outcome: a role you can describe and delimit in front of a client.
The tools and practices that exist today
What exists today for developing with agents: the tools, the ways of assembling them and the practices that hold up in a team.
The outcome: tooling choices you can justify by the need and the cost.
Scaling a development process
How a team moves from scattered individual use to a tooled chain: where to start, what to automate first, what stays human and how to sequence it over several months.
The outcome: a development process that holds at the scale of a team.
The guardrails
Review, quality, security, code ownership and costs. What has to be written down, what has to be measured and what never leaves the company.
The outcome: a framework on data and risk the leader can present.
Bringing teams on board, beyond tech
The rituals and cross-department meetings that circulate practices, the use cases by department, how to lean on early adopters and how to handle resistance without forcing it.
The outcome: developers who use the tools without you.
Building and selling the offer
Scope, engagement rhythm, deliverables, price and renewal terms. We also work on the first conversation with a leader on the topic.
The outcome: an AI offer with a scope, a rhythm and a price.
Deliverables
What you leave with
Pricing
Format and pricing
3 days
€2,700 excl. VAT
The full journey: the roles and their market, the existing tools and practices, scaling development, the guardrails, bringing teams on board and building the offer.
The price shown is per person. For any group or in-house training, please contact us.
Frequently asked questions
Questions we get asked
Become the person your clients call about AI
Steer the subject end to end, and turn it into an offer in its own right.