Enterprise learning · IT services and consulting

Prepare your delivery teams to design and deliver AI agents for clients.

Live, project-based learning with Sunil Mathew for engineers, architects and delivery leaders who will scope, build and review agentic systems on client work.

Clients are asking for AI agents

Winning that work, and delivering it without surprises, needs people who can scope what an agent should do, explain the risks to a client in plain terms and build a system that keeps working after handover.

An awareness session or a tool tour doesn't give a delivery team that judgment. Building, testing and reviewing a working system does.

An example the group works through

Illustrative. A client wants an agent that drafts and sends supplier emails. The group scopes it the way a delivery team would: what the agent may send without review, what evidence it needs, how failures are handled and what the client signs off.

Then the group builds that boundary and tests it, so the architect can defend the scope and the engineers can show it holds.

You can start from an industry example. Confidential material is not needed for a first conversation; company-specific work, data access and any agreements are scoped separately. No client material is needed.

Who takes part

  1. Engineers

    build and test the workflow, including failure handling and cost.

  2. Architects and solution or pre-sales leads

    scope client work, set the agent's boundaries and explain the trade-offs.

  3. Delivery and engineering managers

    review designs before they reach a client and decide who owns sign-off.

Sunil Mathew

Led by Sunil Mathew

Sunil has 26 years of engineering experience, including past leadership roles at Google, Amazon and Walmart Labs. He has hired, developed and assessed senior technical professionals, and today builds agentic-AI products alongside consulting and teaching.

He builds agentic-AI products today, so the practice reflects how these systems behave once real users depend on them.

More about Sunil

How a programme is agreed

A group normally has 8–10 participants, so everyone builds, tests and takes part in the review.

  1. Tell us about the group, its current work and the capability you want to develop.
  2. Discuss technical starting points, suitable practice and the learning scope with Sunil.
  3. Agree live hours, independent work, group size, schedule and fee in a separate proposal.

Each group stays at 8–10 so the format remains live and hands-on. Larger programmes run as repeated groups, agreed in the proposal.

Funding one person instead? Compare the individual Agentic AI programmes. An employer can sponsor a place.

Not sure it's training you need?

If one client architecture needs an independent review now, see bounded advisory.

Other organisations: Product companies · Global capability centres · All enterprise learning

Discuss your delivery teams

Tell us about the teams, the client work you expect and what they need to handle better.

Sunil reads every request and replies within 2 working days to discuss your group, learning goals and availability. A request does not confirm a programme or quotation.

Prefer email? Write about enterprise learning.