If an image tells a thousand words, how about a visuals slide deck? Meet our work:

UX-UI References Cloudoki
UX/UI References Presentation of functional designs and flows by Cloudoki

Now that you have an appetite, what does our SaaS UX team actually assist with

TL;DR Our UX and UI team applies our experience of 100s of apps to your ecosystem, with focus on user expectation - what we call functional design, formatted to tech team oriented design systems.

Research and Analysis

Heuristic analysis of the current application, analysis on provided usability data (if given), research and analysis on current user flows and user personas.

By getting full access to the full scope of the Saas’s tool, we’ll be able to understand in depth which actions, flows and behaviours characterise the tool itself. Together with this, we hope to get access (if it exists) to analytical or qualitative data gathered among the users of the SaaS, from users that have actually used the application extensively.

Based on the above we can start to paint an accurate picture of which and where improvements are, and which problems to solve.


Redesign of user flows and information architecture for the app based on previous research and analysis (if applicable), creation of wireframes for all needed interfaces with the new inputs from previous research and analysis.

Flow deconstruction

The application flow refers to the group of actions a user needs to take to achieve a given end goal. Most of the time applications grow in feature offering without regularly taking a step back to look at the bigger picture and see what is the impact of these small iterations on the general product.

By understanding the target audience and their use cases, and breaking down the tool into the essentials, we will be able to rethink and favour those flows that are the most critical for the users, optimising these while we piece the rest of the application together around them.

Creating interfaces

Redesigning any product is a complex task on its own. However, at this stage we will already have a solid understanding of the user base and the general application flow and feel. We then start combining all of our insights, and give live to the flows and basic structure through wireframing.

Later on, based on the SaaS’s new CID indications, we can adapt the complete UI components to match the new identity’s look & feel, while making sure the “how’s and where’s” are optimised for the existing, and possibly improved, flows.


The end goal is to deliver a fresh and actual look to the general application, but also to make sure it’s individual behaviours are uniform across the complete customer journey, and that these match the flow expectations those end-users have when interacting with the product.

We’ll create high-definition mockups for all needed interfaces and definition of UI elements in a style guide, which include: typography, colour palette , UI components and Iconography (if needed).

Next step

General application architecture

Our applications are always shipped with the best code standards and principles, topped with our own specific intake on front-end architecture. As such, we always follow a strict component reusability policy.

In this specific case we can already anticipate that some components are actually reusable between both Mobile and Desktop web versions, thus lowering the amount of time we would take to make those as well as keeping the code clean and less prone to errors.