Frameworks and credentials

Credentials held

AWS Certified Cloud Practitioner

Amazon Web Services: verifiable badge record

AWS Certified AI Practitioner (Early Adopter)

Amazon Web Services: verifiable badge record

FinOps Certified Professional

The Linux Foundation: verifiable badge record

FinOps Certified Instructor

The Linux Foundation: verifiable badge record

HRD Corp Accredited Trainer

Human Resource Development Corporation, Malaysia: verifiable trainer record, accredited 25 July 2024 to 25 July 2027

Certificate of Competence in Zero Trust (CCZT)

Cloud Security Alliance: badge record to be added

FinOps Certified Engineer

FinOps Foundation

PyTorch and Deep Learning for Decision Makers (LFS116)

Linux Foundation

Cybercrime Investigations

Maltego: subject area published by the vendor, not a record of completion

BBA (Hons) International Business

Universiti Teknologi MARA

Diploma in Banking

Universiti Teknologi MARA

Institutional standing

What an engagement looks like

Framing

Duration is not fixed. One conversation before any scope is written, to establish what has already moved, what decision is waiting on it, and whether this is the right practice for the question at all. Part of that conversation is about the organisation rather than the estate: who would have to concede something for the likely recommendation to proceed, and whether that is currently a safe thing for them to do. A recommendation nobody can act on is a more common outcome than a wrong one.

What you receive: A written statement of the question as he understands it, which is often the first time it has been written down in one place. Where the honest answer is that someone else is better placed, that is said rather than worked around.

Assessment

Two to four weeks. Establishing what has actually changed, what is now exposed, and what can be measured. Risk engagements open here rather than with an implementation plan, because an implementation plan written before this stage is a guess with a timeline attached.

What you receive: A written assessment: the findings, the evidence for each one, and an explicit list of what could not be established in the time. That last list is the part most often left out, and it is the part that tells a board how much weight the rest will bear. Where an assessment returns a suspiciously short list of problems, that is reported as a finding about reporting rather than as a clean result.

Architecture and decision support

Duration is not fixed. Turning the assessment into something a board or an engineering team can act on: the options, what each will cost beyond the licence, and which parts should be decided rather than delegated.

What you receive: Written architecture or a decision paper, in the register the audience actually reads. The doctrine documents on this site are published specimens of that writing, so the standard can be judged before it is commissioned.

Handover

Duration is not fixed. Implementation and managed service are not undertaken here, so the work ends with material a client’s own team or supplier can execute against, rather than with a dependency on the person who wrote it.

What you receive: The documents, the reasoning behind them, and a named list of the assumptions that would have to be revisited if the situation changes. An engagement that cannot say what would falsify its own conclusions has not finished.

Shape set out 2026-08-09. The assessment duration above is the same figure published on the advisory enquiry page, not a second estimate.

Not taken on