In house CMS


We had a client that requested us to build a particular website, that would use our Data Management Platform tool, so manage product samples.

However, the client had multiple sub brands that he wished would have the same structure, but not the same branding

Key Drivers

Ease of use

The tool should at least be as easy to use as wordpress, the CMS that the client was used to.


Integration with DMP tool

The application needs to inject and feed of our DMP tool, so it can manage all the samples - this means that the distribution itself would be managed elsewhere, and this would be just the management of the "store"

This meant that there would also be a need to quickly access DMP if necessary.


Backoffice / Client Side

The CMS has to levels - The backoffice level, where the store is managed, but also the translation to the client side. This means that the site generated should be generic enough that allows all types of different images, logos, etc, to be changed.

UX Research


We were working with SCRUM methodology, so I just gathered enough information to build some proto personas, that later become the foundation for our roles on the application.


Information Architecture 

I helped the team by thinking about the information architecture, that allows me to build wireframes much faster


User Flows

Having personas, turned them into user stories, we then started building wireframes that would show the user flow and what he needed to do on each case.


Early Development

The team worked with the wireframes and quickly were able to test our assumptions with the in-house users.

UI Examples


  • Brand Connections

  • 2018

This internal CMS has the objective to help us create effortlessly websites that would be prepared to accept branding, and other customisation, and still allow upload and management of products samples.

This would also work with another app we developed, that manages the whole distribution of these samples.


My roles



Screen Flows

Visual Design

Interaction Design