Vladislav Iushev

forDesign Systems

Built for adoption, scale, and AI-assisted teams

How this works

Audit

Stakeholder interviews, maturity assessment, a map of UI debt and duplication.

Architect

Token strategy, component model, naming, Figma architecture, governance blueprint.

Pilot

The system applied to real product workflows, with docs and specs.

Adopt

Team enablement, onboarding, and the measurement that tells you it's working.

Fixed-scope engagements

DS Diagnostic

For disagreement about what's broken

From $8,000

2 weeks

  • Stakeholder interviews
  • Maturity assessment
  • UI debt and duplication map
  • Prioritised roadmap
  • Architectural recommendation

System Foundation

For architecture that needs rebuilding

From $20,000

4–6 weeks

  • Design principles
  • Token strategy
  • Component model
  • Figma architecture
  • Governance blueprint
  • Engineering alignment

Pilot to Production

For adoption that isn't happening

From $35,000

8–12 weeks

  • System applied to real workflows
  • Figma and docs
  • Pilot flows
  • Adoption model
  • Team enablement
  • Governance

Ongoing partnerships

DS Advisory

For owners who need direction

From $4,000/mo

Month to month

  • Two workshops per month
  • Async review
  • Strategic input for owners

Embedded DS Lead

For the gap before an internal lead

From $9,000/mo

2–3 days a week · 3-month minimum

  • Design principles
  • Token strategy
  • Component model
  • Figma architecture
  • Governance blueprint
  • Engineering alignment

Exclusive Partnership

For full ownership, one client at a time

On request

Full-time · 6 months minimum

  • System applied to real workflows
  • Figma and docs
  • Pilot flows
  • Adoption model
  • Team enablement
  • Governance

Question & Answers

Do we need to pause product work?

No. The system gets built against real workflows, not beside them.

We already have a library. Does that change anything?

That's the most common request. Building a new system is the easy part. Updating a live one without breaking what already shipped is where the real work is, and that's what I specialise in.

Who owns the system afterwards?

Your team. Part of the engagement is making sure someone internal can run it without me.

How do you work with engineers?

Both ways. I deliver specs in Figma, or stand up a Storybook myself and build the components in React, Svelte, or whatever the stack is. My side is styling, animation and interaction. Complex logic and backend integration stay with your front-end team.

What about accessibility?

Contrast, focus order, keyboard shortcuts and interaction states get checked against the rules as I design. Alt text and style fallbacks are part of the spec, and I can support screen readers when the product needs it.

Can the docs work with AI coding tools?

Yes. Documentation goes out as Markdown, so coding agents read the same rules your team does.

NDA, B2B contract and Independent contractor agreement?

Yes. I work through my UAE company or as an individual, whichever your legal team prefers.

Start a conversation