We do design work for software products and the websites around them, and the right starting point depends on what you are trying to fix. If you already know your need, jump to the matching page. If not, the table below maps problems to work.
Tell us what you are designing
Which design service do you need?
| Your problem | The work | Where to read more |
|---|---|---|
| Users drop off, setup is confusing, the app feels dated | UI and UX design with research and prototypes | UI/UX design services |
| You have an idea or a new product line and no design yet | Product design from discovery to a tested prototype | Product design services |
| Your marketing site is slow to change or looks off brand | Website design with templates editors can compose | Web design services |
| Six teams build six versions of the same button | A design system delivered as code | Design system agency |
| You have a finished design and need it built | Figma to HTML, React or Astro | Figma to code |
Some projects need two of these in order. A new product often starts with product design, then moves to UI work, and ends with a design system once several teams are building on it.
What does each kind of design work involve?
Product design
Product design starts before screens. We interview users, map the main journeys, decide what the first release must do and test a clickable prototype with real people. The output is a scoped design that engineers can estimate. It suits founders and product leads who are still deciding what to build.
UI and UX design
This is the work on an existing or planned interface: research on how people use it, information architecture, flows, wireframes, visual design and handoff specs. It suits teams with a live product and a known problem, such as activation, navigation or a feature nobody finds.
Web design
Web design covers marketing sites, landing pages and content hubs. The brief here is different from an app: editors need to publish without a developer, pages must load fast and search engines must read them. We design the page templates and the content model together.
Design systems
A design system is the shared set of tokens, components and rules behind a product. We deliver it in code, with Storybook documentation and CI checks. It fits when more than one team ships UI. The long definition is in our guide on what a design system is.
Research and testing
Research runs inside the other work: interviews, moderated usability tests, session recording review and A/B plans. A short test before build is cheaper than a redesign after it.
What does a design project look like with us?
Most projects follow the same four steps, with the length set by scope:
- Discovery. We review the product or site, the analytics and any existing research, and agree on one measurable goal.
- Direction. Wireframes and flows first, then visual design on top, reviewed with you at each stage.
- Validation. Prototypes are tested with users before engineering starts, when a mistake is still cheap to fix.
- Handoff. Annotated specs, Figma components that match the code, and a call with your engineers. If you want us to build it, the same team continues.
Designers and developers work together from step one, so designers know what the component library can do and engineers see the design before it is final.
What results can design work produce?
A European Series-B B2B SaaS was losing trial users in a 14-step onboarding wizard. We audited the flow, tested it with real trial accounts, and rebuilt it as a three-step progressive disclosure model in their existing Storybook library. The case study reports ~30% improvement in trial activation rate, 4 min time-to-first-value down from 12+ min, and ~40% reduction in onboarding drop-off. The study marks these figures as directional. Read it here: UI and UX redesign for a B2B SaaS onboarding flow.
How do you hire designers from us?
You can buy a project, or add designers to your own team. For ongoing work, our hire a designer page describes the roles, and a dedicated team can combine design and engineering in one squad. Hourly work falls in the band of $50 to $150 per hour, depending on seniority and role. Project prices depend on scope and are given after discovery.
Where does design end and engineering begin?
For us they overlap on purpose. A design that cannot be built within your stack and budget is not finished, and a build that drifts from the design has to be fixed twice. We keep one backlog for both, name components the same way in Figma and in code, and review work together.
