Who We Are
Cortex Bay
Cortex Bay started from a straightforward observation: a lot of AI work in Malaysian organisations stalls not because of technical difficulty, but because the initial question was poorly formed, the scope grew unchecked, or no one structured the process well enough for the team to learn from it. Pilots ran, but the results were too ambiguous to act on.
We set up Cortex Bay to address that specific gap. We are a facilitation practice, not an AI vendor. We do not build models, sell platforms, or push particular tools. What we do is help teams define a clear, answerable pilot question, run the experiment in a structured way, and then read the results honestly — so that the outcome, whether positive or negative, is actually useful.
Our approach draws on facilitation methodology, project management discipline, and a practical understanding of where AI pilots tend to go wrong. We work in English with teams across Malaysia, and our base in Bangsar South, Kuala Lumpur means we can meet in person with Klang Valley clients while serving teams further afield by video call.
The three services we offer — scoping, a guided sprint, and production advisory — are designed to be used in sequence or independently, depending on where a team is in its journey. Each engagement produces written artefacts that the team can use internally, share with leadership, or carry forward to any implementation partner they choose.
Our Mission
To help organisations in Malaysia run AI pilots that produce clear, documented, and actionable results — regardless of the team's level of AI experience.
Our Approach
Facilitation first. We structure the process so that teams make better decisions — about scope, methodology, and what to do with the results.
Our Position
Vendor-independent. We advise on process, not product. Our role ends before any implementation begins, which keeps our advice unbiased.
The Team
People Behind Cortex Bay
Amirul Hakim
Lead Facilitator
Amirul leads scoping sessions and pilot sprints, bringing a background in organisational process design and technology strategy to each engagement.
Sharmini Lau
Advisory Lead
Sharmini manages production advisory engagements, helping teams translate pilot findings into documented transition plans and well-reasoned decisions.
Rizwan Nasir
Documentation & Methods
Rizwan develops the structured frameworks and documentation standards that make Cortex Bay's outputs useful beyond the engagement itself.
How We Work
Standards We Hold Ourselves To
Defined Scope Before Work Begins
Every engagement starts with a written scope. We do not begin facilitation until the question, the team, and the success measures are documented and agreed.
Written Artefacts at Each Stage
Every session produces something the client can keep: a scoping brief, a risk list, a sprint plan, a results review, or a transition document. Nothing is purely verbal.
Vendor-Independent Stance
We have no commercial relationship with any AI platform or tool provider. Our advice reflects your team's situation, not a licensing arrangement.
Data Handling with Care
We handle client materials and documentation with discretion. Engagement outputs belong to the client; we retain no proprietary claim on your pilot findings.
Plain, Direct Communication
We avoid jargon in our facilitation and documentation. If something is not working in a pilot, we say so plainly rather than dressing up a weak result.
Continuous Method Refinement
We review our facilitation frameworks after each engagement and update them based on what worked and what needed adjustment in practice.
Our Expertise
Facilitation as a Discipline
AI pilot facilitation sits at the intersection of process design, organisational decision-making, and applied technology planning. It is not a technical discipline in the engineering sense — it is a structured practice for helping teams think clearly about what they want to test and how to know whether it worked.
In Malaysia, many organisations are at an early stage of AI exploration. They have seen case studies from elsewhere, they have ideas about where AI might help, and they have data — but they do not yet have a reliable internal process for turning those ideas into structured experiments. That is the gap Cortex Bay occupies.
Good facilitation brings a team to a shared understanding of the pilot's purpose, its scope limits, the data requirements, and the criteria for a useful result. It also surfaces the risks and constraints early — before they become blockers mid-sprint. A well-facilitated pilot is one where the team knows, at the outset, what they will do if the answer is yes and what they will do if the answer is no.
Our documentation standards reflect the same principle. Written artefacts — scoping briefs, sprint plans, results reviews, transition plans — are not bureaucracy for their own sake. They are the mechanism by which a team's learning becomes portable: transferable to leadership, to implementation partners, or to the next iteration of the pilot.
We value steady, documented progress over speed. A pilot that takes an extra week to scope properly is far more likely to produce a result worth acting on than one that rushes into execution with a vague question.
Work With Us
Want to work with a team that keeps the process honest?
Tell us what you are working on. We will take the time to understand your situation before suggesting where we can help.
Get in Touch