METHOD

We draw the plan before anyone touches a wall.

Six phases, every engagement. You always know which one you're in and what you get at the end of it.

01

GROUND — Understand the business before the technology

Five to eight interviews across leadership, management and the people actually doing the work. We inventory your systems, capture your constraints — regulatory, contractual, political — and find what's already being done with AI unofficially. There is always something.

You receive: interview findings, systems inventory, constraint register, agreed success criteria.

Gate: We can state your core bottleneck in one sentence, and you agree with the sentence.

02

REVEAL — Draw what actually happens

Not what the SOP says happens. Three to five core workflows, including handoffs, decision points and the exceptions nobody documents. Every step gets a time and a cost.

You receive: process maps, time-and-cost table per process, exception register, draft SOPs.

Gate: Every mapped process has a number attached — hours per week, or ringgit per month.

03

OPTIONS — Generate every intervention, then score them

For each bottleneck, at least five routes: eliminate the step, buy off the shelf, automate without AI, automate with it, or build the application if nothing fits. Each scored on impact, effort, risk, data sensitivity and durability.

You receive: scored opportunity register, build-versus-buy analysis, and an explicit list of things not to do.

Gate: The options include at least one "eliminate" and one "buy". If neither appears, we haven’t looked hard enough.

04

NUMBERS — Model the return honestly

Built from your figures, not ours. We assume only sixty to seventy percent of theoretical time saving is realised, because that's what happens. Running costs included, and we show you the case if only half the benefit materialises.

You receive: ROI model, payback analysis, sensitivity table, prioritised roadmap.

Gate: You accept the numbers as your own.

05

KNIT — Build it properly

In your accounts, under your credentials. Guardrails before features: input validation, an explicit failure path, a fallback, spend limits, and human approval on anything that leaves the building. Something visible works in week one.

You receive: working system, technical documentation, runbook, test results, monitoring.

Gate: Five consecutive working days on real volume, including two exception cases, with no intervention from us.

06

DEVOLVE — Make ourselves unnecessary

A recorded walkthrough, a plain-language runbook, a named owner inside your organisation, and a thirty-day support window. We measure results at thirty days — and at ninety, we re-score the process against what has become possible since we built it.

You receive: runbook, recorded handover, credentials transfer, measurement plan.

Gate: Your named owner handles a live exception without calling us.

What we won't do

Recommend AI where a RM200 subscription would work better, or where the right answer is to delete the step. This happens more often than you'd expect. Telling you costs us one project and earns a decade of referrals.