Work

Projects, and what changed

Each case study names the problem, the decision that mattered, and only what the client agreed to publish. Where a number or a name is missing, the client asked us not to share it yet.

Operations dashboard of the order system built for TGPCB

Featured Business operations TGPCB

Paper and spreadsheets to one order workflow

TGPCB, an electronics components distributor in Vietnam, moved quoting, supplier purchasing, goods-in and collections out of paper and Excel into one system its office, warehouse and customers all read from. Status is derived from what staff record, never typed.

4Supplier APIs

8Derived order states

6Staff guides

Read the case study →

Slot for the next one

Every completed Build should produce a case study with one agreed measure.

Publication standard

What every case study must show

Context — the operating constraint and its cost Decision — what changed, what was left alone, and why Evidence — a baseline and result, or an attributable quote; never an invented number

Not published until

The client has approved it

Names, screenshots, quotes and figures stay private until verified and approved. Screens shown before approval come from demonstration data with fictional customers.

Your problem probably looks like one of these

A Blueprint defines the baseline, risks and success measure before anyone commits to a Build.

Request a call →