A product people understand without a walkthrough.
App, SaaS and dashboard design for startups, from the first clickable prototype to a design system your developers can build from.
- App & product design
- SaaS & dashboard UI
- Design systems
- UX audit
- Wireframes & clickable prototypes
- MVP design for startups
- Usability testing
- No-code MVP builds
- App & product design
- SaaS & dashboard UI
- Design systems
- UX audit
- Wireframes & clickable prototypes
- MVP design for startups
- Usability testing
- No-code MVP builds
“Our users sign up, click around, and leave.”
“We built what the spec said. Every feature works. But new users keep asking the same questions on support chat, and half of them never finish onboarding.”
“The developers designed most screens as they went, so every page has its own buttons, its own spacing and its own idea of where the save button lives. Adding a feature now takes twice as long as it should.”
“We need to show investors something clickable next month, and we don't want to spend six months building the wrong thing first.”
Before
After redesign
Eight services, one product people get first time.
Pick one or several. Each starts from how your users actually behave, not from the feature list.
Mobile and web app screens that make the main task obvious, designed in Figma and ready for your developers to build.
Who it's for: Startups with a working product or a clear spec who need the interface designed properly, for iOS, Android or web.
Dashboards and admin screens where people find the number they came for in seconds, even when the data is dense.
Who it's for: B2B SaaS teams, internal tools and analytics products with tables, filters, settings and several user roles.
One shared set of components and rules, so designers and developers stop rebuilding the same button in five slightly different ways.
Who it's for: Products that have grown screen by screen and now feel inconsistent, or teams about to scale design and engineering.
A ranked list of what is confusing users in your product today, and what to fix first.
Who it's for: Live products with drop-off in sign-up, onboarding or checkout, where the team suspects the design but can't point to the problem.
A prototype you can click through on your phone, good enough to test the idea or show investors before anyone writes code.
Who it's for: Founders validating an idea, preparing for a fundraise, or briefing a development agency who needs to see the product, not read about it.
The smallest version of your product that is still worth using, scoped tightly and designed to be built quickly.
Who it's for: Pre-seed and seed founders with a long feature wish-list and a limited budget for the first build.
Watch real people try your product, so decisions are based on what users do rather than what the team argues about.
Who it's for: Teams about to commit development time to a new flow, or trying to settle an internal debate about a design.
A working product that real users can sign up to and pay for, built on a no-code platform in weeks rather than months.
Who it's for: Non-technical founders who need to test demand with a live product before hiring a development team.
Test early, design once, keep improving.
Every product project follows the same four steps, whether it is a two-week audit or a full app.
-
Week 1
Understand
We read your analytics, talk to your team and, where possible, a few users. You get a one-page brief with the problem, the users and what success looks like.
-
Weeks 1–2
Map and wireframe
Flows and grey-box wireframes first. It is cheap to change a wireframe and expensive to change a built screen, so this is where most decisions get made.
-
Weeks 3–5
Design and test
High-fidelity screens in Figma, turned into a clickable prototype and put in front of real users before we call anything final.
-
Week 6 onwards
Build and keep improving
Specs, components and assets your developers build from, design support through the first release, then we keep testing and improving the product with you as it grows.
Every project in this area is quoted to scope.
Tick what you need and we'll send a fixed quote.
Product & UX, answered.
How is the price decided?
After a 30-minute call where we go through your product, your users and what you need designed. We then send a fixed quote for that scope. If the scope changes during the project, we agree the change in writing before doing the extra work.
Do you write the code as well?
For custom apps, no. We design, work alongside your developers or agency while they build, and keep designing the next releases with you. For no-code MVPs on Bubble, Glide, Softr or Webflow, yes, we build the working product ourselves.
Will I own the Figma files?
Yes. Everything is built in a Figma project that is transferred to your team account, including components, prototypes and exported assets. If we carry on working together, we keep designing in that same file.
We already have a product. Where should we start?
Usually with a UX audit. It tells you what is actually causing drop-off before you spend money redesigning screens that may not be the problem.
Can you work with our existing brand?
Yes. We apply your existing colours, type and logo inside the product. If you don't have a brand yet, we can set up a light version as part of MVP design, or you can pair this with our brand identity work.
Show us the product. We'll show you where users get stuck.
A 30-minute call about your product, a written scope and a fixed quote. No obligation after that.