Ameer M.

Give me your complicated product. The dashboard nobody understands. The workflow that takes too many clicks. The SaaS app that made sense six months ago but doesn't anymore. **That's the kind of design problem I enjoy solving.** I don't start by asking what the screens should look like. I start by asking why they need to exist. What is the user actually trying to accomplish? Where are they getting stuck? What information do they need at that moment? Which steps are unnecessary? What business rules are hiding behind the interface? And what can we simplify before we add another button, filter or feature? Then I turn those answers into a product that feels clear, purposeful and easy to operate. Because AI can generate beautiful screens in seconds. Templates can make almost anything look polished. But neither solves the harder problem: **What should the product actually do, and how should it work for the people using it?** That's where 14+ years of product and UI/UX experience matters. I've worked on SaaS platforms, dashboards, admin systems, workforce products, operational software, mobile apps and startup products, often taking complicated requirements and turning them into structured experiences that users can actually understand. My process is simple: **Understand → Question → Simplify → Structure → Design → Systemize** I work from the user's goals and the product's logic first, then build the UI around them. That means thinking through user flows, information architecture, navigation, states, edge cases, permissions, responsive behavior and interaction patterns, not just making individual screens look good. And when the UI is ready, I don't throw a pretty Figma file over the wall. You get a properly structured, developer-ready design system with Auto Layout, reusable components, variants, states and clear interaction logic, so your developers know what to build instead of having to guess what I meant. **The goal isn't a beautiful Figma file.** It's a product that is easier to understand, faster to use, harder to get wrong, and easier for your team to build and scale. So if your product is complicated, half-finished, overloaded with features, difficult to explain, or simply not working as well as you think it should. **send it over.** I'll look at it as a product, not just a collection of screens.