Mikhail VodopianovProduct & Digital DesignerSelected Work ↙

VisCap.ai

Designing the product ecosystem behind UGC production

Shipped SaaS product · Sep 2023 — Dec 2025

Role
Product Designer
Team
5 engineers
Users
VisCap Media’s production teamand selected external clients

Overview

VisCap Media was both the product team and the primary user.

Over more than two years, I owned the end-to-end design of a connected ecosystem for producing UGC advertising — from ideas, casting, and reusable media to configurable workflows, performance tracking, Education, and desktop media tools.

VisCap.ai Media Library showing a dense masonry catalogue of reusable vertical video assets with production labels and statuses.
Media Library · A dense reusable asset catalogue presented as a continuous production surface.

01

From a live operation to a product ecosystem

The production process already worked, but it lived across documents, spreadsheets, cloud storage, and browser tools.

I translated that operation into a connected product model centred around Storyboards. Actors, reusable media, production stages, testing variants, and final Deliverables all became parts of the same system rather than separate tools.

VisCap.ai Actor Hub desktop interface presented with the mobile Storyboard
VisCap.ai Actor Hub and mobile Storyboard product composition.
IdeationActor HubMedia LibraryProduction WorkflowDesktop Application
StoryboardsDeliverablesPerformance Hub
  • IdeationStoryboards
  • Actor HubStoryboards
  • Media LibraryStoryboards
  • Production WorkflowStoryboards
  • Desktop ApplicationStoryboards
  • StoryboardsDeliverables
  • DeliverablesPerformance Hub
  • EducationProduct ecosystemconnected product branch
VisCap.ai production system centred around Storyboards, with Education as a connected product branch.
  • Storyboards
  • Media Library
  • Actor Hub
  • Production Workflow
  • Ideation
  • Performance Hub
  • Education
  • Desktop Application

02

The production core

Storyboards became the central production object.

I redesigned them around versioning, A/B testing, reusable media Elements, and rules governing what happened when source content changed.

The underlying media model connected Clips, reusable Elements, Storyboards, and finished Deliverables.

A configurable workflow then allowed teams to build custom Stages and Statuses tied to application areas and system behaviour — not just use them as labels.

  1. Clips
  2. Elements
  3. Storyboards
  4. Deliverables
Reusable media model
Video Builder · Product information and audience inputs assembled into an AI-supported script workflow.

03

Education as a product of its own

Education served both VisCap Media’s internal team and external paying customers.

I designed the learner-facing experience alongside a dedicated content-management system for creating, versioning, reviewing, and publishing theory materials.

The same system included a builder for theory tests, connecting learning content, assessment, review, and content maintenance inside one product architecture.

  • Learning experience
  • Content management
  • Versioning
  • Review workflows
  • Theory-test builder

04

Designing through technical constraints

Large production files exposed browser limitations, so I designed a Windows Electron application for Digital Imaging Technicians and actors.

It allowed users to upload, download, and manage large media files directly inside Storyboards instead of relying on a disconnected file-transfer utility.

Later, during the product’s move to Ant Design, I led a system-wide interface redesign across navigation, layouts, interaction patterns, states, and visual hierarchy.

I worked directly with five engineers and owned the product design from underlying logic and edge cases through responsive behaviour and implementation handoff.

05

What shipped

The completed ecosystem connected:

  • modular Storyboards and reusable media;
  • casting and configurable production workflows;
  • ideation and operational performance;
  • a commercial Education product;
  • large-file workflows across web and desktop.

The production platform was used primarily by VisCap Media’s own team, with limited external-client use. Education supported both internal learning and external customers.

The visible interface was the final layer.Most of the design work happened in the structure underneath.