What teams say after working with us

Challenge

A 40-person technology firm in KL was preparing to roll out a new ERP system across finance, HR, and operations. Four departments were involved but there was no agreed scope, no defined roles, and no shared timeline. The project had already been delayed twice.

What We Did

We ran a Project Setup Session over four days — an initial call to understand the state of play, a working session with department heads, and a one-page brief covering scope boundaries, milestones by department, role assignments, and three identified risk areas.

Outcome

The rollout started on schedule the following Monday. Stakeholders cited the brief as the single document they referenced throughout. The project completed within the agreed timeline — the first time the firm had achieved that on an initiative of that scale.

"The brief was actually on the table at every meeting." — Operations Director

Challenge

A consulting firm in Bangsar was redesigning its client onboarding process to reduce setup time from three weeks to five days. The project team was strong but the project lead was also handling day-to-day client work, and things were beginning to drift.

What We Did

We provided six weeks of Delivery Support — fortnightly check-ins, a shared tracker in the team's existing project board, and brief written summaries after each session. When a key dependency with IT slipped, we helped the team replan the affected workstreams within 48 hours.

Outcome

The new onboarding process launched at week seven — one week later than the original plan, but well within acceptable bounds given the mid-project IT delay. Average client setup time dropped from 17 days to 6 days in the first quarter post-launch.

"Having an external check-in made us more accountable than any internal meeting ever had." — Managing Partner

Challenge

A Subang Jaya e-commerce company had grown from eight to twenty-two staff over two years and was running six to eight internal projects simultaneously. There was no shared approach — different teams used different tools, timelines, and reporting formats, causing confusion at the leadership level.

What We Did

Over seven weeks, we ran three discovery workshops, designed a template set covering scoping, status tracking, and project close-out, and produced a 12-page practice guide. The guide was tested with two live projects before being finalised.

Outcome

Within three months, all internal projects were tracked using the new templates. Leadership reported a significant reduction in "status update" requests — teams could find project status independently. The company has since onboarded four new staff using the same materials.

"We use the scoping template for everything now, even small things." — COO