
Shashank
Head of Technical Delivery
Looks after architecture, applied AI, engineering quality and what is allowed to go live.
The Team
Years running programmes, vendors and live systems. The people below own the work. Others join when the brief needs them.

Head of Technical Delivery
Looks after architecture, applied AI, engineering quality and what is allowed to go live.

Managing Director · Business Head
Looks after the client relationship, the partner network, and the rooms where work is won and renewed.

Business Head
Looks after how we engage: standing teams, time and materials, and short sprints. Turns the work into a contract procurement can sign.

Delivery and VP, Business Development
Looks after whether the work lands. Scope, programme management, and the weekly rhythm across offices and teams.
The wider team
People in science, data, product and delivery join when the brief needs them.
How we engage
A standing team when the roadmap is clear. Hours when the edges are still moving. A short sprint when you need to see something live. Reserved capacity when you need people without standing up a full team.
The team starts in your tools. First useful work in week two. AI tools are how they move, not a workshop on the calendar.
The same lead owns the code and the quality bar. No pilot left sitting on its own. No model you cannot turn off.
You are not standing up a hiring machine and a separate AI lab. One team. Offices and people already running.
A standing team in your Slack, Jira and stand-ups. We hold the week. You keep the IP.
Senior people on a live backlog. Scope can move. You pay for the work that is done. A lead holds the week together.
Reserved hours each week or month. Useful for overflow work, production support, or one named expert.
A fixed window and a defined piece of work that can go live. Used when the question is “does this work,” not “do we need another workshop.”
A core team plus extra hours. Or a sprint that grows into a standing team. The contract can change as the work settles.
Week one is access and a clear picture. Week two is useful work. After that the team stays in your tools. You keep the product.