Digital transformation · Kuala Lumpur

Most AI projects don't fail on the technology.They fail on the questions nobody asked first.

Business analysis, process re-engineering and change management for organisations modernising how they operate. Diagnosis before deployment. Evidence before spend.

Start a conversation See the services

Who you'd be working with

Muhammad Danial bin Kamal

Kuala Lumpur · 2026

I'd rather tell you not to build it.

Most of the transformation work I've been called into started the same way: the technology was already chosen, and nobody could say what problem it was for.

I spent two years on the other side of that — mapping how an operation actually runs rather than how the org chart says it does, and writing down what "working" would look like before anyone signed a licence. It is a slower first month than most consultants promise.

It also means that when I do recommend building something, there's a reason on paper — and when I don't, you've saved a year finding that out.

Muhammad Danial bin KamalFounder · Lead Digital Transformation Consultant

The number worth planning around

40%

of agentic AI projects will be cancelled by the end of 2027.

01

Escalating cost

Spend that grows past the case that justified it, because the case was never sized properly.

02

Unclear business value

Nobody wrote down what "working" would look like, so nobody can prove it did.

03

Inadequate risk controls

No named owner for the decisions the system makes when it makes them badly.

~130 of the thousands of vendors now describing themselves as "agentic", Gartner judges roughly this many to be legitimate.
Claiming it
Legitimate

Gartner, "Over 40% of Agentic AI Projects Will Be Canceled by End of 2027" (25 June 2025). Ratio bars are schematic — Gartner states "thousands" without a fixed denominator.

What that actually says

None of those three failure modes are engineering problems.

Cost, value and control are business-analysis problems. They are decided long before anything gets built — in how the process was mapped, how the case was written, and who agreed to own the outcome. That is the work here, and it runs in a deliberate order because the fast version is precisely how projects join the 40%.

Phase 01

Discovery

Stakeholder, process and requirements analysis. A digital maturity assessment scored across 25 factors and 5 domains.

↳ Establishes the baseline

Phase 02

Strategy

The case in writing: objectives, budget, sequencing, and the decision the system is actually meant to make.

↳ Answers cost & value

Phase 03

Pilot

A bounded test with defined success criteria, before procurement commits anyone to a vendor or a platform.

↳ Answers risk controls

Phase 04

Deployment

Rollout with training, adoption tracking and knowledge transfer, so the capability stays after the engagement ends.

↳ Answers adoption

Services

Four disciplines, assembled around one problem at a time.

Engagements are built per client rather than sold as a package — the mix below is chosen against what the diagnosis actually finds.

01

Business Analysis

Understanding the operation as it genuinely runs, not as the org chart describes it.

  • Stakeholder analysis — who decides, who is affected, who is missing
  • Process analysis — BPMN for human-readable maps, BPMN 2.0 for technical execution
  • Requirements analysis and design definition
  • Digital maturity assessment — 25 factors across 5 domains, scored, evidenced and benchmarked
02

Strategic Consulting

Turning executive intent into a sequence someone can actually be held to.

  • Stakeholder strategy — alignment before commitment
  • Project strategy — scope, phasing and delivery structure
  • Risk strategy — named ownership for what the system decides
  • Framework development built on a client-by-client basis
03

Market Intelligence & Strategy

The outside view — what the market and the regulator do to the plan.

  • Documentation and reporting for boards and investors
  • Analytics dashboards — Power BI, Tableau, Excel
  • Market and competitive analysis with positioning matrices
  • Regulatory impact analysis against live compliance deadlines
04

Change Management & Process Adoption

The half that decides whether any of the above survives contact with the organisation.

  • Corporate training, workshops and info sessions
  • Roadmap design — phased delivery plans with owners and dates
  • Quality assurance and requirements gathering
  • Stakeholder reporting and knowledge transfer

Operating philosophy

Five commitments every engagement is held to.

Method is what gets done. This is how it gets done — and what a client is entitled to hold me to when it isn't.

Clarity

Make the current state legible before proposing a future one. Mapped processes, named owners, and a written definition of what "working" means — agreed before anything gets built, not reverse-engineered afterwards to fit the result.

Communicate

The same finding, in the form each audience can act on. Executives get the decision, operators get the change to their working day, technical leads get the specification. Most transformation stalls in translation rather than in execution.

Competent

Recommend only what can be delivered and then maintained. Where a capability doesn't exist internally yet, it is named as a dependency and planned for — not assumed away, and not quietly left for the client to discover at deployment.

Confident

Decisions made on evidence rather than momentum. A scored maturity baseline means the case for change can be defended to a board — or abandoned early and cheaply, which is a legitimate outcome and a far better one than discovering it in year two.

Consistent

The improvement has to outlast the engagement. Documentation, training and knowledge transfer are built into delivery rather than offered afterwards as an extra, so the capability stays with the organisation when I leave.

Recent analysis

The concentration you hold is larger than the allocation you chose.

A short read of what the 2026 market data says about AI concentration — and why exposure is now a governance question rather than an investment opinion. Eighteen seconds.

Contact

Bring me the process you're least confident about.

Diagnosis first. If there isn't a case worth building, that is a finding too — and a cheaper one than the alternative.

muhammaddanialkamal49@gmail.com @pers_pect_hub LinkedIn

Muhammad Danial bin Kamal
Lead Digital Transformation Consultant
MBusIT, RMIT Melbourne · CDTP (AI-Driven Digital Transformation) · HRDC Train-the-Trainer