UI/UX Design
UI/UX design for screens people actually use.
We research how people work, sketch the flow, prototype it in Figma and test it with real users before anyone writes code. That includes the ERP screens your staff open dozens of times a day, not just the marketing site.
- User research
- Wireframes
- Figma prototypes
- Design systems
- Usability testing
- Layouts tested in both scripts
- AA contrast and focus checks
- Figma files and design tokens you own
- Reply time on business days
What we design
Research, design and testing under one roof
Design work only pays off when it gets built. Design and engineering sit in the same team that builds your web, mobile and Odoo screens, so what ships matches what was tested.
UX research and audits
Interviews, task observation and analytics review that show where people get stuck, written up as a prioritized list of fixes.
Wireframes and user flows
Low-fidelity screens and flow maps that settle structure and content before visual design begins.
Figma prototypes
Clickable prototypes with real content in Thai and English that stakeholders and users can try on a phone or desktop.
Design systems
Tokens, components and usage rules in Figma, matched to code components so web and app teams build from the same parts.
Usability testing
Moderated sessions with around five real users per round, recorded, with issues ranked by how often and how badly they block the task.
ERP and back-office screens
Odoo forms, lists and dashboards redesigned around the task: fewer fields, smarter defaults and keyboard or barcode flows.
ERP UX
ERP screens designed around the person using them
An ERP rollout fails quietly when staff go back to spreadsheets because the screen fights them. We sit with the warehouse clerk and the accountant, count the clicks in their most common tasks, and redesign the Odoo views so the everyday path is short and the rarely used fields get out of the way.
- Fewer fields on the screens used most
- Field order that matches the paper document
- Keyboard and barcode paths for speed
- Thai and English labels checked at real length
Watch the task
We observe the real job at the desk or in the warehouse.
Map the fields
Every field is kept, moved or hidden for a reason.
Prototype the screen
A Figma version of the new form, list or dashboard.
Test with the same people
The users we watched try it before it is built.
Use cases
Design work that changes daily work
A cluttered Odoo form, simplified
A sales order screen crowded with fields nobody uses becomes a focused form built from standard Odoo views, so upgrades stay simple.
A customer portal, tested first
Before building a portal, we prototype ordering, invoice download and support requests in Figma and test them with a handful of your customers.
One design system for web and app
A shared set of tokens and components used by the website, the mobile app and the portal, so a button, a date or a price looks the same everywhere.
Industries
Design for screens that run operations
Good design matters most on the screens people cannot avoid: order entry, check-in, picking and billing.
- ManufacturingShop-floor tablet screens for work orders.
- Wholesale & DistributionFast order entry for inside sales.
- Retail & E-commerceCheckout and POS flows with fewer taps.
- Hospitals & ClinicsPatient intake and appointment booking.
- EducationParent and student portals.
- Freight & LogisticsDriver apps readable in sunlight.
- Real EstateBuyer portals with payment schedules.
- Professional ServicesTimesheet entry that takes seconds.
How we work
From research to dev-ready handoff
1. Research
Interviews, observation and analytics to learn who the users are and where they struggle.
2. Wireframe
Flows and low-fidelity screens agreed before any visual polish.
3. Visual design
On-brand screens with real Thai and English content and accessible contrast.
4. Prototype and test
Clickable Figma prototypes tested with real users, then refined.
5. Hand off
Specs, assets and a design system matched to code, with designers on hand during the build.
Toolbox
Tools from first sketch to shipped screen
- Figma
- FigJam
- Storybook
- Tailwind CSS
- React
- Next.js
- OWL
- Odoo Studio
- Microsoft Clarity
- Google Analytics 4
- Lighthouse
- axe DevTools
Commitments
Design you can own and build
We do not quote engagement uplifts from other people's projects. We commit to deliverables you keep and standards we check.
Book a free design call- AA checks on contrast, focus and targets
- Copy and type tested in both scripts
- Steps from research to handoff
- Price per phase, in writing
- Reply time on business days
FAQ
Questions clients ask first
What is the difference between UI and UX design?
UX design is how a product works: the flows, structure and decisions that let someone finish a task. UI design is how it looks and feels: layout, type, color and components. We do both together, because a beautiful screen with the wrong flow still loses users.
Can you redesign Odoo screens without breaking upgrades?
Yes. We start with standard view changes, such as field order, visibility and defaults, made in XML views or Odoo Studio, and build custom OWL components only where a screen needs behavior Odoo lacks. Those changes live in separate modules that are tested and ported with each upgrade, rather than edits to Odoo's own code.
Which design tools do you use, and do we get the files?
We design in Figma and FigJam, and you get full edit access to every file, component library and prototype. Design tokens are exported for developers, so colors, spacing and type stay consistent in code. Nothing is locked in our account.
How do you run usability testing?
We recruit a handful of real users per round, often your own staff or customers, and give them realistic tasks on a Figma prototype or the live product. Sessions are recorded in English or Thai, and each issue is ranked by how often it happened and how badly it blocked the task. Each round leads straight to design changes and a retest.
Do you design for Thai and English together?
Yes. Thai script needs taller line height and fonts with proper Thai glyphs, and the same label can be much longer or shorter than its English version. We design with real copy in both languages from the first wireframe, so layouts hold up when the language switches.
How long does a UI/UX project take and what does it cost?
An audit of an existing product is a short, fixed-fee engagement; a full product design runs in phases from research to handoff. We quote a fixed price per phase after a scoping call, and because the same team can build the design, you do not pay a second team to interpret it.
Get started
Show us the screen your team struggles with
Send a screenshot, a link or a short description of the task. We reply within one business day with first observations and a proposed design phase.
- Reply within one business day
- Figma files you own
- Design and build from one team
Prefer to talk first? Call us or WhatsApp us.