Product UI/UX design for SaaS and web apps by Alex ZhytnykovProduct UI/UX design for SaaS and web apps by Alex Zhytnykov
Product UI/UX design for SaaS and web appsAlex Zhytnykov
Cover image for Product UI/UX design for SaaS and web apps
Product design for teams shipping a web app: flows, a design system your developers can build against, and screens that survive contact with real data. I can implement the front end too, so design and build stay in one contract.
Who this is for
Seed to Series A SaaS with a product and no designer. The interface grew feature by feature and each release drifts further from the last. You are about to rebuild the dashboard and do not want to arrive at the same place a second time. You run an agency and need a white label product designer for a client app.
What you get
Audit of the product as it is today: screen inventory and the places where patterns contradict each other User flows for the paths that carry the business: signup, first run, and the job the product exists to do A design system in Figma Variables: semantic tokens for surface, border, text and action states, then components with their states, not only the default view Hi-fi screens for desktop and the breakpoints your users are actually on, including empty, loading, error and permission denied A clickable prototype for testing and for the stakeholders who need to see it move Handoff in Dev Mode with tokens and Code Connect, or the front end built in Next.js, Tailwind and shadcn/ui
How it runs
Week 1. Audit and flows. Nothing visual yet. Week 2. Tokens and core components, reviewed with whoever will implement them. Weeks 3 to 4. Screens. Main flows first, edge states after. Two rounds of revisions per flow. Week 5 onward. Handoff, or build if that is in scope.
What I need from you
Access to the current product. Staging is fine, plus an account with data that looks real. One person who can approve design decisions without a committee. 45 minutes a week for review. Async works, silence does not. Your developer in the review from week 2, so the system is built against the code you actually have.
Timeline and price
From $3,000 for an agreed scope, usually three to six weeks. Half up front, half at handoff. For teams shipping continuously there is a retainer after launch: 20 to 25 hours a month at $1,200 to $1,800, priority in the queue.
8 years in design, focused on web and product interfaces, 4 of them running a studio. So the project gets planned like a producer would plan it and drawn like a designer would draw it. When scope grows past one person, my team at ZTNK picks up development and motion.
FAQs

Starting at$3,000
Duration4 weeks
Tags
Dashboard Design
Figma
Design Systems Specialist
Mobile Designer
Product Designer
UI/UX Design
UX Designer
Web App Design
SaaS
Service provided by
Alex Zhytnykov Kyiv, 02000
5
Followers
Product UI/UX design for SaaS and web appsAlex Zhytnykov
Starting at$3,000
Duration4 weeks
Tags
Dashboard Design
Figma
Design Systems Specialist
Mobile Designer
Product Designer
UI/UX Design
UX Designer
Web App Design
SaaS
Cover image for Product UI/UX design for SaaS and web apps
Product design for teams shipping a web app: flows, a design system your developers can build against, and screens that survive contact with real data. I can implement the front end too, so design and build stay in one contract.
Who this is for
Seed to Series A SaaS with a product and no designer. The interface grew feature by feature and each release drifts further from the last. You are about to rebuild the dashboard and do not want to arrive at the same place a second time. You run an agency and need a white label product designer for a client app.
What you get
Audit of the product as it is today: screen inventory and the places where patterns contradict each other User flows for the paths that carry the business: signup, first run, and the job the product exists to do A design system in Figma Variables: semantic tokens for surface, border, text and action states, then components with their states, not only the default view Hi-fi screens for desktop and the breakpoints your users are actually on, including empty, loading, error and permission denied A clickable prototype for testing and for the stakeholders who need to see it move Handoff in Dev Mode with tokens and Code Connect, or the front end built in Next.js, Tailwind and shadcn/ui
How it runs
Week 1. Audit and flows. Nothing visual yet. Week 2. Tokens and core components, reviewed with whoever will implement them. Weeks 3 to 4. Screens. Main flows first, edge states after. Two rounds of revisions per flow. Week 5 onward. Handoff, or build if that is in scope.
What I need from you
Access to the current product. Staging is fine, plus an account with data that looks real. One person who can approve design decisions without a committee. 45 minutes a week for review. Async works, silence does not. Your developer in the review from week 2, so the system is built against the code you actually have.
Timeline and price
From $3,000 for an agreed scope, usually three to six weeks. Half up front, half at handoff. For teams shipping continuously there is a retainer after launch: 20 to 25 hours a month at $1,200 to $1,800, priority in the queue.
8 years in design, focused on web and product interfaces, 4 of them running a studio. So the project gets planned like a producer would plan it and drawn like a designer would draw it. When scope grows past one person, my team at ZTNK picks up development and motion.
FAQs

$3,000