Services
UI/UX and product design
Screens people can use without a manual. Dashboards are our favourite, because they're so easy to get wrong.
Product design is the work of deciding what each screen of an app, SaaS product or dashboard shows and how people move through it, before it gets built. Vyorde does it for startups and small and mid-size companies that want software people can use without a manual or a training call.
What you get
Flows and wireframes
A map of every screen and how people move between them, before anyone argues about colours.
Interface design
Final screens for desktop and mobile, in Figma unless your team works in something else.
Dashboards
Charts and tables someone can read in a few seconds, with the important number where the eye lands first.
Every state
Empty, loading, error and full. The screens nobody remembers to draw until a user hits them.
Clickable prototype
Something you can put in front of real users before a line of code is written.
Design system
Components and rules your developers can reuse, so screen forty looks like screen one.
What's included
- User flows for every main task, agreed before any screen is drawn
- Wireframes for desktop and mobile
- Final interface designs in Figma, with the empty, loading and error states
- A clickable prototype you can test with real users
- A component library and written rules your developers can reuse
- Handover notes on spacing, behaviour and edge cases
- A walkthrough call with whoever builds it
What's not included
- A logo, colours and brand rules from scratch. That is Brand Identity.
- Writing the code. We build it under Websites & Apps or Custom Software, or hand the files to your developers.
- A formal accessibility check of a product that is already live. That is part of the Technical Audit package.
You'll probably like this if
- Your users keep asking how to do things your product already does.
- You want to see the product before you pay developers to build it.
- Your dashboard shows every number and nobody opens it.
How it goes
We look at what exists.
Your product, your users and whatever data you have about where they get stuck.
We sketch the flows.
Rough screens first, so changing direction costs an afternoon instead of a week.
We design the screens.
In rounds you review, with every state drawn properly.
We hand it over.
Files, prototype and notes clear enough that the developers don't need to guess.
Every project follows the same five steps. See the full process.
What changes the price
- How many screens and flows there are
- Whether we need to talk to real users first
- A full design system, or a few screens
- How many rounds of feedback you want
Tell us what you need and you get a quote in writing before anything starts.
Before you start
- A list of the main things a user needs to get done in the product
- Logins to the current product, or screenshots if nothing is built yet
- Any data on where users drop off, or what they ask support about
- Your logo, colours and fonts, if they exist
- The name of one person who can approve design decisions
You don't need all of it for the first call.
Questions about product design
Do you only design, or build as well?
Both. We can hand the designs to your developers, or build them ourselves.
Can you redesign part of an existing product?
Yes. The best start is often one painful flow rather than the whole product.
What do we get at the end?
The design files, a clickable prototype and notes for whoever builds it. They're yours.
How long does product design take?
It depends on how many flows and screens there are, and how quickly feedback comes back. A single painful flow is a much shorter job than a whole product. As a reference point, design is one part of our MVP Build package, which runs 6 to 12 weeks for design and build together. You get dates in writing with the quote.
What do you need from us to start?
Access to the current product if there is one, any analytics or support tickets that show where people get stuck, and one person who can answer questions and approve decisions. Brand colours and fonts help if you have them. If you don't, we work in plain greys until that is settled.
Whose Figma account do the files live in?
Yours, where possible. We work in a Figma team or project you own and give ourselves edit access, so nothing has to be transferred at the end. If your team uses another design tool, we agree that before starting. The designs themselves are yours once the work is paid for, and the contract says so.
What happens to the designs after the product is built?
They need looking after, like code does. The design system we hand over has written rules, so your developers or another designer can add screens that match. If you want us to design new features, we quote that as new work. Small tweaks can go through a support agreement if we look after the product.
More questions are answered on the FAQ page.
Want to start smaller?
Try the MVP Build package first. For founders and teams with a product idea who want a first working version in front of real users, without building everything at once. Typical timeline: 6 to 12 weeks. The exact dates are in your quote.
Often paired with
- 04Websites & AppsWebsites, web apps and mobile apps that stay fixable.
- 09Brand IdentityLogos and visual systems your team can actually use.
- 01Custom SoftwareCustom software for when spreadsheets give up.
Last updated