Consulting

Advice that holds up in production.

Consulting at Trinio is senior, written down, and biased toward what actually runs. Identity is a deep specialty — IAM and IGA — not the whole practice. I also advise on software delivery, and on AI: using it in development, shipping it in products, and deciding where it belongs in an organisation.

Where I help

From target state to the messy middle.

Strategy

Programme operating model

What to own, what to buy, how work actually runs, and how governance stops being theatre. Practical target states, not vendor brochures — identity programmes included, not assumed.

Delivery

Programme and solution leadership

Standing up teams, shaping backlogs, reviewing designs, and keeping implementations honest against the architecture they were sold on.

Identity

IAM & IGA

Directories, lifecycle, federation, privileged access, access reviews, Saviynt and the Microsoft identity stack. Joiner-mover-leaver that operations can run.

AI · build

AI in development

Using AI as a tool in the engineering process, and shipping it in products — on-device and cloud — with the same privacy and production bias as the rest of the practice. TrAIner is one working example.

AI · advise

AI in the organisation

Where generative and applied AI belong in the estate, what not to buy this year, data and identity implications, and how to keep a proof-of-concept from becoming a second enterprise.

Scale

Enterprise programmes

From compact deliveries to global platforms spanning many connected systems. Microsoft estates, identity platforms, and the join between applications and operations.

How an engagement usually looks

Short, senior, and written down. Typical starting points: a current-state and target-state architecture, a programme health check, an AI options paper, a vendor-neutral identity review, or a design authority role alongside your delivery partner.

  • Discovery that talks to the people who run the thing — operations, security, product, engineering — not only the slide owners
  • Architecture views you can implement: capabilities, integrations, risks, and the identity or AI domain when it is in play
  • Clear recommendations on build vs buy, sequencing, and what not to do this year
  • Optional follow-on: design authority, team coaching, or delivery leadership

Contact me

Describe the problem, not the tool.

A paragraph on the organisation, the pain, and the constraint is enough to start. Identity, AI, delivery, or the join between them — no procurement theatre required for a first conversation.

Related

Architecture

Consulting sits next to software and enterprise architecture. If you need capability maps, target states, or application architecture, see the architecture practice.