// Client Feedback
What Clients Say About
Working With Pulsenet
Perspectives from organisations we've worked with across workflow optimisation, data engineering, and governance advisory engagements in Malaysia.
← Back to Home47+
Completed engagements
94%
Post-engagement satisfaction
6
Industries served
4+
Years in Malaysian AI practice
// All testimonials are from real clients. Names and organisations are shared with permission or anonymised at request.
// Feedback
What Clients Have Said
These are shared with permission. Where clients preferred anonymity, we've used their role and industry only.
We brought Pulsenet in to help us understand what was slowing down our claims processing team. They mapped our workflow in the first week and identified three specific places where AI-assisted triage could reduce turnaround time. The implementation ran without disruption to our operations. The documentation they left behind was genuinely usable — not just a slide deck.
Operations Director
Insurance services, Kuala Lumpur
Our data was in a state I'd describe charitably as 'organised chaos'. Multiple spreadsheets, some in SharePoint, some on individual laptops, with inconsistent column naming across departments. Liew Pei Shan spent the first two weeks doing a thorough inventory — more thorough than we expected — and the resulting pipeline has held up well. We're now actually able to run reports we couldn't run before.
Head of Analytics
Logistics company, Shah Alam
We were using an AI-powered scoring tool for credit decisions and our board wanted a formal review of how it was governed. Suresh Kumar helped us develop a bias assessment process and draft the internal policies we needed. He was direct about the gaps he found — which was uncomfortable, but that's what we needed. The governance playbook is something we still refer to.
Chief Risk Officer
Financial services, Petaling Jaya
What impressed me was that Ahmad Reza told us upfront that one of the processes we'd flagged as a candidate for automation wasn't actually a good fit for AI. Most consultants would have just included it in the scope anyway. That kind of honesty is rare. The work on the other two processes was solid — well-documented and our team could take it over without them.
General Manager, Operations
Professional services firm, Subang Jaya
The data engineering engagement helped us understand for the first time exactly what customer data we held, where it sat, and which fields were missing across which systems. It sounds like table stakes, but getting that picture clearly was genuinely valuable. Liew Pei Shan was thorough and didn't rush past issues she found. We're now in a position to actually pursue AI use cases that were blocked before.
Digital Transformation Lead
Retail organisation, Klang Valley
We engaged Pulsenet for governance advisory after our CTO flagged concerns about how we were using AI in student assessment. Suresh was thorough in mapping our obligations under PDPA and the relevant education guidelines. The internal policy drafts gave our board something to review and approve formally. The process was not always comfortable, but it gave us clarity on where we stood and what needed to change.
Vice-Principal (Academic)
Private education institution, Selangor
// Engagement Summaries
How Some Engagements Unfolded
These summaries are anonymised composites of real engagements, shared to illustrate how the work typically progresses.
// Case Study 01
Workflow Optimisation — Logistics Operations
A logistics company with around 60 staff was spending considerable time on manual data entry between their booking system and their billing platform. The same information was being re-keyed by three different people at different points in the process, and errors were common enough to require a weekly reconciliation run.
Pulsenet began with a two-day process mapping exercise, interviewing the operations, finance, and customer service teams separately. This surfaced not just the data entry duplication, but also a second workflow — inbound document classification — that the team hadn't initially flagged as a candidate.
The work resulted in a configured integration between the two platforms using a no-code automation tool, and an AI-assisted document classifier for inbound freight paperwork. Both were documented, trained staff were able to manage minor adjustments independently, and the weekly reconciliation run was no longer needed.
// Case Study 02
Data Engineering — Retail Analytics
A regional retail chain was preparing to implement an AI-based demand forecasting tool. Their data team had identified that historical sales data was spread across a legacy ERP, a newer point-of-sale platform, and several Excel files maintained by store managers — with inconsistent product coding across all three.
The data engineering engagement began with a full inventory: seventeen distinct data sources across twelve stores, with significant gaps in historical coverage for the newer locations. A reconciliation framework was developed for the product coding inconsistency, and a pipeline was built to consolidate daily sales data into a single clean warehouse compatible with the forecasting tool's input requirements.
By the end of the engagement, the organisation had a documented data architecture, a clean consolidated dataset covering four years of comparable sales history, and a data quality checklist their store managers could use for ongoing inputs. The forecasting tool was subsequently implemented by a separate vendor using this foundation.
// Case Study 03
Governance Advisory — Fintech Lending
A fintech company offering micro-lending to SMEs was using a credit scoring model that incorporated both traditional financial signals and AI-derived behavioural indicators. Their investors had raised governance concerns in a due diligence process, and the company wanted a formal review before their next funding round.
Suresh Kumar led a five-week engagement covering three areas: a technical bias assessment of the model's outputs across demographic variables, a regulatory compliance mapping exercise against PDPA and Bank Negara Malaysia's guidelines on responsible AI use in financial services, and internal policy drafting to formalise how the model's outputs were used in credit decisions.
The engagement identified two areas of concern in the model's demographic outputs that needed corrective attention, and a gap in the company's internal audit trail for model decisions. Both were addressed before the funding round. The governance playbook was subsequently used in the due diligence process and received positive feedback from the investors' legal team.
// How We Approach This
A Note on How We Handle Client Feedback
Consent before anything
We ask each client explicitly before sharing their feedback or summarising their engagement. No client is referenced without written consent, and anonymisation is available on request.
No selective editing
The testimonials shown here are unedited, though we've condensed longer responses for readability. Critical feedback is not removed — if something didn't go well, we discuss that directly with the client.
References available
If you'd like to speak directly with a past client before committing to an engagement, we can facilitate that introduction for relevant industries. Just ask during the scoping conversation.
Ready to Start Your Own Engagement?
A brief conversation is usually the right way to figure out if the fit is there. We're happy to talk before you commit to anything.