Case study
Developing a SaaS App

Qvistorp Growth

My role

  • Personalizing

    Personalizing the application for companies — this included not only changing visual identity (logo, colors), but also modifying the application structure: adding and changing features.

  • design system

    Creating a design system (atomic design) based on the existing interface, ensuring its standardization and visual consistency.

  • testing

    Collaborating with the product team to ensure that the designed solutions aligned with business logic and the system's technical capabilities.

Personalizing

Designing for B2B clients

When designing the CRM for store owners, one of the key tasks turned out to be simplifying the business registration process in the system, so that it would be understandable and executable even for people who don't have daily contact with technology. The process was technically necessary for automating transaction reading and cashback allocation. The stages of this process were as follows:

  • Product Owners met with company representatives, presenting the platform's capabilities and gathering their expectations. As a result of these meetings, a detailed list of business and functional requirements was created.
  • Based on these guidelines, I designed solutions tailored to the specific needs of each organization. These were mockups and prototypes in Figma. Our goal was not only to reflect the client's expectations, but also to maintain consistency with the logic of the entire system.
  • The proposals were then presented to clients, who provided feedback or approved the designs. After acceptance, the final designs went to the development team, which began implementing the changes.

Within Qvistorp Growth, I collaborated with among others:

Design system

Design system based on an existing system

The need to create a design system arose directly from experience gained while working with the system and my observation of visual inconsistencies in the existing interface. The system had been developed over years and lacked unified principles — this was particularly visible in color schemes (e.g., dozens of different shades of gray used simultaneously), typography, and component styles.

I decided to base the design system on the Atomic Design approach. This allowed me to organize the interface at the level of basic elements (atoms), complex components (molecules), and complete views (organisms), which facilitated further system development.

Working on the design system, I achieved both increased visual consistency of the product and accelerated design work.

developing the system

Developing the system based on PO requirements

Not all changes to the system resulted directly from client needs. Many initiatives came from our Product Owners, who, thanks to years of experience working with end users, were able to accurately identify areas requiring improvement.

In such cases, my task was to redesign system elements — to adapt them to new standards while maintaining consistency with the overall interface.

The need to create a design system arose directly from experience gained while working with the system and my observation of visual inconsistencies in the existing interface. The system had been developed over years and lacked unified principles — this was particularly visible in color schemes (e.g., dozens of different shades of gray used simultaneously), typography, and component styles.