Our story
How Permata Partners came to be.
"Permata — the Malay word for gem — captures what we look for in every engagement: something of lasting value, not a surface polish."
Founded
2016 · Shah Alam, Selangor
Focus
Engineering teams of 10–60, Malaysia
Deliverable
Written documents — always
Permata Partners was established in Shah Alam in 2016 by two engineers who had spent the previous decade watching software teams wrestle with the same avoidable friction: deployments that required an undocumented ritual, pipelines that only one person understood, release nights that stretched into early morning because no one had written down the rollback procedure.
The observation that troubled us was not that the problems were difficult. Most of them were not. What made them persistent was that no one had taken the time to sit quietly with the pipeline, name what they saw, and write it down in terms the team could return to. Consulting firms either arrived with a predetermined tooling recommendation or proposed a lengthy transformation programme. Neither answered the actual question: where, precisely, is this particular team right now, and what are the two or three things most worth changing first?
Our practice is small by intention. We keep a short client list so that we can give each engagement the attention it requires. We do not subcontract. When you engage Permata Partners, the people you meet at the outset are the people who will attend your sessions and write your documents.
The name reflects something we genuinely believe: that a thoughtful written account of where a team stands, and what it might do next, is a thing of lasting value — a document worth returning to as the team changes and grows.
Mission & values
What we are here to do.
Observation before opinion
We read what is actually present before we form a view. Advisory built on observation is more useful than advisory built on assumption.
Writing as a discipline
A slide deck invites agreement. A written document invites scrutiny. We write because we want clients to be able to challenge what we say.
Proportionate advice
Every recommendation is weighed against the team's actual capacity. We suggest what is worth doing given the conditions that exist, not what would be best in ideal circumstances.
Candour with clients
If an engagement is not the right fit, we say so before it begins. If the sessions reveal something different from what was described, we name that in the deliverable.
The people
Who you will be working with.
Permata Partners operates as a small team. There is no staffing bench — the people named here are the people who attend your sessions and write your documents.
Zulkifli Ibrahim
Principal Advisor
Fifteen years in software delivery across fintech and platform engineering in Malaysia. Zulkifli leads most pipeline advisory and maturity review engagements, and writes every final deliverable himself.
Nadia Rashid
Release & Operations Advisor
Nadia spent eight years in release engineering and SRE before joining Permata Partners. She leads release discipline workshops and brings particular focus to on-call and incident review practices.
Ariff Kamarudin
Pipeline & Infrastructure Advisor
Ariff brings a background in build infrastructure and cloud platform work, with particular experience in Kubernetes-based delivery systems. He supports pipeline advisory engagements and leads technical observation sessions.
Standards & practice
How we maintain the quality of our work.
Written scope before engagement
Every engagement begins with a brief written scope document. Both parties agree on what will be observed, what will be written, and when it will be delivered — before any sessions begin.
Evidence-grounded findings
Every finding is traceable to a specific observation from a session, a log, or a document the team shared. We do not write general industry statements dressed as findings about your team.
Confidentiality as standard
What we observe in your pipeline, repository, and team conversations does not leave the engagement. We do not use client details as case studies without explicit written permission.
One revision included
Every deliverable includes one round of written comments from the client team, addressed before the document is considered final.
PDPA-compliant handling
All personal data gathered during sessions is handled in accordance with Malaysia's Personal Data Protection Act 2010. We retain only what is needed for the engagement.
Continuous professional reading
Our advisors maintain an active reading practice in DevOps, site reliability, and software delivery. We work to stay current with how the field is actually evolving.
Our expertise
DevOps advisory grounded in Malaysian engineering practice.
Software delivery in Malaysia carries particular characteristics that a practice founded elsewhere will often miss. Teams here operate across a mix of on-premises infrastructure, hyperscaler cloud, and Government infrastructure platforms. Procurement timelines shape what tooling is available and when. Engineering talent is concentrated in the Klang Valley and Penang, with teams in other states facing different constraints.
Permata Partners has operated within this context since 2016. Our clients have included engineering teams in financial services, e-commerce, SaaS platforms, logistics, and government-linked companies. In each setting, the fundamental discipline has been the same: read carefully, write clearly, recommend proportionately.
The three engagements we offer were developed through years of practice, adjusted each time we found that a different framing made the deliverable more useful to the team receiving it. They are the forms that have, over time, produced the most consistently useful output for teams at the scale we serve.
Come and talk to us about your team's situation.
An initial conversation costs nothing. We will listen carefully, ask a few questions, and tell you honestly whether we think an engagement would be useful.
Open an enquiry