Websites and products
Public sites, portals, SaaS products, directories, member systems, APIs, and internal tools built around a complete user task rather than a page count.
Work and capabilities
Build for the Thailand operation, not a generic export.
The useful starting point is the workflow already in place: who uses it, what must stay working, where the data goes, and what changes for people in Thailand.
Automation and integration
Connect CRM, identity, payments, documents, reporting, messaging, and operations with visible errors, safe retries, and a clear system of record.
Practical AI
Assistants, retrieval, classification, research, and workflow support with defined data access, human review, evaluation, and a fallback when the model is wrong.
Repair and modernization
Recover fragile systems, preserve useful data, replace risky dependencies, improve accessibility and performance, and leave a release path the owner can understand.
Country-specific acceptance
The Thailand assumptions belong in the test plan.
Language, privacy behavior, commerce, accessibility, release timing, and support need named owners. These are the current issues to carry into discovery.
- Thailand's PDPA requires current review of roles, lawful basis, consent, notices, sensitive data, processors, transfers, rights, retention, security, DPO, and incidents.
- THB, VAT on electronic services, customer and service classification, invoices, payment providers, identity, and foreign settlement require current Thai guidance.
- Thai needs qualified review; test font shaping, line breaking, Buddhist and Gregorian dates, names, provinces, +66 numbers, THB, mobile browsers, and accessible controls.
Next step
Turn the Thailand context into a workable brief.
The clearest scope starts with the actual Thailand operation: people, access, content, transactions, deadlines, support, and acceptance.