You bought the AI tools. A few people use them. I'll get the rest of your organisation there.

AI adoption programme for engineering and product teams

Over eight live sessions, your people learn to do their own work with Claude Code, Anthropic's AI assistant for files and code. I run office hours between every session. Your organisation finishes with hackathon projects, a written way of working and a before-and-after comparison of each team.

Office hours with StephanThursday 14:00
Developer

Can I get it to update the Jira ticket and write the release note when my pull request merges?

Yes. Let's set that up in office hours.
Marketing lead

I run our email campaigns. Can Claude Code help me draft them and test which subject lines work?

Good one. Bring an example campaign on Thursday and we'll build it together.

Real kinds of questions from people in marketing, engineering, QA, product, delivery and operations.

Most organisations reach the same point. The licences are in place, a few enthusiasts are getting real value, and everyone else tried the tools twice and went back to the old way.

Nobody can say with confidence what the AI tools have changed, and the board is starting to ask.

Getting everyone else using the tools takes practice on real work, habits shared across roles, and someone to ask when the work gets awkward. Most training stops before that third part. My programme includes it, with office hours between every session.

How I work with your organisation

I stay with your whole organisation from the kick-off to the hackathon.

Everyone learns together

Developers, testers, product people, delivery leads, and the people in marketing and operations who were told AI would help them too all take the same sessions. The whole group works from one written way of working.

Office hours between every session

People bring their own constraints: the legacy system, the compliance question, the workflow nobody else has. We work through each constraint together.

A hackathon on real problems

At the end of the programme, teams take real problems from your backlog and build with what they've learned, with me alongside them.

More office hours if the outcomes fall short

If the outcomes we agreed aren't reached by the hackathon, I keep running office hours at no extra cost for up to 60 days.

What your organisation has after the programme

Every package includes the comparison, the projects and the written way of working. Internal champions come with the Several teams package only.

A before-and-after comparison of each team

Everyone answers the same questions before the first masterclass and again after the last session. The report shows how each team moved and keeps individual names private, and your organisation keeps the report.

Working projects built on real problems

Your own teams take real problems from your backlog into the hackathon and build working projects from start to finish.

A written way of working

By the hackathon, your teams have a written working agreement. The agreement says which problems AI is used on and where the limits are, what a person must review, what an automatic check covers, and what must never run without a person watching.

Internal champions, on the Several teams package

On the Several teams package, I train internal champions to carry the practice on after the programme ends. Champions are the people their colleagues ask first.

How the programme runs

The programme is a kick-off, eight masterclasses and a hackathon, with office hours between every masterclass.

Before the kick-off: everyone's AI tools are set up and I check where each person is starting from, so no live session time is lost.

  1. Kick-off
  2. Masterclass 1
  3. Office hours
  4. Masterclass 2
  5. Office hours
  6. Masterclass 3
  7. Office hours
  8. Masterclass 4
  9. Office hours
  10. Masterclass 5
  11. Office hours
  12. Masterclass 6
  13. Office hours
  14. Masterclass 7
  15. Office hours
  16. Masterclass 8
  17. Hackathon
Kick-off

Leaders and teams agree what good looks like, and cross-role teams are formed.

Eight masterclasses

Each masterclass runs for two hours and is applied to your real work, from requirements through to review.

Office hours

Office hours run between every masterclass. Each person can bring the problem only they have.

Hackathon

Your own teams build real projects from start to finish.

Also included: Everyone on my courses can join the AfroLabs AI Show & tell, on Monday afternoons from 15:00 to 16:00 SAST, where people from all over share their AI journeys. That access continues after the programme ends.

My track record and what your board will see

The three results below come from my work as an engineering leader with two clients. They measure software delivery and DevOps training, and they are separate from the results of this AI programme.

Software delivery cycle shortened by 75%

At Magna BC, I have been Fractional CTO since February 2021 and run an engineering department of five cross-functional teams.

Developer onboarding cut from three months to under three weeks

At Magna BC, an average developer used to take three months to start contributing. Getting an average developer contributing now takes under three weeks.

More than 200 employees trained

At ProLink Arabia, where I led engineering and DevOps as a consultant, I trained more than 200 employees in DevOps fundamentals.

What your board sees at the end of the programme

The board report shows how each team moved between the first survey and the last. The figures in this example are illustrative and do not come from a real client.

Team A's average confidence rating rose from 2.1 to 4.3 out of 5. Team A's correct answers on the scored questions rose from 48% to 91%.

Each measure is reported as a separate number, with no single total. The report shows team movement only and never names individuals.

What participants say about the programme

Who the programme is for

The programme is a good fit for organisations that already have AI tools.

The programme is for you if

  • Your organisation has AI tools and wants people across roles to use them well.
  • You can protect a few hours a week for practice on real work.
  • You want something you can point to when the board asks what changed.

Look for something else if

  • You want a one-hour webinar on prompting tips.
  • You want a watch-the-videos course people do on their own.
  • You want to learn Claude Code yourself first, as one business leader. The AI Bootcamp for Business Leaders is my evening programme for that.

Programme sizes and prices

A fixed fee, agreed once we've scoped your programme.

Show prices in
Most chosen

One team

from $13 000 ex-VAT

One cross-role team of 3 to 15 people takes the full programme, with office hours and the hackathon included.

Several teams

from $35 000 ex-VAT

Groups of up to 15 people start at staggered times and share one written way of working. I train internal champions to carry the practice on.

Organisation-wide

Let's scope it

The programme is tailored to your setup, data rules and governance, and includes a kick-off for your leadership team.

AI tool licences are billed separately. The prices above are indicative bands, and the final figure depends on team size and how much we tailor the programme.

Stephan Swart

Who runs the programme

I'm Stephan Swart, and I'm the person your teams will work with.

I've led software teams and architecture for years, and run Leadership Nomad since 2011. For the last five years I've been putting AI-assisted ways of working into real client work. I run every session, every office hour and the hackathon myself, so you always know who you're talking to.

If the outcomes we agreed aren't reached by the hackathon, I keep running office hours at no extra cost for up to 60 days.

More about me Connect on LinkedIn

Questions about the programme

Is this programme only for developers?

No. Developers, QA, product, delivery, marketing and operations all join, because a new way of working only lasts when the people around the developers work the same way.

We use Copilot or another tool. Is this for us?

The programme can still work for your organisation. The sessions use Claude Code, so each participant needs a Claude subscription. The working practices carry over to Copilot and other AI tools, including how to brief an AI tool, check its output and set limits on what it can do.

Is it safe to use Claude Code on our organisation's data?

Claude Code is as safe as the access you give it, so the sessions set that access up deliberately. Claude Code runs on each person's own machine and works only on the files that person points it at. What Claude Code reads is sent to Anthropic to be processed, so I cover what should never go near the tool and what each subscription tier does with your data. Your organisation decides what people bring to a session, and the Organisation-wide package is tailored to your data rules and governance.

How do you measure AI adoption in software teams, and what can I show my board?

I ask everyone the same questions before the first masterclass and again after the last session, so you can show your board how each team moved. The report gives team-level numbers and keeps individual names private. The hackathon adds evidence a board understands: working projects, built by your own teams on your own problems.

Will the new way of working stick after you leave?

Office hours are where people fix problems while the new habits form, and on the Several teams package I also train internal champions to carry the practice on. By the hackathon, your own people are answering each other's questions and the way of working is written down.

Our people aren't technical. Will they keep up?

Yes. The sessions are built for mixed groups, and office hours are where anyone can bring the question they didn't want to ask in front of the group.

How do we get people using the AI tools after buying the licences?

People start using the tools when they practise on their own work, with someone to ask when it goes wrong. Every masterclass is applied to a real task from your teams, and the office hours between sessions catch the people who got stuck, which is where most rollouts quietly stall.

How long does it take to roll AI out across an engineering organisation?

The programme is a kick-off, eight weekly masterclasses with office hours between each, and a hackathon, which takes about ten weeks if it runs weekly. We agree the spacing around your calendar before the kick-off. By the hackathon, your teams are building real projects from start to finish and the way of working is written down.

Talk me through where your organisation is with AI.

Tell me what you've bought, what's happening, and what the board is asking. I'll tell you plainly whether this programme fits, or what would fit better.

  • A short call, no obligation
  • I look at where your organisation is today
  • You get a straight answer on fit

A short call, no obligation. I'll never share your email.