Hà Lữ Minh Anh · Portfolio

Export PDF

Mode
Detail

00
Portfolio Portfolio · Services

Hà Lữ Minh Anh

Project Manager & Business Consultant / 2022 – 2026

  • 4 years — of total experience, including 3 years in project management and business analysis for AI products and implementation work; earlier experience spans ERP, cross-border e-commerce, and logistics operations.
  • 32.473 — recorded conversations across six systems with verified counters; all delivered systems have handled more than 100,000 conversations in total.
  • 16.853 — invoices generated automatically for three facilities in one hospital system.
Which version would you like to view?

The Selected version highlights representative projects for a quick read. The Full version includes additional projects and more implementation detail.

Emailhaluminhanh@gmail.com Phone+84 768 008 880
01
01 Contents

Nine areas of work

The Selected version highlights representative projects for a quick read. Each group still shows its full scale and links to the complete project list.

A
Advisory and sales agents for chat channels
10+ projects
C
Platform Products
Selected: 3 featured products · Full group: 5+ products View full list
Selected: 3 featured products · Full group: 5+ products View full list
Account-based SaaS platforms with service plans
5+ products
F
ERP & International Trade
Selected: 2 featured projects · Full group: 4+ projects View full list
Selected: 2 featured projects · Full group: 4+ projects View full list
Business analysis, implementation, and import-export operations
4+ projects
H
20 practical videos · 56 role-based scenarios
20 videos · 56 scenarios
I
Brand control, video production, and an Amazon storefront
3 projects
01
02
02 Scale

Key figures

32.473Conversations · 6 verified systems
247.255Messages exchanged
16.853Invoices generated automatically
36+Projects presented
1.236AI agents created · Conductify
790Users · Conductify
237+Users with a transaction after 1 month · MentorX
13ERP modules · Odoo
2022–2026Period

About the figures in this portfolio

  • Every figure identifies the project it comes from.
  • More than 100,000 conversations were recorded across all delivered systems. The 32,473 figure is the verified total from six systems with detailed counters included in this portfolio.
  • Any estimates used in proposals are clearly marked as estimates.
  • Each metric is presented with its corresponding scope and data source.
02
03
03 Product Screens

Screenshots from live systems

A selection of screens from products and systems I have delivered. Select any image to view it in full.

MentorX learner dashboard
MentorX · Track courses and learner activity
AI Co-Worker drag-and-drop workflow builder
AI Co-Worker · Build automated workflows with drag-and-drop blocks
Crawbot application dashboard
Crawbot · Manage AI tasks in a desktop application
Enterprise knowledge graph
Knowledge Graph · Explore entities and relationships in data
Conductify agent list
Conductify · Manage created AI agents
MentorX access-control screen
MentorX · Control content access by user group
AI Co-Worker execution sequence
AI Co-Worker · Review each step running in a real browser
Crawbot model-provider selection screen
Crawbot · Configure multiple model providers in one place
03
04
04 Capability Map

Four areas
covered end to end

01

Business analysis

Business Analysis
  • Interview stakeholders and uncover cross-functional requirements
  • Write requirements, functional specifications, and business rules
  • Map current and proposed processes in BPMN
  • Compare business needs with system capabilities before selection
02

Product management

Product Management
  • Define product requirements, roadmaps, and phased scope
  • Prioritize features using real usage data
  • Work with developers, testers, and designers
  • Price and package services
03

AI systems

AI Systems
  • Design how AI retrieves business documents and handles each step
  • Connect business systems so AI can use live operational data
  • Control errors with rules, review layers, and human handoff
  • Measure conversation quality after launch
04

Delivery & operations

Delivery
  • Run projects from discovery through production launch
  • Manage user acceptance, exceptions, and handover documents
  • Train end users
  • Monitor and refine systems after handover
04
05
05 More in the Full version

Six projects worth exploring
beyond the selected set

Open any project that interests you. The portfolio will switch to the Full version while keeping the current portfolio mode.

05
A-00
Group A Advisory and sales agents

AI Sales Agents

Agents that assist customers through chat. They use product knowledge, understand promotions, record orders, and hand over to a person when a question falls outside their scope.

10+Projects 31.103Conversations 237.930Messages 2024–2026Period

The two totals combine verified counters from five systems: AB Beauty World, Lekofe Coffee, 1ManBiz, ABTravel, and Ladalat.

Shopping agent answering customer questions
A shopping agent answering customers directly in the chat window
Sales agent working on an e-commerce marketplace
A sales agent working on an e-commerce marketplace
A product information agent on the retailer's website
Product information agent
A-01
A-01 Retail · Beauty · Live operations

AB Beauty World

Beauty retail chain with 5 stores in Ho Chi Minh City and more than 4,000 SKUs.

Context

  • More than 4,000 SKUs, with prices and promotions changing daily on the website.
  • The support team could not keep up with incoming requests.
  • No staff were available outside business hours.

Approach

  • Used a Mindflow chatbot, a custom API, and n8n to orchestrate the workflow.
  • Connected the AI Co-Worker extension to a VectorDB for product lookup.
  • Recorded AI-captured orders and complaints in Google Sheets.
  • Used Telegram to alert a person when a request exceeded the agent's scope.

Outcome

  • Ran across three channels: Web, Zalo, and Facebook Messenger.
  • Handled requests around the clock and recorded orders without manual entry.
  • Kept product answers consistent across channels.
4.216Conversations 52.898Messages handled 4.000+SKUs in the knowledge base 3Intake channels
Implementation details
  • Collected product data in real time and ran a full synchronization every day.
  • Validated data before creating an order, then sent it to Haravan.
  • Handed conversations between the agent and staff based on conversation status.
  • In early 2024, no available chatbot solution fit this use case, so the system had to be built in-house.
My roleBusiness analysis, workflow design, product knowledge setup, operations, and ongoing refinement.
Mindflown8nVectorDB HaravanGoogle SheetsTelegram
Conversation counters and daily charts in the admin dashboard
Agent conversation and message statistics
Daily conversation chart
A-02
A-02 F&B · E-commerce · Live operations

Lekofe Coffee

A 12-store chain with several overlapping promotion types.

Context

  • Twelve stores with promotion programs that changed frequently.
  • Six promotion types ran at the same time: buy one get one, buy two get one, percentage discounts, buy X get Y, threshold rewards, and cross-product promotions.
  • A standard rule engine could not cover every possible combination.
  • Staff calculated prices manually, which led to inconsistencies.

Approach

  • Maintained a promotion reference table in Google Sheets and connected it directly to Haravan.
  • Used a Python backend to calculate prices. Eligibility rules were enforced in code instead of left to the model.
  • Added an AI review pass before sending the result to the customer.
  • Connected Pancake to route each conversation to the right support person.

Outcome

  • Handled 16,324 conversations and 101,563 messages.
  • Detected applicable promotions automatically from the shopping cart.
  • Created orders directly in Haravan with no re-entry.
16.324Conversations 101.563Messages handled 12Stores 6Promotion types
Implementation details
  • The agent handled Vietnamese without diacritics and regional wording, rewriting questions before searching the knowledge base.
  • Responses were adjusted for older customers: short sentences, fewer technical terms, and a clear restatement of the final price.
  • Intake channel: Facebook Messenger.
My rolePromotion-rule analysis, pricing workflow design, reconciliation testing, operations, and ongoing refinement.
MindflowPythonGoogle Sheets HaravanPancake
A-03
Sales agent on an e-commerce platform
A sales agent handling several product categories in one conversation
A-03 SaaS · Marketing tools · Live operations

1ManBiz

A marketing-tools platform with a catalog spanning several product categories.

Context

  • A large catalog covering tools for Facebook, TikTok, email, and Zalo.
  • Customers often asked about several product lines in the same conversation.
  • The team needed to identify prospective customers and handle a high volume of orders.

Approach

  • Built one sales agent for several channels, grounded in controlled product information.
  • Each question went to the right product category, and the answer used only that category's guidance and data.
  • After each conversation, n8n sent the customer's details and conversation record to the CRM automatically.
  • Supported responses in multiple languages.

Outcome

  • Handled 6,051 conversations and 65,962 messages over 6 months.
  • Routed questions to the right product category instead of giving a generic answer.
  • Prospective customer details were recorded in the CRM during the conversation.
6.051Conversations 65.962Messages 6Months in operation 4Product categories
Implementation details
  • Used GPT-4 and GPT-4o mini, selecting the model based on question complexity.
  • Documents were separated by tool category, so the answer used only the relevant product data.
  • The system used the purpose of the question to choose the right category instead of relying on a fixed keyword list.
My roleDesigned the information base and category-selection flow, integrated the CRM, and monitored and refined the live system.
MindflowWebhookCRM n8nRAG
A-04
Agent conversation and message statistics
Agent admin dashboard
Conversation counters and the sales-agent admin dashboard
A-04 F&B · Health foods · Live operations

Nấm Lý Tưởng

A recipe-led sales flow: suggest a dish first, then sell the ingredients.

Context

  • A varied catalog of fresh mushrooms, dried mushrooms, processed products, and mushroom tea.
  • Each product included several data dimensions: ingredients, health benefits, and storage instructions.
  • Promotions included buy N get M and weight-based pricing.
  • Inventory was stored in the client's internal Google Sheets workbook.

Approach

  • Each answer went through two steps to reduce errors before it reached the customer.
  • The first step selected the right recipe, product, inventory, and promotion data.
  • The second step checked the item code, weight, and promotion before sending the answer.
  • Matched recipes to the right products, then checked item codes and inventory in Google Sheets.

Outcome

  • Reached 98.8% accuracy with a 1.2% error rate.
  • Handled 667 messages in the first 3 months.
  • Recorded orders with area-based delivery fees across three channels.
98,8%Accuracy 1,2%Error rate 667Messages / 3 months 2Review layers
Implementation details
  • Synchronized live inventory from the client's stock workbook without re-entering data.
  • The cross-check layer stopped most errors, including incorrect product codes, weight units, and promotion levels.
  • Intake channels: Facebook, Zalo, and Website.
My roleDesigned the two-step answer and review flow, organized recipe and product data, measured accuracy, and refined the live system.
MindflowGoogle SheetsSemantic search ZaloFacebook
A-05
A-05 Travel · Live operations

ABTravel

A travel agent that answered questions and recommended tours through chat.

2.255Conversations 8.728Messages

Scope

  • Recommended tours and answered common customer questions.
  • Ran on the same agent platform as the other sales projects in group A.
My roleKnowledge setup, agent configuration, operations, and ongoing refinement.
MindflowRAG

Figures were verified against the project's operations summary.

A-05
Conversation and message counters in the admin dashboard
Ladalat agent admin dashboard
A-06
A-06 Retail · Live operations

Ladalat

A retail product advisory agent for chat channels.

Scope

  • Answered product questions and helped customers choose suitable items.
  • Used the same agent platform as the group's other retail projects.

Recorded

  • 2,257 conversations and 8,779 messages at the reporting date.
  • Figures came directly from the system counters.
2.257Conversations 8.779Messages
My roleProduct knowledge setup, agent configuration, operations, and ongoing refinement.
MindflowRAG
A-07
A-07 Beauty · Cosmetics · Live operations

VHN

Seven brands running on one agent system.

Context

  • Seven cosmetics brands, each with its own catalog.
  • Five skincare protocols used to advise customers based on their needs.

Approach

  • Built one shared sales-agent system with separate knowledge for each brand.
  • Added BI reporting to track conversation outcomes.
  • Rolled the system out in phases instead of launching every brand at once.

Recorded

  • Seven brands shared one platform instead of requiring seven separate systems.
  • Five advisory protocols were standardized for consistent use across the system.
7Brands 5Advisory protocols
My roleBrand-specific knowledge design, protocol-based advisory flows, and phased delivery coordination.
MindflowRAGBI
A-07
A-08
A-08 Logistics · Transport · Live operations

Proship

Shipping service advice and order tracking.

Context

  • Several service lines: container transport, international logistics, customs services, and vehicle rental.
  • Pricing depended on pickup and delivery addresses, transport type, and related conditions.
  • Customers requested order status frequently, forcing staff to look it up manually in an internal system.

Approach

  • Built a service knowledge base so the agent could answer within the correct scope for each service line.
  • Calculated rates from addresses, transport type, and applicable conditions.
  • Connected the internal tracking API so customers could check shipments during the conversation.

Recorded

  • Customers could check order status without waiting for staff to look it up.
  • Rate questions followed one consistent calculation method.
My roleService knowledge setup, rate-calculation workflow design, and shipment-tracking API integration.
MindflowRAGTracking API
A-08
A-09
A-09 Education · Preschool · Live operations

TalentEdu – Bé Ong Sài Gòn

A preschool admissions agent that collected parent information and scheduled school visits.

Scope

  • Answered parents' admissions questions through chat.
  • Collected contact information step by step instead of asking for everything at once.
  • Scheduled school visits during the conversation.

Recorded

  • Parent information was stored in one place instead of scattered across chat threads.
  • School visits were recorded as soon as a parent agreed.
My roleAdmissions Q&A design, information-capture flow, and visit-scheduling flow.
MindflowRAG
A-09
A-10
A-10 Health supplements · Live operations

Megavita

A health-supplement product advisor for chat channels.

Scope

  • Answered product questions and helped customers choose based on their needs.
  • Used the same agent platform as the group's other sales projects.
My roleProduct knowledge setup, agent configuration, and operations.
MindflowRAG
A-10
B-00
Group B Operations automation

Operations Automation

Replacing repetitive manual work with controlled workflows. Every step records its status, exceptions are visible in a dashboard, and failed operations can be rolled back.

2+Projects 16.853Invoices automated 20 hoursManual entry removed each week 2024–2026Period

The invoice total combines three facilities in one hospital system. Time saved comes from the shipment-update project and was reported by the operations team.

B-01
B-01 Healthcare · Live operations

Saigon ENT Hospital

The former software provider stopped operating, while three facilities still needed to issue invoices every day.

Context

  • The manual invoice-consolidation process had many steps and was prone to error.
  • The previous invoice-consolidation software provider had stopped operating.
  • At the time of delivery, MISA did not provide an API for this exact process.
  • Daily invoice volume across three facilities caused significant delays.

Approach

  • Built a new BOT around the business workflow, with no dependency on the former provider.
  • Integrated directly with MISA and handled missing API functions through controlled UI actions.
  • Sent automatic emails based on processing status.
  • Added an exception dashboard showing which invoice failed and at which step.

Outcome

  • Automated 16,853 invoices across all three facilities.
  • Main facility: 12,601 invoices from May 2025 to April 2026; District 7: 837; General Hospital: 3,415.
  • Removed manual invoice issuance and provided real-time status tracking.
16.853Invoices automated 12.601Main facility, May 2025 – April 2026 3Facilities 0Manual issuance steps remaining
BOT running the invoice workflow
BOT running the invoice workflow
Invoices waiting to be processed
Invoices waiting to be processed
Processing status for each invoice
Processing status for each invoice
Validation step before issuance
Validation step before issuance
My roleCurrent-process discovery, replacement-flow specification, exception-dashboard design, operations, and ongoing refinement.
MISABusiness Workflow BOTAutomated emailDashboard
B-01
B-02
B-02 Healthcare · Process comparison

ENT Hospital — Before and After

The same work, shown under two operating models.

StepOld processAfter automation
Data consolidation Staff collected figures from several screens and copied them into a spreadsheet. The BOT read data on schedule with no manual copying.
Invoice creation Staff entered each invoice in MISA, with one person responsible for each facility. The BOT worked in MISA following the specified business sequence.
Error checks Errors were found after issuance and required corrective work. Pre-issuance checks stopped errors and recorded the reason for each stop.
Status tracking Staff had to ask the person responsible for each facility. A shared dashboard showed real-time status.
Notifications Sent manually when someone remembered. Automatic email based on processing status.
Volume Limited by available staff 16,853 invoices across 3 facilities
Invoice summary by facility
Invoice summary for each facility
Step-by-step processing log
Step-by-step processing log
Exceptions and stop reasons
Exceptions and stop reasons

This comparison was reconstructed from the process description and operating figures in the project documents.

B-02
B-03
Bot extracting shipment details
Updating an order in the internal system
The bot collects shipment details, then updates the internal systems
B-03 E-commerce · Logistics · Live operations

Update Tracking Bot

Updated Amazon shipment details in two internal systems at the same time.

Context

  • Entering Amazon shipment data manually took about 5 minutes per order.
  • The 3–5% error rate led to customer complaints.
  • About 20 hours each week were spent on repetitive data entry.

Approach

  • Used Conductify AI browser automation to sign in to Amazon and collect shipment details.
  • Orchestrated the steps with n8n.
  • Stored action logs and reconciliation data in MySQL.
  • Used an Apizer script to update both internal platforms at the same time.
  • Updated multi-item orders atomically; any failure rolled back the entire order.

Outcome

  • Reduced manual entry time from about 5 minutes per order to zero.
  • Reduced the error rate from 3–5% to below 0.1%.
  • Saved about 20 working hours each week.
<0.1%Error rate, down from 3–5% 20 hoursSaved each week 2Platforms updated in parallel 0Minutes of manual entry per order
Implementation details
  • Source data covered orders from several markets and intermediate warehouses in different countries.
  • Shipments arrived in several batches, so orders had to be consolidated without breaking tracking accuracy.
  • MySQL logs supported reconciliation when a complaint was raised.
RoleDeveloper. Built the automation, designed atomic updates and rollback behavior, and measured the before-and-after results.
Conductify AIn8nMySQLApizerAmazon
C-00
Group C Platform products

Platform Products

Five SaaS platforms built to serve multiple clients through user accounts or service plans, with operating metrics tracked for each product.

5+Products 1.236User-created agents 790Agent-platform users 237+Users with a transaction after 1 month

Agent and user totals come from Conductify. The transaction-user figure comes from MentorX. Each metric is shown with the product it belongs to.

C-01
C-01 SaaS platform · Browser automation

AI Co-Worker

Turns an authenticated browser session into an agent that works directly on websites.

Context

  • Organizations needed to automate closed systems such as CRMs, social networks, and portals with no public API.
  • Traditional scraping tools were easily blocked by Cloudflare, CAPTCHAs, and anti-bot controls.
  • XPath and CSS selectors broke whenever an interface changed, creating high maintenance costs.
  • Non-technical users could not build their own automated workflows.

Approach

  • A Chrome extension ran inside the user's real authenticated session.
  • Visual Grounding inserted numbered markers into the DOM and took a screenshot, allowing a vision model to identify the correct click coordinates.
  • Used the Chrome DevTools Protocol to simulate real mouse and keyboard input.
  • A Spatial Element Locator found elements by relative position instead of fragile selectors.
  • A drag-and-drop workflow builder let non-technical users create automations.

Outcome

  • Automation ran inside a real authenticated session, avoiding many anti-bot barriers.
  • Agents adapted to interface changes instead of breaking like fixed selectors.
  • Turned almost any web interface into an integration point callable from another system.
5Architecture layers 8Node groups 30+Node types in the workflow builder 30+Functional requirements in PRD v1.2
Natural-language instructions
Natural-language instructions
Agent repeating actions on a page
Agent repeating actions on a page
CV-screening tool built on the platform
CV-screening tool built on the platform
Tool management dashboard
Tool management dashboard
Drag-and-drop workflow builder
Drag-and-drop workflow builder
Node groups in a workflow
Node groups in a workflow
AI Co-Worker extension after browser installation
Installed extension
AI block for model selection and instructions
AI block: model and instruction selection
Five-layer architecture and personal contribution
  • Internet/Relay — an HTTP proxy server receives commands from external systems.
  • Background — a Service Worker routes messages, manages tabs, and connects to model APIs.
  • Content Scripts — injected into the page to analyze the DOM and perform actions.
  • AI/NLP — Vision Grounding turns natural-language instructions into interface coordinates.
  • Execution — the Apizer Engine interprets workflows and manages the action queue.
  • My contributions included a two-way HTTP Relay architecture; message transport across iframes and isolated Shadow DOM; a Visual Grounding pipeline connecting multimodal models to CDP; a spatial element locator based on BoundingRect intersections; and PRD v1.2 with more than 30 functional requirements across 6 phases.
My rolePRD authoring, relay architecture and element-location design, and coordination of the vision-pipeline implementation.
Chrome ExtensionChrome DevTools ProtocolGPT-4o Gemini VisionBlocklyApizer Engine
C-01
C-02
C-02 Education platform · Live operations

MentorX

Community, courses, and mentor bookings on one platform, with Vietnamese payment support.

Context

  • The local market lacked an affordable platform combining community, courses, and bookings.
  • International platforms were expensive and did not support Vietnamese payment methods.
  • Instructors needed to protect videos from redistribution and charge by membership level.

Approach

  • Three separate services: a Next.js application, a real-time Socket.IO server, and an FFmpeg media processor.
  • Transcoded video into three quality levels, streamed it through HLS, encrypted it with AES-128, and added a viewer-specific watermark.
  • Four membership levels controlled access to content.
  • Integrated PayOS and SePay VietQR, with atomic transactions and electronic invoices.

Outcome

  • More than 237 active users completed a transaction within the first month.
  • More than 60 major features running in production.
  • Video used a dedicated protection layer instead of a direct embed from a public service.
237+Users with a transaction after 1 month 121API endpoints 40+Database tables 60+Major features
Learner dashboard
Learner dashboard
Course page
Course page
Lesson screen
Lesson screen
Community area
Community area
Four membership levels
Four membership levels
Course file and document management
Course file and document management
MentorX learning-group list
Learning-group list
MentorX class and consultation calendar
Class and consultation calendar
Modules and codebase scale
  • Modules — LMS (classes, courses, lessons, progress, certificates); four membership levels; video DRM; community (posts, comments, polls, mentions); messaging; mentor bookings; and payments.
  • Platform — Next.js 15, React 18, TypeScript, PostgreSQL 16, S3-compatible MinIO, and Socket.IO with JWT authentication.
  • Scale — 386 TypeScript files, 156 React components, 121 API endpoints, more than 40 tables, 35 migrations, more than 45 indexes, and more than 15 triggers and functions.
  • Three permission groups shared one dataset while retaining separate learning groups and consultation calendars.
My roleProduct specification, membership-tier and payment-flow design, business testing, and operations.
Next.jsPostgreSQLSocket.IOFFmpeg HLSMinIOPayOSSePay
C-02
C-03
C-03 AI agent platform · Live operations

Conductify

A low-code platform where users can build their own AI agents.

Role

  • Business analysis for platform features.
  • Manual quality control before releases.
  • User-experience improvements in the agent builder.

Recorded

  • 1,236 agents created by platform users.
  • 790 users.
1.236Agents created 790Users
Agent list on the platform
Agent list on the platform
Agent configuration screen
Agent configuration screen
User management
User management
RoleBusiness Analyst and Manual QA.
Low-codeAI Agent
C-03
C-04
C-04 SaaS platform · Desktop application

Crawbot

A desktop application that brings multiple AI providers and chat channels into one place.

Problem

  • Each model provider had its own key, interface, and calling method.
  • Daily recurring tasks had to be started manually every time.
  • Replies were scattered across several chat channels.

Approach

  • Created one setup screen for multiple AI providers, allowing model changes without changing the workflow.
  • Built a skill library where each skill represented a ready-to-run task.
  • Scheduled recurring tasks to start automatically.
  • Connected chat channels so messages could be received and answered inside the application.

Recorded

  • One configuration point replaced several separate tools.
  • Scheduled work ran without someone pressing a button.
Application dashboard
Dashboard
In-app chat
Chat
Connected-channel management
Connected channels
Ready-made skill library
Ready-made skills
Automated scheduling
Automated scheduling
Receiving and answering Zalo messages in the app
Receive and answer Zalo messages
My roleDefined the problem, designed the skill and scheduling structure, and used the product in daily work.
Desktop appMultiple AI providersZaloCron

This page shows the main workflow in the product interface.

C-04
C-05
C-05 Data platform · Graph-based Q&A

Knowledge Graph

Built a knowledge graph from enterprise documents, then answered questions using that graph.

Problem

  • Text-chunk search returned isolated passages without showing relationships between entities.
  • Similarity search could not answer questions that crossed several documents.
  • Users found it difficult to verify where an answer came from.

Approach

  • Extracted entities and relationships from documents and represented them as nodes and edges.
  • Grouped data by topic to reveal dense areas and gaps.
  • Traversed graph edges for Q&A and linked answers back to their source nodes.
  • Built an admin interface to view, filter, and query the graph directly.

Recorded

  • Relationships became visible instead of remaining buried in text.
  • Answers could be traced back to the nodes and edges used.
Full knowledge graph
Knowledge graph
Entity and relationship cluster
Entity and relationship clusters
Graph-based Q&A
Graph-based Q&A
Knowledge-graph admin screen
Admin interface
Query result
Query result
My roleEntity and relationship modeling, graph-based Q&A design, and query-result testing.
Knowledge GraphEntity extractionQ&A

This page shows the knowledge structure and the main workflow in the product interface.

C-05
D-00
Group D Education and public sector

Education & Public Sector

Two types of work for related audiences: answering admissions questions for learners and digitizing paper records to reduce manual entry.

7+Projects 40+Academic programs in the knowledge base 1.000+Forms per admissions season 2024–2026Period

Program and form totals combine two projects at HIU.

D-01
Admissions-chatbot admin dashboard
Admissions-chatbot conversation count during peak season
D-01 Higher education · Live operations

HIU — Admissions Chatbot

More than 40 academic programs, 5 admission methods, and one peak season.

Context

  • Peak admissions season overloaded the advisory team.
  • The team had to advise on more than 40 programs across several faculties.
  • They also had to explain 5 different admission methods.
  • Slow responses caused the university to lose interested applicants.

Approach

  • The chatbot answered from official information for more than 40 programs on the university website.
  • Supported multiple languages and adjusted forms of address based on who was asking.
  • Interested-applicant details were recorded directly in Google Sheets.
  • n8n scheduled follow-up automatically after the conversation.

Outcome

  • Handled 1,370 conversations and 9,325 messages over 2 admissions months.
  • Covered more than 40 programs, including scholarship information.
  • Scheduled school visits during the conversation.
1.370Conversations 9.325Messages 40+Academic programs 5Admission methods
Implementation details
  • Intake channels: Facebook Messenger and the university website.
  • Knowledge came directly from the university website and followed its published updates.
  • The form of address changed depending on whether the user was a parent or an applicant.
My roleAnalyzed advisory needs, organized program information, designed interested-applicant capture, and operated the system during peak season.
RAGn8nGoogle Sheets Facebook MessengerWebsite
D-02
Extracting data from form images
Review interface before Excel export
Data is extracted from form images, reviewed, then exported to Excel
D-02 Higher education · Delivered

HIU — NeuronsAI Digitizer

A Chrome extension that digitized admissions records and replaced manual entry.

Context

  • Entering each form manually took 5–10 minutes.
  • Vietnamese names, addresses, and phone numbers were frequent sources of error.
  • Forms were submitted without complete data-integrity checks.
  • More than 1,000 forms arrived each season, creating a staffing bottleneck.

Approach

  • A Chrome extension read form images and extracted data through a Gemini API proxy.
  • Staff signed in with organizational accounts through Microsoft SSO and loaded images directly from OneDrive.
  • Vietnam-specific validation covered province and school lists, 10-digit carrier prefixes, Vietnamese names, and date normalization.
  • A review interface let staff correct data before exporting it to Excel.

Outcome

  • Reduced processing to under 1 minute per form, saving 85–90% of the time.
  • Reached more than 90% extraction accuracy and detected more than 95% of validation errors.
  • During peak season, 1–2 staff processed more than 1,000 forms instead of overloading a team of 2–5.
85–90%Time saved per form 90%+Extraction accuracy 95%+Validation-error detection 100Files per processing batch
Implementation details
  • Processed 100 files per session to control model-call costs.
  • Called Gemini through a proxy server so the API key was never exposed in the browser.
  • Integrated OneDrive through the Microsoft Graph API.
  • Implemented rules for Vietnamese diacritics, valid carrier prefixes, province and school matching, and normalized dates.
My roleData-entry process analysis, Vietnam-specific validation rules, review-interface design, and before-and-after measurement.
Chrome ExtensionGemini APIMicrosoft SSO Microsoft Graph APIOneDriveExcel
D-03
Admissions agent answering an applicant
The agent answers admissions questions directly in chat
D-03 Education · College · Live operations

Van Lang College

An admissions agent for applicants and parents.

Scope

  • Answered questions about programs, admission requirements, and tuition.
  • Used the same admissions-agent platform as other institutions in the group.

Recorded

  • Applicants received answers outside office hours.
My roleAdmissions knowledge setup, agent configuration, and operations.
RAGWebsite
D-04
University admissions agent
The agent answers questions about programs and admission methods
D-04 Higher education · Live operations

Thai Nguyen University

An admissions agent for a university system with several member institutions.

Scope

  • Answered admissions questions and directed users to the right institution.
  • Used the group's shared admissions-agent platform.

Recorded

  • Repeated questions were answered from one consistent information source.
My roleAdmissions knowledge setup, agent configuration, and operations.
RAGWebsite
D-05
D-05 Education · Online learning · Live operations

Galaxy Edu – Hocmai

A learner-support agent for an online learning platform.

Scope

  • Answered questions about courses and how to join classes.
  • Used the education group's shared agent platform.
My roleCourse knowledge setup, agent configuration, and operations.
RAGWebsite
D-05
D-06
D-06 Public sector · Live operations

Vietnam E-Commerce Authority

An information agent for a public-sector organization.

Scope

  • Searched and answered questions using documents supplied by the organization.
  • Used the group's shared Q&A agent platform.
My roleDocument-based knowledge setup, agent configuration, and operations.
RAG
D-06
D-07
Citizen Q&A agent
The Q&A agent answers citizen questions
D-07 Public sector · Live operations

Vietnam Fatherland Front — District 1

An online Q&A agent for citizens.

Scope

  • Answered common questions using documents supplied by the organization.
  • Preserved the wording of source documents when quoting information.

Recorded

  • Citizens received information outside office hours.
My roleDocument-based knowledge setup, agent configuration, and operations.
RAGWebsite
E-00
Group E Enterprise consulting & proposals

Enterprise Consulting & Proposals

Current-state discovery, multi-level stakeholder interviews, solution design, and pricing for large clients—the work before the first line of code.

5+Enterprise clients 25+Stakeholders interviewed 6Modules in the largest proposal 22Decisions recorded during negotiation

Clients in this group are anonymized by agreement; only their industry and scale are shown. The three figures above come from the same proposal for the diversified group on page E-02.

E-01
E-01 Automotive data analysis · United States · Discovery and solution design

US Automotive Data Company

A technical research agent running inside the client's infrastructure, with no data leaving its servers.

Five pain points found during discovery

  • Each vehicle manufacturer formatted technical bulletins differently: tables, lists, prose, and proprietary abbreviations.
  • Inputs varied from text PDFs and scanned documents to images, each requiring a different process.
  • A hard requirement: the system must not invent information. If uncertain, leave the field blank.
  • Output had to match the client's dictionaries for model years, fault names, and part names.
  • The team was manually collecting technical Q&A from forums and videos.

Solution design

  • A 10-step process turned source files into structured data.
  • Three anti-hallucination layers: dictionary matching, cross-field validation, and detection of model-inferred content.
  • Automated parts-price collection from more than 30 manufacturer websites.
  • A forum and video Q&A collector with automatic model-year classification.
  • Validation results were used to adjust the AI's instructions before the revised version was deployed again.
  • A manufacturer-level accuracy dashboard with alerts for declining performance.

My contribution

  • Analyzed real data samples and identified five core challenges.
  • Designed the 10-step data-processing flow.
  • Used a measure-first, commit-later approach: establish a baseline before accepting a target.
  • Structured three packages with a clear upgrade path.
  • Defined acceptance metrics by data-field type and manufacturer.
PackageScopeTimelineInvestment
A — Foundation AI infrastructure, a working first version, and baseline measurement. About 6 weeks ≈ USD 12,000
B — Production rollout Production-ready technical-bulletin extraction plus the Q&A collector. About 4–5 months ≈ USD 23,000–25,000
C — Self-improvement Both systems in production, a self-improvement loop, and client ownership. About 8–9 months ≈ USD 38,000–42,000
My roleData discovery, architecture design, package structure, and acceptance metrics.
On-premiseThree-layer hallucination controlDictionary normalizationDSPy

Content is shown within the agreed scope; the client's identity is withheld under a confidentiality agreement.

E-01
E-02
E-02 Diversified group · Real estate, hospitality, education · Solution design

Diversified Group with 4,500+ Employees

An enterprise-wide AI roadmap for internal infrastructure.

Five pain points

  • Documents were scattered across several locations, and employees spent hours searching manually.
  • Procurement checked several sources without retaining price history.
  • HR collected candidate profiles manually, taking days per role.
  • Organization charts in slides and spreadsheets quickly became outdated.
  • Handwritten meeting notes missed action items.

Approach

  • Interviewed 25+ stakeholders across executives, managers, and frontline staff.
  • Assessed AI readiness in five dimensions to choose a starting point.
  • Selected four capabilities for the first release and deferred two to a later phase.
  • Proposed transferring the project source code while retaining ownership of the core technology.
  • Used Vietnamese market pricing and explained every item.

Delivered outcome

  • All six capabilities had their own measurable acceptance criteria.
  • Three packages with clear upgrade paths and timelines.
  • Twenty-two decisions recorded during negotiation.
CapabilityBusiness problemAcceptance metric
Internal research assistantAn internal chatbot searched the document repository and let users rate each answer.Immediate answers across thousands of files
Price trackingCollect, compare, and retain prices from several sources.≥90% accuracy, one run per day
Candidate sourcingScan recruitment channels and score candidate fit.Query <5 seconds, keyword match ≥80%
Organization chartsTurn text into charts matching the group template.Render <30 seconds, up to 500 nodes
Meeting assistantTurn meeting audio into minutes and action items.Word error rate ≤15%, action-item capture ≥80%
Supplier sourcingCollect supplier data from public sources.Successful extraction ≥85%
Five lessons from enterprise pricing and negotiation
  • Start with Vietnamese market pricing, not global prices followed by discounts.
  • Separate recurring core-technology fees from project implementation costs at the start.
  • Reduce the entry barrier by narrowing phase one: VND 350 million instead of VND 725 million.
  • Do not price intellectual property line by line. State the assets and their total value.
  • Check more than 15 risk terms before sending, including “permanent,” “100%,” and competitor names.
  • Three packages: Foundation at about VND 725 million over 2 months; Standard at about VND 2.76 billion over 7 months; Comprehensive at about VND 4.2 billion over 10 months.
My roleInterviews, readiness assessment, phased capability design, business model, and pricing.
Local AIKnowledge GraphPyramid InterviewAI Readiness

Content is shown within the agreed scope; the client's identity is withheld under a confidentiality agreement.

E-02
E-03
E-03 Restaurant chain · F&B · Discovery and solution design

Restaurant chain with 400–500 locations

High-volume, year-round recruitment across several provinces, with frequent employee turnover.

Proposal scope

  • A 24/7 recruitment chatbot accepting applicants at any time.
  • Applicant routing to the right location and role.
  • End-to-end status tracking for every applicant.
  • Onboarding through short lessons broken down by shift.

Roadmap

  • Quick win: launch the chatbot and routing to show early results.
  • Mid-term: centralize applicant status and recruitment data.
  • Long-term: transform both recruitment and initial training.

Estimated impact

  • Reduce hiring time from 4–5 days to about 1 day.
  • Reduce the risk of losing applicants by an estimated VND 15–45 million per month.
  • Reduce the risk of poor hiring decisions by an estimated VND 300–750 million per month.
My roleRecruitment-process analysis, chatbot-flow design, and a three-step roadmap.
Recruitment chatbotApplicant routingMicro-learning

Impact figures are estimates from the proposal; the client's identity is withheld under a confidentiality agreement.

E-03
E-04
E-04 Coffee · Manufacturing and F&B · Discovery and solution design

Leading Vietnamese Coffee Group

An AI transformation program spanning communications, factory operations, and internal training.

Three proposal tracks

  • Communications and marketing agents targeting 80% workload automation.
  • AI Vision for factory operations.
  • An AI capability program for employees.

Communications modules

  • Create content in several formats.
  • Analyze the market.
  • Check compliance before publishing.
  • Keep the brand voice consistent across channels.

Framing the solution

  • Designed a multi-track program rather than a standalone chatbot.
  • Included training from the start so users could keep pace with the tools.
  • Separated compliance and brand voice from content creation instead of combining them into one module.
My roleNeeds discovery, program-track design, and communications-module design.
AI AgentAI VisionBrand voiceInternal training

The 80% automation target comes from the solution proposal; the client's identity is withheld under a confidentiality agreement.

E-04
E-05
E-05 Coffee chain · F&B · Discovery and solution design

Coffee Chain with 12 Branches

Payroll automation for a multi-branch chain, organized into four modules.

Four modules

  • Process timekeeping data from each branch's attendance device.
  • Consolidate data from all 12 branches.
  • Create payslips using the chain's payroll rules.
  • Route employee questions about payslips.

Estimated impact

  • Reduce attendance-entry time by 90–95%, equivalent to 30–40 hours per branch each month.
  • Save 2–3 days each month on data consolidation.

Budget

  • Implementation: about VND 115–119 million.
  • Operations: about VND 1 million per month.
  • The budget was sized for a 12-branch chain rather than a large-enterprise pricing model.
12Branches 4Modules 30–40 hoursPer branch, per month
My rolePayroll-process analysis, module breakdown, and implementation budgeting.
TimekeepingPayrollMulti-branch consolidation

Impact figures are estimates from the proposal; the client's identity is withheld under a confidentiality agreement.

E-05
F-00
Group F ERP & international trade

ERP & International Trade

The work before AI: requirements, process mapping, ERP delivery, cross-border storefront operations, and sourcing.

13ERP modules in use 3Alibaba storefronts +329%Search impressions 8Product categories sourced

The module total comes from the internal ERP project on page F-01. The impression increase comes from the three Alibaba storefronts on page F-04, rising from 91,000 to 390,000.

F-01
F-01 Cross-border e-commerce · ERP implementation

Internal Odoo ERP

About 13 modules, from requirements through production launch and user training.

Scope

  • Focused on HR: attendance, leave, employee records, payroll, and recruitment.
  • Also covered operations modules for sales, inventory, projects, and vehicle booking.
  • Worked directly with four departments: HR, accounting, R&D, and finance.

Approach

  • Mapped the current process in BPMN before configuration.
  • Documented attendance rules and reconciled them with the manual calculations in use.
  • Specified the attendance-device integration parameters, with a definition for every field.
  • Wrote end-user guides and trained each department separately.

Recorded

  • Thirteen modules running with internal users.
  • Attendance rules became documented knowledge instead of remaining with one person.
Attendance-process BPMN diagram
Attendance-process BPMN diagram
Attendance calculation rules
Attendance calculation rules
Attendance API parameter table
Attendance API parameter table
Data-field definitions
Data-field definitions
Guide for connecting attendance devices to the ERP
Attendance-device integration guide
My roleRequirements, business documentation, configuration, user acceptance, production launch, and training.
OdooBPMNBRD/SRSUATInternal training
F-01
F-02
F-02 Rail transport · Product research

Ratraco Solutions – Wokatech

Product research and solution options for a North–South rail container operator.

Context

  • A North–South rail container operator with more than 20 years of experience.
  • The company needed to choose a suitable transport-management platform based on fit, not brand recognition.

Approach

  • Analyzed competitors and the Vietnamese logistics-software market.
  • Compared Vietnamese TMS, FMS, and logistics ERP products across six areas: order management, transport operations, fleet management, accounting, reporting, and access control.
  • Presented the comparison so decision-makers could choose against clear criteria rather than intuition.

Recorded

  • The six comparison areas became a reusable evaluation framework.
  • The outcome was a side-by-side product comparison, not a one-sided recommendation.
My roleMarket research, product-comparison framework, and solution presentation.
TMSFMSLogistics ERPCompetitor analysis
F-02
F-04
F-04 Agricultural exports · B2B storefront operations

Alibaba

Three agricultural export storefronts: macadamia nuts, cashews, and coconuts.

Scope

  • Managed three storefronts at the same time.
  • Published products, sent quotations, and handled inquiries.
  • Tracked and optimized three metrics: impressions, clicks, and inquiries.

Approach

  • Read the impression-to-inquiry funnel to locate bottlenecks.
  • Adjusted listings and keywords using data rather than intuition.
  • Maintained response rates and regular posting, two factors affecting search visibility.

Outcome

  • Increased search impressions by 329%, from 91,000 to 390,000.
  • Measured the funnel by period and compared each month with the previous one.
+329%Search impressions 91K → 390KImpressions 3Storefronts
Storefront metrics
Storefront metrics
Response rate and post count
Response rate and post count
Impression-to-inquiry funnel
Impression-to-inquiry funnel
Following month's result
Following month's result
Advertising metrics by period
Advertising metrics by period
My roleStorefront operations, data-led listing optimization, inquiry handling, and quotations.
AlibabaB2BAgricultural exportsFunnel optimization
F-04
F-05
F-05 Import-export · Sourcing

Market Research & Sourcing

Sourcing and supplier or contract-manufacturer coordination across several product categories.

Work covered

  • Found and screened suppliers against each order's requirements.
  • Negotiated prices and delivery terms.
  • Worked with contract manufacturers on products made to specification.
  • Researched target markets before selecting a source.

Eight product categories

  • Eco-friendly fabrics.
  • Cashews.
  • Macadamia nuts.
  • Coconuts.
  • Rice for the Ghana market.
  • Gloves and protective equipment.
  • Leather goods.
  • Scented bags.

Recorded

  • Each category had its own supplier criteria rather than one generic checklist.
  • This experience also supports supply-chain business analysis.
My roleMarket research, sourcing, price negotiation, and contract-manufacturer coordination.
SourcingSupplier negotiationExport
F-05
G-00
Group G How I work with AI

How I Work with AI

A custom toolkit for BA and PM work: requirements discovery, planning, modeling, specification, change tracking, and output quality control.

69Business-analysis skills 8Specification workflows 34Automated hooks 18Role-based agents

Counts were taken directly from my workstation on August 24, 2026. The toolkit supports the full BA and PM lifecycle, from discovery and planning to change management and quality control.

G-01
G-01 Business-analysis skill set

69 business-analysis skills

Each custom skill handles one specific BA task with a defined input and output. The six groups below cover the work from requirements discovery through document approval.

Requirements discovery · 4 skills
  • Create interview questions for each stakeholder role instead of reusing one generic list.
  • Read client documents and surface requirements that were not stated directly.
  • Review interview notes and flag missing information before specification begins.
Local commandselicitation-qna-gen · stakeholder-doc-analysis · interview-doc-gen · elicitation-validate
Modeling · 5 skills
  • Turn business descriptions into BPMN processes so everyone can see each step and handoff.
  • Build data models, data flows, and sequence diagrams that connect business requirements to system design.
Local commandsbpmn-doc-gen · erd-gen · dfd-level-0-gen · sequence-spec · concept-modeling
Specification · 5 skills
  • Write user stories for the correct use-case type so create, read, update, and integration flows are not missed.
  • Extract business rules and processing conditions into items that can be reviewed, tested, and handed over.
  • Combine approved material into a consistently structured product requirements document.
Local commandsuser-story-by-uc-type · us-cud-spec · business-rules-extract · integration-spec · prd-create
Impact analysis · 4 skills
  • Trace a requirement to related documents and system areas before proposing a change.
  • Compare the current and target states to identify gaps and required scope.
  • Assess what a requirement change affects so the team neither misses work nor changes unrelated areas.
Local commandsimpact-analysis · traceability-sync · gap-analysis · change-sync-router
Visualization · 4 skills
  • Build interface mockups from requirements so clients can review and respond before development.
  • Specify components, states, and screen behavior to reduce conflicting interpretations.
  • Turn an approved sketch into a working mockup for discussion and flow validation.
Local commandsform-mockup-gen · ui-spec · layout-brainstorm · html-to-nextjs-code-gen
Quality control · 4 skills
  • Review documents for vague, unsupported, or untestable requirements.
  • Reconcile use cases with the data model before approval.
  • Check specification type and output structure so every requirement follows the right workflow.
Local commandsprd-validate · elicitation-validate · uc-dm-reconcile · us-type-classifier

These 69 BA skills sit within a local library of 195 skills; the remainder cover technical work outside BA. Command names are retained as implementation evidence. The table shows representative commands rather than the full list.

G-01
G-02
G-02 Specification workflow · Quality criteria

Quality-Controlled Specification Workflow

Eight connected steps, with each output feeding the next. Before delivery, documents are reviewed against principles tied directly to implementation and handover.

01 Discover requirements 02 Analyze gaps and processes 03 Define the product 04 Design the 05 interface 06 Specify user stories 07 Analyze change impact 08 Run an end-to-end check

Step 08 reruns checks across the full chain to find conflicts between documents; it does not create a new document.

Match real work

  • The description must match the operating process. If a rule has not been confirmed with users, mark it as an assumption instead of filling the gap.

Cover all scenarios

  • Specifications must include alternate flows, exceptions, and system responses, not only the happy path.

One interpretation

  • Each sentence should carry one meaning. Field names, states, and terms stay consistent across documents.

Ready to implement

  • Developers should be able to build and testers should be able to write cases without asking again about the main intent.

These four principles apply to outputs from all eight steps, not to one specific project.

G-02
G-03
G-03 Hooks · Agents · Commands

Workflow Automation

A custom automation layer handles repeated work: retaining project context, controlling risky actions, assigning work by role, and wrapping up each session.

GroupCountPurpose
Automated hooks 34 Thirty-four hooks run at 9 points in the session lifecycle, from loading context to wrap-up. They retain project rules, check risky write areas, and update work status without relying on memory.
Role-based agents 18 Eighteen roles have separate scopes and permissions, so each agent receives only the right work: planning, research, coding, testing, review, documentation, project management, interface design, or data administration.
Commands 50+ More than 50 commands package recurring work into reusable workflows: planning, coding, testing, review, documentation, presentation, context retention, and version management.
Output detail levels 6 Six levels tailor the same material to its reader, from business users who need a clear conclusion to technical users who need implementation evidence.

Why build it

  • Questioning, recording, reconciliation, and review are packaged as reusable workflows.
  • A fixed structure keeps output consistent across work sessions.
  • Documented steps help new team members take over without relying on verbal handover.

Safety principles

  • Hooks check overwrite operations and warn when content may expose confidential information.
  • Client-project context remains on the workstation.
  • A responsible person reviews every system-assisted document before it is shared.

Where it appears in this portfolio

  • The toolkit supported the specifications presented in group E.
  • The document extraction and normalization work in group F also used this tool layer.

The command count is shown as 50+ because the command set changes weekly. The counts of 34 hooks, 18 agents, and 6 detail levels were taken directly from the workstation on August 24, 2026. Screenshots are omitted from this group to avoid exposing client-project content.

G-03
H-00
Group H Personal assistant

Personal Assistant

Assistant workflows I built for personal use and to teach learners how to run them on their own computers: reading files, entering data into systems, running on schedule, and supporting role-specific work.

20Scenarios with video 56Role-based scenarios 9Business roles

The library includes 20 screen-recorded scenarios and 56 scenarios across nine roles. Some videos and scenarios are simulations, and all displayed data is sample data.

H-01
Morning briefing prepared by the assistant and viewed on a phone
Assistant scanning a folder and organizing files by type
A scheduled morning briefing and folder cleanup — real screen recordings
H-01 Everyday work

Everyday Work

Four assistant workflows I built for personal use and to teach learners how to run them on their own computers.

Run on schedule

  • Prepare a morning briefing — combine important email, meetings, and industry news into one summary delivered before work.
  • Control a computer from a phone — send a remote instruction, let the office computer perform it, and receive the result.

Clear the backlog

  • Clean up and organize files — scan a disorganized folder, identify file types, rename files, and put them in the right place.
  • Process meeting notes — extract decisions, action items, and owners, then send reminders by due date.

How this differs from a chatbot

  • A chatbot answers questions. These assistants work with real files and applications.
  • Tasks start on schedule instead of waiting for someone to ask.
ExamplesFour scenarios from the 20-video practical library; some workflows use simulated sample data.
Scheduled runsFile operationsRemote control
H-02
H-02 Data and finance

Data & Finance

Five scenarios that turn scattered documents into usable decision-making data.

Documents to tables

  • Paper invoices to a tax statement — read a folder of PDF invoices, extract the supplier, date, amount, and tax, then place them in a statement.
  • Consolidate invoices in one spreadsheet — normalize documents with different formats into one column structure.

Raw data to reports

  • Clean and structure data — standardize inconsistent values across files and produce a usable management table.
  • Turn raw data into a complete report — analyze survey or CSV data and write findings with charts.

Continuous monitoring

  • Build and publish a dashboard — create a shared dashboard that updates when source data changes.
  • The common outcome is a ready-to-use file, not an answer inside a chat window.
Assistant reading PDF invoices and completing a tax statement
Raw data turned into a report with charts
Team dashboard built and published automatically

Images come from practical and simulated videos; all displayed data is sample data.

H-02
H-03
H-03 Sales and marketing

Sales & Marketing

Eleven scenarios covering market research, clean customer data, content production, and sales tools.

Research and monitoring

  • Research a market on Reddit — collect discussions and product reviews, then group them by topic.
  • Analyze competitors through the Meta Ads Library — collect active ads and compare messaging and frequency.
  • Assist with online shopping — find products against criteria and add them to the cart.
  • Update CRM records from Gmail — read email threads, extract opportunity details, and write them back to the CRM.

Content

  • Create a presentation from brand guidelines — research the topic and build slides that follow the brand template.
  • Create visual content and publish it on social media — write the post, create an accompanying image, and schedule publication.
  • Turn a video into short clips — read the transcript, select strong segments, and export the clips.
  • Turn company documents into a portfolio — read contracts and operating documents, then write a company profile.

Build tools and pages

  • Build a landing page and newsletter — create a campaign page and a related customer email.
  • Build a mobile application — write and revise code from a requirements description.
  • Build a web application — use the same process for an internal tool.
Collecting competitor ads from the Meta Ads Library
Updating CRM customer records from Gmail
Building a landing page and campaign newsletter
Creating visual content and scheduling social posts
Creating a presentation from brand guidelines

Some scenarios are simulations; images use sample data.

H-03
H-04
H-04 Role-based library

56 Scenarios Across 9 Roles

Each scenario explains why a standard chatbot cannot complete the work—the line between an assistant that answers and one that takes action.

RoleScenariosRepresentative exampleWhy a standard chatbot falls short
CEO8Track decisions and commitments after meetingsRequires long-term memory, structured storage, and automatic reminders.
Marketing Director8Analyze cross-channel marketing performanceRequires data from several sources to be combined and normalized.
Sales Director8Flag sales opportunities at riskRequires continuous CRM analysis against historical patterns.
Sales Representative8Update the CRM after every interactionRequires event capture, structured extraction, and write-back to the system.
Marketing8Produce a campaign landing pageRequires both copywriting and a working page.
Customer Support4Classify and route tickets automaticallyRequires ticket-system integration, routing rules, and automated action.
Human Resources4Onboard new hires by roleRequires internal documents and a repeatable workflow for each person.
Finance4Reconcile invoices, contracts, and paymentsRequires document extraction, matching, and exception handling.
Operations4Track process bottlenecksRequires event data, process state, and early warnings.
View all 56 scenarios

CEO

  • Prepare context before a meeting.
  • Track decisions and commitments.
  • Create a weekly executive report.
  • Flag unusual metrics.
  • Model business scenarios.
  • Prepare board-meeting materials.
  • Track strategic projects.
  • Maintain a company decision repository.

Customer Support

  • Classify and route tickets.
  • Draft context-aware responses.
  • Track SLAs.
  • Analyze the voice of the customer.

Marketing Director

  • Analyze cross-channel performance.
  • Automate performance reports.
  • Monitor competitor marketing.
  • Flag campaign-budget risks.
  • Write data-informed campaign briefs.
  • Review brand consistency.
  • Model channel attribution.
  • Monitor market response.

Human Resources

  • Onboard by role.
  • Coordinate interview workflows.
  • Summarize interview feedback.
  • Provide an internal policy portal.

Sales Director

  • Flag opportunities at risk.
  • Forecast revenue.
  • Detect stalled opportunities.
  • Analyze sales-coaching needs.
  • Control CRM data quality.
  • Assign prospective customers to the right salesperson automatically.
  • Analyze wins and losses.
  • Prepare weekly sales meetings.

Finance

  • Reconcile invoices, contracts, and payments.
  • Track overdue invoices.
  • Report budget against actual spending.
  • Forecast cash flow.

Sales Representative

  • Summarize an account before a call.
  • Track buying signals.
  • Run controlled personalized outreach.
  • Update the CRM automatically.
  • Track follow-up actions.
  • Create account-specific proposals.
  • Handle post-call work.
  • Build a customer ROI calculator.

Marketing

  • Repurpose webinar content.
  • Collect content ideas.
  • Manage the content-production workflow.
  • Check analytics tagging.
  • Produce campaign landing pages.
  • Analyze content performance.
  • Monitor competitor content.
  • Maintain a searchable content library.

Operations

  • Track process bottlenecks.
  • Run supervised standard workflows.
  • Automate operations reporting.
  • Detect unusual transactions.

The full list of 56 scenarios appears only on screen. The print version keeps the nine-role summary so it fits on one page.

H-04
I-00
Group I Content & creative

Content & Creative

Content generated under brand control, video built from a written process, and a branded storefront run on Amazon.

3Brand control layers 2Video production routes ≈15'From raw footage to finished cut 3Shorts delivered for a client

The three control layers come from page I-01. The two production routes and the 15-minute mark are my own tests, timed on my own machine, recorded on page I-02. The three shorts are client work, made to a normal brief and schedule.

I-01
Building a video from a reference character, previewing it, then approving and exporting
Four brand character options, each with its own approve and download control
From one line of description to a preview cut, then to the map of the brand library
I-01 In-house product · Simulated data

Brand Content Studio

The brand guideline stops being a PDF and starts controlling what gets made.

The problem

  • AI makes content fast. Nobody checks it against the brand.
  • The rules are scattered across dozens of files.
  • Nothing catches a mistake before it goes out.

What it does

  • You ask the brand rules a question instead of hunting through a PDF.
  • Every image it makes is checked against the logo and the rules.
  • Video is built from a reference image and one line describing the action.
  • Nothing leaves the system without someone pressing Approve.

Why it matters

  • The knowledge base and document search here sit on brand assets, not technical documents.
  • It reads what a studio actually has, InDesign files included.
  • Blocked keywords, a competitor blocklist and an approval gate keep client assets where they belong.
Details
  • Three layers of control: filter the request, limit the topics, check the result before it appears.
  • The competitor blocklist is set per brand.
  • Every screenshot here runs on simulated data. No real client document appears.
My roleBusiness analysis, the flow from guideline to finished content, and where the checks sit.
RAGBrand safetyKnowledge GraphGuardrailsApproval gate
Image studio with brand styles and a self-check step
Pick a brand style; the result is checked against the logo
Brand library showing its source documents
Guidelines, service standards, an InDesign flyer and product specs as the source
Screen for configuring blocked keywords and topics
Blocked keywords, limited topics and a competitor blocklist

An in-house product built to present to a bank. Vietnamese interface, simulated data, client not named.

I-02
I-02 Content production · Client work and my own tests

Two ways to a finished video, one habit: write the process down, then let it run

I run social media content for a client brand: scripts, edits and the production process behind them. No dragging a timeline; each step is a written command that can be re-run.

RouteInputWhat the machine didTime
From raw footage One uncut 4K clip, 32 seconds Speech to text, three takes kept, slow zoom added, audio cleaned, a headline banner made, captions with keywords highlighted, sound levelled ≈ 15 min
From a written script An eight-part script, no footage, no voice Voice generated, footage found for each scene, royalty-free music picked, word-by-word captions built, exported vertical ≈ 20 min
Vertical short: a location tour with captions burned into the frame
Vertical short with captions burned into the frame
Vertical short: a tax question answered with an on-screen data card
An on-screen data card answering one specific question
Interview-style short with a question card and a QR code
Interview format with a question card and a QR code on screen
Three consecutive scenes from the vertical video built entirely from a script
Vertical video built from a script: voice, footage, numbers and captions
Figma board managing the creative set for an Amazon storefront
Managing the creative set and its versions for an Amazon storefront

Speed is not the point

  • The process is written down, so someone else can run it without depending on one person's memory.
  • Every choice has its reason written next to it, and the better option if there were a budget.
  • There is a check at the end: cut points reviewed, length reconciled, captions verified.

Limits, upfront

  • The two routes in the table are my own tests, timed on my own machine. The three shorts are client work, made to a normal brief and schedule.
  • This suits templated content at volume. It does not replace a creative person.

Both routes have a step-by-step write-up, errors included.

I-03
I-03 Cross-border e-commerce · Store operations

Amazon FBA

Store and supply-chain operations, from product listings to inventory, costs, and profit and loss.

Operations

  • Published and optimized listings and managed ASINs.
  • Planned FBA shipments alongside production and transport plans.
  • Tracked inventory, periodic revenue, and profit and loss.
  • Managed the cost structure to understand profit by product.

Brand and channels

  • Developed the brand, product-image set, and trademark registration.
  • Built the brand storefront and ran on-platform advertising.
  • Researched and developed social channels for the products.
  • Handled post-sale customer care.
Profit-and-loss report
Profit-and-loss report
Cost-management workbook
Cost-management workbook
Revenue by period
Revenue by period
Inventory tracking
Inventory tracking
Shipping report
Shipping report
Product-image design board
Product-image design
Rendered storefront image set
Rendered storefront image set
Product introduction video
Product introduction video
My roleStore operations, inventory and shipping planning, cost management, and brand development.
Amazon FBAASIN managementAmazon AdsP&L
I-03
S-01
S-01 Engagement · Services

Three Ways to Work Together

Choose based on how clear the requirement is, not on company size.

EngagementBest whenWork coveredDelivered outcome
Discovery and proposal The problem is visible, but the right starting point is not clear. Interview stakeholders at several levels, establish a baseline, map the current process, and prioritize the problems. Current-state report, prioritized problem list, and an itemized proposal with costs.
Deliver one complete solution The requirement is clear and a working system is needed. Specify, build, test against business scenarios, train users, and launch in production. A system running on real data, operating documents, and trained users.
Phased partnership Several modules are needed and should be phased to control risk and cash flow. Split delivery into separately accepted phases. A later phase starts only after the previous one passes. Each module is handed over independently, with acceptance metrics written into the contract.

Pricing approach

  • Price after discovery instead of guessing before the current state is known.
  • Separate one-time and recurring costs so the buyer can see total cost of ownership.
  • Price by work item, with a clear explanation for each item.

Where this has been applied

  • Page E-01: three progressively broader packages for an automotive data company.
  • Page E-02: six modules, each with its own acceptance metric.
  • Page E-05: a smaller package for a 12-branch chain, with recurring costs shown separately.

I do not accept

  • Committing to a figure before establishing a baseline.
  • Building a leadership demo without a plan for real operations.

Costs are based on the scope of each problem. Group E includes examples from real proposals.

S-01
S-02
S-02 Delivery process

From Discovery to Acceptance

Six stages, each with a verifiable output. The next stage does not begin until the previous one passes.

01 Discover and measure the baseline 02 Propose and price 03 Specify and agree acceptance 04 Build and run the pilot 05 Expand and train 06 Accept and hand over

The baseline measured in step 01 is compared with the result in step 06. Without a baseline, there is no basis for claiming improvement.

PeriodWhat the client providesOutput
01 · DiscoveryFrontline users join interviews and demonstrate the real work.A current-state report with baseline measurements.
02 · ProposalAgree on scope and priorities.An itemized proposal with cost and timeline.
03 · SpecificationApprove the process, business rules, and acceptance metrics.Requirements and acceptance metrics written into the contract.
04 · PilotOne real user group and real data.A working narrow-scope version with error and exception logs.
05 · ExpansionOperations staff join training.A full-scope running system with user guides.
06 · AcceptanceReview new measurements against the baseline.Acceptance record against each agreed metric.

This phase structure comes from the proposal on page E-02, where a large project was split into smaller, separately accepted parts instead of one all-in contract.

S-02
S-03
S-03 Commitments · Data protection

Commitments & Data Protection

Terms made clear before work begins, so neither side has to guess when an issue arises.

Scope and acceptance

  • Each module has a numeric acceptance metric rather than a descriptive adjective.
  • Out-of-scope work is quoted separately instead of being added silently.
  • No promise of absolute accuracy. Any committed level includes its measurement conditions.

Data

  • Client data is used only for that project and never to train systems for another client.
  • For sensitive data, choose on-premise model execution instead of sending data to an external service.
  • Personal information is masked before it appears in documents or illustrations.

Handover

  • Handover includes custom source code, operating documents, and a training session.
  • The client owns custom work. Reusable foundation components are clearly identified as licensed.
  • Any recurring cost is separated from one-time cost in the initial quotation.
Client confidentialityThis portfolio anonymizes group E clients under confidentiality agreements and shows only industry and scale.
ImagesScreenshots have been edited to hide personal and client-identifying data.
FiguresMeasured figures identify their source. Proposal figures are clearly marked as estimates; the two are never combined.

These principles were applied in group E projects where contracts required on-premise model execution and commitment wording was reviewed before proposals were sent.

S-03
R-01
R-01 Profile · Work history

Work History

Four years of experience, including three years in project management and business analysis for AI products.

PeriodRoleMain work
07/2025 – 05/2026 Project Manager Managed up to 6 AI projects at once, from presales and prototypes to live operations. Led presales and solution design for the two largest enterprise proposals in this portfolio.
10/2024 – 06/2025 Delivery Lead Delivered more than 20 systems serving over 100,000 conversations. Reduced implementation time for one system from 2 months to 1 week.
02/2024 – 09/2024 AI Trainer / AI Engineer Trained and refined AI agents, and built business workflows and knowledge bases for the first projects.
06/2023 – 02/2024 Team Lead Led a research and development team delivering an internal ERP and a cross-border shipment-tracking workflow.
09/2022 – 06/2023 R&D Specialist Delivered about 13 ERP modules from requirements through production launch and training. Researched transport-management products in Vietnam.
07/2022 – 09/2022 R&D Intern Operated cross-border e-commerce storefronts, sourced products, and worked with suppliers.
6AI projects at once 20+Systems delivered 100.000+Conversations served 2 months → 1 weekImplementation time

Enterprise-consulting clients are anonymized under confidentiality agreements.

R-01
R-02
SAP Business Analyst Professional Certificate on Coursera
SAP Business Analyst Professional Certificate · Coursera
R-02 Education · Certifications

Education & Certifications

A university foundation in quality management, followed by certifications in business processes and ERP.

University

  • University of Economics Ho Chi Minh City, Bachelor's degree in Quality Management, 2019–2023.
  • Graduated with distinction; GPA 8.49/10.
  • Top 5 in the major.
  • Distinction Scholarship — Scholarship for outstanding performance in Academic and Extracurricular Activities.

Professional certifications

  • SAP Learning: Cloud ERP.
  • SAP Learning: SAP S/4HANA Sourcing and Procurement.
  • SAP Learning: E2E Business Processes in SAP Business Suite.
  • Coursera: Business Analyst in SAP.

Languages

  • Vietnamese: native.
  • English: TOEIC 855.
8,49/10GPA Top 5Across the major 855TOEIC
Relevant to my workThe certifications focus on business processes and ERP and apply directly to the projects in group F.
Quality ManagementSAPBusiness analysis
R-03
R-03 Awards · Recognition

Awards & Recognition

Recognition received during university.

RecordedAwarded byContent
Winner EPIC · Event Planner Planned and developed an event concept, sourced venues, balanced the budget, and pitched the proposal to a judging panel.
Second Prize Faculty-level Student Research Competition Student research project.
Distinction Scholarship University of Economics Ho Chi Minh City Scholarship for outstanding performance in Academic and Extracurricular Activities.
Top 5 in the major University of Economics Ho Chi Minh City Ranked across the major and graduated with distinction.

Relevant to my current work

  • The EPIC Event Planner role required creative thinking, planning, venue sourcing, budget management, and pitching to a judging panel—direct practice in solution design and proposal presentation.
  • The research project developed my ability to collect data and present evidence-based findings.

Recorded

  • Achievements are presented against their corresponding records and certificates.
R-03
99
99 Contact

Contact

This portfolio is updated regularly. Get in touch if you need the latest version or would like to discuss a specific project in more detail.

Emailhaluminhanh@gmail.com
Phone+84 768 008 880
LinkedInlinkedin.com/in/haluminhanh

We can discuss

  • The technical details of any project in this portfolio.
  • How each reported figure was measured and calculated.
  • Discovery and pricing for a specific business problem.

Notes about this portfolio

  • Clients in group E are anonymized by agreement; only their industry and scale are shown.
  • Screenshots have been edited to hide personal and client data.
  • This portfolio prints in landscape A4 and includes two content modes with three detail levels.
99