I build the commercial machinery underneath marketing: ad networks with their own P&L, data departments that bill, reporting pipelines that halve turnaround, and — since 2022 — a governed multi-agent AI operation running a live cross-border commerce business at my own risk.
This is not a portfolio of campaigns. It is a set of artifacts: the architecture diagram, the escalation log, the failure that got killed in five days, and the P&L line at the end of each intervention. Read the parts that would survive your due diligence.
Ordered by size of commercial consequence, not by recency. Currencies as reported at the time. Every line is defensible in a reference call.
| Intervention | Result | Where |
|---|---|---|
| Proprietary premium ad network, built and scaled | SGD $100K in 30 days → $2M / yr | SPH |
| Cross-market search advertising strategy | SGD $22M over 3 yrs · +22% YoY | Yahoo |
| Data Performance department, built from zero | HKD $600K net-new, year one | DDB HK |
| First-party data & segmentation, HKD $2M+ budget | ROI +120% · CPR −60% in 2 qtrs | Jardines |
| Reporting pipeline rebuild | 7 days → 3 days (−57%) | DDB HK |
| KPI re-engineering, cross-functional conflict | Revenue +150% · SLA 5d → 3d | Yahoo India |
| Zero-budget organic strategy, 40+ markets | 50K → 3.2M (+3,100%) | Greenpeace |
| Print-to-digital migration, eight luxury titles | 8 of 8 live · on time · on budget | SPH |
| B2B demand generation overhaul | 0.3% → 1.0% conversion, 12 mths | New Energy Nexus |
| Enterprise recruitment programme, 4 markets | Sign-up conversion +120% / 3 yrs | Jardines |
| Multi-agent automation of daily commerce ops | Near-zero marginal cost per task | WONGSO |
WONGSO is a real company — Hong Kong entity, Indonesian supply chain, 190+ SKUs, four currency markets. Headcount: one.
The system below is what makes that arithmetic work. Three engineering decisions moved it from demo to production: cost tiering, retry ceilings, and a governance gate that will not let an agent do anything irreversible without me.
<!-- rejected at parse if any node is absent --> <agent_return id="catalog-compliance" run="0714-02"> <status>complete</status> <tier>amber</tier> <scope>190 SKU · GMC feed US/SG/AU/UK</scope> <findings> <item sev="2">14 SKU miscategorised cat-3</item> <item sev="1">GTIN absent, 6 SKU</item> </findings> <actions_taken>recategorised 14 · feed resubmit</actions_taken> <escalate>false</escalate> <cost model="haiku" tokens="18.4k"/> </agent_return>
Structured output is not a formatting preference. It is the reason an agent's work can be audited, costed and rejected — the same reason finance will not accept a narrative in place of a line item.
| Tier | Event | Disposition |
|---|---|---|
| AUTO | Meta title rewrite, 41 product pages | Shipped. Logged. Reversible in one commit. |
| AUTO | Currency feed refresh, AU + UK | Shipped. Diff attached to log. |
| NOTIFY | 14 SKU recategorised, GMC cat-3 → cat-1 | Acted, then reported. Reviewed same day. |
| NOTIFY | Pinterest catalog re-sync, 109 items | Acted. Approval confirmed downstream. |
| HUMAN | Merchant compliance review, account-level | Halted. Audit, remediation, staged resubmit — by hand. |
| HUMAN | Sales channel closure (permanent policy block) | Halted. Fix-vs-pivot priced. Pivot approved. |
| HUMAN | Any price change, any market | Standing rule. No agent touches price. |
Tier is assigned by reversibility and blast radius, never by the agent's confidence. An agent that is certain about an irreversible action is precisely the case the gate exists for.
What transfers
The store is not the asset. The asset is the governance layer, the unit-cost model and the failure-mode map — the three things every enterprise AI programme discovers it needs about eighteen months after the pilot. I have already paid for that learning with my own capital, which means it arrives at your organisation pre-tested rather than theoretical.
Each file runs the same four movements: the failure state, the diagnosis, the intervention, and what showed up in the P&L. No narrative without a number at the end of it.
Singapore Press Holdings · 2013–2015 · Digital Operations & Key Partnership Manager
Harper's Bazaar, L'Officiel and six sister titles were generating declining print ad revenue with no digital inventory to sell against. The newsroom read "digital transformation" as a threat to craft. Previous attempts had been announced from the top and quietly ignored.
Two failures stacked. Commercially, every proposed launch plan assumed traffic would arrive first and revenue second — eighteen months of cost before a single dollar. Culturally, the migration was being sold to journalists as a mandate rather than a capability, so the most senior and most influential staff were the most resistant.
Three tracks, deliberately sequenced. Technical: I built the SEO architecture myself — sitemaps, site trees, crawl governance — so all eight properties launched search-ready instead of retrofitted. Human: I designed capability training pitched at print craft and converted the loudest sceptics first, so adoption spread laterally rather than downward. Commercial: rather than wait for organic traffic, I architected APEX — a premium ad network pooling our luxury inventory with external publishers including The Diplomat — so the new properties carried a revenue line from launch week.
Transformation fails on culture, not technology. Convert the sceptics first, and give the new platform a P&L from day one so it survives the second budget cycle.
Yahoo Inc. · Bangalore deployment from Singapore · Senior Creative Strategist
Sales and editorial had stopped cooperating. Turnaround SLAs had blown out to five days, regional revenue was suffering, and HQ directives had worsened the standoff by picking sides. I was sent in as an outsider, more junior than several people in the room.
Neither team was behaving irrationally. Their KPIs were structurally opposed — sales measured on volume of commercial placement, editorial on metrics that placement degraded. Every individual was optimising correctly against a broken measurement system. The people were not the problem; the scoreboard was.
I refused to arbitrate disputes and instead re-engineered what each side was measured on, so both teams won from the same outcomes. I instituted shared testing frameworks so disagreements were settled by data rather than seniority, and built a communication cadence that kept the new incentives honest after the novelty wore off.
When two competent teams are at war, the org chart is the problem. Change what people are measured on before you change anything else — and never before you understand why their current behaviour is rational.
DDB Hong Kong · 2021–2022 · Data Performance Lead
Campaign reporting took seven days — arriving too late to change anything it described. Data sat at the end of the process as a post-mortem. Pitches were being lost to data-literate competitors, and there was no internal capability to build against.
The brief was to build a data function, but building it as an internal cost centre would have guaranteed its death in the first downturn. The real problem was position, not tooling: data was being consumed at the wrong end of the workflow and had no commercial constituency inside the agency to defend it.
I rebuilt the reporting pipeline end to end on cost-effective analytics tooling, then moved data to the front of the creative process instead of the post-mortem. Then I made it commercial — packaged the capability as a billable service and took it to flagship clients: Jardines, Allianz Global Investors, Manulife. For Jardines I ran first-party data analysis and audience segmentation across a media budget above HKD $2M annually. And I trained the entire agency rather than only my team, so data literacy became house style rather than a department.
Do not build reporting systems. Build decision systems, then make them a profit centre — a capability that bills is a capability that survives the next restructure.
Cross-border commerce fails in the plumbing: feed rejections, currency drift, category misclassification, stock ghosting between markets. The stack exists to make those failures visible before a customer finds them.
| Market | Currency | Feed surface | Localisation handled |
|---|---|---|---|
| United States | USD | Google Merchant Center | Pricing · tax display · sizing · cat 1–4 taxonomy |
| Singapore | SGD | Google Merchant Center | Pricing · GST treatment · shipping bands |
| Australia | AUD | Google Merchant Center | Pricing · GST · apparel sizing · returns terms |
| United Kingdom + EU | GBP | Google Merchant Center | Pricing · VAT · EU compliance categorisation |
| Social commerce | Multi | Pinterest Catalogs | Domain claim · 109-item approved catalog · ad approval |
Shopify Liquid — mobile-first template work, dynamic upsell logic, JSON-LD schema, technical SEO built in rather than bolted on.
AppSheet — custom database routing cross-border stock between Indonesia and Hong Kong. 0% stock discrepancy across O2O retail.
GMC · Pinterest · Meta Commerce — four-currency product feeds with automated compliance categorisation across 190+ SKUs.
Klaviyo — lifecycle flows and an affiliate programme, contributing to 25% YoY revenue uplift.
GA4 · Looker Studio · SEMrush — one reporting surface, built so an agent can read it as reliably as I can.
Living state docs · SOPs · session logs — any agent or human resumes any workstream cold in minutes. The same discipline as agency handover design.
02 Jul — Incumbent social commerce channel returns a permanent regional policy block. Not a bug; a jurisdiction exclusion, no appeal path.
03 Jul — Fix-versus-pivot priced. Cost of pursuing an exception: indefinite, with no probability estimate available. Decision: kill it.
04–06 Jul — Catalog re-cut for an alternative surface. Domain claim filed, 109 items submitted.
07 Jul — Replacement channel live and ad-approved. Total elapsed: five days.
Included deliberately. A portfolio without a failure in it is a brochure.
A platform-level merchant compliance review is an account-existential event: feeds suspended, paid surfaces dark, revenue at zero until cleared.
Method — systematic audit of all 190+ SKUs against the platform taxonomy, product-data remediation at source rather than at feed level, then staged re-submission in tranches so a second rejection could be isolated to a specific batch instead of restarting the clock.
Governance — tier-red throughout. No agent action; human sign-off on every submission.
Platform compliance is programme management, not a support ticket.
Clients to date: Jardines · Allianz Global Investors · Greenpeace Southeast Asia · New Energy Nexus · Mr. Ripley · Magifarm.
Available for permanent leadership mandates in Hong Kong, Singapore and Bangkok, and for the engagement modes opposite on a remote or hybrid basis.
Two to three weeks. I take your funnel, feed infrastructure, martech stack and reporting pipeline apart, and hand back a prioritised intervention list with cost, effort and expected commercial impact against each line. You keep the document whether or not you keep me. Most engagements should start here; several should end here.
For teams already spending on AI tooling without a decision-rights framework, a cost model or a failure-mode map. I map what your agents and automations are actually permitted to do, price what they cost per task, install the escalation tiers, and write the SOPs your team will still be running twelve months later. Almost nobody offers this work, because almost nobody has run it in production.
Retained, two to three days a week. I own the growth number, build the operating cadence, hire and train the permanent team, and design my own redundancy. Suited to companies that need director-level judgement before they can justify a director-level salary.
End-to-end launch infrastructure for product businesses: Shopify build and conversion logic, Klaviyo lifecycle and reactivation, multi-market feed setup, campaign asset systems, and the reusable template library that stops every launch starting from zero. Built on my own catalog first, then on yours.