Konstantin Zhuck

A design system shaped around your product, your workflows and your codebase, not a generic component checklist dropped on top of them. Built for teams that ship while it is being built.You receive:• Audit of the current product and Figma library• Foundations: type, colour roles, spacing, layout, radius, elevation, motion• Variables and tokens across primitive, semantic and component levels, light and dark• Core component library: up to 60 components with variants and their required states• Up to 3 product areas, named in the scope document before we start• Naming and structure agreed with your engineers rather than invented in isolation• Usage guidance per delivered component: what it is for, when not to use it• Migration plan for up to 40 existing screens, ordered by cost of leaving them• Figma handoverTools: Figma, variables and modes. Tokens exported to CSS custom properties, Tailwind config, SwiftUI or a Style Dictionary feed on request.Week 1 audits what exists across the areas in scope: duplicates, detached instances, hardcoded values. Weeks 2 to 5 build foundations and core components. Weeks 6 to 8 cover the long tail, documentation and handover. Two rounds of refinement per phase.The most recent system I shipped supports a live coaching platform: 163 component sets and 1 043 variants. A second supports an enterprise legal tech product: 189 component sets.Component count refers to distinct components, not to their variants or states, which are included per component. Work beyond 60 components, 3 product areas or a 40-screen migration plan is quoted separately rather than absorbed. Code implementation is not included; token export to your format is.Not included: repairing a library that does not need rebuilding, and compact single-area systems with no migration. Both are smaller engagements, message me and I will quote them directly.

The working surface of a B2B SaaS product. Admin, settings, permissions, bulk operations, the screens nobody puts in a portfolio and every user hits weekly.You receive:• 20 to 25 desktop screens, light and dark• Agreed critical states for the in-scope workflows: empty, loading, error, partial data, no permission• Role-based variations where the product has more than one kind of user• Navigation and information architecture for the whole surface, not only the screens in scope• Component library with variants and documented behaviour, built to keep scaling• Naming and structure aligned with your engineering team• Figma prototype for handoverTools: Figma, variables and modes, tokens exported to your format on request.Week 1 audits the current product and maps the workflows. Week 2 sets structure and one reference screen. Weeks 3 to 5 build the surface. Week 6 covers the agreed states, documentation and handover. Three rounds of refinement.Nine years in dense product interfaces. 163 component sets and 1 043 variants on a live platform, 189 component sets on an enterprise legal tech product.Screen count refers to unique layouts. Themes, states, and role-based variations are defined separately in the agreed scope.

Product design for sports, coaching and fitness platforms: the athlete side, the coach side, and the data that connects them. I have shipped this exact product shape, not a template applied to it.You receive:• Both sides of the platform: what the coach operates and what the athlete experiences• 20 to 25 screens across web and mobile, light and dark• Programme, session and schedule builders, the part every platform underestimates• Performance data: metrics, progress, comparison, thresholds, alerts• Agreed critical states for the in-scope workflows: no history yet, missed session, offline, restricted access• Component library with variants and documented behaviour• Figma prototype for handoverTools: Figma, variables and modes. Design tokens exported to your codebase format on request.Week 1 maps the coach and athlete workflows. Week 2 structure and reference screens for both sides. Weeks 3 to 5 the surface. Week 6 agreed states, documentation and handover. Three rounds of refinement.Track record: lead product designer on a live coaching platform, 163 component sets and 1 043 variants, plus product design for a sports analytics product.Screen count refers to unique layouts. Themes, states, and role-based variations are defined separately in the agreed scope.

Interfaces built around data people have to act on: reporting, monitoring, telemetry, operations. Charts are the easy part. The work is deciding what the person needs to see first, what they can ignore, and what has to interrupt them.You receive:• 12 to 15 screens covering the reporting and monitoring surface, light and dark• A chart system: which visual for which question, with rules for scale, colour and empty data• Data tables with sorting, filtering, grouping, segmentation and export• Alert, threshold and anomaly patterns where the product needs them• Agreed critical states for the in-scope workflows: no data yet, partial data, stale data, permission-limited• Component library and Figma prototype for handoverTools: Figma, variables and modes.Week 1 audits the questions the interface has to answer. Week 2 structure and one reference screen. Weeks 3 and 4 the remaining surface. Week 5 agreed states, documentation and handover. Three rounds of refinement.Background: product design for a sports analytics platform, plus dense operational interfaces in legal tech and coaching products.Screen count refers to unique layouts. Themes, states, and role-based variations are defined separately in the agreed scope.

A dense B2B dashboard designed for how it will actually be used: real data volumes, real edge cases, real permission levels. Not a portfolio screen with four tidy cards.You receive:• 8 to 10 desktop screens, light and dark• Data tables, filters, charts, detail panels, bulk actions• Agreed critical states for the in-scope workflows: empty, loading, error, no permission• The component set behind the screens, ready to extend• Figma prototype for handoverTools: Figma, variables and modes. I stay close to the code, so decisions survive implementation rather than being reinvented by the frontend.Week 1 sets the structure and takes one screen to completion so you can approve the direction. Weeks 2 and 3 cover the remaining screens and the agreed critical states. Three rounds of refinement.Best for B2B and SaaS products with dense workflows. The screen list is agreed before we start.Nine years in product design. 163 component sets and 1 043 variants on a live platform, 189 component sets on an enterprise legal tech product.Screen count refers to unique layouts. Themes, states, and role-based variations are defined separately in the agreed scope.

An outside read of one core flow in your live product, by criteria rather than by taste.You receive:• One core flow reviewed, up to 20 screens• Annotated screenshots for every issue found• The user or business risk each issue creates, stated plainly• A recommended fix detailed enough for design or engineering to act on• Findings ranked by impact, quick wins separated from structural problemsTools: Figma for annotation, a written report you can paste into your tracker.Delivered in one week. Useful when a flow feels harder than it should, when the team disagrees about what to fix, or when you need evidence before committing budget to a redesign.A recent audit of this kind documented and prioritised 48 friction points across a product's core workflows.Scope covers one core flow and the available product context. User research, usability testing and redesign are separate services.