Users don't talk about good interfaces. They talk about the bad ones, in support tickets, in app store reviews, and to their friends. UI/UX design is the work that prevents those conversations.

This engagement designs digital products that people actually want to use. Mobile apps, web apps, SaaS dashboards, CRM platforms, e-commerce stores, internal tools. Whatever the surface, the goal is the same: the user gets their job done without friction, and your product feels obvious to use.

A marketing site has to convince a visitor in 60 seconds. A product has to work for the same user across hundreds of interactions over months. The unit of design isn't a screen, it's a task: what the user is trying to accomplish, what state they're in when they start, what could go wrong, and what success looks like at the end.

I design for the task first, then build the screens around it. Every flow accounts for the messy reality of real use: loading states, errors, empty states, edge cases, the moments most designs ignore.

Every screen has one primary action and answers "what do I do here?" before anything else.

The flow handles success, failure, and the in-between states (not just the happy path).

The system is designed once and reused across the product, so consistency holds as it scales.

The design hands off to engineering with the spec they actually need, not a Figma file full of unanswered questions.

Mobile apps. iOS, Android, or cross-platform (React Native, Flutter). Designed against platform conventions, not in spite of them.

SaaS dashboards & admin panels. Data-heavy interfaces, complex filters, tables, charts, settings, multi-role permissions.

CRM platforms. Pipeline views, contact management, workflows, automations, custom views for different team roles.

E-commerce stores. Storefront, product pages, cart, checkout flow, account, post-purchase. Optimized for conversion and trust.

Internal tools & custom web apps. Operations dashboards, workflow tools, anything your team uses daily that should feel as good as the products you ship to customers.

Founders building a new product from scratch and wanting to get the UX right the first time

Companies whose product has outgrown its original interface and needs a redesign

Teams launching a mobile app, dashboard, or e-commerce store

Startups that have product-market fit on a rough interface and need to make it feel professional

Discovery & user understanding. A structured intake covering who uses the product, what they're trying to do, where current friction lives, and what success looks like.

User flows & information architecture. The full map of how users move through the product, with every screen and state accounted for.

Wireframes. Structure agreed before any visuals, so revisions happen on the cheap layer.

Hi-fi UI design. Polished, on-brand interface design across all required screens, including the states that get forgotten (loading, error, empty, success).

Design system. Reusable components, typography, color, spacing, motion. Designed once, used everywhere, documented for your engineering team.

Interactive Figma prototypes. Click-through flows so stakeholders and developers can experience the product before it's built.

Responsive or platform-specific layouts. Web responsive across desktop, tablet, mobile, or native designs that follow iOS Human Interface Guidelines and Material Design where it makes sense.

Dev-ready Figma file. Organized, named, with proper auto-layout and components. Built so your developer (any platform, any framework) can ship from it.

Loom handoff walkthrough. A recorded walkthrough of the system, the flows, and the intent behind key decisions.

Two weeks of post-handoff support. I answer your developer's questions, clarify edge cases as they come up, and adjust details as the build progresses.

Scope varies a lot here. A focused mobile app or a clean SaaS dashboard usually runs 5 to 7 weeks. A complex CRM, multi-role platform, or full e-commerce experience runs 8 to 12 weeks. We scope to actual screens and flows in the intake, not to a fixed template.

Week 1. Discovery, user flows, information architecture. Week 2. Wireframes and flow validation. Weeks 3 to 6+. Hi-fi design across all flows and states. Final week. Design system documentation, prototype, handoff.

Access to anyone on your team who knows the user (founder, support, sales, customer success), any existing research or analytics, brand basics (logo, fonts, colors, voice if you have them), and around 1 to 2 hours per week across the project for reviews and decisions. Everything else I handle.