Tangensys • Plan, deliver, measure
UI/UX design
Make the user journey understandable before polishing the visuals. Design should show how the product behaves when input is missing, a request fails or a user needs help.
The work to plan together
A scope shaped around this requirement.
- User journeys and wireframesScope
- Interface design and design systemReview
- Clickable prototypesCheck
- VisitorArrives on a phone or desktop
- NavigationFinds the right page quickly
- Form or integrationEnquiry, booking or order
- Your teamReceives it in the right place
In short
What does UI/UX design involve?
UI/UX design plans and designs how a website or app works and looks: user journeys, wireframes, interface design and prototypes, for websites and mobile apps.
When UI/UX design is a useful fit
Product teams
Clarify the tasks users must complete and the decisions that need prototyping.
App and SaaS companies
Design consistent screens for onboarding, core actions and the states when something goes wrong.
Businesses redesigning complex sites
Test navigation and information hierarchy before investing in a complete visual rebuild.
Problems worth addressing first
Use these situations to identify the work that deserves attention before expanding the scope.
- Users get lost or drop off
- Developers build without clear designs
- The product looks inconsistent
A practical example
A booking prototype should include choosing a slot, correcting a mistake and seeing a confirmation, not only the ideal first screen.
This is an illustrative scenario to explain the approach, not a claimed client project.
The work we can include
The final quote identifies the deliverables, quantities, approvals and exclusions. Select the work that serves your goal rather than assuming every item is required.
- User journeys and wireframes
- Interface design and design system
- Clickable prototypes
- Handover to developers
Where we usually begin
Research access, screen count, prototype detail, testing and developer handover are scoped. Design files alone are not a working application.
Practical detail
Turn a user task into clear design states
For a booking interface, the important task is choosing an available slot and understanding whether it was confirmed. A prototype should show that journey before detailed visual polish.
| Part of the work | Example output | How to review it |
|---|---|---|
| Wireframe | Information order and the shortest useful booking route | A reviewer can explain what the user should do next. |
| Prototype | Available, unavailable, loading and confirmation states | A participant can complete a representative task without coaching. |
| Design specification | Components, spacing, labels and keyboard behaviour | The developer can implement the agreed states without guessing. |
| Review record | Observed problems and the changes made | Findings describe the task and evidence rather than personal preference. |
Research participants, supported devices and revision rounds are scoped explicitly. A clickable design is not a working booking system; development and integration are separate outputs.
Use design to clarify a real user task
UI and UX work starts with what the person is trying to achieve. A booking, checkout or internal approval flow should make the next step clear and explain errors in language the user understands. Attractive components support that task; they do not establish that the journey works.
Choose the evidence available: support questions, existing analytics, user interviews or a review of the current flow. The method and access should match the budget and uncertainty. A prototype can test assumptions about structure before development, but it is not evidence of production performance.
The handover should describe components, states and interaction rules, including empty, loading, error and permission states. Ask a developer to review feasibility before treating a prototype as the final specification. User testing and accessibility review are scoped activities rather than automatic results of a design file.
Free website review
Start with a clear scope and a practical next step.
Tell us what you want to improve and share the relevant website or project details. We will review the starting point, recommend a suitable scope and provide a custom quote.
The initial review is free. Delivery, third-party charges and ongoing support are quoted separately.
Process
How the work is delivered
Review the starting point
Review the current setup, examples of the problem and the information needed to agree the work.
Agree scope and sign-off
Design starts with the pages visitors need and the information you can supply. We agree the sitemap, visual direction, mobile behaviour and editing requirements before building.
Deliver and review
A review of the staging website checks content, forms, redirects and important mobile journeys. Launch responsibilities and the handover are agreed in the scope.
Hand over the next steps
Review the agreed outputs together. Confirm what your team maintains and what needs a separate ongoing arrangement.
What progress should mean
Measures that match the work
Evaluate task completion, usability findings and design coverage. Resolve confusing interactions before they become expensive development changes.
A record of delivery
See what was completed, reviewed and still dependent on access or approvals. Project delivery and business results are reported separately.
Clear limits in the data
We explain what can be verified and where a result is only an estimate. Contact clicks, conversations and sales are different actions.
Scope and responsibilities
You keep ownership of your business accounts and approved deliverables under the agreed contract. Any third-party licences, subscriptions or usage fees are identified before you commit.
What is included in a design handover?
Agree screens, responsive behaviour, components, source files and interaction notes. For a workflow, include the relevant error and alternate states. Research findings and testing records are included when commissioned. Development, production analytics and ongoing optimisation need separate ownership.
What if we cannot arrange user interviews?
We can agree a smaller discovery route using staff knowledge, existing support questions and task reviews. Those inputs have limits and should not be presented as user research.
Does the design include development?
Only if the proposal includes it. A design engagement usually hands over approved screens, states and implementation guidance.
Do you design mobile apps too?
Yes, app UI/UX is part of this service.
How is UI/UX design priced?
We quote against your goals, current setup and agreed scope. The quote separates delivery from third-party costs and ongoing support. You receive a custom quote within 2 working days.
How long does the work take?
The timeline follows the size of the agreed scope, access, content and approvals. We confirm milestones in the quote; a simple change and a full implementation need different schedules.
How will we communicate?
Your point of contact agrees a review rhythm with you. We use email, WhatsApp and scheduled calls, with decisions and scope changes recorded clearly.
What do you need to get started?
Share your current website or system, your main goal and examples of what is not working. We then agree the access and information needed for discovery.
Is everything included in the free review?
No. The free initial review helps define the next step. Detailed research, design, implementation and ongoing support are included only when stated in your quote.
Explore the related services
Let’s agree the right next step.
Tell us your goals and current setup. We’ll recommend a practical starting point and provide a custom quote.
Custom quote within 2 working days