Product Design
Starting at
$
7,000
About this service
Summary
FAQs
Do I need usability testing?
Yes. Testing catches things you won't notice on your own. It's the difference between a design that looks good and a design that actually works for the people using it. If user engagement matters to you, testing pays for itself.
What if testing shows major problems?
That's actually why you test. It's better to find problems now than after you've built and launched the product. Testing is meant to be honest—it usually reveals things worth fixing. We iterate based on what we learn.
Can I see the Figma file?
Yes, you own it. You get the complete Figma project with all screens, the design system, prototype, and documentation. Your team can reference it, extend it, or hand it to developers.
What if we want to add features later?
The design system is built to scale. New features follow the established patterns and components. The documentation makes it easy to stay consistent even as the product grows.
How many revisions are included based on testing?
One round of optimization based on testing insights is included. If major new directions are needed, that would be a separate scope.
Is this just for apps or does it work for websites too?
It works for both. The process is the same whether you're designing an app, a web product, or something more complex. We just adapt the approach to what you're building.
What's included
Research and Planning
The user research report includes interview insights, behavioral patterns, and pain points documented in a comprehensive report with findings and summary. You also get 2-3 detailed user personas with goals, behaviors, and needs that are professionally documented in a PDF format. The information architecture document shows how content and features should be organized, presented as a sitemap and structure overview. User flow diagrams cover all key user journeys, showing 2-5 main flows that break down step-by-step how users complete important tasks in your product.
Design System and Components
I create a reusable component library with 20-30+ components including buttons, forms, cards, modals, navigation, and everything else your product needs. The design system documentation covers spacing, sizing, typography, colors, and states so that everything is organized and documented in Figma. Each component has interactive states for hover, active, disabled, loading, and error states documented so developers know exactly what should happen. The system also includes specific accessibility guidelines that follow WCAG 2.1 AA standards tailored to your product.
High-Fidelity Designs
You get high-fidelity screen designs that cover all major user flows, with both desktop and mobile layouts included. Micro-interactions and animation specifications are documented for each animation and transition. Visual hierarchy and layout documentation explains the design thinking and is useful for both designers and developers. Each screen also includes state variations for loading, empty states, error states, and success states.
Prototype & Testing
An interactive Figma prototype connects all screens together with user flows working end-to-end so you can actually click through and experience the product. The usability testing report includes findings from 5-8 target users and contains insights, quotes, and video clips if applicable. Testing recommendations are prioritized by impact so you know what to fix first and what's nice-to-have. Before and after documentation shows exactly how the design evolved based on testing feedback.
Developer Handoff
A comprehensive design specifications document includes component details, spacing, sizing, colors, and interactions so developers have everything they need. The Figma design system file is organized with all components, layers, and annotations so developers can access exactly what they need quickly. Interaction documentation shows animations, transitions, and timing with video walkthroughs if the interactions are complex. An accessibility checklist confirms that everything meets WCAG 2.1 AA compliance. File naming conventions and organized component structure make it easy for your team to work with the design system.
Duration
5 weeks
Skills and tools
