Who this is for
- Founders who want to validate a product idea with a prototype before building it.
- Teams whose product works but is hard to use, and who want a redesign grounded in evidence.
- Businesses that need one consistent design language across web and mobile.
Problems we solve
- Users get lost, and support answers the same questions every day.
- Every screen looks slightly different because there is no system behind them.
- Developers guess at spacing, states and edge cases.
- Redesigns are argued from opinion because nobody has watched a user.
What is included
- Research: interviews, reviewing how the product is used today and where people struggle.
- User journeys and wireframes for the flows that matter most.
- Visual design and a clickable Figma prototype for review with you and, where possible, with users.
- A design system: components, states, spacing and typography, documented for developers.
- Developer handoff and review during implementation.
Not included
- Brand identity, logo design, illustration and print.
- Marketing campaign assets, unless agreed in the plan.
What we need from you
- Access to some of your users or customers for research, where possible.
- Your existing brand assets and any product analytics you have.
- A decision-maker who can approve directions between reviews.
How the work runs
- 01Discover
We learn who uses the product, what they are trying to do and where it fails them today.
- 02Design
Journeys, wireframes, then visual design and a clickable prototype, reviewed with you at each step.
- 03Build
If we also build the product, design and development run in the same sprints; if not, we support your developers during implementation.
- 04Launch
A design system and handoff notes so the product stays consistent as it grows.
- 05Support
Design of new features and refinements based on what you learn after launch.
What you receive
- A research summary and user journeys.
- Wireframes and visual designs for the key flows.
- A clickable prototype in Figma.
- A documented design system.
- Developer handoff notes.
Proof and examples
We have not yet published case studies for this service. The product previews on the home page are illustrative concepts. Ask us to explain the proposed approach and what evidence is available for your particular scope before commissioning the work.
How we quote
- A written quote before any work starts. Custom work is quoted per phase after discovery.
- Changes are priced in writing before they cost anything.
- What shapes the quote: the number of flows and screens, how much research is possible, whether a design system already exists, and whether we also build the product.
Ownership and support
- Design files, the design system and all research material belong to you.
- Everything is delivered in your own Figma workspace, or transferred to it at handover.
- After launch you can continue design work with us or with your own team using the design system.
Questions about ui/ux design
Can you design only, and let our developers build it?
Yes. The design system and handoff notes are written for developers, and we can stay available for questions during implementation.
Which tools do you use?
Figma for design, prototypes and the design system, so your team can open, comment on and continue the work.
How do you validate a design?
Through prototype reviews with you and, whenever your users are reachable, short sessions watching them complete real tasks. We adjust the design based on what we see, not on preference alone.