Ryan K.

Hey there! I turn complex, inconsistent or unfinished interfaces into products users can understand and developers can build without guessing. Over the past 8+ years, I’ve designed SaaS, AI and healthcare software used by more than 7 million people. My work has contributed to a 5% increase in free-to-paid conversion, reduced completion time on key workflows by up to 50% and helped shorten design and development cycles by 35%. I’m usually brought in when a product has traction but the experience has not kept pace. What looks like a design issue is often already costing the business: trial users abandon important flows, customers struggle to reach the value they signed up for, support teams answer avoidable questions, and developers lose time fixing inconsistent patterns and overlooked states. I find where users are dropping off, getting stuck or making errors, then improve the workflow, clarify the interface and design the edge cases that reduce bugs during development. I do not assume the answer is to start over. I take what already works, remove the friction around it and create a clearer foundation for future features. The result is a product that is easier to use, easier to ship and better positioned to convert and retain the people it was built for. ⚡ WHAT I HELP IMPROVE • Activation, adoption and free-to-paid conversion • Completion rates across onboarding and multi-step workflows • Usability issues, missing states and UX bugs that lead to errors • Repeated support questions caused by unclear product behaviour • Dashboard clarity, discoverability and repeat use • Visual consistency and trust across the product • Design and development speed through reusable components and patterns 🧩 WHAT I CAN HELP YOU DESIGN • B2B SaaS platforms, web apps and internal tools • Dashboards, data tables, filters, calendars and reporting views • Multi-step workflows, forms with conditional logic, and role-based journeys for multiple user types • Onboarding flows and first-run experiences • Mobile apps for iOS and Android • AI products, and the interface patterns that make AI features feel built in rather than bolted on the side • Design systems in Figma: components, variants, variables and tokens 📈 SELECTED WORK • Helpjuice. Rebuilt the core article editor used by 7M+ people across 7,500+ businesses, cutting completion time on key authoring tasks by up to 50%. Built the company's first design system, 2,000+ components, which product and engineering still ship against. • Staticflow, now Konvert. Designed AI-assisted ad-creation workflows that took an hours-long production process under 60 seconds. The Templates, Explore and Remix redesigns contributed to a 5% lift in free-to-paid conversion. • Vibrant Practice, now Ultralight Healthcare. Built the mobile design system and redesigned the patient-to-doctor chat and health-records experiences so lab results and conversations were easier to follow. • Theranie. Designed the client and provider journeys for a mental-health platform, including the matching questionnaire that connects people to the right provider. • Daddy & Me. Designed connected tablet and mobile experiences covering emotional check-ins, rewards, call scheduling and gifting, with a developer-ready UI kit across both. 🎯 WHAT I HAND OVER • A Figma file built from reusable components, with named tokens for color, type, spacing and variables • A style guide documenting the system, so the design stays consistent as the product grows • Every state designed, not just the ideal case: hover, loading, empty, error and validation • Responsive layouts across desktop, tablet and mobile • A clickable prototype with the core flows wired together, so you can click through it before anyone writes code • Clean developer handoff: organised layers, sensible naming, exported assets, documented spacing and behaviour • Comment access on the working file so you can leave feedback in context I started in front-end development and still write HTML, CSS and JavaScript. On teams building with React, Next.js and Tailwind that means I design in components, states and edge cases from the start, so the Figma library maps onto the codebase instead of fighting it. I also use AI-assisted tooling day to day, including Claude Code, to get a real clickable version of an idea in front of people fast rather than describing it in a document. How I work: I design one screen first and get it approved before building the rest, so the direction is settled before the volume of work happens. You get a reply the same day, a link you can check at any point, and a heads up when something in the brief won't work as written instead of a silent workaround. Send me what you already have. A prototype link, a Figma file, a set of screenshots, or a description of what isn't working. I'll tell you what I would change and what it would take.