erchoo.com Erwin Choo Visibility, control, practical AI
Email Book a diagnostic
WhatsApp LinkedIn

Work

The work usually starts when the business has become harder to read than it should be.

I am usually brought in when reporting is too slow, handoffs are too brittle, key people are carrying too much hidden logic, or the systems stack still needs human translation.

Anchors that matter

The lane should resolve quickly.

The strongest signal is not a client list. It is whether the operating pattern, sector fit, and background line up in a credible way.

Restaurant groups

Multi-outlet reporting and coordination pressure

The clearest public wedge is in restaurant groups dealing with outlet coordination, reporting rhythm, and practical automation around recurring manual work.

Best fit when outlet visibility is slipping.

Manufacturers & distributors

Commercial visibility and demand-sensing strain

The adjacent cluster sits around demand signal, commercial visibility, and growth-stage operating strain in more complex product businesses.

Best fit when the issue is signal and reporting.

GE

Large-scale operating baseline

Signals experience inside environments where process discipline, reporting quality, and operating consequence matter.

Shows the operator lens was learned under real consequence.

PwC

Structured analytical and advisory discipline

Adds a public institutional anchor for rigorous problem framing, business analysis, and decision support.

Shows commercial literacy as well as practicality.

Citibank

Institutional complexity and control awareness

Rounds out the named background with another environment where governance, controls, and clarity were not optional.

Signals calm under operational pressure.

Operating stories

The strongest proof usually sits inside what changed in the operating day.

These stories stay anonymized because the useful part is the pattern: where the drag sat, what changed, and why the business became easier to run.

Restaurant-group story

Replacing brittle coordination with a steadier reporting and review rhythm

A restaurant group had too much coordination work living between outlets, spreadsheets, and people carrying too much operating context in their heads.

The operating problem
The real problem was recurring manual drag between outlets, reporting, and management review.
What changed
The work tightened the handoffs, reduced avoidable repetition, and put practical automation around the tasks that kept interrupting the operating day.
Why it mattered
Leadership got a cleaner picture of what was happening, while the team spent less energy stitching the basics together by hand.

Expansion-stage story

Making growth-stage reporting easier to trust before the next layer of expansion

An expansion-stage business had grown past the point where informal reporting habits still gave leaders enough confidence to steer cleanly.

The operating problem
Key decisions were being made with reporting that arrived late, depended on manual compilation, or required too much interpretation to trust quickly.
What changed
The work clarified the reporting logic, simplified the operating chain underneath it, and rebuilt the review rhythm around what leaders actually needed to see.
Why it mattered
Management visibility improved without adding more theatre, more tools, or another layer of process the business would resent maintaining.

Manufacturer-distributor story

Turning fragmented commercial signal into something operators could actually use

A business dealing with product movement, commercial visibility, and growth pressure needed a more usable read on what was happening across the operation.

The operating problem
Signal was scattered across teams, manual updates, and disconnected systems, making it harder to see demand, exceptions, or the true state of execution.
What changed
The operating work focused on reconnecting the signal chain, reducing unnecessary manual translation, and making the useful view easier to review consistently.
Why it mattered
The business gained clearer visibility and a more reliable decision surface without publishing sensitive mechanics or private metrics.
A stack of papers, glasses, and a notebook on a warm wooden surface.

What usually matters first

The first useful changes are rarely glamorous.

Usually it starts with cleaner reporting, fewer repeated handoffs, less copying, and less key-person dependence.

Start with the business pressure, not the tool list

Weak visibility, repeated manual work, fragmented systems, and growth-stage strain are easier to recognise than a polished technology story.

Look at what people are still stitching together by hand

That is usually where the business is paying more than it realises in time, confidence, and avoidable dependence on specific people.

Then decide what to keep, rewire, or rebuild

Once the history and constraints are clear, the right next move is usually much less mysterious.

If the pattern already feels familiar

The next step should sharpen the diagnosis, not keep you reading route explanations.

Quiet constraint

The useful proof is the pattern, not the private detail.

The public site should show the kind of work without turning private delivery detail into marketing copy.

  • Former-employer and background anchors can be named where they are already public and useful.
  • Client work stays anonymized so private metrics, workflow detail, and internal context do not get flattened into marketing copy.
  • If deeper detail is needed, it belongs in a conversation where context and permission can be handled properly.

Sharper routes

If the pattern already feels familiar, use the next route that fits it best.

The point of the work hub is to help you choose cleanly.