UX / UI design
Interfaces that make the next step obvious.
Page structure and interfaces planned around how customers actually find and do things.
- Good for
- Businesses needing this done properly, once
- Includes
- 4 agreed deliverables
- Pricing
- Quoted on scope, agreed before work starts
What this usually looks like
The problem
Visitors land on the site but cannot tell what you do, what to read first, or how to get in touch. Staff find the tools they use every day slow or confusing.
How we approach it
We map the journeys that matter — enquiry, purchase, booking, support — and design page structures and interfaces around them, on desktop and mobile.
What you receive
- Sitemap and page hierarchy agreed before design
- Wireframes for the key journeys
- Desktop and mobile interface designs
- Interaction notes for build (states, empty and error cases)
Deliverables are confirmed in your proposal. Anything outside that list is quoted before it starts.
What we need from you
- 01Confirm the audiences and the actions that matter most
- 02Supply content or help us plan it
- 03Review layouts at the agreed checkpoints
Pricing approach
Scoped by the number of page types and journeys. Reusing a system of sections across pages usually costs less than one-off layouts for every page.
Cost and scope
What this typically costs, and what changes it
Scoped by the number of page types and journeys. Reusing a system of sections across pages usually costs less than one-off layouts for every page.
Published rates and package inclusions are still being confirmed. Anything not confirmed is quoted in writing rather than estimated here — no totals are invented to make the page look complete.
Typical engagement
- Quoted as
- Fixed scope, agreed before work starts
- Review points
- Named in the proposal
- Next step
- A short call, then a written scope
Related work
Where this work appears
- QNP Group
Digital commerce · 2025
- BFS Plastics
Digital commerce · 2026
Contribution and engagement details for each project are being confirmed. We do not publish testimonials or results we cannot evidence.
Process
How a project runs
The same checkpoints apply across services, with review points agreed for your scope.
Review
We look at your business, customers and what the website or system needs to achieve. Goals and priorities Opportunities to improve
Plan
Priorities become a sitemap, content requirements and technical approach. Sitemap and feature scope Agreed schedule and review points
Design
You review desktop and mobile layouts and approve the direction before build. Desktop and mobile layouts Design approval checkpoint
Build
The agreed design is built. A staging preview lets you review before going live. Working staging preview Content and functionality review
Launch
Pages, links and forms are checked. Where a CMS is included, your team gets a walkthrough. Launch checks and deployment Editor handover (if CMS included)
Staging previews
Review the working site or application before it goes live.
Handover
Editor walkthrough where a CMS is included in the project.
Support after launch
Support and maintenance terms are agreed in your proposal (to be published).
Good to know
Frequently asked
questions.
Tell us what is not working and what you would like instead. We reply by email, then arrange a discovery call if it looks like a fit.
Reading
Related guides and case studies
Case study · Creative & digital experience
Real Serious Games: one identity across a studio site and its interactive workA games studio with a serious technical offer. The site had to look creative without losing the credibility of the work underneath.
Case study · Digital commerce
QNP Group: product content that holds up across a catalogueA commerce site is a content system. The hard part is not the home page, it is the two hundredth product entry.
Other studio services
Developer? Explore the UI Library
The UI Library is a different audience: reusable Payload CMS blocks and React components you install in your own project. It is not a finished website service.
