UI/UX design services for products full of numbers

My UI/UX design services cover how the product works (the flows, navigation and structure) and how it looks and reads (layouts, components, charts and copy on the screen). In practice I start with the tasks users come to do, fix the structure around them, then design the screens. You can hire me for a UX audit only, for design files, or for design plus a built front end.

Yes, as close as possible to what you describe. There's no fixed package: you tell me in your own words what the product or screen should do, share references you like, and I design to that. If you already have a design system or a component library, I work inside it so your developers don't have to rebuild anything.

A UX audit is a structured review of how real tasks work in your product today. I go through the main flows, note every point where users hesitate, get lost or need support, and rank the fixes by how often users hit them and how hard they are to change. You get a written report with annotated screens. It's a custom quote with a fixed price, agreed before I start.

For most focused projects, one designer who can also build is enough. A SaaS design agency makes sense when you need research, branding, product design and development running in parallel for a large product. I'm one person, so you work directly with whoever designs and builds your screens. That suits a redesign of one area, a new reporting module, or an internal tool.

Both are possible. If you have developers, I deliver annotated designs, component specs and the edge-case states they need to build without guessing. If you don't, I build the front end myself in React and Next.js and connect it to your API or a Supabase database. Many clients start with design only and add the build later.

Dashboard UI design is mostly about choosing what not to show. A normal screen supports an action; a dashboard supports a judgement, so the design has to make comparison, change and exceptions obvious at a glance. That means picking the right chart for each question, consistent number formats, sensible defaults for date ranges and filters, and clear states for missing or late data.

I do the practical version that a small team can afford. I watch real users or session recordings, read support tickets, and talk to the people who handle customer questions. That's usually enough to find the worst friction in a B2B product. I don't run large formal studies or recruit panels; if you need that, a research agency is a better fit.

It's a custom quote with a fixed price, agreed before work starts. What drives it is the number of screens and flows in scope, how much of the product needs new patterns versus reuse, and whether I also build the front end. A UX audit or a focused redesign of one area, such as a reporting module, is a common and affordable first project.