5 min read
Client
Startup studio and B2B SaaS teams
My role
Product Designer
Timeline
2020 – 2024

Overview
The problem
In startup and SaaS environments, product direction can change fast. Some projects started with an idea, a business model or a technical need, but no existing design system, no stable product base and very little time to move. The challenge was to turn unclear starting points into usable flows, prototypes and interfaces that teams could actually build.
The solution
I worked directly with founders, product owners, developers, users and business teams to shape mobile apps, SaaS products, onboarding journeys, workspace tools and influencer workflows. I created product flows, UI foundations, design systems, research notes, prototypes and delivery-ready screens across projects that often had to move from zero to something usable in a few weeks.
Who I worked with
Partners from idea to delivery
Shaping product direction
Founders
Co-founders
CEOs
Product owners
Business teams
Startup partners
Turning work into products
Developers
Users
Clients
International teams
Influencers
Brand users
Approach
01. Start from zero fast
Early-stage work rarely started with a clean brief. Some projects began with a business idea, a short timeline, a founder’s vision or a technical need that had to become a product quickly. I had to understand the goal, identify what mattered first, and turn scattered input into a direction the team could discuss, test and build from.
02. Shape the core journeys
The work covered very different product types: real-estate investment, premium car rental, workspace management, influencer onboarding and campaign workflows. Each project needed its own logic, audience and product flow. I moved quickly from research and notes to user journeys, wireframes, prototypes and high-fidelity screens.
03. Build product foundations from scratch
Most of these projects did not have an existing design system. Each product needed its own UI base, component logic and reusable patterns. I had to design from scratch, but also make the work easy to understand for developers and reusable enough to support future screens.
Product foundations without inherited systems

04. Move designs into delivery
In small teams, design could not stay theoretical. I worked close to developers, product owners and founders to make sure the work could move into production. That meant preparing screens, states, Jira tickets, user stories, prototypes and handoff material while adapting to changes in scope, priority and technical reality.
Impact













