UI/UX Design services
UI/UX design for business websites, web applications, and mobile products. Salt helps US teams turn complex information and workflows into clear journeys, interfaces, and implementation-ready designs.
Relevant experience
Explore a documented UI/UX engagement, an ERP MVP design-and-development project, and a website UX redesign. These show the scope of our work; they do not imply a guaranteed conversion uplift.
Client industry not published
Salt’s published UI/UX engagement describes user research, information architecture, visual design, mobile responsiveness, and iterative user testing.
Interior contracting
Salt designed and developed an ERP system MVP for Kokal Interior Contracts through an end-to-end product engineering engagement.
Technology consulting
Salt redesigned a technology consultancy’s website to improve how visitors navigate its services, understand its expertise, and reach the next step.
Where we can help
Choose a focused engagement or combine the work your project needs.
Review the existing experience and available customer feedback. Agree stakeholder interviews, user research, or usability sessions where access allows. Map the tasks, friction points, and assumptions that need validation.
Organize navigation, content, and workflow steps. Use wireframes to agree hierarchy and interactions before investing in detailed visual design.
Design responsive screens for public websites, portals, SaaS tools, or mobile flows. Include loading, validation, error, empty, and permission states where relevant.
Create clickable prototypes for key journeys and define reusable components, typography, spacing, and interaction patterns. Scope a design system to the product’s actual needs.
Example starting points
These are illustrative examples, not the limit of what we can scope. Tell us about your own workflow.
Reorganize the service information, proof, and enquiry path so visitors can find an appropriate next step.
Clarify task hierarchy, statuses, tables, and approval steps while keeping exceptions and permissions visible.
Prototype the critical journey so business owners, users, and developers can review how it should behave.
What we agree to deliver
Your proposal identifies the selected outputs, exclusions, and acceptance criteria.
Audience, user tasks, journey maps or findings, assumptions, and the decisions still needed from your team.
Navigation, content hierarchy, wireframes, and interaction flows for the selected scope.
Design files covering agreed screens, states, layouts, and reusable elements, with accessibility considerations defined upfront.
A reviewable prototype where useful, behavior notes, assets, and design walkthroughs. Validation findings and follow-up changes are included when commissioned.
From brief to handover
Review the product, business goal, user feedback, and available evidence. Agree research access and what can realistically be validated.
Work from structure and wireframes to detailed design. Review the selected journey with stakeholders and representative users when available.
Document behavior and reusable patterns, resolve developer questions, and agree whether design QA during development is included.
Agree US time-zone overlap, a decision owner, review cadence, and access before starting. Your proposal defines scope, fees, milestones, intellectual-property terms, and handover. Choose a defined project or discuss ongoing delivery support when your roadmap needs it.
Budget and timing
Research depth, user roles, unique screens and states, responsive layouts, prototype detail, and review rounds affect design effort. Recruitment, content writing, development, and ongoing design QA should be explicitly included or excluded.
We confirm assumptions, dependencies, review rounds, and availability before proposing a schedule. Third-party costs and work after launch should be listed separately.
Discuss your design challengeBefore you begin
Yes. Website design focuses on information discovery, brand presentation, and actions such as enquiries. Product design also needs to address tasks, permissions, data, and exception handling. We scope the relevant journeys rather than treating every engagement as a set of marketing pages.
Yes. A design engagement can cover the agreed research, flows, interfaces, prototype, and handover for your own development team. Implementation and ongoing design support are separate scope decisions.
Yes. Share your existing identity, typography, visual assets, and product conventions. We agree what to retain, refine, or extend. A full brand strategy or identity redesign is not assumed to be part of a UI/UX engagement.
We can use task walkthroughs, prototype reviews, and usability sessions with representative users, depending on access and scope. Record findings and unresolved assumptions. Stakeholder approval alone should not be presented as evidence of user validation.
Agree the accessibility requirements, design checks, deliverables, and handover depth before work begins. Design can address matters such as contrast, focus behavior, labels, and error states; implementation and testing are needed to assess the finished experience.
We can address confusing journeys and define how to measure changes. Conversion and adoption also depend on traffic, product fit, pricing, content, and implementation. Establish a baseline and measurement plan rather than promising a predetermined uplift.
Yes. We can map journeys across a website, portal, and mobile application so navigation, language, and interaction patterns remain coherent. Scope research access, design-system components, accessibility requirements, and how task completion or abandonment will be measured. Development, implementation testing, and brand strategy are separate scope decisions.
Tell us what you need
Share your website, application, or product idea, the users you serve, and what feels difficult today. Existing screens, feedback, or a short walkthrough can help us identify a useful first scope.
