Agicap
Agicap
Agicap
2021
2021
2021
Embedding companies’ cashback process within their existing cashflow management tool
Embedding companies’ cashback process within their existing cashflow management tool
Embedding companies’ cashback process within their existing cashflow management tool
Role
Role
Lead designer
Lead designer
Product Team
Product Team
Rose Valette - Product Manager
Rose Valette - Product Manager
1
1
Context
Context
Context
In September 2021, Agicap was 5 and had built their success thanks to a first product.
After a new round of fundraising, they wanted to create a product about payment delay across multiple countries, and I was the lead designer for the first 3 months.
In September 2021, Agicap was 5 and had built their success thanks to a first product.
After a new round of fundraising, they wanted to create a product about payment delay across multiple countries, and I was the lead designer for the first 3 months.
My 5 objectives
My 5 objectives
Understand the need through research
Help create the product foundations and roadmap
Design the MVP and the new design system
Define the post launch testing method
Create the product branding, marketing page, and branding guidelines across the different Agicap product lines.
Understand the need through research
Help create the product foundations and roadmap
Design the MVP and the new design system
Define the post launch testing method
Create the product branding, marketing page, and branding guidelines across the different Agicap product lines.
TL;DR : what we delivered
TL;DR : what we delivered
TL;DR : what we delivered
In 3 months, we built a product around key principles for our customers, some of they didn’t found anything matching enough their expectations in others products : visibility and actions.
Each principle is tied to the research insights we discovered during the research (composed of interviews, surveys and data analysis) and have a key feature made around it.
The interface emphasis visibilty by being a mix of exhaustive listing and key informations summary, whereas actions were made to be flexible, to suit the needs of our customer’s habits.
For the launch, we defined beforehand what was the point of the MVP, what we wanted to discover, and how the team will monitor activities.
It lead us to a beta version running for 2 months with key users, helping us achieve a retention above 80% and 85% weekly usage rate.
In 3 months, we built a product around key principles for our customers, some of they didn’t found anything matching enough their expectations in others products : visibility and actions.
Each principle is tied to the research insights we discovered during the research (composed of interviews, surveys and data analysis) and have a key feature made around it.
The interface emphasis visibilty by being a mix of exhaustive listing and key informations summary, whereas actions were made to be flexible, to suit the needs of our customer’s habits.
For the launch, we defined beforehand what was the point of the MVP, what we wanted to discover, and how the team will monitor activities.
It lead us to a beta version running for 2 months with key users, helping us achieve a retention above 80% and 85% weekly usage rate.
2
Research
Research
Research
We conducted around 20 interviews, mainly from our customers base. I wrote the interview guide, conducted them while the PM wrote the report on Dovetail, from where I did the analysis.
We also did a first data analysis on a feature the existing Agicap product has, where users can enlist their current invoices. We wanted to know how much of those created where followed, what pain points were still present, what were the favorite actions.
The result were insights and problematics I used to create the first version of our customer journey map.
We conducted around 20 interviews, mainly from our customers base. I wrote the interview guide, conducted them while the PM wrote the report on Dovetail, from where I did the analysis.
We also did a first data analysis on a feature the existing Agicap product has, where users can enlist their current invoices. We wanted to know how much of those created where followed, what pain points were still present, what were the favorite actions.
The result were insights and problematics I used to create the first version of our customer journey map.
3
Foundations and roadmap
Foundations and roadmap
Foundations and roadmap
We knew the competition was way ahead on some aspect, so we needed to identify what could be the key elements to base our product on, and what would be the problems we will solve first. Our goal was to bring something new and useful to our customers, and strengthen Agicap brand.
We then pondered the different problematics with the How Might We method, correlated with the principles we defined, and the technical difficulties. We ended up with 2 main problematics to tackle, and a handful of secondary one to include in this first batch.
We knew the competition was way ahead on some aspect, so we needed to identify what could be the key elements to base our product on, and what would be the problems we will solve first. Our goal was to bring something new and useful to our customers, and strengthen Agicap brand.
We then pondered the different problematics with the How Might We method, correlated with the principles we defined, and the technical difficulties. We ended up with 2 main problematics to tackle, and a handful of secondary one to include in this first batch.
4
Solution
Solution
Solution
Moving fast to launch a beta
Moving fast to launch a beta
Starting with HMW, we quickly advance from functional blueprint to high fidelity mockups. The main difficulty was that in order to have relevant feedbacks from our customers, we needed to have real data in our tests. As we spend a lot of time doing exploration research, we decided to design those first 2 features using as much known patterns as possible, in order to develop them, and test post launch.
It was unusual for a product process, but time was running, we knew those features were known from our customers, so we were confident that a worst case scenario had but an insignificant chance to happen.
Starting with HMW, we quickly advance from functional blueprint to high fidelity mockups. The main difficulty was that in order to have relevant feedbacks from our customers, we needed to have real data in our tests. As we spend a lot of time doing exploration research, we decided to design those first 2 features using as much known patterns as possible, in order to develop them, and test post launch.
It was unusual for a product process, but time was running, we knew those features were known from our customers, so we were confident that a worst case scenario had but an insignificant chance to happen.
Brand
Brand
As it was Agicap second product to launch, we also bet to explore a bit on the art direction. Contrast was an issue of today’s product, so to create discussions among the team and have customers feedback as concrete as possible, we pushed the boundaries of the UI.
As it was Agicap second product to launch, we also bet to explore a bit on the art direction. Contrast was an issue of today’s product, so to create discussions among the team and have customers feedback as concrete as possible, we pushed the boundaries of the UI.
5
Testing
Testing
Testing
Without test pre launch, we had to be extremely prepared to monitor our product right after launch. I created a method based on data analysis and users feedbacks that would run for a month, each week having different points of focus.
We wanted to have hot takes right after launch in order to iterate quickly on functionality or accessibility issues, but also gather informations to take a step back, and confront users to our design doing data monitoring and interviews.
Without test pre launch, we had to be extremely prepared to monitor our product right after launch. I created a method based on data analysis and users feedbacks that would run for a month, each week having different points of focus.
We wanted to have hot takes right after launch in order to iterate quickly on functionality or accessibility issues, but also gather informations to take a step back, and confront users to our design doing data monitoring and interviews.
6
Branding
Branding
Branding
The first business take on this product was to be abler to exist even as a stand alone. Hence, I created a brand, strongly inspired by Agicap existing brand, but distinct enough to but differentiated. And the marketing page, building onto the CMS used by Agicap teams, but defining a slightly different tone and voice, to see how customers would react, and evolve the whole brand if proven successful.
The first business take on this product was to be abler to exist even as a stand alone. Hence, I created a brand, strongly inspired by Agicap existing brand, but distinct enough to but differentiated. And the marketing page, building onto the CMS used by Agicap teams, but defining a slightly different tone and voice, to see how customers would react, and evolve the whole brand if proven successful.
Agicap sub product art direction and layout.
Agicap sub product art direction and layout.
Agicap sub product art direction and layout.