Yura Bruskov

Senior Product Designer. End-to-end design for B2B SaaS — collaboration, monetization, complex enterprise flows. AI-augmented workflow: Figma → MCP → working React prototype the same day. On the side I build fun pet projects — 9 mobile apps independently shipped to the App Store, plus a stack of weird web experiments.

Case Studies — Q1 2026

01. CSAT Survey Widget

Designed a customer satisfaction survey widget from scratch — the first standardized feedback mechanism at the company. Challenged the initial brief: proposed time-based triggers instead of action-based to reduce sampling bias. Went through 8 iterations with 5 stakeholders over 3 weeks.

Discovery UI Design Accessibility Analytics React Prototype
Feb 2026 · 3 weeks · Sole designer
Outcome
Shipped to development as the company's first standardized CSAT widget.
  • Smooth handoff — few clarifying questions during dev
  • PM: "meaningful briefing approach"
  • 8 iterations, all logged with reasoning
  • Targeted 300+ responses/month at 95% confidence

02. Guests Redesign

Existing UI pushed conversion to paid seats — the GA4 funnel showed it wasn't working. Mined 26 support cases and pulled funnel data with Analytics to reframe the problem: users needed self-service management, not an upsell. Redesigned the entire guest management flow around free collaboration value.

User Research Data-Driven Support Case Mining Collaboration Features
Jan–Feb 2026 · 4 weeks · Sole designer
Outcome
Self-serve deletion covering 90% of Support tickets
  • 90% of "remove guest" tickets — now self-serve
  • 40% of "which assets" tickets — now visible in UI
  • Data changed the entire design direction
  • PM: "Super useful CJM, great tab separation"

03. Same-Domain Guest Suggests

Self-initiated concept. While mapping the invite CJM, I noticed users always invited the same colleagues. Proposed smart suggestions based on sharing history — reducing "type an email from memory" to one click. Explored a few UI directions with the team to pick one to take forward.

Self-Initiated Conversion Concept Exploration Invite Flow
Mar 2026 · 2 weeks · Sole designer
Outcome
Three UI directions reviewed with the team — Dropdown picked as the one to ship.
  • Concept originated from my CJM analysis
  • 11 design iterations across the explorations
  • Head of Product chose Dropdown: "cleaner when money is involved"

04. Value for Money Messaging

Users saw the team seat price and abandoned — it felt expensive without context. Collaborated with the Marketing Lead to reframe the charge as a deal: "68% cheaper than an individual subscription." Designed dynamic messaging that adapts per plan tier.

Monetization Copywriting A/B Testing Pricing UX
Mar 2026 · 3 weeks · With Marketing Lead + UX Writer
Outcome
"68% cheaper" value framing for conversion lift — A/B test in preparation
  • Dynamic percentage per plan (Pro: 68%, Business: 80%)
  • Honest charge display + value context in one block
  • Head of Product: "Улала, мне нравится! Оч клево!"

05. Next Steps After Invite (Concept)

Identified a missed monetization moment: right after inviting a teammate, the user was abandoned with no next step — peak motivation, zero action. Self-initiated concept exploration. Coordinated with a separate product team to map technical constraints, then designed a full upsell step inside the existing success modal.

Concept Monetization Cross-Team Self-Initiated
Mar–Apr 2026 · 2.5 weeks · Cross-team (2 product teams)
Outcome
Concept exploration filling the post-invite gap — toggle-driven upsell inside the same modal.
  • Gap identified from CJM — not from a brief
  • Coordinated with 3 engineers across teams to map constraints
  • Success metrics defined: CTR on upsell + MRR from conversions
  • Status: exploratory design, not shipped

06. Collaboration CJM

Asked to map the collaboration area — sharing, inviting, guest management, multilogin — into a single CJM. Until then, each was being designed in isolation. Built it in Figma with real screenshots at every step across 4 scenarios. Turned out to be the artefact the team kept coming back to.

CJM Systems Thinking Cross-Team 4 Scenarios
Jan–Mar 2026 · Ongoing
Outcome
Surfaced 2 new design tasks from gaps in the mapped flow. Used as a reference in subsequent reviews.
  • PM: "Super useful, loved how you mapped user confusion"
  • Directly led to the Post-Invite Upsell task (Case 05)
  • Aligned Marketing Lead on messaging across all flows
  • 4 scenarios, real product screenshots at every step

07. Multilogin Page A/B Experiment

Redesigned the session-limit page from a single-screen upsell into a 2-step flow: first an awareness/friction screen, then the commercial offer. Hypothesis: building user intent before the ask would lift trial conversion without increasing churn. Ran as a 50/50 experiment with defined MDE, sample size, and cooldown period.

A/B Experiment Conversion Monetisation Friction Design
Shipped · Rolled out to all users
Outcome
+35.5% relative uplift in trial conversion rate. No churn increase. Positive MRR impact.
  • +34% more trials started (volume, not just rate)
  • Trial-to-purchase rate directionally positive (+3.1%)
  • No statistically significant churn change
  • Variant won — deployed to 100% of users

08. Asset Haus — Brand Identity Concept

Pitch concept for a real-estate tokenization platform. Instead of a static brand book, I delivered the identity system as a working landing page — palette (lime / beige / black), Inter type stack with a serif accent, isometric pattern language, and a component library (property cards, business card, mobile screens, data viz, ad creative) all shown in real context. The deck IS the website.

Asset Haus hero — Tokenize Your Realty Asset Haus — 3D 'O' sculpture rendered in Three.js on the live demo
Brand Identity Visual System Concept Pitch Landing Page
Concept delivered · Live demo →
Approach
Brand book as a living website — every component shown in actual context, not on slides.
  • 3-colour palette, type pairing, pattern system
  • Property cards, business card, mobile UI, data viz
  • Interactive Brand Element Constructor
  • Working front-end as a deliverable
How I Work

Every task starts with a structured discovery: I mine support cases, pull analytics, and generate 4 solution variants before opening Figma. Each task gets a context.md — an append-only decision log with full reasoning and stakeholder feedback that survives scope changes.

Figma designs flow through MCP directly into working React prototypes. Stakeholders see something interactive the same day. Handoff means a complete spec: all states, accessibility, analytics events, component imports. I stay available during dev — fewer surprises, faster shipping.

On the side: 9 mobile apps independently shipped to the App Store — concept, UX, development, monetization, live users. I know what it takes to go from idea to profit as the sole decision-maker.

Get in touch →

Prague · CET · Open to senior product design roles