Portfolio-grade operating work for growing businesses

I help growing businesses run with the operating discipline of a portfolio company.

Daily visibility for owners.Finance teams that don't scale with outlet count.Operating systems your team can run without you.

I am an ex-Portfolio Director from a leading Asian private equity firm: 13 years, 22+ portfolio companies, and roughly USD 2B aggregate enterprise value across ASEAN, Australia-New Zealand, North Asia, and Europe. I now apply that operating discipline to growing owner-operated businesses across ASEAN and ANZ.

On the work right now: a quarterly engagement with a US manufacturer-distributor (Malaysian parent). Already shipped brand identity, new public website, full SKU catalogue, the foundation of a commercial operating system that routes web and email enquiries straight to fulfilment, plus demand-sensing from search analytics, market data, and the industry registry, plus channel strategy. Built single-handed. Plus continuing relationship support for a premium 13-outlet SG F&B group whose owner now reads outlet-level margin every morning, not weeks late. Phase 2 (supplier AP into the accounting system) is now run by the team without me.

erchoo.com / Regional: ASEAN + ANZ / 4 engagements per quarter / From USD 4,000 per month

4 slots
Concurrent engagements only
From USD 4K
Forward-Deployed Operator entry
Regional
ASEAN + ANZ
Erwin Choo reviewing operating documents at a desk
erchoo.com Regional: ASEAN + ANZ / 4 slots per quarter

Relationship support / client-autonomous

13-outlet premium F&B group, Singapore. The owner now reads outlet-level margin data overnight.

See if this fits

Outlet revenue and discount data used to land on the owner desk two to three weeks after the fact, long after suppliers had already repriced. Margins are thin in F&B, and the data was too old to act on.

Per-outlet ingestion now reads operator emails overnight, extracts revenue and discount-by-department data, builds a three-period view per outlet, and drops a clean reconciled file into the finance workspace every night. The owner starts the morning on yesterday data, not last month data.

Weeks late -> overnight Owner visibility
3 months Legacy platform migration
~90% Annual automation cost reduction
Client-autonomous Phase 2 status
Finance team didn't grow Adding outlets = configuration
  1. Outlet email intake
  2. Revenue and discount files
  3. Extraction and validation
  4. Three-period outlet view
  5. Finance workspace output
  6. Owner review

Phase 2, supplier AP keyed into the accounting system, is now run by the client team without us.

See the case study
Public-safe case study diagram of a 13 plus outlet F&B reconciliation workflow

More operating proof

How the same approach works in other industries.

Confidential / anonymised

02

Anonymised operating proof

Invoice processing that catches banking-detail fraud before it pays out.

Public-safe invoice operations control diagram showing invoice intake, vendor checks, duplicate risk, banking-detail review, and payment file release
Regional PE fund, anonymised Anonymised prior operating work. The system checks every vendor against the master record and every invoice against the live ledger for duplicates. If a vendor's banking details have changed, a human reviews it before any payment goes out.
  • Every invoice read and structured before payment
  • Every payment file built only after verification
  • Banking-detail changes always go to a human first
See the architecture
03

Forward-Deployed Operator

One operator across brand, web, data, channels, and D2C.

Public-safe commercial operating spine diagram connecting demand signal, enquiry, product evidence, quote, and fulfilment handoff
US manufacturer-distributor with Malaysian parent. Quarterly engagement, currently in flight. Brand identity rebuilt. New public website shipped. Full SKU catalogue migrated, taxonomy enriched, measurements verified. Foundation of a commercial operating system: routes web/email enquiries to fulfilment, pulls search, market, and registry signals into one layer, adds factory-direct buyer maths, and opens a D2C storefront alongside distribution. A regional market expansion is in flight.
  • Brand identity and new public website
  • Full SKU catalogue migration with verified measurements
  • Lead-to-fulfilment spine: web/email enquiry to warehouse system
  • Demand-sensing engine: search, market data, industry registry to one layer
  • Pricing intelligence: cost-vs-market, geo-arbitrage
  • Factory-direct value calculator for buyer transparency
  • D2C storefront alongside the existing distribution channel
See how this engagement runs

Why this approach

Decode the work. Give people time back. Leave the system running.

Most of the operating work I find inside growing businesses was never designed on purpose. A spreadsheet that became month-end close. A WhatsApp group that became the operating system. A finance team that grew with outlet count because nobody ever stopped to ask why.

Nobody built a broken process on purpose. The first move on every engagement is to decode the work: sit with the team, watch how things actually happen, ask why it ended up this way.

The second move is to give people their time back. The four hours of manual keystrokes should run overnight. The owner should read the business every morning, not weeks late. The finance team should do the work an accountant should actually do, not data entry.

The third move is to leave. Your team runs the system without me. It's a design constraint, not a slogan.

How I think about this work
Fragmented operating picture before the work
Rebuilt operating spine after the work

How the work gets done

Two engagement shapes. The owner picks.

Some owners want transfer: train the team, step back. Some want operate-with: stay deep, be the go-to operator, extend where the business expands. Both shapes are real, and both are priced the same.

01

Bring the next tool before the market does.

The work shows up where the business needs it: restaurant reconciliation, invoice controls, industrial catalogue systems, or channel buildout.

02

Train the internal team on real work.

The migration runs while the team is learning the new tool. The team learns on the live process, not in a slide deck.

03

Owner picks the engagement shape.

Transfer mode trains the team and steps back. Operate-with mode keeps one trusted operator deep in the business. Same price, different operating role.

04

Look for the moment the team starts asking where else this helps.

That is when the way of working has actually shifted. The unit of value is a live system the team can use, not a deck.

05

Decide the right mode on the first call.

Strong team that wants to learn fast: transfer. Lean team that wants one trusted operator in the work: operate-with.

Transfer mode

I work alongside the internal team, then step back as they internalise the new way of working. Best for owners with a strong internal team, or owners who want to build one.

Worked example: a premium 13-outlet F&B group migrated off a legacy automation platform in under three months. The next process is now run by the team without us.

Operate-with mode

I stay deep in the business as the go-to operator. Best for owners with a lean team who want one trusted person across systems, vendors, and geographies.

Worked example: a US manufacturer-distributor on a quarterly engagement - brand, new public website, full SKU catalogue, lead-to-fulfilment spine, factory-direct buyer maths, D2C storefront, market expansion, and channel buildout - all shipped solo in the first sprint.

Engagement options

Three ways to start.

Start with the smallest useful decision: is there a real operating problem worth fixing? From there, move into an embedded operator rhythm or a larger fixed build, depending on whether you need ongoing operating capacity or one specific system handed over.

Business Assessment

USD 2,000

Scope
1 week. Fixed scope.
Output
A written report on where work is leaking, where automation can pay for itself, what to fix in the first 60 days, and a recommended scope for the Forward-Deployed Operator engagement.
Worked example
Use it when you need a senior outside read before deciding whether there is a real operating problem worth funding.
Right for
Owners who want a senior outside assessment before committing to a retainer.
Book the assessment

Forward-Deployed Operator

From USD 4,000 / month

Scope
Roughly 1.5 days a week, embedded in the business. Sprint flex when a build needs it.
Output
Working operating systems shipped each month: automations, dashboards, reconciliations, weekly operating review, and monthly progress report.
Worked example
A US manufacturer-distributor quarterly engagement: brand, new public website, full SKU catalogue, lead-to-fulfilment spine, factory-direct buyer maths, D2C storefront, market expansion, and channel buildout shipped solo in the first sprint.
Right for
Owners who want a senior Forward-Deployed Operator without hiring a full-time CFO or COO.
Discuss the engagement

Install & Exit Build

USD 10,000-30,000

Scope
4-8 weeks. One specific operating system built, handed over, the client team runs it.
Output
A working system in production, scoped per business: outlet recon, AP hands-off, lead-to-fulfilment, demand-sensing, fraud guardrails, or cost-line audit. Documentation and team handover included.
Worked example
Phase 2 of the 13-outlet F&B engagement is exactly this shape: supplier AP keyed straight into the accounting system, built and handed over, the team now runs it without me.
Right for
Owners who want a specific lift shipped fast, with no ongoing retainer commitment.
Discuss a build

What an embedded engagement looks like

An embedded engagement should compound, not reset every month.

Month 1 Fix the first visible leak

Map the work, ship one margin-visibility or follow-up reliability win, and set up the weekly review.

Month 2-3 Make the system dependable

Make sure the workflow holds, train the team using it, document the handoffs, and decide what they should run themselves.

Month 4-6 Extend where the business needs it

Move into adjacent systems: catalogue, lead-to-fulfilment, channel, finance, reporting, or owner review.

Month 7-12 Keep building what works

Keep adding live systems until the business runs on a different weekly rhythm.

First 14 Days

What the first two weeks look like.

Kickoff / day in the life / build / review

Day 1

Kickoff with the owner

Goals, constraints, calendar, current reporting rhythm, and the decisions the owner cannot see clearly enough today.

Day 2-5

A day in the life across the business

Sales, ops, floor, production, finance, and owner review. I look upstream where the chaos starts, not only where it lands.

Day 6-7

First written read

Where the work is leaking, what a 60-day shape would look like, and where the quickest margin-visibility win is.

Day 8-12

Build week

The first system in production, usually a margin-visibility or follow-up reliability win the owner can see by Friday.

Day 13-14

Owner review

What landed, what is next, and whether the shape of the engagement should change.

Alternative Who you are hiring Seniority Typical cost When it is right
Full-time C-suite hire One person, full-time CFO or COO 20+ years USD 200K-400K / year all-in The role is permanent and broad enough to hire.
Enterprise consultancy team Partner-led team with junior-to-mid delivery Partner senior; delivery often 1-5 years Often USD 500K+ for a serious project Board-scale transformation requiring large teams.
Install & Exit Build One scoped build, then handover 20+ years, hands-on USD 10K-30K one-time You need a specific lift shipped fast, no retainer.
Forward-Deployed Operator One senior operator, embedded around 1.5 days per week 20+ years, hands-on USD 48K-60K / year You need senior help and real systems shipped now, without hiring full-time.

First step is the paid Business Assessment. If there is nothing worth fixing, the report is yours and we end there. No pressure to take it further.

Erwin Choo portrait
Erwin Choo Founder / erchoo.com

About

13 years inside Asian private equity. Now applied to owner-led growth.

I am Erwin Choo. I spent 13 years at a leading Asian private equity firm as Portfolio Director, working across portfolio operations and value creation. erchoo.com is where I now apply that operating discipline to growing businesses now. Building the systems they need, not selling slide decks.

Finance team did not grow

In the 13-outlet F&B engagement, adding outlets became configuration and process discipline instead of another finance hire.

~USD 20M value creation

At a separate portfolio company, one decisive operating call created roughly USD 20M in enterprise value.

~6 years GE

Six Sigma Black Belt, IMLP graduate, MES rollout across 6 plants in 4 countries, USD 1M+ annualised savings, Korea Oracle ERP with USD 616K in benefits, and two GE Plastics Management Awards.

~4 years PwC Advisory

Performance Improvement, promoted through Associate Director, 5-year strategic plan for a government regulator, and PMO for a major Malaysian telco transformation.

~2 years Citibank Malaysia

Vice President, Performance Improvement Head. Rebuilt the function into the Consumer Bank internal consulting and PMO unit.

13 years Leading Asian PE firm

Portfolio Director across 22+ portfolio companies and roughly USD 2B aggregate enterprise value, 25+ countries. Embedded 9 years as Group CIO then CTO of one portfolio company; Core Team on its roughly 6x exit at unicorn valuation, IRR above 20%. Cash cycle 30 days to 2 days. 10 acquisitions integrated into one stack. At a separate portfolio company, one operating call created roughly USD 20M in enterprise value.

Founded 2025 SS33 Pte Ltd

Operating vehicle behind erchoo.com. Current work includes a quarterly manufacturer-distributor engagement, continuing relationship support for a premium 13-outlet Singapore F&B group, and a deliberately small engagement load: four slots per quarter.

Tools brought early

~2021

Brought a leading RPA platform to a premium 13-outlet F&B group when Southeast Asian F&B was still spreadsheet-driven.

2025

Brought a modern RPA and parsing-grade extraction stack to the same group. Migrated off the legacy platform in under three months.

2025

Brought parsing and verification into invoice operations for a regional PE fund. Banking-detail fraud guardrails and payment-file workflow are in production.

2026

Brought an industrial-grade web stack and controlled engineering-diagram pipeline to a US manufacturer-distributor. Brand, website, SKU catalogue, lead-to-fulfilment spine, demand-sensing, pricing intelligence, and channels built single-handed.

FAQ

The questions owners usually ask first.

Fit / terms / ownership / handover

How long does a Forward-Deployed Operator engagement run?

The standard shape is a 3-month minimum, then month-to-month with notice. Three months gives enough runway to ship a full operating cycle instead of a cosmetic fix.

What do I get from the Business Assessment?

A written report that names the leaks, the first 60-day fix sequence, where automation is worth using, and whether a Forward-Deployed Operator engagement makes sense.

Can we stop after the Business Assessment?

Yes. The assessment is yours. There is no obligation to convert into an engagement if the problem is too small, the timing is wrong, or the fit is not there.

Do you transfer or stay deep?

Both modes are real. Transfer mode trains your team and steps back. Operate-with mode keeps me deep in the work as your go-to operator. We choose based on your team and preference.

Do you deliver personally?

Yes. Erwin delivers the assessment, the weekly review, and the core build direction personally. If specialist help is ever needed, it is discussed first.

Who owns the systems and IP?

The client owns the deliverables built for the business. SS33 may publish anonymised case studies only where confidentiality allows it.

Where do you work?

ASEAN and ANZ are the natural base. Regional travel is possible when the work needs on-site operating context.

What if there is nothing worth fixing?

Then the Business Assessment ends there. The value is the clarity: what not to build, what to leave alone, and what would be a poor use of money.

Are these familiar?

Do these sound like the problems you are facing today?

  • You only see margin after supplier prices have already moved.
  • Customer enquiries, stock answers, and fulfilment handoffs live in different places.
  • Weekly meetings start with people rebuilding numbers from scattered files.
  • Adding outlets means hiring more finance staff, even though the systems are the bottleneck.
  • You cannot show progress to the bank or to investors because the team is still waiting for last month's numbers.
  • Expansion into a new country depends on the same few people remembering every handoff.
  • The strategy is clear, but the business does not yet have the daily system to run it.

Get in touch

Book the first Business Assessment conversation.

In 30 minutes I will tell you whether there is a real operating problem to fix, where I would start, and whether a Business Assessment is worth your money.