Improving an influencer marketing tool to power smarter campaigns

SERVICE TYPE
- Web app design
Industry
- Influencer marketing
My role
- Sole UX/UI Designer
Timeline
- May’23 – present
About the project
Julius by Triller is a dedicated SaaS solution built for influencer marketing. Tailored for enterprise brands, PR agencies, and major media companies, it empowers teams to launch effective marketing campaigns on their own.
This platform has been around for a long time (since 2015!) and has seen multiple designers over the years. As the most recent one, I was responsible for improving the UX of the legacy platform and introducing new features – both in the main system and within the Campaigns suite, which had its own fresh UI.

The full case study is still in progress, feel free to reach out if you’re curioz about the design process!
Problem statement
As mentioned earlier, the web application consists of two parts, each with its own UI design that differs significantly from the other. One of them is a smaller section focused only on Campaigns management, with a modern, somewhat playful purple look. The other, larger part includes all remaining sections of the platform (from main search to user settings) and is presented in a gray-blue color palette.
The final goal is to redesign the entire app. However, due to a limited budget, the work is being done quite slowly, piece by piece. While the process is still ongoing, I have to constantly switch between the two interfaces when preparing designs for new functionality, taking into consideration the specific guidelines of each style guide. In this case study, I’ll walk through some of the most interesting projects and solutions across both UIs.
Payouts
The ability to pay influencers directly through the platform feels like an absolute must. A similar feature had existed in the past, but due to poor usability, it wasn’t much in demand and was eventually turned off and sent into oblivion. Recently, however, customers have started asking for the payments functionality again. This time, our Julius team wanted to avoid the same fate for this feature.
The required changes affected a significant part of the app and involved the two different UIs I mentioned earlier. That’s why we decided to divide the workflow into three phases and gradually expand the interface, step by step.
Phase 1
At this stage, the team defined the core functionality of the Payouts project and created the most important pages and flows (along with several smaller elements and screens):
- Wallet along with Transaction History;
- Payouts List and Single Payout Details;
- Upload or Send Funds;


However, as a designer, I understood that any activity involving money transfers requires an extremely high level of trust from the user. That’s why I wanted to ensure that the navigation and flows I created were logical, predictable, and as user-friendly as possible. To confirm (or refute!) that we were on the right path, I suggested running a series of moderated usability tests.
My Project Manager helped me recruit participants with varying experience: some had advanced knowledge of payment tools (e.g., accountants), while others had only a basic background. Before the tests began, I prepared a script organized into four discussion blocks, with five tasks spread across them. After fruitful testing, the designs were updated and delivered to devs.
Phase 2
In the next phase, as agreed with the team, I completely redesigned the New Payout flow using the aforementioned second style guide to make it look more professional and sleek, and to follow industry‑standard principles.
We also introduced the option to specify what the payment is for (called Deliverables), which includes previously planned creatives that influencers are expected to deliver within the current campaign, such as Instagram posts, YouTube videos, etc.


Phase 3
Initially, this step was meant to be short and straightforward, simply presenting the reverse of the functionality introduced in Phase 2, letting our clients either enable payments when creating a new Deliverable or link a payout to an existing one. However, after reviewing user feedback and discussing it with the team, it became clear we needed to go beyond the original scope.
Despite the fact that the functionality itself was in high demand and considered a bare minimum for competitor platforms, it failed to meet expectations: the UX/UI at the time was so poorly designed that Julius users tended to skip the feature. In the next section, I’ll go into more detail about the problems our users faced and how I addressed them.


A curated selection of web platforms and landing pages I’ve designed – some without comprehensive research, but still worth sharing!