Product and UI/UX design
QBLab designs the product before it is built — research, the flows, every screen at the size it will ship at, and a design system that holds — so the build starts from something decided rather than something hoped for.
Design
Who it's for
- You have a product in mind and no screens yet.
- You have something live that people find hard to use.
- You are about to build and want the screens agreed before anyone writes code.
What's included
Researched, drawn and tested before a line of code is written.
- UI/UX
- Product design
- Design systems
- Websites
How an engagement works
The four-week shape is a first release of the scope we agree on the call — the version that is genuinely usable, not the finished product. Bigger products get there in stages, and most keep growing for months afterwards. Your case studies below carry their real timelines.
Day 1
A 30-minute call
You describe the product. We ask the questions that change the estimate, and you leave with a plan and a fixed quote.
Week 1
Plan and design
Scope, screens and data model agreed. You see what will be built before anything is built.
Weeks 2–3
Build
Working software every few days, not a reveal at the end. AI does the fast part; a senior engineer reviews every change.
Week 4
First release
The agreed scope goes live on your accounts and your infrastructure, with the stores and domains pointed at it. Usable by real people, and the starting point rather than the finish line.
Ongoing
Keep building
Month by month: the rest of the roadmap, new features, updates, monitoring and looking after the tech. This is where a first release grows into a complete product. Pause or stop whenever you like.
The work
CareFlow
A telehealth platform for clinics: patients, appointments and an AI clinical assistant in one place.
TypeScript · React · Vite · Tailwind CSS
Rimberio
An online store with AI product recommendations and a shopping assistant that helps people find what they came for.
TypeScript · React · Vite · Tailwind CSS
Questions
Can you design without building?
Yes. A design engagement can stop at the screens and the design system, and you can take them to any team. Most people keep going, because the team that drew it building it is a large part of why a first release lands in weeks.
What do I have at the end of the design work?
The flows, every screen at the sizes it will ship at, and a design system — type, colour, spacing and components — in a file that belongs to you. Enough for an engineer to build from without asking what a screen is supposed to do.
Do you work from a brand I already have?
Yes. If you have an identity, the design follows it rather than inventing a second one. If you do not, that is the branding work, and the two run together.
How long does the design take?
For a first release of an agreed scope it is week one: flows, screens and the data model, so you see what will be built before anything is built. A larger product's design runs alongside the build, screen by screen, instead of holding everything up.