Tryn Limpa-Amara
Status: available to talk Loc: Bangkok, TH Local time: --:--:-- (UTC+7) Role: AI Translator

// Mission brief

Engineers and executives both say “AI”. I make sure they mean the same thing.

I’m an AI Translator in Bangkok. I work between the people who build AI and the people who have to bet on it, turning technical detail into decisions a business can make with confidence.

Translation consoleLive

Try it. Pick something an engineer might say:

    Input // engineering

    Output // business

    Sec-01

    Why this role exists

    Most AI projects don’t fail on the technology. They fail in the space between the people who build it and the people who pay for it. That space is where I work.

    I started out as a business system analyst, mapping how processes and systems actually behave, not how the org chart says they should. That habit carried into AI. Before anyone writes a prompt or picks a model, someone has to ask what problem is being solved, who it helps, and what “working” will look like.

    Today I do that at StackWise, a Bangkok-based AI firm that builds and runs AI for enterprises. I write the requirements engineers build from, and the explanations leaders decide from. When both sides read the same page and nod for the same reason, I’ve done my job.

    Sec-02

    Selected work

    Each file follows the same arc: a gap between two groups of people, the translation I did, and why it matters to the business.

    File 01 // HoplineIn development
    Role
    Product Owner & BA
    Org
    StackWise
    • AI governance
    • Product ownership
    • Data modelling

    Hopline: making enterprise AI visible, and governable

    Ask most companies which AI tools their staff use, and whether that use follows the rules, and you’ll get a shrug. Hopline is StackWise’s governance layer, built so leadership can answer that question with evidence.

    The gap
    Compliance and leadership talk in policies and risk. Engineers talk in logs, models and APIs. Neither side can design the product alone.
    What I do
    I turn governance needs into a prioritised backlog, process flows and data models, then take engineering trade-offs back to the business as clear choices.
    Why it matters
    Governance only works if people use it. My job is making sure what gets built answers the questions leaders actually ask.
    File 02 // AI literacy workshopsOngoing practice
    Role
    Designer & facilitator
    Format
    3 hours to full day
    • Workshop design
    • Facilitation
    • Change adoption

    AI literacy workshops: from fear to first use

    Sessions for managers and frontline teams who have heard a lot about AI, tried very little of it, and quietly wonder whether it’s coming for their job.

    The gap
    Teams are told AI will change their work, but rarely shown how. The fear of being replaced goes unspoken, so adoption stalls.
    What I do
    I design each session around the team’s real pain points, with clear learning objectives, hands-on activities in Miro and Mentimeter, and a plain-language definition for every term.
    Why it matters
    People adopt what they understand and trust. A session that ends with “here’s what I’ll try on Monday” beats any demo.
    File 03 // TallyPersonal project
    Role
    Designer & builder
    Platform
    iPhone
    • SwiftUI
    • Privacy by design
    • Product roadmap

    Tally: privacy by design, built by hand

    An expense tracker for iPhone, made for anyone who wants to know where their money goes without handing their spending data to someone else.

    The gap
    It’s easy to recommend “privacy by design” under data protection laws like Thailand’s PDPA. I wanted to know what it takes to actually build.
    What I do
    I designed and built the app in SwiftUI with on-device storage only: no server, no account, nothing to leak. I also planned its roadmap from first release onward.
    Why it matters
    When I tell a client privacy by design is achievable, I’m speaking from experience, not from a slide.
    File 04 // Weekly AI briefingEvery week
    • Research
    • Writing

    A weekly briefing with a translator’s lens

    Every week I compile what changed in AI and the industries we serve for my colleagues, and end each item with the part most digests skip: what it means for the people we advise, in plain language.

    Sec-03

    Rules of engagement

    Four habits that shape every document, diagram and workshop I make.

    Directive A

    Value first, then the how

    A decision maker needs to know what changes for the business before they need to know how the model works.

    Directive B

    Analogies over jargon

    If a term needs a glossary, it needs a better explanation. Every concept gets a plain-language version the first time it appears.

    Directive C

    Numbers over opinions

    Claims about AI should be tested, not repeated. When something breaks, I trace it to the root cause, adjust and test again.

    Directive D

    Respect the fear

    People worried about their jobs deserve a straight answer, not a pep talk. Realistic beats impressive.

    Sec-04

    Toolkit

    What I use to get from a fuzzy business problem to something a team can build and run. Read it the way you prefer.

    Analysis and modelling

    Working out what to build, and why.

    • Requirements and user stories
    • Backlog and prioritisation
    • Process mapping
    • Data modelling

    AI fluency

    Knowing what AI can and can’t do, well enough to explain it.

    • Prompt engineering
    • RAG and grounding
    • Agentic workflows
    • AI governance and risk

    Facilitation

    Getting a room of people to the same understanding.

    • Workshop design
    • Stakeholder interviews
    • Live engagement
    • Executive briefings

    Build

    Enough hands-on skill to know what I’m asking engineers for.

    • Git and GitHub
    • Python scripting
    • iOS with SwiftUI
    • AI-assisted development
    Loadout LucidchartMiroConfluenceGitHubMentimeterPowerPointExcelVS CodeClaude Code
    Sec-05

    Path so far

    From systems analysis to AI, one layer at a time.

    1. 2024

      GraduatedStamford International University

    2. 2024 – 2025

      Business System Analyst Tech StellarMapping how systems and processes really work, gaps included.

    3. 2025 – 2026

      Business Analyst BE 1 DigitalTurning business needs into requirements teams could deliver.

    4. 2026 – now

      AI Translator StackWiseBangkok-based AI advisory, engineering and products for the enterprise.

    Sec-06 // Open a channel

    If your AI plans need translating, let’s talk.

    Open to conversations with teams building or adopting AI, and with anyone working on the same gap between technology and business.