For delivery teams · Enterprise AI

Available now for new programmes

Your AI programme has a strategy. Now it needs someone who can make it work.

Architect, engineer and technical project manager in one senior person. 20+ years building the ERP, warehouse, EDI, CRM and data systems that AI now has to plug into. AWS, Azure or your own stack. Honest about what you need, including the people I'm not.

Overview

How a real AI solution fits together, in one video.

Coming soon. Until it's ready, the playbooks below show the same thing in writing.

Which of these is you?

Delivering AI

You've been asked to deliver AI

You understand the theory, maybe from a certificate course. You need to see what a real solution looks like on your systems, and who you need to build it.

→ Start with the playbooks

Have a partner

You already have a transformation partner

The strategy is agreed. Now it has to work with your core systems, and pass security and compliance.

→ How I work alongside your partner

Existing client

You already work with me

The board wants AI. I already know your systems, your data and your people, so adding AI is a continuation, not a new start.

→ How I'd approach it

Consultancy or SI

You're the transformation partner

You've won the programme and need a senior architect-engineer who can work on your client's AWS or Azure estate and legacy systems, under your governance.

→ How I work inside your team

Lead or support. Whichever your team needs.

Option A

Lead the architecture

When it fits
There's no architect yet, or the AI work is bigger than the current team can design.
What I do
Own the target architecture and the design decisions, set the standards, guide the engineers, and report to your programme board.
What success looks like
A design the team can build and run, with every decision recorded and nothing hidden.

“I'll take responsibility for the design, and make sure it works on your systems.”

Option B

Support your architect

When it fits
You already have an architect, internal or from a partner, who owns the design.
What I do
Work under their lead: take on the AI, integration or cloud parts, review designs, de-risk the hard pieces, and add senior hands-on capacity.
What success looks like
Your architect has more time, fewer unknowns, and a second senior opinion they trust. I don't quietly take over.

“Your architect stays in charge. I make their job easier and their design stronger.”

Six roles, one person

Where I fit on your team

Each one is a named gap in your RACI, not a parallel workstream.

Solutions architect / design authority

Owns the target architecture across AI, data, middleware and your systems of record, and signs off design decisions.

Technical project manager

Turns the programme plan into engineering work, runs technical risks and phase gates, and translates between the board and the engineers.

Integration and cloud engineer

Builds the hard, hands-on pieces: APIs, events, pipelines and infrastructure as code, on AWS, Azure or your own stack.

AI/ML engineer

Retrieval, agents, document AI and predictive models, tested and monitored on your own data.

Security and compliance lead

Threat modelling, DPIA support, AI-specific threats, UK GDPR and PCI DSS, from the first gate.

Independent technical assurance

A second pair of eyes on a partner's or vendor's design before you commit to it.

The playbook library

80 playbooks across 18 sectors, plus cross-functional and horizon playbooks

Worked examples: the business problem, the UK rules, the architecture on AWS, Azure or your own stack, the agents, the middleware, the delivery plan and the team. All 80 of the 80 planned playbooks are published.

Sector
Pattern
Platform
Every playbook shows AWS, Azure and a sovereign or on-prem option. On Google Cloud? The same patterns apply. Ask me.

80 playbooks

For students

Studying for an AI certificate?

Use these playbooks as worked examples. Each one has the business case, measures of success, risks and RACI your coursework asks for. I hold a Leadership with AI certificate myself, so I know what the courses cover, and where real projects differ.

From course to project →

Honest about scale

I'm one person, not a 200-person consultancy. Most AI programmes don't need 200 people. They need one senior person who understands the business, the systems and the technology, and who can tell the rest of the team what to build. Where the work needs more hands, I bring in people I trust, or work inside your partner's team.
FAQ

Questions people ask

Something not covered here? Ask me directly →

Are these real client projects?

No. Each playbook is an illustrative scenario with typical numbers, written to show how a real solution fits together. Where one draws on my own work, it links to the anonymised case study and says so.

Which cloud do you work on?

Whichever you already run. Every playbook shows the same design on AWS, on Azure, and on an open, portable stack you can run in your own data centre or with a UK or European provider. On Google Cloud? The same patterns apply. Ask me.

Do you lead, or work under our architect?

Either, and both are real offers. If there's no architect, I'll lead the design. If you already have one, internal or from a partner, I work under their lead and make their design stronger. We agree which on day one.

You're one person. What happens when the work needs more?

Most AI programmes need one senior person who can join up the business, the systems and the technology. Where the work needs more hands, I bring in people I trust, or work inside your partner's team.

Can I use the playbooks for my course or my own programme?

Yes. They're written as worked examples, with the business case, measures, risks, RACI and delivery plan your coursework or programme board will ask for. A link back is appreciated.

Talk through your AI programme.

What you're delivering, on which systems, and who's already on the team. I'll tell you honestly where I'd fit, and where you need someone else.

Sam Naseem
Sam NaseemBirmingham, UK · UK & Europe
Available now