Product design for AI products
We design AI products and AI features for SaaS teams. AI changes the hard parts of UX: people wait, answers can be wrong, and someone has to know when a human takes over. We design those moments, not just the chat box, and hand over a UI system your engineers can extend.
What’s different about designing for AI
Waiting
Generation takes time. Show progress and partial results, and let people keep working.
Uncertainty
Show confidence and sources where it matters, and make it easy to check the answer.
Errors
Most AI errors aren’t the user’s fault. Design a recovery path, not just an error message.
Control and handoff
Let people edit, undo and escalate to a human. Agents need clear limits and visible actions.
Trust over time
Onboarding that sets honest expectations about what the AI can and can’t do.
What we design
- Core flows for AI-first products and agents.
- AI features inside an existing SaaS, without breaking the rest of the product.
- States: empty, loading, streaming, partial, failed, needs review.
- A UI kit and written rules your team and your AI coding tools can follow.
We use AI in our own process too. Here is how: Where AI belongs in a design workflow.
How to work with us
Launch
From US$12k, about 4 weeks: a new AI product, from idea to launch, with brand and landing page. See Launch in detail.
Partner
From US$6k/mo: AI features in a live product, one focus at a time. See Partner in detail.
Both are on engagements and pricing.
Further reading
- Designing AI product UX: trust, waiting, errors and handoffUX patterns for AI features and agents: progress while it thinks, uncertainty, errors that aren’t the user’s fault, and handing off to a human.
- SaaS onboarding and activation: designing the first sessionWhy trial users don’t activate, and how to design a SaaS first session that gets new users to real value fast: sign-up, empty states, first task, follow-up.
- Designing a health tech SaaS: patient side, clinician side, consent and accessibilityHow designing a health product differs from other SaaS: separate patient and clinician experiences, consent on screen, accessibility and trust.
- SaaS dashboard design: what the first screen of a B2B product should showWhat a B2B SaaS dashboard should show first, how many KPIs belong on it, how to keep a data-dense screen readable, and when a redesign is worth it.
FAQ
You design for time, uncertainty and handoff, not only for screens and clicks.
Yes, when chat is the right pattern. Often it isn’t, and an inline suggestion or a review queue works better.
Yes: what the agent can do, how it shows its actions, and when it asks a person.
Tell us what your AI product does
A short note about the product, your stage and your timeline is enough. We reply within two working days.
Send your brief