Our Work

Real engagements. Anonymised, but not sanitised.

We do not publish client names or specific numbers without permission. We do publish the actual problems we found.

These are real engagement summaries. The sectors and business situations are accurate. The names are not here — not because the results are uncertain, but because the clients operate in environments where discretion matters.

If you are evaluating whether to work with us, the pattern is more useful than the name. Most businesses we work with recognise themselves in one of these descriptions.

01

Singapore

Distribution — Regional Operator

Context

A mid-size distribution business with a regional footprint. Operations were largely undocumented — every process lived in someone's head. Reporting required manual extraction from three separate systems, stitched together in Excel by one person who had been doing it the same way for four years.

What the diagnosis found

  • No standardised operating procedures — onboarding new staff took months, not weeks
  • Reporting cycle consumed approximately three full working days per week
  • Three separate data systems with no integration — reconciliation was done manually
  • Stakeholder alignment issue: one department head was resistant to process change, creating silent blockers

What was done

  • Documented and standardised core workflows across five operational areas
  • Consolidated reporting inputs and automated extraction — the three-day cycle was reduced to under three hours
  • Resolved the alignment gap directly with the resistant stakeholder before implementation began — not after
  • Deployed two automation tools: one for reporting, one for internal task coordination

Observation

The bottleneck was not the tools. It was the undocumented process underneath them. Once documented, the automation was straightforward.

02

Singapore

Professional Services — Singapore-Based Firm

Context

A professional services firm that had accumulated seven tools over three years, each bought to solve a problem the previous tool created. The team was spending more time managing the toolstack than using it. The founding team had been meaning to consolidate for a year but never had a clear picture of what was actually being used.

What the diagnosis found

  • Seven active subscriptions — four with overlapping core functions
  • No single source of truth for client project status
  • Estimated annual spend on redundant tools: mid-five figures SGD
  • Onboarding new hires required explaining a tool maze instead of a workflow

What was done

  • Mapped every tool against actual usage patterns — not intended usage, actual usage
  • Consolidated to two tools that covered all functions the seven were supposed to cover
  • Built a single project-status view that the whole team could operate without training
  • Onboarding documentation created — new hires can now follow the process without hand-holding

Observation

The consolidation saved budget, but the bigger gain was visibility. The founding team could see the status of every client engagement without asking anyone.

03

Southeast Asia

Scaling Operator — Early-Stage Business

Context

A founder-led business preparing to scale beyond the founding team. The founder was the single point of knowledge for almost every process. Onboarding was informal — new hires watched the founder do things, then tried to replicate it. The business had grown to a point where this was no longer sustainable.

What the diagnosis found

  • No documented operating procedures — knowledge lived entirely with the founder
  • Onboarding a new hire took four to six weeks before they could work independently
  • Role boundaries were unclear — team members frequently escalated decisions they should have been able to make
  • Founder was involved in operational decisions that should have been resolved at team level

What was done

  • Built an operator framework: documented roles, decision rights, and escalation thresholds
  • Created a playbook for each core function — written to be followed by someone with no prior context
  • Onboarding structure rebuilt around the playbooks — not around the founder's time
  • Piloted with one new hire: independent operation achieved within six days

Observation

The founder's bottleneck was structural, not personal. Once the knowledge was extracted and documented, it was no longer a founder dependency — it was a system.

If you recognised your business in one of these, that is probably worth a conversation.

The diagnosis starts with a structured intake. No commitment required until both sides agree there is a fit worth pursuing.

Book a Diagnosis