Currently a Staff Product Designer, leading a team of 8 Product Designers and owning platform-level design decisions.
Hi, I am Ritik
I design
platforms &
systems
that let
SaaS
products scale
without breaking.
I own design systems, platform architecture, and complex builder experiences for large-scale SaaS products — ensuring design decisions survive growth, engineering constraints, and team scale.
View Selected Works →
View My Thinking →
case studies
Selected Works
A selection of platform-level problems I’ve owned end-to-end — from architecture to execution.
Design System 3.0 – Rebuilding the Foundation of a SaaS Platform
Led, rebuilt, and redefined the foundation of a growing SaaS platform using a token-driven, multi-context design system that scales across teams and brands.
View Details
FLAGSHIP CASE STUDY
Builder Architecture: Email, Landing Pages, Forms & Dashboard
Designed a flexible builder platform that enables non-designers to create complex experiences — without sacrificing consistency, performance, or usability.
View Details
how i work
How I Think About Designs
The principles that guide how I design platforms, systems, and complex product experiences — especially at scale.
1
I design systems, not screens
Screens change quickly. Systems endure. I focus on architectural decisions that survive product growth, team scale, and long-term maintenance. This means designing relationships, constraints, and foundations — not just individual interfaces.
2
Constraints are part of the design
Real products operate within engineering constraints, performance limits, and delivery timelines. I treat these as inputs, not blockers. With a strong frontend background, I design solutions that are feasible, dev-proof, and faster to ship — reducing rework and misalignment.
3
Builders are products, not features
Builder experiences succeed or fail based on mental models — not flexibility alone. I design builders with intentional constraints and progressive complexity, enabling non-designers to create confidently without breaking the system.
4
Design systems are living products
A design system is not a static library — it’s a maintained platform that evolves with the product. I treat design systems as products with ownership, governance, documentation, versioning, and tight design–engineering sync.
My IDEAS
Design Explorations
These are conceptual explorations — ideas I would build without roadmap, tech debt, or delivery constraints. They are not shipped products, but they reflect how I think about systems and interfaces.
View Visual Explorations
Case studies
Writing & Thinking
Writing helps me clarify how I think about systems, scale, and complex product design beyond what shipped work alone can show.
Design Systems Don’t Fail — Teams Do
Why most design systems decay over time, and why ownership, governance, and collaboration matter more than components.
Why Most SaaS Builders Are Badly Designed
A breakdown of common mental-model failures in builder products — and how excessive flexibility often harms usability and scale.
Designing for Scale Is Not About Components
Scale is an architectural problem, not a UI one. This piece explores how structure, constraints, and decisions age over time.
View More on Medium
WHO I AM
About Me
Current Work
I’m a Staff Product Designer at Fello, currently leading a team of eight designers, working across design systems, platform architecture, builders and complex product workflows in large-scale SaaS products.
Fello.ai
Staff Product Designer
Design Leader
Education & Qualifications
With a strong frontend background, I design dev-proof solutions that ship faster — without sacrificing consistency or quality.
Almost 8 Years in Design
Front-end Engineer turned Designer
How I handle problems
I stay hands-on with problems — whether they’re mine or my team’s — and work closely with engineering to ensure design decisions are feasible, scalable, and maintainable over time.
View More on LinkedIn
Let’s Talk
If you’re working on a complex product or platform and want to talk about systems, scale, or architecture, feel free to reach out.
© 2025 · Ritik Raj · Designed and built with 💜
Currently a Staff Product Designer, leading a team of 8 Product Designers and owning platform-level design decisions.
Hi, I am Ritik
I design
platforms &
systems
that let
SaaS
products scale
without breaking.
I own design systems, platform architecture, and complex builder experiences for large-scale SaaS products — ensuring design decisions survive growth, engineering constraints, and team scale.
View Selected Works →
View My Thinking →
case studies
Selected Works
A selection of platform-level problems I’ve owned end-to-end — from architecture to execution.
Design System 3.0 – Rebuilding the Foundation of a SaaS Platform
Led, rebuilt, and redefined the foundation of a growing SaaS platform using a token-driven, multi-context design system that scales across teams and brands.
View Details
FLAGSHIP CASE STUDY
Builder Architecture: Email, Landing Pages, Forms & Dashboard
Designed a flexible builder platform that enables non-designers to create complex experiences — without sacrificing consistency, performance, or usability.
View Details
how i work
How I Think About Designs
The principles that guide how I design platforms, systems, and complex product experiences — especially at scale.
1
I design systems, not screens
Screens change quickly. Systems endure. I focus on architectural decisions that survive product growth, team scale, and long-term maintenance. This means designing relationships, constraints, and foundations — not just individual interfaces.
2
Constraints are part of the design
Real products operate within engineering constraints, performance limits, and delivery timelines. I treat these as inputs, not blockers. With a strong frontend background, I design solutions that are feasible, dev-proof, and faster to ship — reducing rework and misalignment.
3
Builders are products, not features
Builder experiences succeed or fail based on mental models — not flexibility alone. I design builders with intentional constraints and progressive complexity, enabling non-designers to create confidently without breaking the system.
4
Design systems are living products
A design system is not a static library — it’s a maintained platform that evolves with the product. I treat design systems as products with ownership, governance, documentation, versioning, and tight design–engineering sync.
My IDEAS
Design Explorations
These are conceptual explorations — ideas I would build without roadmap, tech debt, or delivery constraints. They are not shipped products, but they reflect how I think about systems and interfaces.
View Visual Explorations
Case studies
Writing & Thinking
Writing helps me clarify how I think about systems, scale, and complex product design beyond what shipped work alone can show.
Design Systems Don’t Fail — Teams Do
Why most design systems decay over time, and why ownership, governance, and collaboration matter more than components.
Why Most SaaS Builders Are Badly Designed
A breakdown of common mental-model failures in builder products — and how excessive flexibility often harms usability and scale.
Designing for Scale Is Not About Components
Scale is an architectural problem, not a UI one. This piece explores how structure, constraints, and decisions age over time.
View More on Medium
WHO I AM
About Me
Current Work
I’m a Staff Product Designer at Fello, currently leading a team of eight designers, working across design systems, platform architecture, builders and complex product workflows in large-scale SaaS products.
Fello.ai
Staff Product Designer
Design Leader
Education & Qualifications
With a strong frontend background, I design dev-proof solutions that ship faster — without sacrificing consistency or quality.
Almost 8 Years in Design
Front-end Engineer turned Designer
How I handle problems
I stay hands-on with problems — whether they’re mine or my team’s — and work closely with engineering to ensure design decisions are feasible, scalable, and maintainable over time.
View More on LinkedIn
Let’s Talk
If you’re working on a complex product or platform and want to talk about systems, scale, or architecture, feel free to reach out.
© 2025 · Ritik Raj · Designed and built with 💜
Currently a Staff Product Designer, leading a team of 8 Product Designers and owning platform-level design decisions.
Hi, I am Ritik
I design
platforms &
systems
that let
SaaS
products scale
without breaking.
I own design systems, platform architecture, and complex builder experiences for large-scale SaaS products — ensuring design decisions survive growth, engineering constraints, and team scale.
View Selected Works →
View My Thinking →
case studies
Selected Works
A selection of platform-level problems I’ve owned end-to-end — from architecture to execution.
Design System 3.0 – Rebuilding the Foundation of a SaaS Platform
Led, rebuilt, and redefined the foundation of a growing SaaS platform using a token-driven, multi-context design system that scales across teams and brands.
FLAGSHIP CASE STUDY
Builder Architecture: Email, Landing Pages, Forms & Dashboard
Designed a flexible builder platform that enables non-designers to create complex experiences — without sacrificing consistency, performance, or usability.
how i work
How I Think About Designs
The principles that guide how I design platforms, systems, and complex product experiences — especially at scale.
1
I design systems, not screens
Screens change quickly. Systems endure. I focus on architectural decisions that survive product growth, team scale, and long-term maintenance. This means designing relationships, constraints, and foundations — not just individual interfaces.
2
Constraints are part of the design
Real products operate within engineering constraints, performance limits, and delivery timelines. I treat these as inputs, not blockers. With a strong frontend background, I design solutions that are feasible, dev-proof, and faster to ship — reducing rework and misalignment.
3
Builders are products, not features
Builder experiences succeed or fail based on mental models — not flexibility alone. I design builders with intentional constraints and progressive complexity, enabling non-designers to create confidently without breaking the system.
4
Design systems are living products
A design system is not a static library — it’s a maintained platform that evolves with the product. I treat design systems as products with ownership, governance, documentation, versioning, and tight design–engineering sync.
My IDEAS
Design Explorations
These are conceptual explorations — ideas I would build without roadmap, tech debt, or delivery constraints. They are not shipped products, but they reflect how I think about systems and interfaces.
View Visual Explorations
MY THOUGHtS
Writing & Thinking
Writing helps me articulate how I think about systems, scale, and complex product design beyond what shipped work alone can show.
Design Systems Don’t Fail — Teams Do
Why most design systems decay over time, and why ownership, governance, and collaboration matter more than components.
Why Most SaaS Builders Are Badly Designed
A breakdown of common mental-model failures in builder products — and how excessive flexibility often harms usability and scale.
Designing for Scale Is Not About Components
Scale is an architectural problem, not a UI one. This piece explores how structure, constraints, and decisions age over time.
View More on Medium
WHO I AM
About Me
Current Work
I’m a Staff Product Designer at Fello, currently leading a team of eight designers, working across design systems, platform architecture, builders and complex product workflows in large-scale SaaS products.
Fello.ai
Staff Product Designer
Design Leader
Education & Qualifications
With a strong frontend background, I design dev-proof solutions that ship faster — without sacrificing consistency or quality.
Almost 8 Years in Design
Front-end Engineer turned Designer
How I handle problems
I stay hands-on with problems — whether they’re mine or my team’s — and work closely with engineering to ensure design decisions are feasible, scalable, and maintainable over time.
View More on LinkedIn
Let’s Talk
If you’re working on a complex product or platform and want to talk about systems, scale, or architecture, feel free to reach out.
© 2025 · Ritik Raj · Designed and built with 💜
Currently a Staff Product Designer, leading a team of 8 Product Designers and owning platform-level design decisions.
Hi, I am Ritik
I design
platforms &
systems
that let
SaaS
products scale
without breaking.
I own design systems, platform architecture, and complex builder experiences for large-scale SaaS products — ensuring design decisions survive growth, engineering constraints, and team scale.
View Selected Works →
View My Thinking →
case studies
Selected Works
A selection of platform-level problems I’ve owned end-to-end — from architecture to execution.
Design System 3.0 – Rebuilding the Foundation of a SaaS Platform
Led, rebuilt, and redefined the foundation of a growing SaaS platform using a token-driven, multi-context design system that scales across teams and brands.
FLAGSHIP CASE STUDY
Builder Architecture: Email, Landing Pages, Forms & Dashboard
Designed a flexible builder platform that enables non-designers to create complex experiences — without sacrificing consistency, performance, or usability.
how i work
How I Think About Designs
The principles that guide how I design platforms, systems, and complex product experiences — especially at scale.
1
I design systems, not screens
Screens change quickly. Systems endure. I focus on architectural decisions that survive product growth, team scale, and long-term maintenance. This means designing relationships, constraints, and foundations — not just individual interfaces.
2
Constraints are part of the design
Real products operate within engineering constraints, performance limits, and delivery timelines. I treat these as inputs, not blockers. With a strong frontend background, I design solutions that are feasible, dev-proof, and faster to ship — reducing rework and misalignment.
3
Builders are products, not features
Builder experiences succeed or fail based on mental models — not flexibility alone. I design builders with intentional constraints and progressive complexity, enabling non-designers to create confidently without breaking the system.
4
Design systems are living products
A design system is not a static library — it’s a maintained platform that evolves with the product. I treat design systems as products with ownership, governance, documentation, versioning, and tight design–engineering sync.
My IDEAS
Design Explorations
These are conceptual explorations — ideas I would build without roadmap, tech debt, or delivery constraints. They are not shipped products, but they reflect how I think about systems and interfaces.
View Visual Explorations
MY THOUGHtS
Writing & Thinking
Writing helps me clarify how I think about systems, scale, and complex product design beyond what shipped work alone can show.
Design Systems Don’t Fail — Teams Do
Why most design systems decay over time, and why ownership, governance, and collaboration matter more than components.
Why Most SaaS Builders Are Badly Designed
A breakdown of common mental-model failures in builder products — and how excessive flexibility often harms usability and scale.
Designing for Scale Is Not About Components
Scale is an architectural problem, not a UI one. This piece explores how structure, constraints, and decisions age over time.
View More on Medium
WHO I AM
About Me
Current Work
I’m a Staff Product Designer at Fello, currently leading a team of eight designers, working across design systems, platform architecture, builders and complex product workflows in large-scale SaaS products.
Fello.ai
Staff Product Designer
Design Leader
Education & Qualifications
With a strong frontend background, I design dev-proof solutions that ship faster — without sacrificing consistency or quality.
Almost 8 Years in Design
Front-end Engineer turned Designer
How I handle problems
I stay hands-on with problems — whether they’re mine or my team’s — and work closely with engineering to ensure design decisions are feasible, scalable, and maintainable over time.
View More on LinkedIn