An Ever-Expanding Web Of Interest

Suprabho Dhenki
The Evolution of a Designer

From crafting user experiences to building products, managing programs, writing code, and founding a creative studio — a career that never stopped widening.

Scroll
"I started by understanding people. Then I learned to move them — with motion, with products, with strategy. Every role I've taken didn't replace the last — it expanded the canvas. Today I design, manage, code, and build companies, because great products need someone who's been on every side of the table.

— The elevator pitch

The Expanding Field

Each phase didn't replace the last — it added a new dimension

2016 –

Phase 01

UX Designer

IIT Guwahati · CHI Publication · Microsoft

User ResearchInformation ArchitectureWireframingPrototyping

UX Designer

2018 –

Phase 02

Brand & Motion Designer

1mg

Motion GraphicsBrand IdentityAfter EffectsStoryboarding

UX Design

Brand & Motion Designer

2020 –

Phase 03

Product Designer

1mg · ClearTax · Merkle Science

Design SystemsEnterprise SaaSData VisualizationComplex Workflows

UX

Brand & Motion Designer

Product Designer

2022 –

Phase 04

Product Designer + Product Manager

ClearTax · Merkle Science · Kidzovo

Product StrategyRoadmap PlanningStakeholder MgmtOKRs

UX

Brand + Motion Designer

Product Design

Product Designer + Product Manager

Now

Phase 06 — Today

Builder & Creative Technologist

Kidzovo · Promad

AI WorkflowsFigma PluginsVideo ProductionVibe Building

UX

Brand + Motion Designer

Product Design

PM + Growth

Builder & Creative Technologist

The Problem

A designer's process is fragmented across 12+ tools that don't talk to each other

From requirement gathering and hypothesis validation, through secondary research and solution brainstorming, to information architecture, user flows, stakeholder alignment, developer handoff, QA, feature marketing, performance analytics, A/B testing, and app store optimization — every phase lives in a different tool, a different context, a different mental model. The work is continuous. The tools are not.

📋
Requirements
Notion / Jira
🔍
Research
Notion
💡
Ideation
FigJam / Miro
🗂️
IA & Flows
FigJam
🎨
UI Design
Figma
📐
Design System
Figma
🤝
Alignment
Slack / Loom
🔧
Dev Handoff
Figma Dev Mode
🧪
QA & Testing
TestFlight / BrowserStack
📹
Feature Videos
After Effects / Premiere
📊
Analytics
Mixpanel / Amplitude
🧬
A/B Testing
Mixpanel / Firebase

12 steps. 12+ tools. Zero continuity.

The Epiphany

Since I started writing code, coming back to design tools feels limited

How Code Works

Reliable — it just works, every time
Translates clearly across stages
Every change is saved, versioned, documented
Every decision has a why attached
Works seamlessly across devices, platforms, IDEs
One source of truth, always

How Design Tools Work

Figma canvas feels limited after code
Adobe suite has become clunky
Repetitive setup for every new client
No real version history with intent
Context scattered across apps
Even Figma's Dev Mode admits design → code gap

What I'm Building

Units of design that compound across phases

Instead of waiting for one tool to rule them all, I've been building small, sharp tools — each one closing a specific gap in my workflow. Each one a "unit" that makes the next phase faster.

01

Brand System Setup — from 1 week to 4 hours

Every new client meant rebuilding the same foundations: color tokens, typography scales, spacing systems, design tokens — all manually, all fragile.

Built 3 Figma plugins and a standalone color tool that generate Tailwind-compatible palettes, duplicate text styles across variants, and update nested tokens in bulk across component libraries. A personal design system that's fast, portable, and only needs to work for one person — but can be compared across projects to spot what's truly different.

1 week → 4 hours
colors.promad.designCross-Collection Color Token MapperVariant SelectorText Style Duplicator
02

Visual Generation — code as the creative medium

Photoshop felt clunky. After Effects felt like overkill for backgrounds. Canvas too basic. Meanwhile, Stripe and others were making stunning visuals — all in code.

Started 'Beautiful Headers' for website hero sections, which evolved into Aura — a tool that generates dynamic, variable backgrounds used in static assets, animated videos, website embeds, and slide decks. Not generative AI, but parametric design: controllable, reproducible, beautiful.

From static to living visuals
aura.promad.design223+ Scene CatalogueVideo ExportWeb Embeds
03

Creative Production — modular, not monolithic

Video ads, feature announcements, and marketing assets were one-shot efforts. Every brief started from zero. No reusable components.

Developed a modular framework where creative briefs generate interchangeable hooks, content blocks, CTAs, and visual screenplays. Mix-and-match any combination to produce 100+ video variations from a single brief. Scene-by-scene breakdowns with timing, assets, narration, and sound design — shoot-ready documentation from AI-assisted workflows.

1 brief → 100+ variations
AI Brief → Screenplay PipelineModular Hook/Content/CTA SystemScene-level Asset Mapping

The Vision

Design should work like code — reliable, versioned, continuous. Each tool I build is a step toward a workflow where design decisions compound instead of being scattered. Where the units of your work grow together, phase by phase, tool by tool.

This is where all my expanding fields converge.

Companies & Projects Along The Way

Microsoft·Merkle Science·ClearTax·1mg·Kidzovo·Promad
1000+
Code Commits
400K+
Lines of Code
3
Figma Plugins Built