<

UX Case - SaaS | Atomic Group

UX Case - SaaS | Atomic Group

UX Case - SaaS | Atomic Group

Technical Challenge.
Technical Challenge.

Role

UX Designer

Industry

Technology

Scope

User flow design

Stage 1. Briefing


The challenge: design the experience of creating and managing mass messaging campaigns (WhatsApp) on a customer service platform integrated with CRM.

The user’s pain point: today, the process of configuring the audience, message, and delivery is confusing—users make mistakes in their settings and have difficulty tracking results after the campaign is launched.

What needed to be solved: Define a clear workflow for users to create and send new campaigns, specifying the name, audience, message, and delivery, and allowing them to track metrics after delivery.

Assumptions:

- The platform already has active integration with a CRM.

- The CRM segments have already been configured.

- Users have basic knowledge of marketing and sales, but not necessarily technical knowledge.

- Users already know the campaign’s objective before beginning creation.

- Users are authorized to create, edit, schedule, and send campaigns.

- Users primarily access the platform via desktop.

- The main content of the template cannot be changed by the user; dynamic variables can be configured.

- The available variables are already linked to existing data in the CRM.

Stage 1. Briefing


The challenge: design the experience of creating and managing mass messaging campaigns (WhatsApp) on a customer service platform integrated with CRM.

The user’s pain point: today, the process of configuring the audience, message, and delivery is confusing—users make mistakes in their settings and have difficulty tracking results after the campaign is launched.

What needed to be solved: Define a clear workflow for users to create and send new campaigns, specifying the name, audience, message, and delivery, and allowing them to track metrics after delivery.

Assumptions:

- The platform already has active integration with a CRM.

- The CRM segments have already been configured.

- Users have basic knowledge of marketing and sales, but not necessarily technical knowledge.

- Users already know the campaign’s objective before beginning creation.

- Users are authorized to create, edit, schedule, and send campaigns.

- Users primarily access the platform via desktop.

- The main content of the template cannot be changed by the user; dynamic variables can be configured.

- The available variables are already linked to existing data in the CRM.


Stage 2. SaaS Research and UI Material

Before diving into wireframes, I researched similar SaaS platforms, including RD Station and Sendflow, to identify common patterns in campaign creation flows, audience segmentation, and message scheduling, as well as recurring usability gaps I could improve on. In parallel, I explored UI component libraries, using Material UI as a reference for structuring reusable patterns like steppers, status cards, and form validation states. This dual research approach, grounded in both product benchmarking and UI best practices, gave me a solid foundation to make informed decisions during the wireframing phase, balancing familiarity for users with opportunities for a clearer, more guided experience.

Stage 3. User flow and Medium-Fidelity Wireframe


With the problem clearly framed and research patterns identified, I mapped the end-to-end user flow, from campaign creation to audience definition, message configuration, and scheduling, highlighting key decision points and potential error moments along the way. Based on this flow, I translated the structure into medium-fidelity wireframes, focusing on information architecture, step-by-step guidance, and reducing cognitive load throughout the happy path. I chose to structure the flow using a wizard pattern, breaking the campaign creation process into clear, sequential steps to reduce cognitive load and minimize the chances of user error. This stage was essential to validate the logic of the experience before moving into visual design, ensuring every screen served a clear purpose within the broader flow.


User flow

link to user flow:
https://miro.com/app/live-embed/uXjVHCVpLKc=/?embedMode=view_only_without_ui&moveTo Viewport=-3653%2C-1549%2C8819%2C6125&embedId=628100546521


Medium- Fidelity Screens

home/campaigns


create a campaign/name


create campaign/selection/audience/CRM segment


create campaign/selection/message/welcome


create campaign/select/submit/submit now


create campaign/review


create campaign/campaign submitted



Key states: empty, error and success

status/empty


status/error


status/success



Key Takeaways

→ Reduced cognitive load through progressive disclosure
→ Added review step before campaign submission
→ Designed empty, error & success states
→ Prioritized CRM familiarity and user confidence

Final Thoughts

This challenge was a valuable opportunity to apply a user-centered approach to a product problem with an open-ended scope, multiple possible solutions, and one that closely mirrors those encountered in the day-to-day use of SaaS products.

More than just thinking about workflows and designing interfaces, the exercise required a deep understanding of the context, identification of potential errors and risks, prioritization of user needs, and a structure that balances simplicity, efficiency, and feasibility, with an eye toward future implementation.

Throughout the process, I was able to delve deeper and reflect on how decisions regarding information architecture, error prevention, and interaction design directly impact user trust and, consequently, the success of the objective. This project helped strengthen my perspective as a problem-solving designer, my ability to justify decisions, and my approach to creating clear, accessible, and results-oriented solutions

Link to wireframe:

https://www.figma.com/proto/m3Iiiub0BpHDzvsNafAgEG/Case-UX--Atomic-Group ----Saas?node-id=7-4716&viewport=114%2C271%2C0.06&t=fwuPOArluQnclImA-1&scaling =contain&content-scaling=fixed&page-id=0%3A1

Stage 3. User flow and Medium-Fidelity Wireframe


With the problem clearly framed and research patterns identified, I mapped the end-to-end user flow, from campaign creation to audience definition, message configuration, and scheduling, highlighting key decision points and potential error moments along the way. Based on this flow, I translated the structure into medium-fidelity wireframes, focusing on information architecture, step-by-step guidance, and reducing cognitive load throughout the happy path. I chose to structure the flow using a wizard pattern, breaking the campaign creation process into clear, sequential steps to reduce cognitive load and minimize the chances of user error. This stage was essential to validate the logic of the experience before moving into visual design, ensuring every screen served a clear purpose within the broader flow.


User flow

link to user flow:
https://miro.com/app/live-embed/uXjVHCVpLKc=/?embedMode=view_only_without_ui&moveTo Viewport=-3653%2C-1549%2C8819%2C6125&embedId=628100546521


Medium- Fidelity Screens

home/campaigns


create a campaign/name


create campaign/selection/audience/CRM segment


create campaign/selection/message/welcome


create campaign/select/submit/submit now


create campaign/review


create campaign/campaign submitted



Key states: empty, error and success

status/empty


status/error


status/success



Key Takeaways

→ Reduced cognitive load through progressive disclosure
→ Added review step before campaign submission
→ Designed empty, error & success states
→ Prioritized CRM familiarity and user confidence

Final Thoughts

This challenge was a valuable opportunity to apply a user-centered approach to a product problem with an open-ended scope, multiple possible solutions, and one that closely mirrors those encountered in the day-to-day use of SaaS products.

More than just thinking about workflows and designing interfaces, the exercise required a deep understanding of the context, identification of potential errors and risks, prioritization of user needs, and a structure that balances simplicity, efficiency, and feasibility, with an eye toward future implementation.

Throughout the process, I was able to delve deeper and reflect on how decisions regarding information architecture, error prevention, and interaction design directly impact user trust and, consequently, the success of the objective. This project helped strengthen my perspective as a problem-solving designer, my ability to justify decisions, and my approach to creating clear, accessible, and results-oriented solutions

Link to wireframe:

https://www.figma.com/proto/m3Iiiub0BpHDzvsNafAgEG/Case-UX--Atomic-Group ----Saas?node-id=7-4716&viewport=114%2C271%2C0.06&t=fwuPOArluQnclImA-1&scaling =contain&content-scaling=fixed&page-id=0%3A1

Other projects

Interested in connecting?

Let’s talk about projects, opportunities, collaborations or anything that involves design! =)

Interested in connecting?

Let’s talk about projects, opportunities, collaborations or anything that involves design! =)

Interested in connecting?

Let’s talk about projects, opportunities, collaborations or anything that involves design! =)

Copyright 2026 by jamilly moraes

Copyright 2026 by jamilly moraes

Copyright 2026 by jamilly moraes

Create a free website with Framer, the website builder loved by startups, designers and agencies.