> Aaron Sananes
Design EngineerTB Auctions
Nine brands. One messy prototype. An industry with no room for mistakes.
Year
2020 - 2015

Problem
When TB Auctions began acquiring multiple auction brands, each brought its own legacy systems, unique auction rules, and established brand identity. Our early SaaS platform could manage auctions but wasn’t built for multiple storefronts with different requirements.
Migrations often took up to 12 months per brand, slowing growth and putting user trust at risk. The challenge was to build a scalable platform that unified all brands while preserving their individuality, in an acquisition-heavy environment with shifting priorities and limited resources.
Project Goals
Design and deliver a scalable, multi-brand platform (Atlas + storefronts + mobile) that could onboard any acquired brand quickly, preserve its identity, and support long-term growth.
Key Decisions
Slow brand migrations
12 months on average to migrate a brand, creating bottlenecks for acquisitions.
High acquisition pace
2+ brands per year, creating constant pressure on design and dev teams.
Shrinking design resources
Team reduced from three designers to just one, requiring me to own and scale the system end to end.
Fragmented requirements
100+ unique auction rules and workflows had to be unified without losing brand individuality.
Revenue at risk
Millions in transactions could be jeopardised if migrations failed or trust dropped.
Slow brand migrations
12 months on average to migrate a brand, creating bottlenecks for acquisitions.
Platform Core
Millions in transactions at stake if performance or trust dropped during migrations.
High acquisition pace
2+ brands acquired per year created a constant backlog of migrations.
Shrinking design resources
Team reduced from 3 to 1 designer, requiring me to own and scale the entire system.
Research
With limited design resources and a shifting leadership team, the approach had to be pragmatic: build a strong foundation in Atlas, create a flexible multi-brand design system, and deliver improvements step by step through live brand launches.
I took ownership of the auction planner and item creation flows, rebuilt them for scale, and partnered closely with the front-end architect to align Figma design tokens with Next.js components. This ensured Atlas, web storefronts, and mobile apps all spoke the same design language.
At the same time, I onboarded and mentored junior designers, collaborated with developers on CMS and marketing templates, and worked with product managers and data analysts to run weekly A/B tests — using the largest brand first to reduce risk.
Goal
Establish a scalable design + development foundation, unify Atlas with storefronts and mobile, and iterate through live launches while maintaining brand individuality.
Matrix Diagram
Stakeholder feedback
My Role
This dual focus — designing products (Atlas + storefronts + mobile) and building the design system that scaled them — created a foundation flexible enough for nine brands and ongoing acquisitions.
I served as both product designer and design systems architect. I designed the core workflows for Atlas (our internal platform) and customer-facing storefronts and mobile apps, balancing internal efficiency with external trust.
I built a multi-brand design system in Figma with code-mapped tokens that unified all channels—Atlas, web, mobile, email, and marketing—while preserving each brand's identity. Working closely with engineering, I implemented this in Next.js, validated through A/B testing, and mentored junior designers to ensure consistent execution.
Goal
Designed Atlas and storefront experiences, while creating the design system that unified every channel — web, mobile, app, email, and marketing.
Key Roles
Designed Atlas
Created visuals and workflows for the internal auction platform.
Built storefronts + mobile
Helped design and build bidder-facing experiences.
Created multi-brand design system
Tokens and components in Figma mapped into code.
Unified all channels
Atlas, storefronts, mobile apps, email, and marketing ran on one system.
Engineering partnership
Integrated design system with Next.js alongside front-end architect.
Validated with data
Refined through A/B testing during live brand migrations.
Scaled the team
Onboarded and mentored junior designers to work within the system.

Design System



SYS_FLOW :: TOKEN_PIPELINE




Outcome
Migrations dropped from 12 months to weeks, enabling TB Auctions to scale quickly without losing trust. We launched nine brands on a unified platform — Atlas powering internal workflows, storefronts, mobile, and marketing — with each brand keeping its own identity.
The design system became a shared language across design and development, cutting publishing from days to hours and improving conversion on brand launches.
Goal
Launched nine brands on a unified, scalable platform, reduced migrations from months to weeks, and improved conversions and workflows across web and mobile.
Key outcomes
Nine brands launched
Launched a scalable platform
Migration speed
Reduced from ~12 months to weeks.
Conversion uplift
Improved results on major brand launches.
Workflow efficiency
Publishing workflows cut from days to hours.
Shared system
A design system adopted across design + development.
Personal growth
Learned to stand firm, balance design/engineering, and mentor under pressure.



Reflection
This project was more than just delivering a platform. It was a five–year journey that stretched my skills as a designer, developer, and mentor.
Looking back, the biggest lesson was learning to stand firm. In the past, I would have focused on keeping everyone happy. Here, I had to say no, push back when foundations weren’t strong enough, and advocate for scalable solutions over quick fixes.
It also taught me how to balance multiple roles at once — design, engineering, and mentoring — while planning ahead instead of reacting to daily challenges. And working through leadership changes reinforced the importance of keeping focus on the product vision, even when priorities shifted around me.
Statement
I grew not only as a designer but as a critical thinker — learning to push back, plan ahead, and balance design, code, and mentoring while keeping product vision intact.
Key learnings
Confidence in decision-making:
Standing firm and protecting long-term scalability.
Multi-role balance
Navigating design, code, and mentorship simultaneously.
Strategic thinking
Planning ahead rather than reacting to problems.
Resilience
Delivering consistent outcomes despite leadership and priority shifts.
Industry insight
Firsthand experience in a highly regulated, high-stakes auction industry.