Where is your team getting stuck with agentic AI?

A pilot can handle the cases in a demo and still leave a sponsor with an unanswered question. What happens when the evidence is incomplete, a tool fails or an agent takes the same action twice?

Bring Sunil Mathew the decision your team is facing. The conversation can lead to private learning, consulting or a review followed by team practice.

Three objects on one review table: a woven operating frame, an inspection lens on a stand, and a small knot of gold and green thread. One for each way of working together.
  1. Build a capability across the team

    Choose a workflow and the people who make decisions about it. Participants practise designing evaluations, setting boundaries on actions and reviewing failures. An L&D lead and an engineering sponsor can use the team programme guide to agree an outcome before discussing dates.

  2. Get an independent view of a pilot

    Approach Sunil directly for a readiness assessment, a bounded architecture decision or ongoing advice. See an illustrative pilot review or compare consulting options.

  3. Review first, then teach

    A review might identify missing escalation tests. A learning engagement can then give engineers practice writing, running and interpreting those tests. You can scope each piece separately.

Which route fits

RouteWhen it fitsWhat you receiveStart here
Private team learningEngineers need practice making agent design, evaluation and review decisions themselvesA team that has built, tested and reviewed one workflow togetherEnterprise learning
ConsultingA sponsor needs an independent view of one pilot or decisionA review of the evidence and a recommendationConsulting
Review, then teachA review finds a gap the team should learn to closeThe review first, then practice on what it found, scoped separatelyScoping form

No fee or duration is published for organisation work. Both are set in a written proposal after the scoping call.

Sunil Mathew

Who you work with

You work with Sunil Mathew directly. He has 26 years of engineering experience, with past roles at Google, Amazon and Walmart Labs. He has led engineering teams, and hired, developed and assessed senior engineers. His current work is agentic-AI products, advice to organisations and teaching experienced engineers.

He brings the engineering consequences into each discussion: what a team can build, what evidence is missing and what it would take to operate the result. Read his background

How scoping works

  1. Send the scoping form

    A short description is enough. Keep confidential material out of it.

  2. Sunil replies within 2 working days

    He reads every request.

  3. Agree the scope on a call

    You agree the people involved, the workflow or pilot, the evidence you can share and the timeline.

  4. Receive a written proposal

    It sets the scope, the fee and the delivery arrangements. Invoicing follows your purchase-order process. The payment schedule is set in the written proposal.

Sending the form does not commit you to anything. Sunil will sign your mutual NDA before you share confidential material. Until then, a description or a reference example is enough. Open the scoping form

What will the scoping conversation cover?

Bring the sponsor’s decision, the people involved, the evidence you can share and your timeline. A sandbox example can stand in for sensitive material. Fees and deliverables depend on the work you agree. You can request consulting even if you have no training requirement.

Discuss your organisation’s needs