Forward-deployed engineer

Most enterprise AI never leaves the pilot.

I get it out. Embedded with the customer, on their own data, one workflow live in weeks rather than a deck that impresses and dies. Currently leading engineering on an agent and knowledge platform in Hong Kong.

Specimen — hover to reveal

Most enterprise AI dies in the proof-of-concept graveyard

A pilot proves the technology works, everyone agrees it is impressive, and nothing reaches production. The way past it is the same shape every time, whether it is a tender comparison, an ad compliance gate, or an agent platform.

How the work goes from a business problem to production A business problem becomes a demo that decides it, then budget and real data, then a narrow deployment shipped in weeks. One constraint identified at the start governs every stage. A business problem named by the people who have it scoped in weeks A demo that decides it clickable, real path, no backend shown, not pitched A decision budget, and real data on their own data Deployment narrow, deep, in weeks one constraint, held the whole way
01

A demo settles what a deck cannot

A clickable path through the real decision, seeded and backendless, is cheaper than the meeting it replaces. The output is not a report. It is software an executive clicks.

Where I did this

A group-level document intelligence service Unstructured documents from several business units pass through one extraction service and come out as structured records those units can query. Contracts Invoices Specifications unstructured Extraction service one contract, every business unit structured Structured records Analytics Operations

Document intelligence, at group level

Li & Fung, Strategic Data Unit

Product owner of the document intelligence service and lead for AI development across the group. One extraction contract serving several business units, rather than a separate parser per team.

One service for the group, or every unit builds its own.

02

Then real data, no exceptions

A demo wins the decision; only the customer's own data proves the value. Sample data hides the fields that do not match the documentation, the third of rows that are null, and the two contradictory answers that are each locally correct.

Where I did this

Fusing five data sources into usable customer segments Telco, profile, transaction, image and text data are fused into one customer view, from which hundreds of segments are cut and handed to campaign teams as target lists. Telco Profile Transactions Image Text entity-resolved One customer view cut into Segments lifestage, interest, behaviour handed to campaign teams Campaign target list

Customer segmentation from five fused sources

Sun Hung Kai Properties, Chairman's Office

Telco, customer profile, transaction, image and text data fused into one view, cut into hundreds of segments by lifestage, interest, behaviour and demographics, and handed to campaign teams as target lists.

A segment is only real if a campaign team can act on it.

03

End to end, or it was not delivered

Owning the pipeline and not just the model is the difference between a notebook and a system: sourcing, cleansing, features, the model, and the serving path that still runs on a Tuesday morning when nobody is watching it.

Where I did this

A recommendation engine delivered end to end Behavioural signals run through a distributed pipeline into a ranked recommendation, and the outcome feeds back into the next round of training. Signals behaviour, usage nightly batch Pipeline Spark, Hive features Ranking tuned, served served Customer what happened next trains the next round

A recommendation engine, end to end

HKT, Group CTO Office

Delivered end to end as team lead: sourcing and cleansing, feature engineering, the model, and the serving path over Hadoop, Hive, Spark and MongoDB. Alongside credit analytics and spatial work with geohash.

End to end meant owning the pipeline, not just the model.

04

Narrow the scope, never the depth

Not a smart assistant for the whole company, but one workflow end to end with nobody in the middle. A slice small enough to finish in weeks, deep enough that the business sees it. Whatever cannot show value in that window was not the core value.

Where I did this

Consolidating a messaging estate behind one agent platform Four scattered channels converge into one agent platform, which reaches the systems of record only through a human approval gate. Channel Channel Channel Channel consolidated Agent platform one estate proposes human approves applies Systems of record

An agent platform that acts under approval

Crewio, current

A scattered messaging estate consolidated behind one agent platform, with operational agents that act inside the systems of record rather than reporting on them: procurement chasing, usage analysis, and an approval step recorded before anything applies.

An agent may propose. A human applies.

Also useful in

Four areas, rather than everything I have touched.

Forward deployment

Embedded with the customer rather than shipping product from a distance: finding the problem worth solving, proving it on their own data, and getting one workflow live before widening it. Product ownership and cross-functional leadership up to group level.

  • Product ownership
  • Team lead
  • Strategy
  • Delivery

LLM and agent systems

Orchestrating language models for performance and scale, and agents that act inside the systems of record rather than reporting on them, under a recorded approval step.

  • Orchestration
  • Inference
  • Tool use
  • Evaluation

Knowledge systems and platform

Ontologies, entity resolution, hybrid retrieval and provenance. Shared engines against per-customer deployments, and deciding what shares a database and what must not.

  • pgvector
  • Hybrid recall
  • Multi-tenancy
  • Row-level security

Ten years of the foundation

Recommendation engines, credit analytics, segmentation, OCR and NLP, over real operational data at group scale. Knowing what a messy production table actually looks like is why the real-data rule above is a habit rather than a slogan.

  • Python
  • PySpark
  • Hadoop and Hive
  • NLP
  • OCR

Experience

CrewioJul 2026 — now

Lead Engineer

Crewio, Hong Kong

Leading engineering on an agent and knowledge platform for enterprise and SME customers: shared engines in a monorepo, per-customer deployments across three tenancy tiers, and the architecture underneath them. Where customisation is allowed to live, what a brain may assume, and what activation actually costs per customer.

Li and FungMar 2022 — Jul 2026

Principal Data Scientist, rising from Senior Data Scientist

Li & Fung and LFX Digital, Strategic Data Unit

Led development of AI-driven products from conception to deployment, with a focus on orchestrating large language models for performance and scale. Product owner of the document intelligence service and lead for AI development at group level; product manager across several data products. Rebuilt the business analytics pipeline with management in each business unit.

Hong Kong Data ClubSep 2022 — now

Founding Committee

Hong Kong Data Club

Founding committee member of Hong Kong's data practitioner community.

Sun Hung Kai PropertiesAug 2020 — Mar 2022

Senior Data Scientist, rising from Data Scientist

Sun Hung Kai Properties, Chairman's Office

Group-level strategy and analysis across mall management, SmarTone, YATA, KMB and The Point. Five data sources fused into hundreds of customer segments, plus bus maintenance optimisation and OCR over vehicles and receipts.

HKTDec 2016 — Aug 2020

Data Scientist, rising from Analyst

HKT, Group CTO Office

Team lead. A recommendation engine delivered end to end, credit analytics, and machine learning pipelines over Hadoop, Hive, Spark and MongoDB.

SAPHSBMP2013 — 2016

Earlier

SAP, Hang Seng Bank, Mecom Power

Big data platform internship at SAP, and before that commercial and retail banking at Hang Seng Bank in Macau. The arc from banking operations to engineering took ten years.

If you are building something where being wrong is expensive, ask me something specific.

Eric Tai. Forward-deployed engineer, Hong Kong.

Set in Inter. The garden is 1,433 points, and so is the code it becomes.