01 Confidential client
Enterprise data integration platform
Twenty-plus enterprise systems that each held part of the truth, connected into governed data flows with reconciliation built in — across twelve business units and five countries.
Case studies
Three enterprise engagements where the client is withheld under confidentiality, and two systems built and run by EthanCorp where everything is inspectable. Context, constraints, architecture, what was actually done, and the numbers — including the ones that are only approximately good.
On confidentiality
Client names, system names and data are withheld for the three enterprise engagements. Inventing a plausible client name would make these read better and would also make them fiction. The figures shown are the ones already published on my professional profile at dattranbi.github.io.
01 Confidential client
Twenty-plus enterprise systems that each held part of the truth, connected into governed data flows with reconciliation built in — across twelve business units and five countries.
02 Confidential client
A five-day manual reporting cycle replaced with governed dashboards on standardised definitions — and the arguments about whose number was right replaced with one KPI dictionary.
03 Confidential client
A ten-step manual document workflow reduced to two guided steps, with an explicit human review gate — and the acceptance rate measured rather than assumed.
04 Live
A production RAG assistant answering iSAMS questions from a curated knowledge base, with an admin console, cost visibility and a feedback loop — free and open to the iSAMS community.
05 In development
A retrieval-grounded tour advisor for the Vietnamese market, built to test a two-layer NLU design: deterministic rules first, the language model only where the rules run out.
The fastest way to find out whether it transfers is a 30-minute scoping call. If it does not, you will hear that.