FluidbyDesign

View case
Contact me

How I work

Fluid on the surface, engineered underneath.

No black box. No "it'll be ready when it's ready." No ghosting. Here's the exact path from kickoff to launch — roughly eight working weeks — the same one I ran at Vista, VistaCreate and Helen Marlen. Based in Kyiv (UTC+2), I overlap 4–6 hours with both EU and US teams, so you're never waiting a day for a reply.

The timeline

Eight weeks. Three phases. Zero friction.

You get the whole map up front, so you can plan around it — the opposite of the freelancer who vanishes for two weeks and comes back with the wrong thing.

W1W2W3W4W5W6W7W8 01 · Discovery & Strategy — 2 wks 02 · Architecture & Design — 5 wks 03 · Final — 1 wk
Three phases across eight working weeks — task chips sit under each phase. No mysteries.
012 weeks

Discovery & Strategy

First I make sure we're not building something pretty and pointless.

I run discovery — a competitive benchmark, audience and journey mapping, and, when the project needs it, hands-on user research: surveys, in-depth interviews and support-call analysis (the way I ran it at Aromateque, a 149-person survey). Strategy and IA are set before anyone opens Figma.

Benchmark & Competitor ScanAudience & Journey MappingUX Research (surveys · interviews)
025 weeks

Architecture & Design

Then I build a system your team can actually run.

IA and flows into an interactive prototype, then high-fidelity, art-directed UI built as a tokenised design system of reusable components — the layer your team can run and extend, not one-off screens that rot into design debt. Exactly how Vista's growth team started shipping campaign pages in days, skipping the dev queue.

Interactive PrototypeHigh-fidelity UI & Art DirectionDesign System & Tokens
031 week

Final Presentation

You leave with dev-ready specs — not a folder of mysteries.

A documented system with dev-ready components and specs (a UI guide + TZ) for the build team, plus the motion, icons and 3D polish that make it feel premium. And I don't stop at handoff — I build too: this very portfolio is designed and shipped by me with AI-assisted code.

Dev-ready Handoff (UI guide + specs)MotionAI-assisted Build (code)

Across a project I can run the whole path myself:

UX Research & DiscoveryIAPrototypingUI & Art DirectionDesign SystemsMotionDev-ready HandoffAI WorkflowsAI-assisted Build (code)

Rigor

Before a single pixel, I map the whole journey.

Every screen, every branch, every edge case — so the build is obvious and nothing gets bolted on later. It's how I turned a genuinely complex US dental-tech workflow into something clean and human for Uniform Teeth.

Splash Sign Up Login Main Navigation Overview Products Customers Orders Content Detail / editedge cases mapped
A user-flow map: splash → auth → main navigation → every sub-screen and edge case, before design begins.

Why it pays off

I design against the costs that actually hurt your bottom line.

Pretty doesn't pay. These are the problems I'm hired to kill:

Weeks Days

Pages stuck in the dev queue become a self-serve system your team launches itself — proven at Vista.

1 hire, not 3

Art direction, UX, UI and design systems from one senior person — senior quality without agency overhead.

Template Flagship

Generic themes that don't convert become bespoke, premium and on-brand — see Aromateque and the Awwwards-winning Oberig Jewelry.

Design SystemsResearch-Led UXConversion UIArt DirectionMotion & 3DAI-Driven Workflows
VIEW MY CASES VIEW MY CASES