Client reviews
These accounts come from clients across fintech, e-commerce, SaaS, and government-linked sectors in Malaysia.
Hafizuddin Shahril
Engineering Lead · Fintech · Kuala Lumpur
"The maturity note gave us something we had not had before — a clear description of where we were and why. We had been running maturity assessments using checklists for a year, and they never felt quite right. This was different. Zulkifli read our pipeline and wrote about what he actually found, not what a framework expected to find."
April 2025 · DevOps Maturity Review
Razlina Che Mohd
VP Engineering · E-commerce · Shah Alam
"We brought in Permata Partners before a major re-platforming to understand where our deployment process stood. The advisory document was thorough and honestly a bit confronting — it named some things we had been quietly aware of but had not articulated. The backlog they produced is what we are working from now, three months on."
March 2025 · Delivery Pipeline Advisory
Tengku Norizan
CTO · SaaS Platform · Petaling Jaya
"We had spent two quarters trying to write release guidelines ourselves and had produced three drafts that no one followed. The workshop got us to a working agreement in two days. The difference was having someone in the room who had done this with other teams and could name the patterns causing the stalling."
April 2025 · Release Discipline Workshop
Khairunisa Aziz
Engineering Manager · Logistics · Selangor
"What I appreciated most was that they did not arrive with a solution already in mind. Ariff spent the first session just watching and asking questions. The recommendations in the maturity note were small, specific things — nothing that required a new tool or a budget request. We did three of the five within a month."
February 2025 · DevOps Maturity Review
Mohd Faizal Ramli
Platform Lead · GLC Technology · KL
"We are a government-linked company and the procurement took some navigation, but the team was patient with that and handled the purchase order process without issue. The maturity review itself was useful — it helped us make the case to leadership for the delivery improvements we had been wanting to pursue."
March 2025 · DevOps Maturity Review
Siew Wei Lin
Head of Engineering · Healthtech · Subang
"Nadia ran our release workshop and had clearly read everything we sent beforehand. The first morning felt almost like a retrospective — she had identified three tension points just from the retro documents. The working agreements we produced have actually stuck, which is not something I expected to say."
April 2025 · Release Discipline Workshop
Case studies
Details have been changed to protect confidentiality. The core patterns are accurate.
Challenge
Deployments to production ran fortnightly and required a four-hour window beginning at 11 pm on Fridays. The team had accepted this as normal. Three engineers were responsible for the ritual, and none had documented it. A fourth engineer had left three months earlier, taking undocumented knowledge with him.
Engagement
We mapped the entire pipeline over three weeks, attended one Friday deployment window, and interviewed six engineers individually. The advisory document identified eight friction points; five were addressable without new tooling. The backlog prioritised three changes that could realistically be completed in the following six weeks.
Outcome
The team moved to weekly deployments, running during business hours. The Friday window was retired. Deployment knowledge was documented and distributed across five engineers. The three changes from the backlog were completed; the team implemented two additional items on their own initiative.
Challenge
A new engineering manager had joined and wanted an independent view of the team's current delivery maturity before making any changes. The team was performing adequately, but deployment frequency was lower than she expected given the pipeline tooling in place.
Engagement
Two sessions over one week. The maturity note placed the team at a mid-pipeline maturity stage, with strong build and test practices but weak deployment observability and post-deploy validation. The note included three recommendations, with the post-deploy gap identified as most worth addressing first.
Outcome
The team implemented basic post-deploy validation checks within a month of receiving the note. Deployment frequency increased from fortnightly to weekly within two months. The manager used the maturity note as a reference in her first planning cycle with the team.
Challenge
Following a merger of two engineering teams, release coordination had become a source of recurring conflict. Product and platform had different assumptions about branching strategy, freeze windows, and who was responsible for rollback decisions. Three consecutive releases had ended in extended incidents.
Engagement
Two-day workshop with both engineering teams, the product owner, and operations. Day one explored current practices and named the assumptions driving the conflict. Day two produced draft working agreements, reviewed and amended in the room. The final document was delivered within three days of the workshop.
Outcome
No release incidents in the two months following. The working agreements were added to the team handbook and referenced during the next three release reviews. The teams reported that having written agreements reduced the number of judgment calls that had previously caused conflict at release time.
Talk to us
Office
9 Persiaran Kayangan
Seksyen 7, Shah Alam
40000 Selangor
Credentials
Active member. Advisors hold current professional certifications in DevOps and cloud delivery practice.
Recognised as a recommended DevOps advisory practice under MDEC's digital technology adoption programme for two consecutive years.
Registered under the Malaysian government's e-Perolehan procurement system for eligible technology advisory services.
Leave us a note with your situation. We respond within one working day and will tell you honestly whether we think an engagement would be useful to you.
Open an enquiry