Clarify before decorating
If the goal and user are unclear, I do not rush into a framework or visual effects.
Tiay / Independent digital studioDigital design & development
Websites with character.Software with purpose.
I’m Trong An. I personally design, build, and hand over websites, web apps, and automation for businesses — from structure to a working product.
Discuss your projectSee the work ↗
Design · Build · HandoverFrom the first sketch to a working product.
01
Direct 1:1 collaboration
02
Clear scope before code
03
Source & handover notes
04
Responsive from day one
Start with what you need.
Choose a goal to explore a direction. The actual problem is reviewed before scope is agreed.
Help visitors understand and get in touch.
A website with clear messaging, identity and a practical next step lets customers explore before a conversation.
One collaborator. From idea to handover.
From brief and wireframes to interface and handover, I stay with the project so decisions do not get lost between layers.
No sales layer. No account layer. The person speaking with you is also accountable for the product.
Design for quick understanding
Content, spacing, and motion should help people know what to do next.
Hand over for continued use
Source, structure, and operating notes stay clear so the product can keep moving.
From conversations to a working system.
I like projects with real questions to answer: what customers need to do, what teams need to operate, and what the system has to handle.
CASE / 01
SYSTEM BUILDOmnichannel AI chatbot system
A system connecting conversations, customer data, and support workflows. The goal is stable operation, visible behavior, and a clean handover for real use.
ROLEProduct / Full-stack
FOCUSReliability & human handoff
HANDOVERBackend, dashboard & deployment
THE PROBLEM
Messages move through several processing steps, so the system needs duplicate protection, consistent data, and a clear point for human handoff.
HOW I BUILT IT
Webhook intake, queues, AI processing, data, and the dashboard are separated into clear layers so the system is easier to observe and extend.
Explore the architecture
Receive conversations
Webhooks bring channel messages into one intake layer for normalization and validation.
System flow explained • Select a layer to explore
01System architecture
02Backend & API
03Admin dashboard
04Automation & AI
05Deployment & handover
Which part do you need help with?
I work with a clear scope. We choose what needs to be built first, then pick the technology that fits it.
01
View service detailsBrand websites & landing pages
Distinct visual direction, clear messaging, fast performance, and calls to action that help turn visits into conversations.
02Custom web apps & internal software
Admin tools, operational systems, and business workflows built around how your team actually works.
03Chatbots & automation
APIs, workflows, and AI connected to remove repetitive work while keeping sensible human handoff points.
04Maintenance & ongoing development
Fixes, performance work, new features, and a codebase that remains understandable for the next person who touches it.
05AI workflow integration
Audit repetitive work, choose the right tools, and build prompts, templates, or workflows that fit real day-to-day operations.
Review. Try. Refine together.
I break the work into reviewable pieces so progress is visible before the final handover.
Understand the problem
Align on goals, users, content, and the real constraints around the project.
Shape the structure
Clarify wireframes, core flows, and visual direction before polishing details.
Design & build
Work in reviewable pieces so you can test and respond while the product is still taking shape.
Hand over
Deliver source, operating notes, and the context needed to keep the product healthy after the project ends.
Small studio. Personal attention.
I’m Huynh Nguyen Trong An. I personally take the brief, design, build, and hand over suitable web, software, and automation projects.
That keeps feedback fast, decisions clear, and one direction intact from the first conversation to handover.
FAQ / TIAY
Before we start.
Questions that are usually useful to clarify before a project moves into design and development.
01Do I need a technical brief before we start?
No. Start with the goal, users, preferred timing, and what is getting in the way. The technical direction comes after the problem is clear.
02Will I receive the source code?
Yes. Source and the notes needed to keep operating or developing the product are part of the project handover.
03Can you take over an existing product or codebase?
Potentially. I review the codebase and current issues first, then define the scope for fixes, performance work, or further development.
04How long does a project usually take?
It depends on scope. Websites can often be estimated in weeks; web apps, chatbots, and integrations are usually split into reviewable stages.
Let’s make something worthwhile.
Send a few lines about the goal, timing, and what is getting in the way. I’ll read it before replying.
AFTER I RECEIVE YOUR REQUEST
01Clarify the real problem and what actually needs to be built
02Suggest an approach that fits instead of forcing a framework
03Confirm scope, milestones, and cost once the requirements are clear