Available for new projects
Menu
About Me
About Me
I'm Navid. I design products that make complex things feel simple.
I'm Navid. I design products that make complex things feel simple.
Seven years designing digital products across B2B SaaS, fintech, and early-stage startups. I work with founders and product teams who need design that moves fast, thinks strategically, and ships clean.
Seven years designing digital products across B2B SaaS, fintech, and early-stage startups. I work with founders and product teams who need design that moves fast, thinks strategically, and ships clean.
My Approach
My Approach
A few things that shape how I work with every client.
A few things that shape how I work with every client.
Principle 01
I write before I design. Getting the problem statement right in words forces a clarity that wireframes alone can't. If I can't explain what I'm solving in one sentence, I'm not ready to open Figma.
Principle 02
I ask uncomfortable questions early. The questions that feel too basic to ask — "who is actually going to use this?" and "what happens if this doesn't work?" — are usually the most important ones. I ask them in week one, not week six.
Principle 03
I treat constraints as design material. Timeline pressure, technical limitations, budget scope — these aren't obstacles to good design. They're the conditions that make design decisions meaningful. I do my best work inside real constraints.
Principle 04
I design the failure states first. Empty states, error messages, edge cases — the moments most designers leave until last are often the moments users remember most. I start there.
Principle 05
I make myself unnecessary. The goal of every engagement is a team that doesn't need me anymore. Clear documentation, thorough handoff, and knowledge transfer aren't extras — they're part of the deliverable.
Principle 01
I write before I design. Getting the problem statement right in words forces a clarity that wireframes alone can't. If I can't explain what I'm solving in one sentence, I'm not ready to open Figma.
Principle 02
I ask uncomfortable questions early. The questions that feel too basic to ask — "who is actually going to use this?" and "what happens if this doesn't work?" — are usually the most important ones. I ask them in week one, not week six.
Principle 03
I treat constraints as design material. Timeline pressure, technical limitations, budget scope — these aren't obstacles to good design. They're the conditions that make design decisions meaningful. I do my best work inside real constraints.
Principle 04
I design the failure states first. Empty states, error messages, edge cases — the moments most designers leave until last are often the moments users remember most. I start there.
Principle 05
I make myself unnecessary. The goal of every engagement is a team that doesn't need me anymore. Clear documentation, thorough handoff, and knowledge transfer aren't extras — they're part of the deliverable.
Awards
Awards
2024 - Awwwards Site of the Day
Awwwards
2023 - UI Design of the Year
CSS Design Awards
2023 - Featured — Designer of the Week
Dribbble
Work With Me
Work With Me
I work with a small number of clients at a time to make sure every engagement gets my full attention. If you're building something worth designing well — I'd like to hear about it.
I work with a small number of clients at a time to make sure every engagement gets my full attention. If you're building something worth designing well — I'd like to hear about it.
Available for new projects
Menu
About Me
About Me
I'm Navid. I design products that make complex things feel simple.
I'm Navid. I design products that make complex things feel simple.
Seven years designing digital products across B2B SaaS, fintech, and early-stage startups. I work with founders and product teams who need design that moves fast, thinks strategically, and ships clean.
Seven years designing digital products across B2B SaaS, fintech, and early-stage startups. I work with founders and product teams who need design that moves fast, thinks strategically, and ships clean.
My Approach
My Approach
A few things that shape how I work with every client.
A few things that shape how I work with every client.
Principle 01
I write before I design. Getting the problem statement right in words forces a clarity that wireframes alone can't. If I can't explain what I'm solving in one sentence, I'm not ready to open Figma.
Principle 02
I ask uncomfortable questions early. The questions that feel too basic to ask — "who is actually going to use this?" and "what happens if this doesn't work?" — are usually the most important ones. I ask them in week one, not week six.
Principle 03
I treat constraints as design material. Timeline pressure, technical limitations, budget scope — these aren't obstacles to good design. They're the conditions that make design decisions meaningful. I do my best work inside real constraints.
Principle 04
I design the failure states first. Empty states, error messages, edge cases — the moments most designers leave until last are often the moments users remember most. I start there.
Principle 05
I make myself unnecessary. The goal of every engagement is a team that doesn't need me anymore. Clear documentation, thorough handoff, and knowledge transfer aren't extras — they're part of the deliverable.
Principle 01
I write before I design. Getting the problem statement right in words forces a clarity that wireframes alone can't. If I can't explain what I'm solving in one sentence, I'm not ready to open Figma.
Principle 02
I ask uncomfortable questions early. The questions that feel too basic to ask — "who is actually going to use this?" and "what happens if this doesn't work?" — are usually the most important ones. I ask them in week one, not week six.
Principle 03
I treat constraints as design material. Timeline pressure, technical limitations, budget scope — these aren't obstacles to good design. They're the conditions that make design decisions meaningful. I do my best work inside real constraints.
Principle 04
I design the failure states first. Empty states, error messages, edge cases — the moments most designers leave until last are often the moments users remember most. I start there.
Principle 05
I make myself unnecessary. The goal of every engagement is a team that doesn't need me anymore. Clear documentation, thorough handoff, and knowledge transfer aren't extras — they're part of the deliverable.
Awards
Awards
2024 - Awwwards Site of the Day
Awwwards
2023 - UI Design of the Year
CSS Design Awards
2023 - Featured — Designer of the Week
Dribbble
Work With Me
Work With Me
I work with a small number of clients at a time to make sure every engagement gets my full attention. If you're building something worth designing well — I'd like to hear about it.
I work with a small number of clients at a time to make sure every engagement gets my full attention. If you're building something worth designing well — I'd like to hear about it.
Available now
Menu
About Me
About Me
I'm Navid. I design products that make complex things feel simple.
I'm Navid. I design products that make complex things feel simple.
Seven years designing digital products across B2B SaaS, fintech, and early-stage startups. I work with founders and product teams who need design that moves fast, thinks strategically, and ships clean.
Seven years designing digital products across B2B SaaS, fintech, and early-stage startups. I work with founders and product teams who need design that moves fast, thinks strategically, and ships clean.
My Approach
My Approach
A few things that shape how I work with every client.
A few things that shape how I work with every client.
Principle 01
I write before I design. Getting the problem statement right in words forces a clarity that wireframes alone can't. If I can't explain what I'm solving in one sentence, I'm not ready to open Figma.
Principle 02
I ask uncomfortable questions early. The questions that feel too basic to ask — "who is actually going to use this?" and "what happens if this doesn't work?" — are usually the most important ones. I ask them in week one, not week six.
Principle 03
I treat constraints as design material. Timeline pressure, technical limitations, budget scope — these aren't obstacles to good design. They're the conditions that make design decisions meaningful. I do my best work inside real constraints.
Principle 04
I design the failure states first. Empty states, error messages, edge cases — the moments most designers leave until last are often the moments users remember most. I start there.
Principle 05
I make myself unnecessary. The goal of every engagement is a team that doesn't need me anymore. Clear documentation, thorough handoff, and knowledge transfer aren't extras — they're part of the deliverable.
Principle 01
I write before I design. Getting the problem statement right in words forces a clarity that wireframes alone can't. If I can't explain what I'm solving in one sentence, I'm not ready to open Figma.
Principle 02
I ask uncomfortable questions early. The questions that feel too basic to ask — "who is actually going to use this?" and "what happens if this doesn't work?" — are usually the most important ones. I ask them in week one, not week six.
Principle 03
I treat constraints as design material. Timeline pressure, technical limitations, budget scope — these aren't obstacles to good design. They're the conditions that make design decisions meaningful. I do my best work inside real constraints.
Principle 04
I design the failure states first. Empty states, error messages, edge cases — the moments most designers leave until last are often the moments users remember most. I start there.
Principle 05
I make myself unnecessary. The goal of every engagement is a team that doesn't need me anymore. Clear documentation, thorough handoff, and knowledge transfer aren't extras — they're part of the deliverable.
Awards
Awards
2024 - Awwwards Site of the Day
Awwwards
2023 - UI Design of the Year
CSS Design Awards
2023 - Featured — Designer of the Week
Dribbble
Work With Me
Work With Me
I work with a small number of clients at a time to make sure every engagement gets my full attention. If you're building something worth designing well — I'd like to hear about it.
I work with a small number of clients at a time to make sure every engagement gets my full attention. If you're building something worth designing well — I'd like to hear about it.