Built from nothing or made far better, by people who know the whole product lifecycle. We shape the work to your stage, pre-seed to Series C, because we’ve done it in-house at every level.
An MVP, a design system or an audit of what you already have. Here’s when founders bring us in, and what comes with each.
Use case / First version
🚀First version
You’re building an MVP and it has to feel like a real product from day one.
What you get
User flows
MVP screens
Clickable prototype
Use case / Users get stuck
🧭Users get stuck
People drop out of a key flow. We find out why, then fix it.
What you get
UX audit
Ranked quick wins
Redesigned flows
Use case / Outgrown it
🌱Outgrown it
Every new feature makes the product messier. We give it room to grow.
What you get
Design system
Clearer navigation
Core screens
Use case / Engineers designing
🛠️Engineers designing
Your developers are making design calls between tickets. We hand them screens to build.
What you get
Specs and handoff
Video walkthroughs
Front-end code
Drag the blocks aroundDrag a block by its label
Product design / How it runsFill × Hug
You ask.We design.You ship.
Product work rarely has a fixed finish line, so it usually runs on the subscription. Fill your backlog and we work through it in priority order, alongside your developers.
“Unlimity moves fast and delivers big. They’ve turned around full decks, branding, and web projects for us in just days, all at a standard that impresses every time.”
01We don’t have anyone with product design experience on the team yet. Is that a problem?
That’s exactly who we’re for. We act as your product design team, from the first flows through to the details, and set things up so your developers can keep building with confidence after each piece of work.
02How would you approach a redesign like ours?
We start by reviewing what’s there: what your users are trying to get done, how the information is structured, then layout, type and colour. That gives us a clear plan with the biggest wins first, and we work through it alongside your team.
03Our product is still changing every week. When is the right time to bring in product design?
Whenever it starts to matter to your users, and we shape the work to your stage. Early on that might be a first version or a few key flows; later it’s design systems, audits and scaling what works, pre-seed to Series C.
04Can you work in our codebase instead of Figma?
Yes. Where it suits your team we contribute front-end code straight into your repo, and we still use Figma when that’s the better tool for the job. We fit around the way your developers already ship.
05How will you work with our developers day to day?
Closely. We join standups when it helps, walk the team through decisions in short video walkthroughs or calls, and stay on hand for questions while things get built.
06You won’t know our industry as well as we do. How do you get up to speed?
Getting to grips with complex products quickly is a big part of the job. We’ve designed for fintech, climate, energy and legal products, and we start with kickoff sessions with your product and data people, then weekly calls and standups where they help.
07Should we test this with customers first, or start with you?
Start with us on the things that don’t need a customer to tell you: structure, layout, clarity. Then take the improved version to customers, so their feedback goes on the questions that really need it.
08We want to move fast and iterate. How do you balance speed with getting it right?
We move fast too, but every release should be usable and useful on its own. Getting the structure right early means you build on it each time, rather than changing the whole thing on your users every month.
Most of our work is with fast-moving startups, but we work with teams of every size. Tell us what you're building and we'll tell you honestly how we'd help.
