NimbleBrain AI
Redesigning the dashboard to speed up onboarding
Industry
AI B2B SaaS
Timeline
3 months
Year
2024
Team
CEO, 2 Product Designers, 1 Engineer
Overview
Helping users get started quicker
Background
NimbleBrain is an AI SaaS platform that connects all your tools—like Google Drive, Slack, and Airtable—into one place. It utilizes AI agents to search across connected platforms, allowing you to find the right information without having to dig through each app.
Project Overview
When I joined, NimbleBrain was pivoting from a Slack-only chatbot into a full SaaS platform. My role was to support stakeholders in reshaping their MVP for this new direction. At the time, early users struggled with a dense interface and had trouble completing core tasks independently.
Business Impact
Through redesigning key workflows and simplifying the interface, we improved usability and gave users confidence to set up and navigate the platform on their own. This reduced customer support load, sped up onboarding, and positioned NimbleBrain for growth beyond its Slack-based origins.
50%
Increase in Task Completion
7 to 1
Reduced Help Request
62%
Increase in User Satisfaction
Challenge
Onboarding was confusing
New users didn’t understand how to set up their dashboards. They kept asking for help, which made customer support tickets pile up.
This was version 1: Users didn’t know where to start.
Solution Highlights
We made the setup simple
Changed technical copy for simple, everyday language
Added alerts and error messages
Added loading indicators
Clarity and Communcation
Designed a step-by-step setup wizard for connecting tools
Made the setup process look and feel the same across tools
Guided Onboarding
Consistency and Scale
Standardized designs with resuable pattterns
Built a system a scablealbe design for future updates
The Process
Aligning on the why
Before starting design or research, I led discovery meetings with the CEO to align on the “why” — why the system was built this way, the product’s long-term goals, and the business outcomes we were aiming for.
Framing the problem
Early usability tests showed that users usually started onboarding and connected tools, but many stalled before finishing—or still asked for help after setup. This loss of confidence spilled into customer support and pulled engineers into support tasks instead of new features.
Tool connection success
At this stage, 81% of users succeeded in setting up their tools, but nearly a third required help, showing fragile confidence and dependence on support.
Balancing Constraints
Focused on three priorities:
User: Enable independent setup without constant support.
Business: Reduce support overhead to free up resources.
Technical: Work within existing API limits and Bootstrap components.
How can we guide users to complete tasks on their own while keeping development fast and scalable?
Designing for Scale
I mapped out workflows across tools to find where users got lost. This revealed opportunities to:
Create a step-by-step setup wizard to guide users through tool connections.
Standardize patterns across integrations so Slack, Google Drive, and Airtable all “felt” the same.
Improve system communication with real-time feedback: loading states, error messages that explained what to do next, and success confirmations.
These weren’t just UI changes—they were system decisions that reduced confusion and laid the foundation for faster future integrations.
To answer these questions, I mapped out the system’s flows to uncover where users got lost and how errors were handled.
Key Design Decisions
Before
After
Business Impact
Validating the Impact
We did another round of usability testing, and the redesign showed measurable improvements. These outcomes demonstrated that the solution wasn’t only usable but also aligned with business growth and scalability.
50%
Increase in Task Completion
7 to 1
Reduced Help Request
62%
Increase in User Satisfaction
Reflections
Balancing growth and usability
In a fast-moving startup, priorities shifted often, and I learned to adapt my design approach to meet evolving growth goals while still laying a foundation for scale. The best solution wasn’t the flashiest—it was the one that balanced user needs, technical feasibility, and business impact. By simplifying flows and clarifying feedback, I reduced support dependence and gave the team space to focus on scaling the product.